Found the files from the install, hope this helps..
the "/future2/on" osc message was setup within the autom window and would trigger a playback fader which then triggered macros to activate cues or cue stacks ..
I also remember having to send a osc command to activate the playback fader, because if it was released in magicQ it would jump that the cue, but would not activate the cue stack.
also check out https://secure.chamsys.co.uk/help/documentation/magicq.pdf Chapter 39.
If your still having problems, feel free to send me your magicQ and qlab file and ill see if i can help :-)
Cheers
I am currently converting midi /osc to a DMX universe with Max4Live and sending that universe internally to MagicQ on the same machine. Then with Autom controlling Cue levels with the values on different dmx channels.
I don't understand why OSC can't also function this way. Having to also activate a playback and adjust the intensity level that way in addition to choosing the cue in the stack seems nonsensical.
Hoping to see more development of this soon! And more available Autom lines... Currently maxes out at 120 rules.
M
Regarding MIDI on Chamsys, don't they require some sort of midi interface to get the MSC going (or is it just required to get us out of demo mode)? Or internal midi is possible thru the IAC Driver once out of demo?