Q Light Controller+

Hi all

Several times I have lost control, always at show time so getting things in control rather than checking.

Saturday night arrive on site setup, House light, work light and some cyc. come back an hour later to open show and no control, the mimics go down but the lights don't or come up either.

Lenovo T410 (early i5, win 10/64, SSD, 12 Gigs, no WiFi, no updates, screen saver, power saver, USB power down all turned off) , Enttec USB Pro, 8 port Bemz splitter, 3 dimmer packs on one port, 8 Beams profiles 4 on each port, all DMX runs in correct cable and terminated.

Exiting QLC (4.13.1) and restarting it and control is back.

Nothing in event logs.

Any thoughts and were to start

Max

Unless a USB port power-saving feature is enabled, I cannot come up with a decent explanation. The Enttec PRO is a very decent device and my favourite workhorse.
Might your splitter have a HOLD function when the DMX signal is lost? Unplugging and replugging your DMX cable (at the Enttec port) might reset the DMX bus.

I have seen power surges cause such problems. It's more likely to happen if the computer isn't on the same circuit as the DMX packs.

Same problem in last nights show:
6:15pm power everything up quick flick around scenes in in virtual console, bring up one FOH on simple desk, all good, set first scene
7:50 (ten minutes to curtin up) bring up same channel in simple desk , all good
8:00 Curtin up, hit second scene, nothing changes,
out of run in VC to design, nope
pull USB out of USB/DMX interface nothing
restart QLC+ finally back in control

Rest of the show, no problems, all through rehearsals, no problems, hardware all good, DMX terminated every where, one bit of unknown fixed cabling (it is labels "data cable")

To me it appears that VC is dying when left idle to long ?

Will put another button on VC tonight and test there rather than simple desk

zl2max wrote: ↑Fri Aug 30, 2024 11:25 pm 7:50 (ten minutes to curtin up) bring up same channel in simple desk , all good
8:00 Curtin up, hit second scene, nothing changes,

Did you clear the red 'X' in Simple Desk? Simple Desk has the utmost priority and oversees everything else. (Even zero will output zero regardless of what function is running.)

Solution: Don't use Simple Desk. Replace the values you set in it with a true scene and call the scene on your VC.

Yes learnt that one early on.

Last nights show was fine, but I had but my test button on and nervesly used that several times before curtin up.

Thanks

Happened tonight at interval time, 2 events in event log:
This one 10 minutes before the next
Fault bucket , type 0
Event Name: MoBEX
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.Windows.StartMenuExperienceHost_10.0.19041.4239_neutral_neutral_cw5n1h2txyewy
P2: praid:App
P3: 0.0.0.0
P4: 5b4094ef
P5: ucrtbase.dll
P6: 10.0.19041.3636
P7: 81cf5d89
P8: 000000000007286e
P9: c0000409
P10: 0000000000000007


Looks like this one happened when I hit the button to dim the house lights:
Faulting application name: StartMenuExperienceHost.exe, version: 0.0.0.0, time stamp: 0x5b4094ef
Faulting module name: ucrtbase.dll, version: 10.0.19041.3636, time stamp: 0x81cf5d89
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x1904
Faulting application start time: 0x01db0022aa8cd347
Faulting application path: C:\WINDOWS\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\StartMenuExperienceHost.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 7d031029-e926-4a3b-b67e-e72478bd4dd5
Faulting package full name: Microsoft.Windows.StartMenuExperienceHost_10.0.19041.4239_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: Application

Agin the laptop is stable for anything else and nothing else in event log.

Thoughts please

ucrtbase.dll isn't part of the QLC+ distribution - so your problem is not related to QLC+
Googling ucrtbase taught me that this .dll is used as part of C++ (C##) distributions.
The lack of it or the misconfigured dependencies may lead to crashes. (Not only related to QLC+)
Here is an article - I'm not guaranteeing a positive outcome... https://www.partitionwizard.com/disk-re ... e-dll.html

I had the same issue last night. I'm on a Dell M6700, Windows 10, i7 processor, 32gb RAM, Enttec DMX Pro, Enttec D-Split (one output to a 12 channel ETC SmartPack, the other to 3 TomShine 30W movers in 11 channel mode), QLC+ 4.13.1.

I have 1 Chase that handles lights. There are only 41 steps in the chase, 24 steps are Shows. QLC+ was started at about 6 PM. The performance started at 8:12 PM. The last step that worked was a Show into a Scene, at 9:45 PM. The scene runs 35 minutes. When clicking into the next step, a Scene, the lights didn't change, going to the next step, a Show, the audio played, but the lights didn't change.

After the performance I checked the Enttec DMX Pro, and the light indicated it was still receiving a DMX signal, but I was unable to control any of the lights.

I stopped QLC+, restarted it, reloaded the project, but still couldn't control any lights. I had to restart the laptop before I could gain control of the lights.

I have already made the suggested changes to both Power and USB. I checked the Event Logs, but there weren't any events in any of the logs around the time of the lighting freeze.

FYI, this same project has been run for 9 other performances, with no problems.

I have the Enttec DMX Pro plugged into a USB 3 port. I am switching it to a USB 2 port and restarting the laptop before opening the house for tonight's performance.

I have had it a couple of time recently,
The ENTTEC disappears from "input/output" patching

Replugging the USB brings it back but still not conneted to the rig, but taking the tick out and putting it back does

So a little less intrustive than restart QLC and all the lights going out !!

Logged a ticket with ENTTEC this morning but maybe there is a bug there in QLC when using the ENTTEC

Nice to know it not just me, thanks

zl2max wrote: ↑Wed Nov 06, 2024 12:02 am Logged a ticket with ENTTEC this morning but maybe there is a bug there in QLC when using the ENTTEC

If you get a response from Enttec, please share it.