Submitted

Playback Go Button(s) adjustable debounce to reduce unintended double-taps

A suggestion posed to us by a student joining our EOS training classes: It might prove helpful to allow the end user to select a waiting time between one hit of the GO button, and before next press would register. Depending on the speed of cue triggering during live event playback this might provide some protection against unintended cue playback.

drozendal
Parents

  • I think the easiest way to implement it uniformly would be in the properties for the target. When the button is configured as GO, there's an Option to Enable Debounce with a Tick Mark so you have to OPT IN. The Default is unticked. When you tick the box, the settings expand to show Re Arm Time with a Box to enter a time in seconds.

    I think Any Fader Target should have this. Subs,Temp Faders, and Cues could use that. For Subs it would be a button set to bump would have the option to Enable Debounce

Comment

  • I think the easiest way to implement it uniformly would be in the properties for the target. When the button is configured as GO, there's an Option to Enable Debounce with a Tick Mark so you have to OPT IN. The Default is unticked. When you tick the box, the settings expand to show Re Arm Time with a Box to enter a time in seconds.

    I think Any Fader Target should have this. Subs,Temp Faders, and Cues could use that. For Subs it would be a button set to bump would have the option to Enable Debounce

Children
No Data

www.etcconnect.com