I have LXConsole working nicely with QLab 3. I can create OSC cues in QLab 3 and use them to trigger LXConsole cues. Everything works fine when I use this format:
/cmd.lxconsole/GO:1
However, I read that LXConsole would also respond to this format of OSC message:
/cue/1/start
- but I cannot make that work.
What am I missing?
Thank you!
LXConsole, QLab 3, and OSC
There's a check box in the OSC preferences "respond to /cue/... messages". This needs to be checked.
The reason there's an option and LXConsole does not always respond is that it has the ability to forward messages that it does not respond to. So, a single controller could send messages to LXConsole and if it diid not respond to them, it could forward them to another application (such as QLab). If this was not available, the controller would have to have multiple outputs one to LXConsole and a different one going to QLab. QLab itself can do this but an application like TouchOSC cannot.
The reason there's an option and LXConsole does not always respond is that it has the ability to forward messages that it does not respond to. So, a single controller could send messages to LXConsole and if it diid not respond to them, it could forward them to another application (such as QLab). If this was not available, the controller would have to have multiple outputs one to LXConsole and a different one going to QLab. QLab itself can do this but an application like TouchOSC cannot.
-
timmrogers
- Posts: 51
- Joined: Sat Sep 06, 2014 4:29 am
-
timmrogers
- Posts: 51
- Joined: Sat Sep 06, 2014 4:29 am
