You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
The message for send level changes is supposed to look like this:
Altering a level in the FX bus in channel Ip1 (channel 0), the following message is sent (i.e. missing the
SndN
byte):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 fixedSendN
channel. But this might break as soon as new messages get implemented that make this fallback ambiguous.The text was updated successfully, but these errors were encountered: