Q Light Controller+

Hey Everyone,

I've been wrecking my brain trying to get this to work. What I'm working on is a project with 28 lights - 5 banks of florescent lights, 2 banks of can lights, and 9 spotlights, as well as 4 sets of RGB LED strips.

The computer is setup to control the lights and works great via QLC+. I have the fixtures programmed, and scenes programmed, and I setup the Virtual Console to control the six scenes that I need controlled. I have LoopBe Internal MIDI receiving MIDI signals from Proclaim presentation software. Basically what proclaim does is allows me to choose a slide in the slideshow and to send out a MIDI signal. The Virtual Console is setup to receive the MIDI signal to turn on the lights, and receives the velocity as the intensity - awesome. The problem that I am having is that when I send the MIDI signal, the solo frame no longer functions like a solo frame and allows multiple sliders within the solo frame to turn on. Sometimes it receives the signal and the slider goes where it is supposed to, but the lights don't turn on, until I reclick on the slider within the virtual console.

All this to say - I need help. I read somewhere that loopbacks may be the answer, but that is above my knowledge to configure at this point.

End Goal: A midi signal turns on a scene and the scene stays on, regardless of how many times that midi note is sent, until another midi note is sent, which case it changes scenes and stays on that particular scene, regardless of how many times the midi note is sent, until the next note comes, and onward.

The most simple solution would have been to have buttons that get triggered by the midi notes, but the presentation software will keep resending the same note throughout the rotation of the slides of a song, and each time the midi note is sent to the button, it toggles on/off. I need it to simply stay on until another button is pushed - or a solution that will mimic that result.

Please help!

Attached is the .qxw that I'm working with. Thanks!

Create a switchboard... a solo frame with buttons bound to all your midi commands. <- this tackles the multiple midi commands and the 'only one' function demand.
But now you are facing the fact that a 2nd midi note will kill these running functions.
Isn't there an option to alter the input profile (???) so only 'on' signals are interpreted?
With this switchboard, you set/reset chosen scenes.

Sliders in a solo frame are a bad thing: they won't work.
The use of loopback channels, allows you to enable functions within QLC+.
Create a virtual dimmer in a loopback universe.
Create a scene, setting this dimmer to 255.
Create a frame and bind this virtual dimmer to the en/disable state of that frame.
Now everything inside that frame will be fired through the switchboard.
The level slider goes inside that frame, so you can control the intensity.

Now the 2nd midi signal kills running functions:
Create a chaser with 2 identical scenes (the 'set 255'-scene in loopback)
Bind another virtual dimmer in loopback to the 'next' command of this chaser.
Change the buttons in the switchboard frame to flash.
Every incoming midi note will fire the chaser, executing the same command - enabling the frame (and functions within)

Now things will get a little complicated because the chaser has to be reset when another midi note is sent.
So create a dimmer and 'reset (0-value)'-scene in the loopback universe. (for every midi note that is)
Bind this dimmer to the stop-function of the chaser. (every note has to have its own chaser now)
In the chasers the first x-steps will be the reset-scenes of the other chasers. Set them to auto continue with 20ms time.

In theory, now the switchboard fires its assigned chaser, resetting other chasers and enables its frame. Function within that frame run.
If another note is sent, it resets all chasers, enables its frame and the 2nd function set starts.
If the note is repeated, the chaser proceeds to the next step, doing nothing but reenabling the frame-state.
If the note is repeated again, the other chasers will stop again (they were stopped before) and the chaser will enable the frame again (doing nothing because the frame was already enabled)

In theory, this should work ... I'm unsure when all comes together dough...

Take it step-by-step - one after the other... and then expand.

Dang. Thanks for the help.

Any chance - at the risk of sounding like a lazy noob - would you be able to download the file I uploaded and modify it to show me what it would look like actually configured? I got lost in it all.