Q Light Controller+

Hello
This is my very first post, so sorry if not at the right place or a too simple question, but trust me, i've tried to find out a solution before posting !

I have RGB led stripes controlled by QLC+. Leds blinks when the value is lower than "20" (dmx value) So, I(ve setup the faders values from 20-255
-> blinking solved
I also have buttons to force the R, G, B values to Max 255; When I click them the selected value goes to 255; When click again, back to the fader value
-> works fine too

The issue now : I'd like to set the R, G, B value to "0". And it seems there is a conflict with the faders that don't allow the "0" value because they start at "20".


This also worth for regular cursors (0-255); I succeeded adding a function to a button to force the max value that allows to switch between max (255) and fader value, but i'd like to do the same with black (pressed = 0, unpressed = back to the fader value)

How should i proceed ?

Thanks for your help !

Use channel modifiers http://qlcplus.org/docs/html_en_EN/chan ... rties.html
Basically they are mapping from 0..255 (QLC+ working values) to whatever you need on output. In your case, draw a curve that maps:
0->0, 1..255->20..255

Start with preheat 5%, that's most similar to your case.

Jano

Thank you Jano.
That is exactly what I wanted! #1 works really fine now !

Would you have an idea for my second problem ?
Maybe the enclosure picture will help to understand my need.
On the top of each fader I have a "full" button that sets the value to 255 and overwrites the value of the fader
When the button is released the value of the fader is taken into account again. (this works fine)

What I did NOT succeed is to set a "off" button at the bottom of each slider that would temporarly set the value to "0" (and of course go back to the fader value when released).

When i tried to do so, with a function "_LedZeroRed", the button blinks with no effect.

Thanks again for your first help !

Roland (Paris, France)

That is because the channels are set to HTP (Highest Takes precedence) - So higher values are always more 'boss' than lower ones.
If you'd change those channels to LTP (Latest Takes precedence) - than the last value sent is 'boss'.
Using LTP can cause some logical problems dough - once you get the hang of it - it will work fine.

Hello

I was suspecting it had someting to do with HTP and LTP.
Now that you give me the confirmation i'll dig a little bit deeper !

Thanks for the answer.