Here is a gig file you can test with,
just replace the Kontakt Plugin by your MINI plugin
The right button when pressed plays C3
The left button sends panic and mutes the gain plugin which is connected after the Kontakt Plugin for about 2 seconds.
With this script the release sound is “muted” by the left widget.
//$<AutoDeclare>
// DO NOT EDIT THIS SECTION MANUALLY
Var
BUTTON : Widget
VOL : PluginBlock
R : Ramp
//$</AutoDeclare>
// Called when a single widget value has changed
On WidgetValueChanged(newValue : double) from BUTTON
if newValue == 1.0 then
TriggerOneShotRamp(R, 2000, 10)
Panic()
SetParameter(VOL, 4, 1)
end
End
// Called by timer ticking
On GeneratorRunning(timeX : integer, timeY : double) from R
Print(timeX)
if timeX > 1900 then
SetParameter(VOL, 4, 0)
end
End
@pianopaul
Thanks. I will test this. But I think one issue is: I can’t expect Gig Performer to stop the long release set on a VST, right? i,e, I might hear it still finishing a long release when unmute the gain?
@dhj
I mentioned it because I think you said you use X32 as audio interface (but not sure if you use X-USB).
And, now that I think of it, if you are on iOS, I guess that uses different (native iOS?) drivers.
Anyway, if I got lucky, and someone happened to chime in and say “Hey I use X32 X-USB on Windows, and the “Stop Audio Engine” (double-click panic) does not cause any issues”.
Then I would have some more comfort to just presume it was a “one-off” event that I had.
At some point I will come back to it, and test “double-click panic” again and see what happens.
An application cannot produce a blue screen of death - something has to go wrong in the kernel for this. When you double-click the Panic button, we are just an application telling the audio interface to reset itself. If that causes a blue screen, then the audio interface driver is causing it.
Understood. I never even intended/wanted to use “audio interface reset”. Someone had suggested trying it in the discussion.
On my quest to have a button to “stop all notes that are in a long release phase”, I think I “get it” now that I will have to do something to the VST itself (like send a program change to each VST that I want to “stop”). Solutions that rely on a widget button that “changes volume to zero” don’t do the trick because the notes can be still fading out when I press a button designed to "set the volume back to the prior level that existed before the ‘stop’ ".
I’d like to come back to the difference between All Notes Off (MIDI CC 123) and All Sounds Off (MIDI CC 120). GP will send CC 123 All Notes Off when Panic is triggered. That means all notes will decay with their programmed decay, and triggered one-shot samples will sound as long as the sample is.
That has been an issue for me with NI Kontakt, using one-shot triggered samples lasting many 10 seconds. They won’t stop by all notes off, in case of emergency.
Therefore, I wrote a little scriptlet, converting all notes off (CC 123) to all sounds off (CC 120) which I place in front of NI Kontakt. Maybe this solves the OP problem also with Arturia.
On ControlChangeEvent(m : ControlChangeMessage) Matching 123
SendNow(MakeControlChangeMessageEx(120, 0, GetChannel(m)))
End
You absolutely can, but the plug-in needs to support that functionality. Many do and can cut off sound on command
If your plugin keeps ringing when you come back to that rackspace (if I understand correctly this is the problem) you hear the tail of the last stuff played there. For example you may have a long reverb or delay set up.
A well developed plugin will know to stop all sounds and clear it’s buffers when given the command to reset itself. Others don’t care as the only test with DAWs and are not optimized for live use.