Sysex Script: bytes after XX

It seems taht the bytes after XX are not detected.

As example, I am trying to detect status of Display Name/Value of Mackie control with a Script button.

This script always shows "2" everytime I press the Display Name/Value button:
[ (sysex:F0 00 00 66 14 XX 50 61 67 65 3A 30 31 2F 30 32 F7) {text: 1} ]
[ (sysex:F0 00 00 66 14 XX 20 F7) {text: 2} ]

If I reverse the script order,  the button always shows "1" everytime I press the Display Name/Value button:
[ (sysex:F0 00 00 66 14 XX 20 F7) {text: 2} ]
[ (sysex:F0 00 00 66 14 XX 50 61 67 65 3A 30 31 2F 30 32 F7) {text: 1} ]

Maybe I am doing something wrong, but it seems the bytes after XX are not recognized.

It isn't documented anywhere, but the script button only reacts to received sysex commands, not sent sysex commands.

TBH, I don't remember if this is due to a design decision or if I just didn't implement it.

The script I posted is reacting to received sysex command, it's not sending sysex.

The problem is that the script is not reacting to the bytes after XX. It reacts only to the bytes before XX.

I try to explain better the issue.

Let's say we have two buttons of the SD routed to the mackie ports of Cubase:

- 1st button press the Mackie button "Display Name/Value" 
- 2nd button is a script button with this code:
[ (sysex:F0 00 00 66 14 XX 50 61 67 65 3A 30 31 2F 30 32 F7) {text: 1} {wait:500}]
[ (sysex:F0 00 00 66 14 XX 20 F7) {text: 2} {wait:500}]
[ (sysex:F0 00 00 66 14 XX 87 F7) {text: 3} {wait:500}]

When I press the 1st button, the following sysex is sent:
F0 00 00 66 14 12 00 50 61 6E 20 20 20 20 20 20 20 20 20 20 20 20 20 4C 65 66 74 2D 52 69 67 68 74 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 50 61 67 65 3A 30 31 2F 30 32 F7

After pressing that 1st button, the 2nd button shows the text "1", then the text "2" and finally the text "3", with a delay of 500 ms in between.

OK, I see what you mean; I'm on it.

I have fixed it.

Version 3.10.0.2

Works perfect!

Thanks!