Old 08-10-2020, 12:20 AM   #1
mkmkm7
Human being with feelings
 
Join Date: Aug 2020
Posts: 1
Default Flush FX Buffer on Bypass

At this time, when you automate the Bypass parameter of any plugin, its buffer does not get cleared. For example, if you were to automate a reverb on>off>on again, it would keep playing the reverb tail right from where it stopped before being turned off. Why is this important? Because it prevents us from using neat tricks like this: https://youtu.be/ZcICh7UsPuU?t=127

I had tested 3 other daws (Ableton Live, FL, Cubase) and Reaper is the only one exhibiting this behavior when automating Bypass. I love this DAW to death and it would be fantastic if you could either change this behavior on default, or give us an option to flush FX buffers on bypass somewhere in Preferences.

Much thanks, and I hope you take this into consideration.
mkmkm7 is offline   Reply With Quote
Old 08-13-2020, 12:13 AM   #2
CH FR
Human being with feelings
 
Join Date: Aug 2020
Posts: 4
Default

This could be a very useful feature if integrated to reaper's default behavior, and I doubt it would cause issues on any existing projects. I think this behavior would improve reaper for the best
CH FR is offline   Reply With Quote
Old 08-13-2020, 05:07 AM   #3
FarfadetFarfelu
Human being with feelings
 
Join Date: Aug 2009
Posts: 51
Default

+1 Absolutely, very useful and important when using Reaper as a live host for FX.
FarfadetFarfelu is offline   Reply With Quote
Old 07-21-2021, 10:34 PM   #4
boolin
Human being with feelings
 
Join Date: Oct 2018
Posts: 237
Default

I was attempting to achieve a similar goal and came across this thread.

I had hoped that there would be a suitable command that could be used with an action marker. There does not appear to be.

I found the SWS actions to 'flush fx on stop' and to 'flush when looping'. These don't solve the problem of flushing (one or multiple) fx _during_ playback.

+1 for an option to flush FX during playback, ideally

* per VST
* accessible through automation

i suspect that a new command would make more sense than retooling bypass, but that isn't my wheelhouse.

As always, thank you Reaper devs and community.
boolin is online now   Reply With Quote
Old 07-21-2021, 11:57 PM   #5
Phazma
Human being with feelings
 
Join Date: Jun 2019
Posts: 2,872
Default

+1 for the option but also keep the current behaviour. The current behavior can be useful for example if you have a long reverb tail and want to have interruptions but keep having it fade out without retriggering it.
Phazma is offline   Reply With Quote
Old 07-22-2021, 11:09 PM   #6
deeb
Human being with feelings
 
deeb's Avatar
 
Join Date: Feb 2017
Posts: 4,813
Default

Yeah , this has been asked before, it would be more flexible since Current behaviour could still be done by automating wet 0 or 100%, and we could have a new musical/sound design approach which makes more sense.
__________________
🙏🏻
deeb is online now   Reply With Quote
Old 09-09-2021, 06:58 AM   #7
boolin
Human being with feelings
 
Join Date: Oct 2018
Posts: 237
Default

Automating between Wet 0% and Wet 100% doesn't quite satisfy the objective here.

It doesn't flush the VST buffer. Switching from Wet 0% to Wet 100% returns the VST with buffer intact (however full it is at the time this automation switch occurs).

This request is to flush the VST buffer entirely on command and to make this feature automatable.
boolin is online now   Reply With Quote
Old 09-09-2021, 07:29 AM   #8
pepe44
Human being with feelings
 
pepe44's Avatar
 
Join Date: Jul 2013
Location: Portugal
Posts: 1,827
Default

There is an option in Audio / Playback / Flush FX on Stop. I think there should be one saying Flush FX on bypass. easy to implement ??
pepe44 is offline   Reply With Quote
Old 09-09-2021, 09:45 AM   #9
deeb
Human being with feelings
 
deeb's Avatar
 
Join Date: Feb 2017
Posts: 4,813
Default

Quote:
Originally Posted by pepe44 View Post
There is an option in Audio / Playback / Flush FX on Stop.
i think this should be default behaviour and probably no need of option. Maybe someone can shine and clarify why current behaviour is useful?
__________________
🙏🏻
deeb is online now   Reply With Quote
Old 09-09-2021, 10:03 AM   #10
pepe44
Human being with feelings
 
pepe44's Avatar
 
Join Date: Jul 2013
Location: Portugal
Posts: 1,827
Default

Quote:
Originally Posted by deeb View Post
i think this should be default behaviour and probably no need of option. Maybe someone can shine and clarify why current behaviour is useful?
I might be wrong but since its a long time known issue i guess it would take deep dive in audio engine to solve it no?
pepe44 is offline   Reply With Quote
Old 09-09-2021, 11:20 AM   #11
deeb
Human being with feelings
 
deeb's Avatar
 
Join Date: Feb 2017
Posts: 4,813
Default

Quote:
Originally Posted by pepe44 View Post
I might be wrong but since its a long time known issue i guess it would take deep dive in audio engine to solve it no?
only they know
__________________
🙏🏻
deeb is online now   Reply With Quote
Old 09-09-2021, 03:46 PM   #12
pepe44
Human being with feelings
 
pepe44's Avatar
 
Join Date: Jul 2013
Location: Portugal
Posts: 1,827
Default

Quote:
Originally Posted by deeb View Post
only they know
Yep eheh
pepe44 is offline   Reply With Quote
Old 09-18-2021, 10:18 AM   #13
jopatius
Human being with feelings
 
jopatius's Avatar
 
Join Date: Aug 2008
Location: Finland
Posts: 509
Default

+1 for the option also from me.

(I encountered this problem now with ReaDelay when automating enable/disable for it, and as a workaround loaded multiple instances of it into a track, enabling always a previously unused instance and thus "simulating a flushed buffer" kind of - but of course this does not work e.g. in a live setting)
jopatius is offline   Reply With Quote
Old 09-19-2021, 02:06 AM   #14
sockmonkey72
Human being with feelings
 
sockmonkey72's Avatar
 
Join Date: Sep 2021
Location: Berlin
Posts: 1,935
Default

+1 here as well
sockmonkey72 is offline   Reply With Quote
Old 10-04-2021, 10:52 PM   #15
Antoine Portes
Human being with feelings
 
Antoine Portes's Avatar
 
Join Date: Jan 2021
Location: the sweet spot
Posts: 22
Default

+1

Every time I automate a plugin's bypass, I have to also automate the volume before and after to mute what remained in the buffer. With this option implemented, I would work 3 times faster.
__________________
"-What a terrible joke!
-But it's my only line..."
And now for some self-promotion: website | bandcamp | spotify
Antoine Portes is offline   Reply With Quote
Old 10-05-2022, 07:32 PM   #16
abnegative
Human being with feelings
 
Join Date: Sep 2022
Posts: 222
Default

+1
I would be very grateful for this.
abnegative is offline   Reply With Quote
Old 10-05-2022, 11:24 PM   #17
FapFilter
Human being with feelings
 
Join Date: Dec 2018
Posts: 47
Default

+5
FapFilter is offline   Reply With Quote
Old 10-06-2022, 05:51 AM   #18
deeb
Human being with feelings
 
deeb's Avatar
 
Join Date: Feb 2017
Posts: 4,813
Default

Yes please yes please
__________________
🙏🏻
deeb is online now   Reply With Quote
Old 12-01-2023, 01:02 PM   #19
Phantasmogenesis
Human being with feelings
 
Join Date: Jun 2022
Posts: 1
Default

+1, this and/or the ability to manually flush FX buffers for a track via the ReaScript API would be very helpful
Phantasmogenesis is offline   Reply With Quote
Old 12-01-2023, 01:04 PM   #20
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,750
Default

As of v7.0, VST and CLAP plugin buffers are flushed when bypassing.
schwa is offline   Reply With Quote
Old 12-01-2023, 03:16 PM   #21
abnegative
Human being with feelings
 
Join Date: Sep 2022
Posts: 222
Default

Quote:
Originally Posted by schwa View Post
As of v7.0, VST and CLAP plugin buffers are flushed when bypassing.
hmmm... I just tested Arturia EFX Fragments and the sound picked up where it left off after bypassing then unbypassing. To check if the plugin was at fault, I tried the same in FL Studio and it worked as expected (complete silence after unbypassing).

In REAPER, expected behavior appears plugin-dependent, whereas in FL Studio it works every time. I wonder what the difference is??
abnegative is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 10:23 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.