• SONAR
  • Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus... (Fixed)
2016/08/27 23:35:44
javahut
Not sure when this problem started, as I haven't been mixing a lot lately...
 
Can anyone verify this behaviour?
 
1) Put a long reverb on a bus, play short snare sample wav file that has a Send to the Bus. Reverb decays okay.
 
2) Put a short processing VST (like EQ, or Channel Tools) before the reverb in the Bus VST chain. Hit play. Reverb decays okay.
 
3) Add another short processing VST after the reverb plugin (like EQ, Channel Tools, Limiter). Reverb decay is now cut off as soon as the WAV or bus send automation stops sending audio to the Bus, it seems.
 
4) Now remove the the 1st VST (the one before the reverb). Again, reverb decays okay.
 
5) Result... unless the reverb is the first or last VST (does this with other long VST processors, like delay, too)... the bus stops passing audio to the output.
 
This is repeatable, on a new Project, one track with individual, short snare WAVs, 1 Send to reverb Bus, Track and Reverb Bus outputting to another Master Bus.
 
Is there some new "feature" setting causing this that I missed? Or is this a bug? Or is it just specific to my system and settings?
 
I'm running latest version of Sonar Platinum x64 on Windows 10, x64 VSTs, i7 5930k, 32GB RAM.
 
Thanks for any help.
2016/08/28 09:27:20
javahut
Update...
 
I am able to reproduce this problem using only Cakewalk/Sonar Platinum plugins, as well. I created a Problem Report ticket, and uploaded a CWB file as an example.
2016/08/28 09:41:35
The Maillard Reaction
This seems like a possible VST3 gating issue.
2016/08/28 09:52:54
javahut
That's what I thought, too. But it happens with VST2 plugins, too. I tried all VST2... same result.
2016/08/28 10:52:35
The Maillard Reaction
It seems like you have been very thoughtful with your diagnostics. I hope you find the cause and a solution is made available.
2016/08/28 11:25:36
Anderton
See if adjusting Clip Tail Duration solves your issue.
 

2016/08/28 11:33:14
brundlefly
This came up in another post recently, and I was unable to reproduce the problem with only one FX (CA-2A was suggested) ahead of the reverb, and nothing after it. But your description seems to be saying it occurs only when the reverb is sandwiched between at least two other plugins so it's neither first nor last; is that right?
2016/08/28 11:54:27
Anderton
For some reason I can't reproduce. The following is the scenario, yes?
 

 
So all I can do is guess at a solution...maybe I have different settings somewhere. In addition to what I mentioned above, try checking "Always Stream Audio Through Effects" under Preferences > Playback and Recording to see if that helps.
2016/08/28 12:22:23
brundlefly
When I checked it, Always Stream didn't make a difference - worked either way. 'Always Stream' is more about what happens when the transport is stopped.
2016/08/28 12:30:10
The Maillard Reaction
I just reproduced the problem on my master bus. When I moved the same FX to a track the reverb tailed off as per my decay settings.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account