Option to NOT Flush FX on playback start

[Rv5]

At present there is an option to 'Flush FX on Stop'. With this enabled, Reaper tells Vienna Ensemble Pro 5 (VEP) to restart its engine per instance upon pressing stop, causing Reaper to pause while this happens.

As Reaper appears to flush FX on start, Reaper does this every time play is pressed, causing a delay in playback when multiple instances of VEP are loaded. The more instances the longer the delay in playback as Reaper tells each instance of VEP to reset its engine. This causes and un-usable delay when working with orchestral templates.

Given that the same happens when pressing stop with 'Flush FX on Stop' enabled, it would make sense that an option to 'Do Not Flush FX on Start' for specific plugins at least, would solve this problem.

Please see:

http://forum.cockos.com/showthread.php?t=144309

for the VEP problem, and:

http://forum.cockos.com/showthread.php?t=140690

for a similar issue regarding other plugins.

This feature would solve some issues it seems, and would certainly make Reaper usable with large orchestral VEP templates.

[nofish]

I can't confirm your bug tracker ticket (at least not if I'm honest ) because it's VEP specific which I don't have, but I'll give this FR a +1 in support also for thread I started and you linked to (as it's presumably the same issue).

[Soli Deo Gloria]

I´ve just posted in the bug report a comment about a setting which, at least here, solves the playback delay problem with VE Pro. (I´ve tested it repeatedly with the same results) If anyone wants to try it out and tell if it had any success with it, read post #9 of this thread :

http://forum.cockos.com/showthread.php?t=156559

[Dstruct]

Preferences/Plugins/VST: Don't flush synthesizer plugins ?


Make sure to disable the option below ("Don't send note offs ...") if you enable it (otherwise you'll get hanging notes)!

[nofish]

Originally Posted by Dstruct

Preferences/Plugins/VST: Don't flush synthesizer plugins ?


Make sure to disable the option below ("Don't send note offs ...") if you enable it (otherwise you'll get hanging notes)!

In my case it's about FX not VSTi's, so I think above option wouldn't help here.

http://forum.cockos.com/showthread.php?t=140690

http://forum.cockos.com/showthread.p...06#post1589606

[EvilDragon]

If you mark VEP as an instrument, then that option will pertain to it.

[Dstruct]

Originally Posted by EvilDragon

If you mark VEP as an instrument, then that option will pertain to it.

I wouldn't do that.

[nirgoren]

Wow can't believe this wasn't added yet! This is also causing issues with S-Gear (Initialization of parameters takes time and introduces a small muted period on playback and rendering).

[casrya]

I had a similar problem recently using STA enhancer 1.51 (CM version).

When rendering an item fx I had a second or two of silence. With the VST3 version it worked after rendering a second time but no workaround for the VST2 version. It sounds like the option to not flush FX might work here as well.

[Anton9]

Devs,

Need this desperately, I have several vst plugins which have a freeze function which allows infinite looping of incoming audio. However as soon as play on REAPER's transport is engaged the plugin buffers get flushed.
Please give us an option to control this if possible.., please.

[mschnell]

Seems like a "silly plugin" problem. They should offer such an option if appropriate. Does the VST creator not have a Feature Request forum ?

(BTW.: when doing a JSFX plugin, you can decide weather or not to re-initialize on "play" in your code.)

-Michael

[nirgoren]

Originally Posted by mschnell

Seems like a "silly plugin" problem. They should offer such an option if appropriate. Does the VST creator not have a Feature Request forum ?

(BTW.: when doing a JSFX plugin, you can decide weather or not to re-initialize on "play" in your code.)

-Michael

Michael, do you mean that you think these issues should be resolved by the developers of the plugin? Does this also apply to VST plugins?

[mschnell]

I suppose the DAW/Plugnin interface functionality is similar for VST and JSFX. The plugin gets a notification that a new "play" is started (with the next block of audio data to be sent/received). It can act on that information as it thinks appropriate.

-Michael

[nirgoren]

Originally Posted by mschnell

I suppose the DAW/Plugnin interface functionality is similar for VST and JSFX. The plugin gets a notification that a new "play" is started (with the next block of audio data to be sent/received). It can act on that information as it thinks appropriate.

-Michael

Do keep in mind that, since it wasn't mentioned before in this thread, this seems to be an issue specific to Reaper and does not appear to happen when using other DAWs. Do you know whether Reaper is doing something different than other DAWs when it comes to informing plugins that a new "play" is started? It appears so..

[nofish]

Yes, in my case at least it seems specific to Reaper and doesn't happen in two other DAWs I checked:

https://forum.cockos.com/showthread....50#post1360450

[mschnell]

Hmm. So this might be not a potential feature but either correct or a bug ?!?!?

-Michael