MIDI functionality
Posted: Mon Jun 05, 2006 6:05 pm
Mike - firstly, thanks for a fabulous piece of kit
I frequently use the hot keys function triggered by a MIDI keyboard. Is it possible to make non-latching triggers - i.e. allow the cue to run only as long as the key is active (with perhaps configurable decay option). This might also include looped cues such as a ringing telephone loop - the loop continues while the trigger is active and ceases immediately on release.
Continuing with the hot key theme, would it be possible for multiple instances of the same cue? At present triggering a cue stops the current instance and re-starts it. I would like to see an option to allow the hot key cue to play without interrupting the playing instance. For example generating overlaying multiple thunder claps from the one cue/trigger.
On a slightly different note: Is it possible to automatically skip cues? In the demo file the intermission sub (50) has a cue (50.1) to fade out intermission. If (50) plays through to end then 50.1 is still waiting to be triggered. An autostart cue added after the end of (50) that skips to (6) or triggers (50.1) would be useful.

I frequently use the hot keys function triggered by a MIDI keyboard. Is it possible to make non-latching triggers - i.e. allow the cue to run only as long as the key is active (with perhaps configurable decay option). This might also include looped cues such as a ringing telephone loop - the loop continues while the trigger is active and ceases immediately on release.
Continuing with the hot key theme, would it be possible for multiple instances of the same cue? At present triggering a cue stops the current instance and re-starts it. I would like to see an option to allow the hot key cue to play without interrupting the playing instance. For example generating overlaying multiple thunder claps from the one cue/trigger.
On a slightly different note: Is it possible to automatically skip cues? In the demo file the intermission sub (50) has a cue (50.1) to fade out intermission. If (50) plays through to end then 50.1 is still waiting to be triggered. An autostart cue added after the end of (50) that skips to (6) or triggers (50.1) would be useful.