I’m using MIDI Patchbay Version 1.0.3 (14) to get LX Console Version 2.3.1 (5117) to communicate with Qlab v2.3.7.
A tech person set up this system for me. I’ve been using it for about a year without problem.
Today in rehearsal Qlab/ MIDI Patchbay unexpectedly lost control of LX Console.
When I fire off an lx cue on Qlab, the exact same cues which were working an hour earlier, no longer work
I had a tech student looking around LX Console/ Qlab, so I’m not sure if she accidentally changed a setting?
I don’t think it’s the lighting equipment (DMX cable, dimmer pack, lights) – when I try to execute a Qlab cue, and look on the “live” display of LX Console, it hasn’t executed the cue.
Here's what i've checked already:
- When I go to “File” and click on “External” I have “MIDI and show control In” ticked,
- The “Preferences” under “MIDI” - “MIDI in connection” is set to “vo”. On my MIDI Patchbay, it says the MIDI out is set to “vo” and MIDI in is set to “vi”. On Qlab both the MIDI and the MSC have patch 1 to “vi”.
- I’ve also tried shutting everything down and restarting. And I’ve tried other files for other shows (which were working previously) and they are having the exact same problem.
Any other suggestions of what to try?
Troubleshooting with LX Console/ MIDI Patchbay/ Qlab
Try downloading MIDI Monitor. This will let you see MIDI messages being passed along. You'll want to select all of the check boxes for MIDI sources. You don't need MIDI Monitor to act as a destination for other programs. And, you'll want to spy on output to destinations.
When you try to send from QLab to LXConsole you should see two messages listed, From vo and To vi. This may help isolate the problem.
The only thing that I don't see listed in what you've done so far is to check that the Show Control ID is set to the same in LXConsole's preferences as it is in your QLab cues. MIDI show control is a system exclusive message so the MIDI channel shouldn't matter but the device ID matters and must match between QLab out (set in the settings of the MSC cue) and LXConsole in (set in the MIDI tab of the preferences).
Depending on what you see in MIDI monitor, you may want to try isolating the MIDI path by testing sending from QLab to the IAC Driver Bus and have LXConsole receive MIDI from the same IAC Driver Bus. (If you don't see this as an option in the list of MIDI connections, you'll need to use Audio MIDI setup to enable it.) This would eliminate MIDI Patch Bay from the route. However, it does not appear to me that this is an issue unless you don't see two messages in MIDI monitor for each MSC sent by QLab.
When you try to send from QLab to LXConsole you should see two messages listed, From vo and To vi. This may help isolate the problem.
The only thing that I don't see listed in what you've done so far is to check that the Show Control ID is set to the same in LXConsole's preferences as it is in your QLab cues. MIDI show control is a system exclusive message so the MIDI channel shouldn't matter but the device ID matters and must match between QLab out (set in the settings of the MSC cue) and LXConsole in (set in the MIDI tab of the preferences).
Depending on what you see in MIDI monitor, you may want to try isolating the MIDI path by testing sending from QLab to the IAC Driver Bus and have LXConsole receive MIDI from the same IAC Driver Bus. (If you don't see this as an option in the list of MIDI connections, you'll need to use Audio MIDI setup to enable it.) This would eliminate MIDI Patch Bay from the route. However, it does not appear to me that this is an issue unless you don't see two messages in MIDI monitor for each MSC sent by QLab.
Thanks so much for your advice!
Still can't get it working unfortunately.
I downloaded MIDI Monitor. When I activate a cue, it is sending 2 messages as you mentioned it should, 1 vo and 1 vi.
I looked into the show control ID - it was mismatching and I changed them both to the same thing but it still didn't work. Oddly, I went to quite an old Qlab file (the original one my tech person set up -i've had quite a number of different files since then which also are strangley not working) but that original Qlab file is working with the original LX Console file he set up, but those working LX Console/ Qlab files also have the mismatching show control ID but still seem to work.
Hmm, I can go back to the original version of the Qlab file (in fact I just cut and pasted all of the new Qlab cues into the old file) and now the new Qlab file works with the old LX console file, but i'd lose quite a lot of changes to just stick with using that old LX console file. Is there a way to copy all of the LX Console cues from the new non-working file into the old working file, similar to what I just did for Qlab?
I haven't tried the IAC Driver Bus thing yet (couldn't understand that, will try to figure that out again tomorrow).
Thanks so much!
Still can't get it working unfortunately.
I downloaded MIDI Monitor. When I activate a cue, it is sending 2 messages as you mentioned it should, 1 vo and 1 vi.
I looked into the show control ID - it was mismatching and I changed them both to the same thing but it still didn't work. Oddly, I went to quite an old Qlab file (the original one my tech person set up -i've had quite a number of different files since then which also are strangley not working) but that original Qlab file is working with the original LX Console file he set up, but those working LX Console/ Qlab files also have the mismatching show control ID but still seem to work.
Hmm, I can go back to the original version of the Qlab file (in fact I just cut and pasted all of the new Qlab cues into the old file) and now the new Qlab file works with the old LX console file, but i'd lose quite a lot of changes to just stick with using that old LX console file. Is there a way to copy all of the LX Console cues from the new non-working file into the old working file, similar to what I just did for Qlab?
I haven't tried the IAC Driver Bus thing yet (couldn't understand that, will try to figure that out again tomorrow).
Thanks so much!
It sounds as though your problem is file specific. You can e-mail a copy of your latest QLab and LXConsole files (the ones that first stopped working) and I'll take a look.
The mismatched Device IDs sound strange unless the one that works on QLab is 127 which is the ID for "All Call".
The command format on the QLab cues and for LXConsole should also match and should be "Lighting (General)".
You have a fairly old version of LXConsole. At some point in the history of LXConsole, there was a logic error in processing MSC cues that had to do with a combination of "All Call" and "All Types".
What should happen is that if the device IDs match, LXConsole should respond to messages with a command format of either "Lighting" or "All Types".
And if the device ID is 127 ("All Call") LXConsole should respond to messages with a command format of either "Lighting" or "All Types" as well.
But, some previous versions did not respond to the correct command format when receiving an "All Call" message. I'm not sure of the specific version number where this was fixed.
But, this gives you something to check. If there is a file specific problem, then it may have to do with the command format of the QLab MSC cues.
The mismatched Device IDs sound strange unless the one that works on QLab is 127 which is the ID for "All Call".
The command format on the QLab cues and for LXConsole should also match and should be "Lighting (General)".
You have a fairly old version of LXConsole. At some point in the history of LXConsole, there was a logic error in processing MSC cues that had to do with a combination of "All Call" and "All Types".
What should happen is that if the device IDs match, LXConsole should respond to messages with a command format of either "Lighting" or "All Types".
And if the device ID is 127 ("All Call") LXConsole should respond to messages with a command format of either "Lighting" or "All Types" as well.
But, some previous versions did not respond to the correct command format when receiving an "All Call" message. I'm not sure of the specific version number where this was fixed.
But, this gives you something to check. If there is a file specific problem, then it may have to do with the command format of the QLab MSC cues.
Just to clarify: On older versions of LXConsole, for an incoming MSC message, if either the MSC Device ID was 127 ("All Call") OR the command format was "All Types", LXConsole would not respond unless the other condition was met.
In other words, LXConsole would only respond in two cases, first, the Device ID matched the one set by the preferences AND the command format was Lighting (General). Second, the DeviceID was 127 (All Call) AND the command format was All Types.
Current versions of LXConsole handle All Call and All Types correctly.
In other words, LXConsole would only respond in two cases, first, the Device ID matched the one set by the preferences AND the command format was Lighting (General). Second, the DeviceID was 127 (All Call) AND the command format was All Types.
Current versions of LXConsole handle All Call and All Types correctly.
Thanks once again for your rapid and helpful replies!
I'll give this to my stage manager tomorrow and see if she can have a play around with it.
I also just downloaded the newer version of LX Console, and freed up a bunch of space on my harddrive in case that was slowing things down.
(today in rehearsal LX console froze several times and we had to force quit). Hopefully having the newer version and more free space will resolve this. If it happens again I'll send you the files - thanks for that offer - much appreciated.
Best,
Sunny
I'll give this to my stage manager tomorrow and see if she can have a play around with it.
I also just downloaded the newer version of LX Console, and freed up a bunch of space on my harddrive in case that was slowing things down.
(today in rehearsal LX console froze several times and we had to force quit). Hopefully having the newer version and more free space will resolve this. If it happens again I'll send you the files - thanks for that offer - much appreciated.
Best,
Sunny
Hi again,
I'm not sure if your email address is lx@claudeheintzdesign.com? I saw that you offered to have a look at the files if I emailed them (thanks!) so i emailed to that address.
Just to re-cap where I'm at:
The set-up:
I'm using qlab on my laptop, along with some lighting software, lx console, which are communicating via midi patchbay. It runs some lighting in my set (i have 2 dimmer packs and about 9 lights). The theatres lighting is run off their lighting board, so this is nothing to do with them.
I've never had problems with my system/ equipt/ software before (which someone else set up for me) and I don't know how to fix it. eek!
The problem:
It's been a few days worth of problem actually!
1. First, Qlab/ MIDI Patchbay unexpectedly lost control of LX Console. When I'd go to fire off an lx cue on Qlab, the exact same cues which were working an hour earlier, no longer worked. I don’t think it’s the lighting equipment (DMX cable, dimmer pack, lights) – when I try to execute a Qlab cue, and look on the “live” display of LX Console, it hasn’t executed the cue. The only way I found to resolve that, after trying some things suggested on the LX Console forum, was to cut and paste all of both the Qlab cues as well as the LX console cues into new files. It worked again for a little while, but then lx console started freezing.
2. So I downloaded the latest version of LX console (i was using Version 2.3.1, I'm now using Version 3.1.2 (65A03). FYI I’m using MIDI Patchbay Version 1.0.3 (14) and Qlab v2.3.7. At first, when I just tried without hooking up my computer to my little entec box via USB (which is then connected to my dimmer pack), it was working - i could see the lx cues ticking over in "live" mode in lx console. then once we hooked everything up (entec box, dimmer etc) it stopped working again (not sure if straight away or a little while later - my tech student was operating it at the time). Now:
- when i press go on the qlab cue, the LX console cue in "live" mode doesn't execute
here's what i've tried:
- Lx Console: when I go to “File” and click on “External” I have “MIDI and show control In” ticked,
- On LX console, the “Preferences” under “MIDI” - “MIDI in connection” is set to “vo”. On my MIDI Patchbay, it says the MIDI out is set to “vo” and MIDI in is set to “vi”. On Qlab both the MIDI and the MSC have patch 1 to “vi”.
- I’ve also tried shutting everything down and restarting. And I’ve tried other files for other shows (which were working previously) and they are having the exact same problem.
- I've tried cutting and pasting the cues into new files like i did last time, and it doesn't work.
- I downloaded MIDI Monitor. When I activate a cue, it is sending 2 messages as it should be, 1 vo and 1 vi.
- I've cleared off a lot of files from my computer so there's a lot more space in case it was my computer having trouble doing so many things at once.
I haven't tried your other suggestions yet because with my limited tech knowledge i'm struggling to follow them, which is why i thought it best to take you up on your offer to look at the files directly.
Or if you'd happen to know someone in toronto who you could recommend for me to pay to come and help troubleshoot in person?
best,
I'm not sure if your email address is lx@claudeheintzdesign.com? I saw that you offered to have a look at the files if I emailed them (thanks!) so i emailed to that address.
Just to re-cap where I'm at:
The set-up:
I'm using qlab on my laptop, along with some lighting software, lx console, which are communicating via midi patchbay. It runs some lighting in my set (i have 2 dimmer packs and about 9 lights). The theatres lighting is run off their lighting board, so this is nothing to do with them.
I've never had problems with my system/ equipt/ software before (which someone else set up for me) and I don't know how to fix it. eek!
The problem:
It's been a few days worth of problem actually!
1. First, Qlab/ MIDI Patchbay unexpectedly lost control of LX Console. When I'd go to fire off an lx cue on Qlab, the exact same cues which were working an hour earlier, no longer worked. I don’t think it’s the lighting equipment (DMX cable, dimmer pack, lights) – when I try to execute a Qlab cue, and look on the “live” display of LX Console, it hasn’t executed the cue. The only way I found to resolve that, after trying some things suggested on the LX Console forum, was to cut and paste all of both the Qlab cues as well as the LX console cues into new files. It worked again for a little while, but then lx console started freezing.
2. So I downloaded the latest version of LX console (i was using Version 2.3.1, I'm now using Version 3.1.2 (65A03). FYI I’m using MIDI Patchbay Version 1.0.3 (14) and Qlab v2.3.7. At first, when I just tried without hooking up my computer to my little entec box via USB (which is then connected to my dimmer pack), it was working - i could see the lx cues ticking over in "live" mode in lx console. then once we hooked everything up (entec box, dimmer etc) it stopped working again (not sure if straight away or a little while later - my tech student was operating it at the time). Now:
- when i press go on the qlab cue, the LX console cue in "live" mode doesn't execute
here's what i've tried:
- Lx Console: when I go to “File” and click on “External” I have “MIDI and show control In” ticked,
- On LX console, the “Preferences” under “MIDI” - “MIDI in connection” is set to “vo”. On my MIDI Patchbay, it says the MIDI out is set to “vo” and MIDI in is set to “vi”. On Qlab both the MIDI and the MSC have patch 1 to “vi”.
- I’ve also tried shutting everything down and restarting. And I’ve tried other files for other shows (which were working previously) and they are having the exact same problem.
- I've tried cutting and pasting the cues into new files like i did last time, and it doesn't work.
- I downloaded MIDI Monitor. When I activate a cue, it is sending 2 messages as it should be, 1 vo and 1 vi.
- I've cleared off a lot of files from my computer so there's a lot more space in case it was my computer having trouble doing so many things at once.
I haven't tried your other suggestions yet because with my limited tech knowledge i'm struggling to follow them, which is why i thought it best to take you up on your offer to look at the files directly.
Or if you'd happen to know someone in toronto who you could recommend for me to pay to come and help troubleshoot in person?
best,
I've tested the files with QLab 2.3.3 and LXConsole 2.3.1 as well as 3.1.9 and have run the light cues several times and they all work. That is, with the exception of cue 11 which has a MSC cue in QLab but no cue 11 in the lighting file.
There are very complicated groupings in the QLab file as well as some referenced applications that I cannot speak to, if they change the operation of QLab or what they do. In some cases, there is a pre-wait assigned to a lighting cue. So, when you fire it in QLab, you would not see the cue triggered in LXConsole until the wait expires. This could lead you to believe the cue was not working when it was really simply waiting to fire.
I would recommend updating QLab to 2.3.9 and see if that makes a difference. The MIDI connection through MIDI patch bay seems to be working although I'm not sure why it is used as opposed to simply using the built-in IAC Bus. I did notice that if the MIDI Patch Bay connection was lost, you need to turn OFF the MIDI/MSC connection in LXConsole and turn it back ON again for it to respond again to MSC messages from the MIDI Patch Bay application. I don't know what is happening when you lose a connection and LXConsole stops responding. It may be that the connection with MIDI Patch Bay is lost somehow and you need to reset LXConsole's MIDI receiver by turning it off then back on.
There are very complicated groupings in the QLab file as well as some referenced applications that I cannot speak to, if they change the operation of QLab or what they do. In some cases, there is a pre-wait assigned to a lighting cue. So, when you fire it in QLab, you would not see the cue triggered in LXConsole until the wait expires. This could lead you to believe the cue was not working when it was really simply waiting to fire.
I would recommend updating QLab to 2.3.9 and see if that makes a difference. The MIDI connection through MIDI patch bay seems to be working although I'm not sure why it is used as opposed to simply using the built-in IAC Bus. I did notice that if the MIDI Patch Bay connection was lost, you need to turn OFF the MIDI/MSC connection in LXConsole and turn it back ON again for it to respond again to MSC messages from the MIDI Patch Bay application. I don't know what is happening when you lose a connection and LXConsole stops responding. It may be that the connection with MIDI Patch Bay is lost somehow and you need to reset LXConsole's MIDI receiver by turning it off then back on.
Just in case someone closed it, note that the Live Window for the cue file you are trying to run must be open. This is true for both manual clicking the GO button as well as MIDI or other triggering of cues. You can adjust levels in the main display in Live mode without the Live window being open. But, you cannot run any cues.
Also, to make sure that the troubleshooting is looking at the correct thing, is it possible to run cues in LXConsole manually by clicking the GO button when this problem happens?
If you are using an DMX USB Pro widget for output, you'd be using the VCP driver with that old a version of LXConsole. This driver connection is very sensitive to being unplugged while LXConsole has a connection with it. Something that could be could be caused by a lose USB cable. This should not cause cues not to appear to run. But could certainly cause loss of DMX output until the entire computer was restarted.
Not that this is the issue here. But, removing the VCP driver and installing a newer version of LXConsole that uses the D2XX driver instead is much more immune to the box being accidentally plugged and unplugged while it is in operation.
If you are using an DMX USB Pro widget for output, you'd be using the VCP driver with that old a version of LXConsole. This driver connection is very sensitive to being unplugged while LXConsole has a connection with it. Something that could be could be caused by a lose USB cable. This should not cause cues not to appear to run. But could certainly cause loss of DMX output until the entire computer was restarted.
Not that this is the issue here. But, removing the VCP driver and installing a newer version of LXConsole that uses the D2XX driver instead is much more immune to the box being accidentally plugged and unplugged while it is in operation.
I've actually got the latest lx console now - 3.1.2.
And have restarted to make sure it was the loose usb, but still no luck.
In LX console, I can hit the GO button and the lx cues are ticking across, but when hooked up to the entec box and dimmer, the lights don't run. the little green light that usually flashes on the entec box to let me know that it's receiving a signal are not lighting up. although when i plug it in straight away there is one green blink of the light, so it's obviously not the entec box indicator light that's broken.
so it could be something wrong with the entec box as well (a dmx usb pro) but nonetheless, qlab is still not activating cues in lx console (lx console will only tick a cue across when i press go in lx console, not in qlab).
So I also just updating to qlab 2.3.9.
I also downloaded the midi patchbay, lx console and purchased a 1 day qlab licence for someone else's computer to replicate my set up on their computer, and once again qlab wouldn't fire off the cures in lx console. So I'm perplexed by why it would fire them off for you!
When you say turn the midi/msc connection off and then on again in lx
console, do you mean under File, external and untick and then re-tick
'midi/show control in'? Or is there another way to do this?
And have restarted to make sure it was the loose usb, but still no luck.
In LX console, I can hit the GO button and the lx cues are ticking across, but when hooked up to the entec box and dimmer, the lights don't run. the little green light that usually flashes on the entec box to let me know that it's receiving a signal are not lighting up. although when i plug it in straight away there is one green blink of the light, so it's obviously not the entec box indicator light that's broken.
so it could be something wrong with the entec box as well (a dmx usb pro) but nonetheless, qlab is still not activating cues in lx console (lx console will only tick a cue across when i press go in lx console, not in qlab).
So I also just updating to qlab 2.3.9.
I also downloaded the midi patchbay, lx console and purchased a 1 day qlab licence for someone else's computer to replicate my set up on their computer, and once again qlab wouldn't fire off the cures in lx console. So I'm perplexed by why it would fire them off for you!
When you say turn the midi/msc connection off and then on again in lx
console, do you mean under File, external and untick and then re-tick
'midi/show control in'? Or is there another way to do this?
It sounds like you may have two separate problems. First, there is the problem with LXConsole not talking to the DMX USB Pro. Second, there is the lack of MIDI connection between QLab and LXConsole.
It is not beyond the realm of possibility for the DMX USB Pro to fail. I've had one die and I know of another person who had one quit as well. Because you started with an old version of LXConsole, you must have had the VCP driver for the widget installed. Later versions of LXConsole install the D2XX version of the driver which is more reliable. Unfortunately, you cannot have the VCP driver installed and have the D2XX driver work:
http://www.enttec.com/support-center/kb ... nect_to_it
If you don't want to use terminal commands to remove the VCP driver, you can use the Finder's Go To Folder command to open the /System/Library/Extensions folder. Locate the file named: "FTDIUSBSerialDriver.kext" Hold down the control key and click on this file. Choose Move to Trash from the menu that pops up. You'll need to authenticate to complete the move to the trash. Re-boot the computer and empty the trash.
In LXConsole's Preferences, go to the DMX Info tab. Choose "D2XX Driver" from the ENTTEC DMX USB Pro Widget list. (Just to be sure, in the DMX Out tab, the out connection should say "DMX-USB Pro") Quit LXConsole. Plug in the ENTTEC box. Restart LXConsole and you should be able to get the flashing light by playing cues. If this does not work, then there is probably something wrong with the widget.
To eliminate MIDI Patch Bay from the possible source of the problem with QLab connecting to LXConsole, I suggest switching to using the IAC Driver Bus. To do this, go to /Applications/Utilities and look for the Audio MIDI Setup application. Open this and choose Window->Show MIDI Window. You should see the IAC Driver icon in the window. Double-click the icon and be sure the "Device is Online" box is checked. Close the IAC Driver Properties window. Then close the Audio MIDI Setup application.
Go to LXConsole's preferences and look at the MIDI tab. Choose "IAC Driver Bus 1" from the popup list of MIDI in connections. Make sure that The File->External-> MIDI/Show Control In command has a check next to it. Make sure that the Live window for the file is open.
Go to your QLab file. Click Preferences. Select the MSC tab. Drag a line from Patch 1 to IAC Driver Bus 1. This will connect the output of your MSC cues to the IAC Driver instead of MIDI Patch Bay. Click Done. In the main cue list, click on one of the MSC cues to select it. Click the GO button. You should see the corresponding cue run in LXConsole's Live window.
MIDI Show control from QLab to LXConsole via the IAC Driver is very well tested over time. However, if anyone has anything to add about tricks that they have found, please chime in.
It is not beyond the realm of possibility for the DMX USB Pro to fail. I've had one die and I know of another person who had one quit as well. Because you started with an old version of LXConsole, you must have had the VCP driver for the widget installed. Later versions of LXConsole install the D2XX version of the driver which is more reliable. Unfortunately, you cannot have the VCP driver installed and have the D2XX driver work:
http://www.enttec.com/support-center/kb ... nect_to_it
If you don't want to use terminal commands to remove the VCP driver, you can use the Finder's Go To Folder command to open the /System/Library/Extensions folder. Locate the file named: "FTDIUSBSerialDriver.kext" Hold down the control key and click on this file. Choose Move to Trash from the menu that pops up. You'll need to authenticate to complete the move to the trash. Re-boot the computer and empty the trash.
In LXConsole's Preferences, go to the DMX Info tab. Choose "D2XX Driver" from the ENTTEC DMX USB Pro Widget list. (Just to be sure, in the DMX Out tab, the out connection should say "DMX-USB Pro") Quit LXConsole. Plug in the ENTTEC box. Restart LXConsole and you should be able to get the flashing light by playing cues. If this does not work, then there is probably something wrong with the widget.
To eliminate MIDI Patch Bay from the possible source of the problem with QLab connecting to LXConsole, I suggest switching to using the IAC Driver Bus. To do this, go to /Applications/Utilities and look for the Audio MIDI Setup application. Open this and choose Window->Show MIDI Window. You should see the IAC Driver icon in the window. Double-click the icon and be sure the "Device is Online" box is checked. Close the IAC Driver Properties window. Then close the Audio MIDI Setup application.
Go to LXConsole's preferences and look at the MIDI tab. Choose "IAC Driver Bus 1" from the popup list of MIDI in connections. Make sure that The File->External-> MIDI/Show Control In command has a check next to it. Make sure that the Live window for the file is open.
Go to your QLab file. Click Preferences. Select the MSC tab. Drag a line from Patch 1 to IAC Driver Bus 1. This will connect the output of your MSC cues to the IAC Driver instead of MIDI Patch Bay. Click Done. In the main cue list, click on one of the MSC cues to select it. Click the GO button. You should see the corresponding cue run in LXConsole's Live window.
MIDI Show control from QLab to LXConsole via the IAC Driver is very well tested over time. However, if anyone has anything to add about tricks that they have found, please chime in.
So:
- I went to the /System/Library/Extensions folder and there is no FTDIUSBSerialDriver.kext file
- I followed your instructions for lx console for the D2XX Driver, ENTTEC DMX USB Pro Widget list and the DMX Out tab and YES! Lx console now sends the cue through the enttec box and lights are working! So, that rules out the enttec box as the problem.
- unfortunately, still can’t get qlab and lx console to communicate! I followed your instructions to hook up the qlab instructions for the IAC Driver Bus 1 rather than via the midi patchbay, and the File->External-> MIDI/Show Control In command has a check and it’s in live mode. I patched the IAC driver bus to patch 1 in the MSC preferences in qlab. But it’s still not firing the cues in LX console!
Any next suggestions?!
A question that may be of no relevance – in lx console under the preferences, should DMX in be disabled or one of the other options such as art net 2/10, dmx usb pro (assuming not since it comes up with “dmx in and out can’t be the same”) or ACN?
- I went to the /System/Library/Extensions folder and there is no FTDIUSBSerialDriver.kext file
- I followed your instructions for lx console for the D2XX Driver, ENTTEC DMX USB Pro Widget list and the DMX Out tab and YES! Lx console now sends the cue through the enttec box and lights are working! So, that rules out the enttec box as the problem.
- unfortunately, still can’t get qlab and lx console to communicate! I followed your instructions to hook up the qlab instructions for the IAC Driver Bus 1 rather than via the midi patchbay, and the File->External-> MIDI/Show Control In command has a check and it’s in live mode. I patched the IAC driver bus to patch 1 in the MSC preferences in qlab. But it’s still not firing the cues in LX console!
Any next suggestions?!
A question that may be of no relevance – in lx console under the preferences, should DMX in be disabled or one of the other options such as art net 2/10, dmx usb pro (assuming not since it comes up with “dmx in and out can’t be the same”) or ACN?