Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Channel sustain pedal #7115

Closed
baconpaul opened this issue Jul 24, 2023 · 8 comments · Fixed by #7244
Closed

Channel sustain pedal #7115

baconpaul opened this issue Jul 24, 2023 · 8 comments · Fixed by #7244
Labels
Bug Report Item submitted using the Bug Report template MIDI MIDI support related
Milestone

Comments

@baconpaul
Copy link
Collaborator

Yeah

sustainpedalCC = value;
the channel hold only applies to the channel with the sustain pedal. That’s an oddity in all our modes. There’s special mpe treatment elsewhere but you aren’t in mpe mode. I’ll open an issue

In octave per channel mode sustain pedal is channel limited basically

Discord user conradtao

@baconpaul baconpaul added the Bug Report Item submitted using the Bug Report template label Jul 24, 2023
@baconpaul baconpaul added this to the Surge XT 1.3 milestone Jul 24, 2023
@mkruselj mkruselj added the MIDI MIDI support related label Jul 24, 2023
@mkruselj
Copy link
Collaborator

Right, so the solution is to accept sustain pedal as omni in channel per octave mode.

@baconpaul
Copy link
Collaborator Author

Yeah exactly

and I should re test mpe

and we should think about 2/3 mode also

@mkruselj
Copy link
Collaborator

I'd say let's keep that mode for 1.x and axe it in XT2.

@baconpaul
Copy link
Collaborator Author

Yeah agree. or perhaps have a better midi control overall. Like if a scene has a midi filter etc then it’s not hardwired and mysterious

if we write arpeggiators and chord modes we are messing with the front of the note stack anyway so it’s a good opportunity

but that’s not this issue! And not this year :)

@mkruselj
Copy link
Collaborator

mkruselj commented Jul 30, 2023

To me, a more elaborate MIDI channel handling only has merit if we resuscitate the old "more than two scenes" feature request. 🙂

Also, we can basically duplicate the current ch23 scheme by setting the scene mode to channel split, and set channel 3 as split point, giving all the more reason to axe the hard-coded behavior...

@baconpaul
Copy link
Collaborator Author

oh yeah excellent points all!

@mkruselj
Copy link
Collaborator

Hell, maybe we should axe this behavior for 1.3 already? Although I can imagine some projects relying on this behavior... maybe we could detect events being received from ch2/3 if MPE is not enabled then throw a dialog to then automatically set channel split accordingly?

@baconpaul
Copy link
Collaborator Author

Nah it works and we have an option. More trouble to axe it than leave it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report Item submitted using the Bug Report template MIDI MIDI support related
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants