Because of all the current issues with USB-FTDI adapters on newer versions of QLC+4 and Windows 10/11 (USB timing, etc.) i have switched to a Dell Latitude E6330 (3rd gen intel) on Windows XP x86. Running QLC+ 4.11.2, but same thing happens, on various newer versions too
The thing is: System Timer Accuracy marker, according to thread: https://qlcplus.org/forum/viewtopic.php?t=10246 works in the way explained below:
"The timer check is limited only to Enttec Open DMX USB output. It shows either GOOD or BAD values.
The check is quite simple: it starts timer, sleeps for 1 ms and checks whether timer shows max 3 ms elapsed.
If the result is BAD it means either sleep was too long, timer to coarse (sometimes the timer can't measure up to ms resolution),
or the CPU is to busy to return control to QLC+/open dmx output thread.
When the check returns BAD, different code is used that does not rely on sleep() function, it actively waits."
~janosvitok
It looks like the result (Bad/Good) behaves very randomly even with original FTDI chips and completely nothing in the background running. Unplugging, restarting QLC+ a couple of times and it's "Good" again. However, I have noticed that flickering issues are less intense with System Timer Accuracy "Bad". I can see that one ADJ Par Z4 fixture flickers very frequently on "good" (every second or two it "misses" one of the RGBW channels"), meanwhile with "Bad" it only happens once every minute or so, and is more-less usable.
BTW, the universe works completely flawless on "classic" consoles like Showtec SM16-2 or Eurolite Scan control 192. But the stability of FTDI-based adapters is a completely different story
I remember the same thing happening with Dell Latitude 5300 (8th gen intel) and both Windows 10 and Linux Mint. However, i do not have that laptop anymore, so can't tell anything more precise.
Had anyone experienced anything similar before? Is there a way to force change the code that uses to measure time, other than manually changing the code and recompiling everything by myself?
Cheers!
P.S it Might, or might not be a partial duplicate of https://github.com/mcallegari/qlcplus/issues/1656