]]>
]]>
can't test here but here is a possible alternative way (maybe you ll need the same wait module out of pass).
the get array element value would scan the index 3 of sysex (since array pos are 0,1,2,3 its the 4th data where your '3' comes from), multiplied by the 1 pulse on receive make 3, or 0 when not receiving.
Statistics: Posted by 23fx23 — 06 Jan 2018, 22:58
]]>
The patch works,I now have 3 on receive and 0 otherwise.
Previously, because of the null between the sysex messages, the output of the Display Array was never changing when I was hitting several times the same button...
Best
Statistics: Posted by Ken29 — 06 Jan 2018, 19:02
]]>
i don't undersnt exactly what should go to your sysex bus aftewards to, it should be 3 on a receive and 0 otherwise?
Statistics: Posted by 23fx23 — 06 Jan 2018, 14:58
]]>
PS : it is not totally exact, on time on twenty Sysex hits, Is null detect it.... So strange...
Kenan
Statistics: Posted by Ken29 — 06 Jan 2018, 13:13
]]>
]]>
I have a sysex message coming from a machine remote. Only the fourth digit matters.
I have one button play and I want to use it as play or pause.
It's clear in the data flow, there's no signal [-1], between two hits, but this Null data isn't detected and the display array sees only the first hit. Thus, the first "3" is send to the BUS and then nothing happens.
"Has changed" doesn't work, it doesn't see the null data has a change...
I could reset the array with a timer but it is really not elegant...
Cheers
Statistics: Posted by Ken29 — 05 Jan 2018, 09:28
]]>