Q Light Controller+

Hi,

I couldn't find a similar question to my own on the forum or in the documentation, so decided to create a new thread here.

My question is how can one trigger a button in QLC+ by sending MIDI CC with value 0?
Only when sending values of 1 and above does QLC+ trigger the button, is there a way for it to toggle when receiving value 0 as well?

Context: I'm programming my show in MIDI from Cubase. Any time I stop the track in Cubase, all my running functions continue running as Cubase does not send an individual note off for every sounding note. Instead, it sends MIDI CC 123 (All Notes Off) with value 0, which is what I want to map my Stop All Functions button in QLC+ to. I could use custom third party MIDI mappers to translate MIDI CC 123 0 into MIDI CC 123 1, but that feels like a workaround I'd rather avoid if it turns out QLC+ has a way of configuring my setup.

Thanks for the help!

Kind regards,
Nils

If you look at the on-line help for Input Profiles https://www.qlcplus.org/docs/html_en_EN ... files.html and go to "Button Properties"you will find:

Generate an extra Press/Release when toggled: this is a quite specific option used for example when dealing with TouchOSC or the Behringer BCF2000.
QLC+ toggle events are triggered when a high+low sequence is received. This means that QLC+ expects a non zero value (typically 255) followed by a zero value to toggle, for example, a button.
Devices like BCF2000 or softwares like TouchOSC, instead, send just a non zero value when activating a button, and a zero value when deactivating it.
When checking this option, QLC+ will generate the "missing" events to standardize the way some controller work. So, for example, the BCF2000 will look like sending 255+0 when pressing a button, and another 255+0 when pressing it again.

This explains the behaviour that you experienced.
I suggest to try if the "Generate an extra Press/Release when toggled" will solve your problem.

As i don't use Cubase i cannot perform this test in my situation (otherwise i would have done it for you).

I tried that setting as per the documentation, should have probably mentioned it sorry. From my testing it doesn't solve my issue, and from reading the description of the setting I get why. Cubase never sends a non-zero value, and as such there's no +0 to add. Hmm, MIDI mapper or a change to the source code it is then :/