Audio effects applied to a track are cut off incorrectly

I have a reverb applied to an audio track. Unfortunately, it stops ringing out when an event on the track ends and there's no event abutting the end of it. So if you're trying to use reverb to make cut-off sounds fade away nicely... it doesn't work.

This behavior is incorrect, because you've applied the effect to the whole track, not to an individual event on it.

I made a video to show how to do it.

For Clip-based Reverb plugins, the plugin window's Additional Options (3 dots) menu provides an “Enable Bounce Tail” option in addition to the “Bounce Audio Effect” option. A "Tail Threshold" parameter is also exposed.

For Track-based effects consider an effects (Aux) Buss and automation rather than applying the reverb plugin on the channel.

Thanks for those replies, guys.

That video, unless I'm missing something, simply shows it working correctly. I don't get that result.

And the regular Fairlight reverb doesn't have any "bounce" or "tail" options in the three-dot menu. It only contains "Lock plugin window" and "Preset manager."

Beyond that, I don't think it should be an option that you have to go hunting for. If you apply an effect to the entire track, that's what it should act on. After all, the reverb continues to decay even after you hit Stop! Why would it instantly stop functioning because an event on the track ends?

Why would it instantly stop functioning because an event on the track ends?

It doesn't. The Fairlight track-based reverb only stops at the LAST event in the timeline ON THE EDIT PAGE. If the audio clip is the last clip in the timeline, the reverb will stop when playback stops on the Edit page. On the Fairlight page the reverb tail plays correctly because the playback continues after the last timeline clip.

If you are not seeing this behaviour, you are probably using an older version of Resolve, because the reverb tail solution I posted was for R16.0 and this issue was addressed in the last R16 version.

Also the 3 dots menu Reynaud mentioned is for CLIP based reverb not Fairlight TRACK MIXER reverb insert.

Screen Shot 2021-02-18 at 10.53.13 am.png (353.6 KiB) Viewed 2416 times

Thanks for the reply. I was using version 17, beta 9.

Interesting, I can't reproduce it now. At the time I encountered it, I sliced a vocal performance up and disabled some events to mute some verses. I found that doing so cut off the reverb. However, it didn't do that when I mashed the volume down to -100 instead of disabling the event. But I just tried the disable method, and it still works correctly so I don't know what was going on. It even works OK past the last event on a track.

For Clip-based Reverb plugins...

Are you saying there are plug-ins that can't be used on tracks, but rather only on events/clips? How is that indicated in the effects list? I don't see anything to denote it.

Are you saying there are plug-ins that can't be used on tracks, but rather only on events/clips?

No. Certain plugins (such as Reverbs) provide additional options within the menu when instantiated as Clip-based effects, which are not relevant to Track-based instances.

No. Certain plugins (such as Reverbs) provide additional options within the menu when instantiated as Clip-based effects, which are not relevant to Track-based instances.

Thanks. That's another example of why it's good to grey controls or menu items out when they're not applicable, instead of just making them disappear; if they're always present, you learn that they exist and where they are.