QLC+ & Q-Lab

[Celardor]

Hello everyone,

I’m having a small issue between Q-Lab and QLC+. I’m using a MacBook Pro M1 with macOS Sequoia, QLC+ 4.14, and QLab 5.4.8.

For a show with a lot of sound and lighting cues, I wanted to manage everything from Q-Lab. I programmed my entire show in QLC+ using a chaser and created a Sequential widget in my virtual console. I set up MIDI cues in Q-Lab that send a MIDI note.

In QLC+, on the second universe under MIDI, I enabled IAC as both input and output and used a generic profile as the MIDI device.

I then opened the settings of the Sequential widget to assign the “next step” button to the MIDI note sent by Q-Lab. So far, everything works fine. QLC+ detects the note and assigns it correctly.

However, when I switch to production mode and trigger my MIDI cues in Q-Lab, nothing happens. The strange thing is that I can make Q-Lab and QLC+ communicate if I restart QLC+. When I send a MIDI cue from Q-Lab, QLC+ correctly moves to the next step—but only once. If I trigger another MIDI cue (with exactly the same parameters), nothing happens. If I restart the application, it works again, but only once.

Has anyone encountered this issue before?

[MichelSliepenbeek]

If you check the Button Properties Section on the On Line Help for Input Profiles (https://docs.qlcplus.org/v4/input-outpu ... properties) you can read:

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 software 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.

It seems to me that this might solve your problem (or as an alternative send a Note Off from Q-Lab before sending the same Note On again).

[Celardor]

Hello, thanks for getting back to me.
I tried adding a cue with a note-off before each cue with a note-on, but unfortunately, it still doesn’t work. :/

[MichelSliepenbeek]

In QLC+, on the second universe under MIDI, I enabled IAC as both input and output and used a generic profile as the MIDI device.

As i do not use Q-Lab and do not own a Mac, i cannot reproduce your situation.
The best i can do is "guess" what it might be.


I had a look at the Generic MIDI Profile and noticed that all MIDI notes (channels 129 .. 256) are set as "Slider".
For the Midi controllers i use (Elation Midicon 1 and Novation LaunchPad mk2, but also for a lot of other profiles i checked) all MIDI notes are set as "Button".
In your description you attach a MIDI note that is set up as Slider (not as Button) as External Control to a Button, that just might explain the unexpected behaviour.

I suggest you to open the Profile with the Profile Editor, on the General Tab change Manufacturer from Generic to (something like) "Personal" and Model from MIDI to "Q-Lab Interface" and then (as a test) change some of the MIDI notes you use to Button (and maybe leave one or a few as Slider for now, that way you can notice the difference).
If this solves the problem, you best change all of your channels from 129 to 256 to Button and (in Q-Lab) adapt yourself to use Control Changes if you need Sliders and MIDI Notes for Buttons.
Remark: by changing Manufacturer and/or Model you have created your own Input Profile (once you save your profile). Make sure to use this profile as Input for IAC.



I also wondered why you enabled IAC as Output?.
If you use QLC+ just as a "slave to Q-Lab" (so you do not want to control Q-Lab from QLC+), it is better to unbox Output (it will prevent you from unnecessary noise on your interface).
If you want Q-Lab and QLC+ to perform some kind of "Hand Shaking" (e.g. QLC+ to confirm Q-Lab about the status of a Button), it is better to use FeedBack (where you set your External Control, you also have the ability to define specific Feedback values).

[Celardor]

I’ve tried all your recommendations, but unfortunately, I’m still facing the same issue. That said, it’s more a matter of convenience than a necessity, as I can still manage Q-Lab and QLC+ separately using an external MIDI controller.
Thanks for taking the time to help me!