QLC is using 255 values for Scenes in Chaser for no reason

[KloMeister]

Hi,

I am using QLC+ 4.13 on my Rasbian Pi 4b (I downloaded it from the reserved area after I spent for it).

My problem is, that simplest things dont work, so I cant use this software in a real case.

I created two Scenes:

Blau: Color-Wheel value = 31
Gruen: Color-Wheel value = 44

Then I created a chaser list which switches between "Blau" and "Gruen" every 3 seconds (holding time). After I play this chaser I will get 255 Values for one of my scenes, which I never defnied.

I also tried to create a new project, i used other values and i also used other names. One of the scenes are always creating 255 values for no reason. This makes this lightning software useless for all my cases and I am a bit frustrated, because I dont know how I should solve this


Watch the file I uploaded to my webspace to understand the problem more clearly:
https://klomeister.eimer-24.de/Daten/QL ... er_Bug.mp4

[janosvitok]

Hello,

can you attach your qxw file here?

Jano

[mcallegari]

Works here.
You're doing something wrong that you omitted to say.
Either the fixture definition is wrong or something else is in place (e.g. virtual console)
Attached working project

[mcallegari]

My best bet is that in your custom fixture definition the color wheel is set as Fine (LSB) instead of Coarse (MSB)

[KloMeister]

I can tell you more in about 4h. Then I have access zu my RPI.

For now I can tell you, that I used an internal fixture called "Color-Imagination LedSpot 90 (SI-052)". I just renamed it in my project to FosMH, because it has nearly identical DMX Channels as the "FOS Spot 150 Pro" which I use.


Looks like it is set as MSB (but I checked it on Windows, will check this on my RPI then too.

I will test everything you told me soon. I will also try your example project to check if this works.

[KloMeister]

I used your project and I got exactly the same issue. It feels like I am crazy but for sure I am not.

I copied your project to my pi home folder and opened it as you can see on my new video here:
https://klomeister.eimer-24.de/Daten/QL ... roject.mp4

As hard as it feels, but it must be something like a bug.

I just installed the newest Rasbian OS on my RPI 4b, than installed the debian package from your "reserved area". Everything else is clean, so there arent any hidden influences.

Everything else in this software is working. I can use a Sequence instead, than it is working. But that cant be a real solution for this problem.



I tested some more cases, so here I show you this bug with 5 Scenes and 3 Channel Values instead, maybe this helps a bit more to identify why this happened:

Black: 3 Channels Value = 0
Blue: 3 Channels Value = 10
Green: 3 Channels Value = 20
Red: 3 Channels Value = 30
Yellow: 3 Channels Value = 40

Here you can see, some Scenes are working some not. But if there is the bug, then all 3 Channels will bet set to 255.
https://klomeister.eimer-24.de/Daten/QL ... hannel.mp4


Im here to find a solution together with you. I am a software developer too and there are strange bugs on earth which are making no sense.

This Bug happened with the newest version of the debian QLC+ package (4.13) at least on my RPI 4b. On my Windows PC QLC+ 4.13 is working fine.

If I can help more, tell me what I can do to support.

3 Things we are knowing for now:
- Bug has not anything to do with the Fixture
- Bug has nothing to do with the project file
- Bug is on (my) RPI4 on newest Rasbian OS with Debian Package QLC+ 4.13



Edit: Okay I just tested a bit more around and found out, that if I am using a Fade-In time for >0ms (at least 1ms) than the values will bet set correctly. Hopefully that can maybe help to fix the problem.

With this work arround I can live for now, but this should be fixed maybe in a later release if the reason is known.

[mcallegari]

I confirm this is a serious bug. I easily reproduced it so I can work on it.
I believe it has something to do with the switch to 64bit architecture and DMX values calculation.
Unfortunately I have already packed version 4.13.1 so it will not include a fix for this.
Good that you have already found a workaround but this has to be solved.

[mcallegari]

I have started to work on this, just a quick update.
I found the exact spot where the DMX value calculation goes wrong.
While I find a proper fix I can suggest another workaround: set the channel as "can fade = false" in the channel properties panel
I'll write again when I fix the issue

[mcallegari]

The issue should be fixed now.
I'll rebuild the Raspberry Pi packages soon