ClearAudio giving the CPU a Heart attack!

[Father]

Yes that's right. I did put a ClearAudio module in my (not small) schematic to clear out the delays and stuff, every time it gets triggered causes a huge CPU spike. Whats wrong with it?!

[KG_is_back]

Nothing is wrong probably... The clearAudio resets all code. That also means the code will have to reinitialize all variables, arrays and code in stage(0) is executed. This may take a lot of CPU (especially in big schematics).

You may observe that using Analyzer primitive. You set your code to it's input (you may have to force it by holding ctrl+shift while creating the link), select number of samples to process and trigger it. The output is the values of processed samples, the code and the number of cycles per sample that were used to process the code. You will see that first sample takes considerably more CPU than all others.

[Father]

I see, its too much. We don't need to clear everything. just delays and reverb in my case. Is there a way to do it just for individual modules perhaps?

[KG_is_back]

Try selector - clicking it off and on

[Father]

OK I'll work on that. but another maybe related question. In some plugins like the NI Kontakt, when you click on the stop button in the host program (FL) twice, it kills all the voices and clears out the audio, of course without any CPU over load. I'm wondering if its possible to do something similar here?

[KG_is_back]

OK I'll work on that. but another maybe related question. In some plugins like the NI Kontakt, when you click on the stop button in the host program (FL) twice, it kills all the voices and clears out the audio, of course without any CPU over load. I'm wondering if its possible to do something similar here?

I always thought it is the same. Did you try that with your plugin too?

[Father]

I always thought it is the same. Did you try that with your plugin too?

yes of course, not working. Its a nice feature to keep notes with long release or delay and reverb feed backs in control. when you press stop, it stops the playback, and if you press stop again, it kills the voices. Not all plugins react to it though. I guess there is access to host's play back controls in the vst SDK.

[KG_is_back]

Well, Flowstone has "is playing" primitive which sends boolean based on host playback (true when is playing). However it sends triggers only when change happens - when the playback is stopped it doesn't detect stop button reclick. I'm also surprised this feature is not present in FS (since it actually is in FL studio).

[Nubeat7]

you should find out when the 'is playing' is working (on one stop click or on double click on stop)

afaik vst sdk has only one playing flag -> http://www.gersic.com/vstsdk/ (look under flags, its the same in 2.4)

all other relevant things are position based parameters, so the question is what is triggered with the first and the second stop click, does other 3rd party vst`s work with this function or only imageline vst`s?

[Nubeat7]

while if you for example use cockos vst extension, which is more or less widely used (afaik) you can use the

GetPlayState() function which returns an integer value representing the project play state. 1=play, 2=paused, 5=recording, 6=record paused.

or maybe better these:
OnPlayButton(), OnPauseButton(), OnStopButton()
void (*OnPlayButton)();
void (*OnStopButton)();
void (*OnPauseButton)();
These functions control the main transport for the host app. Only call these from the UI thread.

http://www.reaper.fm/sdk/vst/vst_ext.php