From: Hendrik Jan Veenstra <h@...> >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. Wanted to give up on send-automation, but this workaround ... works. Hendrik, thank ya. Is there a way, to control Logic's transport functions via Meta-events? I I couldn't get Midi-remote to work from an environment object cabled to sequencer in. Or how can you control play/stop/record via sysex? cheers, bernd

Thoughts from the mind of R/T, 02-04-2002: >From: Hendrik Jan Veenstra <h@...> > >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. > >Wanted to give up on send-automation, but this workaround ... works. >Hendrik, thank ya. Don't know what my remark has to do with send automation, but: you're welcome :-). >Is there a way, to control Logic's transport functions via Meta-events? I >I couldn't get Midi-remote to work from an environment object cabled to >sequencer in. >Or how can you control play/stop/record via sysex? And as far as the transport goes: you can only control Logic's "stop" function with a meta event -- for the other transport functions there's no meta event (weird eh?). If you still want to control them, you can define Midi Remote commands for them and send that to the Physical Input object. So when doing this from the environemnt, cable the "Midi Remote command generating object" to the Physical Input object, instead of the Sequencer object. No sysex needed... -- Hendrik Jan Veenstra <h@...> Omega Art: http://www.ision.nl/users/h/index.html

>>If you still want to control them, you can define Midi Remote >>commands for them and send that to the Physical Input object. So >>when doing this from the environemnt, cable the "Midi Remote command >>generating object" to the Physical Input object, instead of the >>Sequencer object. No sysex needed... In case it might be helpful, there's an example of this in the US428 environment at Swiftkick. Len http://www.swiftkick.com