Feature request: Audio signal triggering cues

[David]

Some more progress on the audio triggers:

[SynthKeyWizard]

It's a great news!

[David]

I now have the new Audio Triggers working, but need to test more before the next release.

You enable the trigger (and set which cue it will start) via a control cue. You can also disable an Audio Trigger via another control cue.

[David]

I think there's a need to easily see the current status of each audio trigger.

Maybe a tab in the Info panel (or possibly a whole new dockable panel) that lists each trigger and shows whether it's waiting (armed), in lockout (after a trigger) or timed out.

Being able to set, cancel or test the trigger there might be useful too. It's hard to know exactly what's required yet without using it for a bit.

[David]

@SynthKeyWizard have you tried the audio triggers yet?

[SynthKeyWizard]

@SynthKeyWizard have you tried the audio triggers yet?

I didn't tested yet, but I will do this next week.

[SynthKeyWizard]

@SynthKeyWizard have you tried the audio triggers yet?

Unfortunately, I can`t test it because I can`t see any of available input devices in Triggers tab.
I have a couple souncards in my system (including built-in audio), but any of audio inputs are available in this tab, as you can see in attached screenshots.

[SynthKeyWizard]

I tested it more and i can`t see any of available inputs at my three computers. I have a three different soundcards and any of them are visible in Triggers tab.

[David]

The input devices were not being enumerated in the release version (I use a debug version).

I have fixed that for the next release (v203).

[SynthKeyWizard]

Is it possible to make possible to retrigger cue with incoming audio signal?

For example, I have a "bell" type sound which i need to trigger using audio input, but I need to trigger it even if it still playing. Currently I can`t do this. I can only trigger it again when it ends playing.

[David]

I'll see what I can do.

[David]

It can be done, but it does raise another question.

At present the 2nd Press Mode is used for Hot Key, Hot Buttons, OSC trigger, MIDI trigger & Schedule Trigger.

Should it be applied no matter what the trigger source is?

The other possible sources are GO, Control Cue (with Start Cue action), Cue Points and the Advance Action of xx Play.

[SynthKeyWizard]

Looks like triggered cue in main cuelist sometimes stuck at a start point. I was experimenting with triggering a very short audio file, and found that if it triggered with a high frequency, it can stuck at start point. MP then stays in a playing state but do not plays anything at fact. The only way to exit this state is to stop all and trigger again.

When I moved that cue to adlib list - it works OK.

[SynthKeyWizard]

It can be done, but it does raise another question.

At present the 2nd Press Mode is used for Hot Key, Hot Buttons, OSC trigger, MIDI trigger & Schedule Trigger.

Should it be applied no matter what the trigger source is?

The other possible sources are GO, Control Cue (with Start Cue action), Cue Points and the Advance Action of xx Play.

In most cases we use the only one way to trigger a Cue. At least, usual we do not need to trigger audio-triggered Cue with a hotkey or a midi. And if we need, we just changing a triggering source. Even if I need to trigger a Cue with a different trigger sources, then cue behavior must stay the same for all sources.

So, yes, I think it should be applied no matter what the trigger source is.

[David]

Have you used the sound trigger in a show yet?