02-20-2025, 09:47 AM
(This post was last modified: 02-22-2025, 12:18 PM by RadekPilich.)
There is no other issue, I have verified other possible causes.
I wasn't aware there is additional "monitor" on the routing screen!
I can see the that switching group on Faderfox actually produces some output.
Here is the message:
0 > sX
After that, the matrix and routing monitors continue to act normally, but the monitor tool + the actual connected devices don't indicate any further messages occurring.
I will catch the SYSEX message on the computer and pay it here.
TBD / Here it is - 3 consequent group switches on the Faderfox.
Also I should note, that it was working alright in the previous beta, so it most likely has something to do with the sysex adjustments in the most recent beta.
I wasn't aware there is additional "monitor" on the routing screen!
I can see the that switching group on Faderfox actually produces some output.
Here is the message:
0 > sX
After that, the matrix and routing monitors continue to act normally, but the monitor tool + the actual connected devices don't indicate any further messages occurring.
I will catch the SYSEX message on the computer and pay it here.
TBD / Here it is - 3 consequent group switches on the Faderfox.
Code:
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
0000959F 3 -- F0 Buffer: 14 Bytes System Exclusive
SYSX: F0 00 00 00 4E 2C 1B 4E 28 16 4E 24 13 F7
0000B3D9 3 -- F0 Buffer: 14 Bytes System Exclusive
SYSX: F0 00 00 00 4E 2C 1B 4E 28 16 4E 24 12 F7
0000CFC1 3 -- F0 Buffer: 14 Bytes System Exclusive
SYSX: F0 00 00 00 4E 2C 1B 4E 28 16 4E 24 17 F7Also I should note, that it was working alright in the previous beta, so it most likely has something to do with the sysex adjustments in the most recent beta.

