Original LXSeries Forum

I'm new to LXconsole. I would like to use it with QLab to trigger my light cues. I have figured it out how to trigger them with MSC and a go command but i really would like to use the Timed go command which is the same thing but with the possibility to choose right in Qlab the fade time. Is that possible? If not, is it possible using OSC or any other way?

With QLab 3 you can send OSC messages to LXConsole. You can either use the Setup window to capture received OSC messages and define actions for them or you can send messages that LXConsole recognizes. In either case, you can have an OSC action perform any command that you might type into the command line.

To set the crossfade time of cue 101 to 12 seconds, send the following OSC message: "/cmd.lxconsole/cue:101time:12"

To set the time of cue 42 to 5 seconds up and 10 seconds down, send the following OSC message: "/cmd.lxconsole/cue:42time:5downtime:10"

To set the time of cue 15 to a 10 second crossfade with a 10 second follow time, send the following OSC message: "/cmd.lxconsole/cue:15time:10downtime:10follow:10"

To run cue 15 send the following OSC message: "/cmd.lxconsole/GO:15"

The latest version has a preference that allows LXConsole to respond to QLab style OSC messages. With this option enabled, to run cue 15 you could also send: "/cue/15/start"

Thank you for the quick reply. I tried what you propose and yes it works! Thanks. Well, it almost works. Each OSC QLab cues works but if i fire them at the same time, it doesn't i have to set the second gue (the Go) a prewait of 1:100th of second to get it to work. Apparently LXConsole can't handle two command at the same time. Does it seem right? Anyway, it works but it is a little bit more of programming. If you could implement the MSC Timed_Go command it would be really great. Same result with just one Qlab cue, one box with the cue number, another for the duration, no programming , no OSC knowledge of the command. It doesn't get easier than this.
Anyway, thank you for the great work.

I spoke too quickly. 1/100th of second is a little bit short. Doesn't work every time. I just tested some duration and 5/100 th of second seems to be the minimum for it to work every time.

There's a new latest build of LXConsole available (65C05) that fixes the issue with the <almost> simultaneous OSC messages. It also adds support for MSC TIMED_GO.