Q Light Controller+

Hi,

i have upgraded to 4.9.2 GIT since my last post http://sourceforge.net/p/qlcplus/discus ... /49774461/ and haven't noticed any improvement.

When setting a scene with any value of a fixture being 0, qlc appears to not send the 0, instead sending no new value at all. So, for example, having a fixture RGBXYZ, 6 channels, LTP,
having a scene 255,0,0,0,0 and additonally switching on a scene 0,255,0,0,0,0 i get a mishmash 255,255,0,0,0,0 on the OLA dmx console. How can this be? LTP should prevent that, using the values from the second scene only.

Here's a video. https://youtu.be/Y_bUBrCY5z0

What am i doing wrong?

Hello,

It seems forcing HTP or LTP creates weird channel handling... I'm looking into it.

Here's your fix:
https://github.com/mcallegari/qlcplus/c ... be1add7ec1
It should also save some CPU during fade in/out transitions

Still, forcing intensity channels to LTP doesn't seem a good idea to me.

@plugz: sorry, I've been faster

GG, you were faster than me

And here's my not-cleaned-up take: https://github.com/plugz/qlcplus/tree/htp-ltp-fix


And here's a demonstration workspace file.

In the virtual console:

The first row buttons affect a fixture with HTP channels: OK
The second row buttons affect a fixture with LTP channels: OK
The third row buttons affect a fixture with HTP channels forced to LTP: OK with your fix
The last row buttons affect a fixture that has LTP channels forced to HTP: NOT OK with your fix
Check out what happens: channels get blocked to 255.



I think your fix is cleaner than what I've done, just needs something else to finally fix the HTP and LTP force issues in both ways

Hi,

i am used to doing whole shows in LTP, because like in my video there could be conflicting values, so i want the last scene/chaser/whatever i pressed the button for to override everything else. IDK why you should switch between HTP and LTP in fixture definitions, care to enlighten me?

Aside from that, thanks for the quick fix, i will try and pull it tomorrow.

Greetz

Hi,

Highpersonix wrote:IDK why you should switch between HTP and LTP in fixture definitions, care to enlighten me?

I don't know where you read "in fixture definitions", but anyway, what you do is forcing 3 HTP channels to LTP behavior, and as you've seen, it does not work perfectly. But now, thanks to Massimo, it's fixed
Some users may want to do the opposite: force an LTP channel to HTP behavior, and it does not work perfectly either, so we should fix it, but you don't need to wait for this.

Yes, that's exactly what i dont understand. Why are these HTP channels? Why isn't everything, the whole Show, LTP or HTP? For colours, HTP doesnt seem to make sense, as you see in my video, i want the colours to change one after another and not override each other and have the old set "linger". What would a correct workflow look like with these lights and why?

Greetz

HP