Partial control with constant but erratic strobing

[Marshallstacker]

Hello from a newbie to the forum... I have a strange and frustrating situation with my new setup. I will try to explain all I have tried to resolve to this point. I have a setup with 13 PARs (mostly ADJs), ADJ Mega Par RGBAs (I just added my custom profile on the site), Chauvet 4Bars, and Chauvet Intimidator 100 IRCs.

I downloaded the most recent version of QLC+ onto my Win 7 Pro desktop and am using a brand new Enttec open dmx USB. With this setup EVERYTHING works perfectly! Then I install the same version of QLC+ and the Enttec drivers (from their site) on my Windows 8.1 laptop and there is some control of fixtures, but every light flashes constantly with random frequency.

I figured the laptop was a bit older so I tried the same install on my Win 10 developer laptop and had the same strobing issues. Plug the Enttec back into my desktop and everything works fine again.

So I've tried to: use different cables (all DMX) and terminators, one light at a time - and I tried all the different models I have, powered USB hubs, I've edited the registry to change master refresh rates/limit DMX output channels, rates on the Enttec itself, device driver settings for the USB devices, Windows power profile settings, you name it, all to the same result. I also have the same issue using FreeStyler.

Here's a clue that may help - I installed Martin (now Onyx) M-PC last night on the offending laptop using the same lighting setup and Enttec, and everything worked fine. Fire up QLC+ and the flickering resumes. I also tried some simple DMX controller software on that laptop that also works fine using single lights.

So I've ruled out: The lights, cables, Enttec, and the laptop. As a software developer the only thing I can see remaining as an issue would be the way QLC+ (and FreeStyler) is passing data packets to the FDI driver but only on my laptops. Maybe parts of the packets are getting lost causing them be addressed incorrectly? Or maybe complete packets are being lost? For example I can bring up the master dimmer, then the red channel on a fixture and the red will light but will flicker even with the strobe setting to steady light. Any ideas would be greatly appreciated since I've spent quite a bit of time developing my show in QLC+ on the desktop but just can't cart it around to our band's gigs

[mcallegari]

Can you please use the "Return" key of your keyboard sometimes ?
I don't even start to read a post like this

[EDIT] thanks

[mcallegari]

Please don't change the MasterTimer frequency !
See this: viewtopic.php?f=17&t=12499
In 4.12.0, you can adjust the output frequency from within QLC+. You might try your luck with a value between 30Hz and 40Hz

[Marshallstacker]

Thanks! That seems to have solved the problem. I reset the master frequency and found the Enttec worked when set between 30 and 39Hz. At 40 the flickering started again. I had tried changing the frequency when I was first having the issue but as luck would have it I didn't try any in that range.

So I'm assuming the cheap open USB devices without a processor don't buffer the input at all?

Keep up the great work - MUCH more user friendly than an interface like M-PC.

[Marshallstacker]

I spoke too soon. Let it run for 15 minutes and it was out of sync again. Guess I'll need to upgrade my interface...

[mcallegari]

Open DMX devices are unbuffered, so I don't understand how it can possibly go "out of sync" after 15 minutes.
Please try at 30Hz, which is the frequency used by QLC+ 4.11.2 for Open DMX devices.

[Marshallstacker]

Thanks. I tried 30Hz and now it's flickering constantly (I was at 35Hz when it started flickering again after 15 minutes). But it works fine in M-PC.

I'm going to do a complete wipe and re-install of QLC+ and the USB drivers after our gig later this week to see if that helps.

If that doesn't work I'm handing over light show duties to my drummer

[andres robles]

Thanks. I tried 30Hz and now it's flickering constantly (I was at 35Hz when it started flickering again after 15 minutes). But it works fine in M-PC.

I'm going to do a complete wipe and re-install of QLC+ and the USB drivers after our gig later this week to see if that helps.

If that doesn't work I'm handing over light show duties to my drummer

For me it worked well a Dmx-Usb clone of enttec rx / tx (512dmx in / 512dmx out) to 22hz ...... test this

[syarbrough]

This may have no relation at all to what you are seeing, but might give this a try... I had some weird things going on with 4.12.0 on my MB..

When they start flashing uncommanded, switch to the 'simple desk', and hit the 'X' to clear the sliders.. See if they go back under control..

I've seen (and going to try the test version to see if it solves) my rig on 4.12.0 with some of the lights randomly getting commands/sliders up that weren't in the program they were sent... As soon as they start acting weird and I hit 'X' to cancel 'manual simple desk control' they all fall right back in line...

Since the freq setting didn't seem to help, you MIGHT be seeing the same thing I have gotten on mine (8 PAR leds, 2 ML units).
I'm using a DMX King USB adapter, connected to wireless DMX link out to the towers on my setup.

[GGGss]

This may have no relation at all to what you are seeing, but might give this a try... I had some weird things going on with 4.12.0 on my MB..

When they start flashing uncommanded, switch to the 'simple desk', and hit the 'X' to clear the sliders.. See if they go back under control..

I've seen (and going to try the test version to see if it solves) my rig on 4.12.0 with some of the lights randomly getting commands/sliders up that weren't in the program they were sent... As soon as they start acting weird and I hit 'X' to cancel 'manual simple desk control' they all fall right back in line...

Since the freq setting didn't seem to help, you MIGHT be seeing the same thing I have gotten on mine (8 PAR leds, 2 ML units).
I'm using a DMX King USB adapter, connected to wireless DMX link out to the towers on my setup.

Flickering has mainly to do with RS 485 (the mother of DMX) timing issues and adapters not being 'strong' enough to enforce correct timing.
* With unbuffered DMX interfaces (cheap and no internal processor) the timing is orchestrated by your computer. So it's your processor inside which composes the bit train. If you have f.i. a fixture at address 510 the chances of bit train timing faults are way bigger than the fixture at address 1.
* With a buffered one (has it own processor inside) QLC+ simply instructs "DMX address 110 value 60" and it's the DMX interface taking care of the rest. Since it only has to take care of DMX timing the bit train is a very precise and steady strong signal. (Even after 32 fixtures and 300m cable length).

In Syarbrough's case this is all just not true because he uses wireless DMX ... driving 8 PARs and 2 movers? And you get flickering? Ow boy ... Chinese ones I presume...
Hitting the 'X' in simple desk does do nothing unless the slider above it is set and the 'X' button is red.
Assuming or declaring that 'pressing the 'X' helps -> it does not (!) your problems are situated elsewhere...

I would urge you to start simple. Computer + DMX interface + 1 fixture (and a very low address), now start playing around and changing your timings until you discover problems. Then expand your setup. Once you get up to your towers and then hell breaks loose? you have wifi to blame, cable quality, fixtures deforming DMX signal train, end reflections in the cable etc etc

[syarbrough]

You misunderstood my post. I'm not getting flickering, I'm getting uncommanded modes in the lights..
The strobe channel is being turned on (in simple desk the slider Shows its up) but the scenes used did NOT use the strobe channel to the lights...
Also I get regularly color channels that ARE used in scenes that aren't 'going away' after a 'stop all' then the next scene is an all white (I get one or two fixtures that are still green), I hit the 'x' on simple desk and all the lights 'wake up' and go to the commanded mode for the current active scene.

Yeah, on mine each wireless receiver is driving no more than 3 lights in total (one receiver per tower, front two towers are 2 par and 1 ml each, rear towers are two par only) so I dont have any issues in signal strength
Only time I had a flickering was in the lights I replaced (2yo generic 127led cheapo-pars that were in the light rig when I took over) it was the circuit board in the light itself that was toast (after 2 years of use plus moving from show to show in less than ideal carrying system before I got involved in the lighting and changed how they were transported) sections of the lights would flicker, go dead, or give entirely different colors than the rest of the leds in the light..

[GGGss]

This may have no relation at all to what you are seeing, but might give this a try... I had some weird things going on with 4.12.0 on my MB..

When they start flashing uncommanded, switch to the 'simple desk', and hit the 'X' to clear the sliders.. See if they go back under control..

I've seen (and going to try the test version to see if it solves) my rig on 4.12.0 with some of the lights randomly getting commands/sliders up that weren't in the program they were sent... As soon as they start acting weird and I hit 'X' to cancel 'manual simple desk control' they all fall right back in line...

Since the freq setting didn't seem to help, you MIGHT be seeing the same thing I have gotten on mine (8 PAR leds, 2 ML units).
I'm using a DMX King USB adapter, connected to wireless DMX link out to the towers on my setup.

And again: your comment has nothing to do with the thread...

[jimbryant]

Hey there, a few days ago I was setting up a new ENTTEC OPENDMX USB, and I had problems much like you described.
I had just upgraded to QLC+ version 4.11. I tried rolling back to version 4.10, no help. I then installed version 4.10.
PROBLEM SOLVED !!!
Try it. You might like it.

[mcallegari]

I had just upgraded to QLC+ version 4.11. I tried rolling back to version 4.10, no help. I then installed version 4.10.

Nonsense. Maybe you meant 4.12.0 ?

[jimbryant]

Oops! Meant to say 4.9 !