-
Notifications
You must be signed in to change notification settings - Fork 404
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
Comments
Right, so the solution is to accept sustain pedal as omni in channel per octave mode. |
Yeah exactly and I should re test mpe and we should think about 2/3 mode also |
I'd say let's keep that mode for 1.x and axe it in XT2. |
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 :) |
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... |
oh yeah excellent points all! |
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? |
Nah it works and we have an option. More trouble to axe it than leave it |
Yeah
surge/src/common/SurgeSynthesizer.cpp
Line 2100 in 448b4ef
In octave per channel mode sustain pedal is channel limited basically
Discord user conradtao
The text was updated successfully, but these errors were encountered: