Turning Off Functions When Activating a New One

[tbutler]

I'm trying to setup MIDI control of our DMX lighting and have run into an issue I can't seem to resolve: we're using our presentations software (Proclaim) to send the MIDI signals and I don't necessarily always know that the slides are going to be displayed in a linear order. Each slide can send a set of MIDI signals when the slides come up, but it doesn't have a way to send additional signals when the slide fades out.

So, if I bring up a slide and send a MIDI signal to turn on the "blue scene," I then need to send another MIDI signal on the next slide to turn off that function before I turn on the next scene, say the "magenta scene," but I don't necessarily know that the blue scene is in fact on, if the slides weren't displayed in order, so I may get an unexpected result, such as toggling on two different functions at the same time or accidentally toggling everything off.

I tried adding a "Stop all functions" button to the virtual console and then triggering that with a MIDI signal before triggering a new function, but that didn't seem to work reliably -- I guess the software was sending both signals so close together, it'd actually cancel the new function.

So, my question: is there a way to make a function button that will automatically "Stop all (other) functions" when it is pressed? That's essentially the result I want anyway and it would be much more reliable if I could send one MIDI signal to accomplish this and then let QLC+ handle it rather than trying to have my presentation software send multiple signals.

Thanks!

[janosvitok]

Try putting buttons in a https://www.qlcplus.org/docs/html_en_EN ... frame.html

[richbass]

Yes, as janosvitok has said.
As long as all of your functions are within the same solo frame, currently running functions are stopped when you trigger a new function; exactly what you're asking for.

[tbutler]

Thanks janosvitok and richbass! That works great! One follow up question that occurred to me now that I've tested this configuration: is there a way to make a solo frame where you can't turn off one function without turning on another one? That is, is there a way if the same MIDI signal gets fired twice, it wouldn't toggle a function off, but if I fire a new signal, that new scene would become the new solo?

Thanks!

[GGGss]

This IS possible but makes things very very complex... aka not-built-in (unless chasers with feedbacks etc)
Does make me think of the toggle buttons on ancient radio's ... you HAD to pick one.

In your (multiple midi users) context I see your point ...
When 'we' use the VC we press a spot or a button deliberately ... = 1 function
you guys think you sent a midi command (pedal, key, ...) to qlc+ but aren't sure if this is one two or even three midi-pulses.

a 'if nothing is selected default to' possibility would be 'a nice to have' in mono-frames

[tbutler]

Yes -- I was thinking of those radios, too. It does seem like it would be really a helpful option. How would the very very complex option work? Is there something you could point me to to get started on that? Thanks so much!

[richbass]

The same function would be useful for me too, but as yet I only have a fudge of a work around.

My issue is that I trigger scenes with a foot controller while playing bass. Some scenes are used more than once, and the order they’re triggered can vary. It’s possible I’ll trigger the same scenes in series and turn the scene off (I’m concentrating on my playing at this point, not looking at the software). So, I think the same problem you’re describing.

My ‘fudge’ solution is to clone the scene, and trigger different clones with my foot controller. A different midi pc message is sent, triggering clones of the same scene. The audience don’t notice a change.

Maybe this is a short term fix until something ‘better’ can be implemented.