"Stop" for audio trigger

Request a feature that you would like to see in QLC+.
Explain in details why you would need it and which is your usage case.
Post Reply
yokosuna
Posts: 204
Joined: Tue Mar 22, 2016 9:07 am
Real Name:

I´tried to use a keyboard shortcuts to start a cue list widget together with the audio trigger.
Works fine, but then I discovered that the "stop"-key for the cue does - as it should - stop the cue but
not the audio trigger. Well, you guess it, the two widgets became out of sync. So this will not work
as long as the audio trigger widget has no "stop" shortcut at all :-(
User avatar
mcallegari
Posts: 4480
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:

I don't really understand what you're asking.
The audio trigger widget has a enable/disable control. A "stop" feature for a live feed doesn't make any sense.

Plus I don't understand what you mean with "out of sync". Again, makes no sense since audio triggers capture live audio.
yokosuna
Posts: 204
Joined: Tue Mar 22, 2016 9:07 am
Real Name:

So let me explain:

Assign the key "A" to start the cue.
Assign the key "B" to stop the cue.
Assign the key "A" to start the Audio trigger.

Now press "A": both the cue and the trigger are running (or enabled - if you like that term better)
Now press "B": the cue stops but the trigger is still running.
Now press "A": the cue start but now the trigger stops.

And no, pausing the cue is not an option.
User avatar
mcallegari
Posts: 4480
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:

Please try this and let me know if it works:

- create a frame, and assign a key to the enable/disable control
- place your cue list inside the frame
- place your audio trigger inside the frame

in theory, when you enable/disable the frame, all the children widgets should be disabled/stopped as well.
plugz
Posts: 637
Joined: Sun Apr 12, 2015 6:30 pm
Real Name: David

mcallegari wrote: in theory, when you enable/disable the frame, all the children widgets should be disabled/stopped as well.
I don't think so, I think it just forbids interaction with the children widgets.
Post Reply