Disconection or else

[gmaincomputerservice]

Hello im using qlc+ on 2 macs and i select a scene to do like wash on a wall or doing some effects on moving and eventually the scene like do a flick or a mini reset position and then keep running the scene, its very fast like a split of second but i notice this and i do some corporate events and most times a need statics scenes.

Itry my macbook pro m3 with 8g ram and 512gb storage and the same specs on the m1, i try entecc open dmx and 2 more generic usb dmx also some usb to usb c converter. i manage to get a debug and i notice this when i choose a scene and after some minutes:

Time is late by 3596334 nanoseconds
virtual void MasterTimerPrivate::run() MasterTimer is running late!
Time is late by 12995833 nanoseconds
virtual void MasterTimerPrivate::run() MasterTimer is running late!
Time is late by 40397166 nanoseconds
virtual void MasterTimerPrivate::run() MasterTimer is running late!
Time is late by 30963541 nanoseconds
virtual void MasterTimerPrivate::run() MasterTimer is running late!
Time is late by 58221625 nanoseconds
virtual void MasterTimerPrivate::run() MasterTimer is running late!
Time is late by 17260709 nanoseconds

[mcallegari]

17260709 nanoseconds is actually 17 milliseconds, so less than one DMX frame.
You probably need to lower the output frequency,

[GGGss]

eventually the scene like do a flick or a mini reset position and then keep running the scene, its very fast like a split of second but i notice this

If I think what you try to say is the beginning of a DMX flicker. (The DMX signal train cannot be fulfilled on time.)
Lowering the DMX bus frequency or limiting the number of channels helps you with your 'open' DMX interfaces.