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

Mixrack sends invalid message for FX sends in Ip1 #13

Open
m-vo opened this issue Apr 8, 2022 · 0 comments
Open

Mixrack sends invalid message for FX sends in Ip1 #13

m-vo opened this issue Apr 8, 2022 · 0 comments

Comments

@m-vo
Copy link
Owner

m-vo commented Apr 8, 2022

The message for send level changes is supposed to look like this:

Sysex Header, 0N, 0D, CH, SndN, SndCH, LV, F7

Altering a level in the FX bus in channel Ip1 (channel 0), the following message is sent (i.e. missing the SndN byte):

Sysex Header, 0N, 0D, CH, SndCH, LV, F7

Note, that this does not happen for other base channels or for aux sends. The current workaround is to still treat sysex messages with a content length of 5 bytes that start with 0D as send level messages with a fixed SendN channel. But this might break as soon as new messages get implemented that make this fallback ambiguous.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant