Hello.
Controlling LX Console via Qlab 4 through an ENTTEC USB PRO.
For the show I need to patch 2 dimmers in 1 channel several times.
When going directly through LX console and by-passing QLab everything is fine.
When I use Qlab to trigger the cues, only the first dimmer patched for the channel is working.
Any idea to make all the dimmers work when using Qlab ?
Thank you
lx with qlab playback issue
Re: lx with qlab playback issue
There is no reason why triggering a cue in LXConsole would be any different than triggering a cue with QLab.
I'm wondering if by chance that you had more than one file open in LXConsole when this happened. That can produce some unexpected results when using external triggers.
You can email a copy of your LXConsole and QLab files and we can see if we can reproduce the issue. But it is likely some simpler explanation.
I'm wondering if by chance that you had more than one file open in LXConsole when this happened. That can produce some unexpected results when using external triggers.
You can email a copy of your LXConsole and QLab files and we can see if we can reproduce the issue. But it is likely some simpler explanation.
-
lilyrosefrit
- Posts: 3
- Joined: Mon Mar 10, 2025 1:11 pm
Re: lx with qlab playback issue
No only one LX Console file open...
What email do I send you the files ?
Thank you
What email do I send you the files ?
Thank you
Re: lx with qlab playback issue
It is claudeheintzdesign [at] gmail.com
I'm not sure if you have QLab setup for lighting at the same time as LXConsole. I don't know if it is possible to have two applications talk to a USB DMX device at the same time. But, certainly something like that could be the issue.
Cues will produce the same output no matter how they are triggered. So, it is likely that the what you experience is caused by something else.
To be clear about the question, you are sending a /cue/n/start message from QLab to LXConsole and that produces a different output than if you just click go for cue n directly in LXConsole?
I'm not sure if you have QLab setup for lighting at the same time as LXConsole. I don't know if it is possible to have two applications talk to a USB DMX device at the same time. But, certainly something like that could be the issue.
Cues will produce the same output no matter how they are triggered. So, it is likely that the what you experience is caused by something else.
To be clear about the question, you are sending a /cue/n/start message from QLab to LXConsole and that produces a different output than if you just click go for cue n directly in LXConsole?
-
lilyrosefrit
- Posts: 3
- Joined: Mon Mar 10, 2025 1:11 pm
Re: lx with qlab playback issue
Just sent you the email.
Normally QLab is the only one sending dmx informations through the ENTTEC but maybe I am wrong.
Normally QLab is the only one sending dmx informations through the ENTTEC but maybe I am wrong.
Re: lx with qlab playback issue
Looking at your files, there is no lighting setup in the QLab file so it shouldn't be sending to the ENTTEC widget.
However, the port for sending OSC to LXConsole is set to 53000. Avoid this as QLab uses port 53000. I recommend using port 17688, the default for LXConsole.
I don't find a problem with the channels that are patched to more than one dimmer. I would note that one of those channels, the houselights on 96, are not recorded at any level but zero in any cues. So, while it is possible that you can control them live in LXConsole, they won't come on when a cue is triggered in QLab. You may want to be sure that the channel(s) recorded into the cue are the ones you think they are.
However, the port for sending OSC to LXConsole is set to 53000. Avoid this as QLab uses port 53000. I recommend using port 17688, the default for LXConsole.
I don't find a problem with the channels that are patched to more than one dimmer. I would note that one of those channels, the houselights on 96, are not recorded at any level but zero in any cues. So, while it is possible that you can control them live in LXConsole, they won't come on when a cue is triggered in QLab. You may want to be sure that the channel(s) recorded into the cue are the ones you think they are.