-
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
CLAP does not respond correctly to Note On velocity 0 #6621
Comments
Wow yeah you are totally correct! surge/src/surge-xt/SurgeSynthProcessor.cpp Line 603 in 1016dd7
that line needs an if velocity 0 release I can patch that into the nightly before the weekend if no one else does it first |
1. Velocity 0 == Note Off was not working in the CLAP_NOTE_EVENT stream. Correct and defensively correct in the juce stream also (although I think juce will have pre-converted for me) 2. Add "synthesizer" as a CLAP feature to surge xt, since surge xt is, in fact, a synthesizer :) Closes surge-synthesizer#6621
1. Velocity 0 == Note Off was not working in the CLAP_NOTE_EVENT stream. Correct and defensively correct in the juce stream also (although I think juce will have pre-converted for me) 2. Add "synthesizer" as a CLAP feature to surge xt, since surge xt is, in fact, a synthesizer :) Closes #6621
I fixed this this morning. it will be in our next nightly release https://surge-synthesizer.github.io/nightly_XT in an hour or so. I also fixed the lack of a "synthesizer" tag while I was in there :) Thanks for reporting it. |
Bug Description:
When using CLAP version of Surge-XT (x64 and x32) and sending notes in CLAP_NOTE_DIALECT_CLAP mode, Surge-XT does not stop playing notes when it receives Note on, velocity 0 on the general channel.
Surge XT Version
1.1.1ecf7fe6
Reproduction Steps:
Steps to reproduce the behavior:
Expected Behavior:
Upon release of keys the notes should enter release phase
Computer Information (please complete the following!):
Additional Information:
@baconpaul Contact me if you need more info or still need NFR.
The text was updated successfully, but these errors were encountered: