Q Light Controller+

Hi,
I'm running QLC+4 on my old notebook with intel i5-2520m and 8gb of RAM, my DMX interface is a cheap FTDI interface bougth on Amazon, the protocol is OpenDMX and the refresh rate is the default one of 30hz.
Unfortunately i get an higher CPU usage with some workspace that i have created.
Here i get a CPU usage of about 40% While here about 1% In both the screenshot i have only opened QLC+ and loaded the workspace, so there aren't running functions.

Any idea about the reason of this high cpu usage?

I have already tried to change the FTDI refresh rate and to remove the elements of the vritual console one by one, but nothing changes

Hi,

to investigate the problem, please:
- tell us your QLC+ version
- attach your qxw files here and also any other files needed to open the workspace (fixtures,...)
- tell us how to reproduce the problem (what functions do you start, or is it right after start?,...)

Jano

Hi,
It is the last QLC+4 version, so 4.12.7.
This zip file contains the folders Fixture and Gobos that need to be placed in the QLC+ folder in the UserProfile folder. This is the .qxw file with low cpu usage While this the one with high cpu usage To reproduce the problem, you have to just open the .qxw file, there isn't need to run any function

What I have observed with the high CPU project, is that if you __just__ open the project, the CPU load instantly uses about 11-12% with my system. Intel(R) Xeon(R) CPU E5-1620 v4 @ 3.50GHz 16Gb
Go into produce, the CPU load stays. But if you go back to Design mode, the CPU load drops to almost nothing and stays this way even when you go back to produce mode.

This is an odd behavior.
[edit]

Looking with resmon, I noticed, while after opening the high CPU project, that the high CPU load is made of 80% Services-Appinfo (group netsvcs). This drops after said produce-design-mode switch. So this is the reason for your high CPU.

[/edit]

To the OP: your strobe-scene will not function properly. This is because the shutter is an LTP channel and you never reset the chutter values. You need a 'reset strobe' scene to function.

Ok, i had not noticed this behaviour (the CPU usage drop when come back to production mode).
On my old laptop with 2 core/4 threads intel i5, the cpu usage drops from 45% to 15%, i think i cannot go under 15%.

To the OP: your strobe-scene will not function properly. This is because the shutter is an LTP channel and you never reset the chutter values. You need a 'reset strobe' scene to function.

Yeah, i had noticed this behaviour