Q Light Controller+

Hi Massimo (and colleagues)

I would love to be able to use the new features that are coming along but I seem to be stuck in 4.8.5

The reason is that I rely on DMX input but, as soon as I connect a DMX desk to my interface, QLC+ just crashes. I have attached some screen shots and a very simple project file (a single dimmer output on universe 1, a single slider control linked to DMX channel 1 on universe 2) My interface is a DMXKING UltraDMX Pro with output 1 assigned to universe 1 and the input assigned to universe 2. This set up works fine on v4.8.5 under Win10 on two different laptops and under WinXP on a third laptop but fails on all later versions as soon as the external DMX desk is connected and switched on.

Please see if you can spot whatever it was that changed after 4.8.5 and put it right so I can gain access to all these lovely new toys you are providing.

Many thanks in anticipation. If you need further information or need me to perform any other tests do, please, let me know.

PS I hope I have posted this under the right category and that I have not missed something in an existing post. I notice there are some similar sounding issues but they related to a different DMXKING interface (without input) and to OSX rather than Windows.

Just tested your same configuration with a ultraDMX Pro on Windows 10 with the latest QLC+. No crashes at all.

Make sure that:
- you have a clean installation of QLC+ (means: uninstall and install QLC+)
- your FTDI windows driver is up to date. I guess you can go to the control panel device list and check for updates

Hi Massimo

Thanks for the speedy response.

So, I de-installed QLC+, Deleted the QLC sub-tree in registry, installed the latest FTDI drivers from their web site, re-booted, checked that the DMXKING utility could see the interface (on COMport 5) and that it was responding to input, installed the latest QLC+ started it up, created my test project, assigned the DMX OP, assigned the DMX IP and it crashed as soon as I did that.

Restarted QLC with the desk off but it crashed as soon as the desk was turned on.

Started it again and it now crashes straight away (even with the desk off)

To be fair it is my own fault. I somehow missed the instruction not to install the VCP drivers for FTDI. In my defense, there is only the one install package which installs both VCP and D2XX and the device itself determines which will be used. For the DMXKING UltrPro that will be the COM port (VCP) driver.

Also in my defense, this install was working in 4.8.5 for both input and output and it works for output only in the latest version and the QLC display says it is using the D2XX driver.

So digging around in the FTDI documentation I found out how to turn off VCP and (presumably) force the use of D2XX. I did this but the DMXKING config utility stops working. QLC fails to identify the serial number of the device and, more importantly, stops working on OP as well as IP.

So, while the documentation clearly says do not install VCP there doesn't seem to be a way to prevent it. Next best thing (turning VCP off) stops the interface working at all. So I am no further forward on that score.

Fortunately I have a DMXKING eDMX4 interface as well. That is working for IP and OP. I was treating it as my backup device but it looks like it will have to be promoted to the main (and only) interface. It still leaves me without a backup for input however and an expensive interface that I can't use (except as a splitter but I have one of those and anyway the eDMX4 can output the same data on any or all of its four channels so I don't really need a separate splitter).

Any further ideas or do I consign my UltraPro to the redundant hardware pile and start saving up for an alternative backup device?

i have the exact same problem with my enntec DMX PRO