Faders with an "in" definition now respond to realtime incoming Sysex messages - hallelujah! But it's worth noting that a fader with an input definition of Sysex cannot output Meta messages or Fader messages. John Pitcairn

Thoughts from the mind of johnpitcairn, 01-04-2002: >Faders with an "in" definition now respond to realtime incoming >Sysex messages - hallelujah! Hola! Waidaminute... you mean as in "incoming sysex, matching the msg defined in the fader definition"? And that also works with messages of, say, 10 bytes or longer? That would be truly awesome... Next question: why wasn't this documented somewhere? >But it's worth noting that a fader with an input definition of Sysex >cannot output Meta messages or Fader messages. This, on the contrary, seems very silly. Not a big deal -- just throw in an extra transformer -- but silly nonetheless. Thanks for the info btw... -- Hendrik Jan Veenstra <h@...> Omega Art: http://www.ision.nl/users/h/index.html

--- In logic-users@y..., Hendrik Jan Veenstra <h@k...> wrote: > And that also works with > messages of, say, 10 bytes or longer? Dunno, you'll have to try it. But it's working with incoming 6-byte Juno 106 slider sysex... John Pitcairn

Thoughts from the mind of johnpitcairn, 02-04-2002: >--- In logic-users@y..., Hendrik Jan Veenstra <h@k...> wrote: >> And that also works with >> messages of, say, 10 bytes or longer? > >Dunno, you'll have to try it. I just did, and this is what I found: SysEx messages of 15 bytes (including StartOfExc and EndOfExc) are still recognised. You can thus use a message like 240 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 - VAL - 247 It doesn't seem to matter where the VAL byte is. Longer messages are not recognised, regardless of the position of the VAL byte. Unrecognised messages (i.e. msgs that are too long) are passed through a fader unaltered, as one would expect. For the rest the following buggy behaviour seems present (Markus, Michael, care to comment? And John, thanks for pointing this one out earlier) Setting a fader to SysEx 'In' and either Meta or Fader 'Out' doesn't work properly: the incoming sysex is recognised, and a value is sent out based on the *third* byte of the message (counting all bytes -- so that would be value "3" in the example message above). An obvious workaround is to have the fader convert incoming sysex to some controller, and use a transformer to make the controller into either a Meta or Fader event. Obvious question: now that this finally works, why on earth is it limited to 15-byte messages??? -- Hendrik Jan Veenstra <h@...> Omega Art: http://www.ision.nl/users/h/index.html