I had to take a break from my lighting journey for personal reasons, roughly a year. Now I can continue embracing QLC+. Or can´t, given the odd issue I face: QLC+ scene changes stopped working the way I was used to and it looks like Artnet is the cause.
So in my setup from a year ago, I was in the middle of creating a mildly complex setup, two universes, a good number of fixtures and everything worked like a charm.
Now I get a very mixed bag: Sometimes scene changes work, sometimes they don´t. It drives me nuts, since the behaviour is not regular in any way.
So to reduce complexity, here is what I did:
1. Detaching the larger DMX installation
2. Connect only a single LED Bar, proper termination.
3. Most simple network setup: Just a crossover cable from PC to the Artnet Node (showtech net-2/3)
4. Reduce windows networking to just IP and that´s it (no fancy services, no ipv6 etc)
4. New QLC project, just the definition of that LED Bar.
So now there are just three scenes:
A) all red LEDs on
B) all blue LEDs on
C) all values zero (to mimic blackout)
So switching to Scene A works. Blackout button works, I can manually blink away happily
Switching from A to B sometimes works, sometimes doesn´t. The same is true for switching back to A if calling B was successful.
However, if switching does not work, as soon as I touch any fader, the scene is called and the lights respond.
If I switch from any scene to blackout, then select a different scene, un-blackout... everything works like a charm.
The DMX monitor shows that QLC is setting the values correctly (except for the blackout not being reflected in the monitor, but that´s ok).
So in your experience: What could cause this weird behaviour?
I already tried different network cables, dmx cables, artnet node modes (htp, ltp, single), but nothing really changed. The complete setup worked as expected when I worked on it last year and that means two universes almost full of devices, switched network in a separate VLAN and whatnot. And now suddenly the easiest setup acts funny. Did I probably miss some issue with any Windows Update lately? Or is it copper worm in the ArtNet node, munching away on the chip
?I´m running out of ideas of what to change/test, maybe you have seen something like this and can point me in the right direction.
Cheers,
Oliver
