-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
MIDI CC messages on channel 2 not working #885
Comments
The second variant is a toggle switch btw: On first press it sends 127 to turn something on, then 0 on second press to turn off. I wanted to use this to toggle module enables. Should this be possible? |
Yes, this is the "latch" behaviour in the MIDI panel. |
Per button? I guess it is only per controller, but I'll check it out, thanks. |
Yes per controller. Most MIDI controllers have some sort of setup software
to change the behaviour of specific buttons though, so worth a look to see
if you can configure it through that. Definitely out of scope on modV’s
side for now.
…On Tue, 5 Sep 2023 at 22:58, Bim ***@***.***> wrote:
The second variant is a toggle switch btw: On first press it sends 127 to
turn something on, then 0 on second press to turn off. I wanted to use this
to toggle module enables. Should this be possible?
Yes, this is the "latch" behaviour in the MIDI panel.
Per button? I guess it is only per controller, but I'll check it out,
thanks.
—
Reply to this email directly, view it on GitHub
<#885 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEHJ26BHV4CMYFFFO3QHHDXY6OBHANCNFSM6AAAAAA3WTHTCI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Operating system and application version
Describe the bug
When connecting a MIDI CC message not on channel #1 (Message 0xbN where N carries the channel) it can be connected (learn button works), but is not working afterwards.
My MIDI controller sends either (different "scene settings in controller"):
Channel 1, CC 23, Value 127 (first message) + 0 (in second message)
or:
Channel 2, CC 18, Value 127 (first message, no second message) <-- Not working
Maybe related to #889
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Connection should work after learning
The text was updated successfully, but these errors were encountered: