Delaying multiple or repeat hot key triggers

[Kilian Waters]

I am setting up a video installation with a button interface so the viewer can essentially select the video they want to watch by pressing a choice of buttons that will send a midi signal to qlab and fire the relevant group.

Is there a way to stop repeat cues? I'm worried that if someone hits the button a number of times in a row or hits multiple buttons all at once (In particular if a small child starts bashing buttons) Qlab may crash or stall. I was hoping that there was a program that might stop further midi signals from being sent for 10 seconds after a button has been pressed or something along those lines.

Thanks

Kilian

[Mark Valenzuela]

There may be more elegant or effective solutions, but the first thing that comes to mind would be to look at arm/disarm cues. The idea would be that whenever one cue is triggered, it also triggers a disarm cue for all other cues. While those cues are disarmed, any midi trigger can be pushed and those cues won't respond. When the currently playing cue is done (or after xx number of seconds, depending on how you program it), an arm cue is triggered, putting all of the previously disarmed cues back into an armed state. 

Depending on how many cues you have, or other specifics of your programming, this might get a little complicated. And again, there may be other solutions. But you can definitely achieve what you describe with this method. 

Good luck!

Mark

--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: http://twitter.com/Figure53
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/ac87957d-56fd-4bfd-8ec7-c8b7c0a89724%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Bradford Chapin]

Yep,

I think arm, disarm, and start cues will be your friend here.

I've attached a screenshot (using v3) of how I might do it. Note the pre wait times. 

[micpool]

just use a post wait (without auto follow or continue)  on the cue that is triggered e.g 10s

A running cue can't be triggered.

Mic

[micpool]

Sorry, I misread your original post. post waits won't directly solve your problem in this case

Mic

[Rich Walsh]

We’ve come up with various versions of “gated GO” or “CD player mode” over the years. Here’s a simple version that uses the OSC method to enable the MIDI overrides: keys 1234 will only work one at a time to fire the respective cues.

You won’t be able to do a MIDI-triggered panic while cues are running. You could adjust the timings of the Start Cues to turn MIDI back on so that the buttons are only locked out for the beginning of a sequence, not the whole sequence.

Rich