javahut
Max Output Level: -83 dBFS
- Total Posts : 361
- Joined: 2005/11/25 19:35:23
- Status: offline
Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus... (Fixed)
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.
post edited by javahut - 2016/10/26 07:24:15
|
javahut
Max Output Level: -83 dBFS
- Total Posts : 361
- Joined: 2005/11/25 19:35:23
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 09:27:20
(permalink)
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.
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 09:41:35
(permalink)
This seems like a possible VST3 gating issue.
|
javahut
Max Output Level: -83 dBFS
- Total Posts : 361
- Joined: 2005/11/25 19:35:23
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 09:52:54
(permalink)
That's what I thought, too. But it happens with VST2 plugins, too. I tried all VST2... same result.
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 10:52:35
(permalink)
It seems like you have been very thoughtful with your diagnostics. I hope you find the cause and a solution is made available.
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 11:25:36
(permalink)
See if adjusting Clip Tail Duration solves your issue.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 11:33:14
(permalink)
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?
post edited by brundlefly - 2016/08/28 12:40:12
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 11:54:27
(permalink)
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.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 12:22:23
(permalink)
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.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 12:30:10
(permalink)
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.
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 12:43:15
(permalink)
I just closed SONAR, relaunched, instantiated the 3 FX, and tried to reproduce the cut off again and everything worked great. It does not cut off like it did a few moment before.
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 12:55:48
(permalink)
I just tried a third time and found that the reverb tail playback was broken again. In this case, I deleted the EFX in the tracks feeding the bus and noticed immediately after that my bus no longer plays the bus reverb decay. I thought, "a-hah, I'll put some EFX back on the source tracks"... so I did, but that didn't fix it. I saved the broken project, closed SONAR, relaunched, and the bus reverb's decay is still cut off at the end of the source track's clips. I am not sure why it is happening, but I do know that this would drive me crazy if I had Platinum installed on my DAW.
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 12:59:37
(permalink)
I just relaunched SONAR, and opened the broken project again. I deleted one of the two EQ EFX I was sandwiching the Reverb with. As soon as I hit "Delete" the lost reverb tail played back for me.
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 13:21:17
(permalink)
What reverb plugin are you using.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 13:27:21
(permalink)
Hi brundlefly, FabFilter Q2 > Valhalla Room > FabFilter Q2
x64 VST2
|
javahut
Max Output Level: -83 dBFS
- Total Posts : 361
- Joined: 2005/11/25 19:35:23
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 14:33:53
(permalink)
Craig... yes, that looks like similar to what I am doing and what I described that's causing the problem. "Always stream audio through effects..." is on. Changing the tail length setting to 10 seconds didn't do anything. Stretching the tail of a short clip does not fix the problem. However, just to check... I set up a long clip on a 2nd track with a send to the reverb bus, so that it starts just before the 1st clip ends, then turned down the 2nd track to barely audible... and the reverb tail works for the first track... I'm guessing since audio continues to stream into the bus from the 2nd track. However, that doesn't explain why putting a short or no decay effect before and after the reverb causes the problem in any case, and removing either of those short decay effects, the reverb tail plays fine. I've reproduced the problem on my system using quite a few different plug-ins, including a long repeat delay... the delay also stops outputting once the input to the bus stops. The CWB file I sent to Cakewalk that has the problem on my system, has a bus containing Channel Tools > Breverb 2 Cakewalk > Boost 11. The bus stops output when either (1) the short audio WAV file ends on the track, or (2) on a long track... say, just after a snare hit... the bus send is automated to go to zero output... the bus output audio stops as soon as the bus send track automation goes to zero output. Quite annoying, when you've been working on multiple projects, that are fairly busy... and you've thought for a while (weeks) things weren't sounding right... and just now realize... it's because some of the reverb/delay buses are no longer working correctly. And I really have no idea when exactly it started happening. Maybe when Aux Tracks and Patch Points were introduced? Or maybe earlier even. No idea, really.
post edited by javahut - 2016/08/28 14:55:50
|
javahut
Max Output Level: -83 dBFS
- Total Posts : 361
- Joined: 2005/11/25 19:35:23
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 16:37:59
(permalink)
Too weird... not all effects cause the problem. And some cure the problem. For instance... I put in Channel Tools > Audio Damage Dubstation 1.5 > Boost 11... bus audio is cut off when clip ends. Same chain... but put in NI Supercharger GT before the other effects... tails start working again. I also have noticed so far the Channel Tools, Boost 11 before and after cause bus output to be cut off... and Sonalksis FreeG causes it. Channel Tools > DubStation 1.5 > A.O.M. Invisible Limiter causes bus cutoff... reversing the order does not. Just when you think Cakewalk and Sonar are getting their act together. Makes you wonder how many other processes within Sonar don't work correctly all the time. Processes that might be even harder to detect not working correctly than this relatively easy one. Maybe I should go back to learning Reaper again.
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 16:57:02
(permalink)
Yes, what I was trying to explain about the symptoms I saw today is that simply adding or deleting anything from any of the EFX bins seemed capable of triggering or fixing the cut of reverb tail problem. It may be specific EFX or it may be how SONAR handles any EFX. FWIW I have been testing with an extra long 20 second reverb decay so the missing tail issue seems plainly obvious when it occurs.
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 17:27:24
(permalink)
☄ Helpfulby kevo 2016/09/25 11:28:20
I wonder if it relates to a mix of VST2 and VST3 plug-ins, where the VST3 versions turn off if there's no input. Might they be checking whether there's audio at the track input, not their input? There has to be some rational explanation or way to reproduce every time. I sandwiched a reverb (the Sonitus) between two Channel Tools and there wasn't a problem. Maybe a different reverb would cause an issue?
|
javahut
Max Output Level: -83 dBFS
- Total Posts : 361
- Joined: 2005/11/25 19:35:23
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 18:27:34
(permalink)
I tried substituting either all VST2 or all VST3, to try to make sure any kind of mismatch between the way they turn the input on or off wasn't the problem. I reproduced the problem with all VST2 and all VST3. But I wouldn't doubt that it has something to do with the way Sonar is handling a dynamic input to the VSTs on the bus. It just shouldn't have anything to do with shutting off the output of the bus based on receiving an input... ever. The output of the bus should only be shut off based on if any audio is being generated anywhere before the output. And, in the reverb case, for instance,... it was definitely outputting the reverb effect until the end of the WAV clip (or bus send automation, as the case may be). It's just that the bus output stops immediately when the WAV file ends. I dunno. WAY over my head, as far as the programming of it all goes.
|
javahut
Max Output Level: -83 dBFS
- Total Posts : 361
- Joined: 2005/11/25 19:35:23
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 18:30:49
(permalink)
But in every case, it seemed to me specific plugins in a specific order caused the problem... every time. It wasn't as if the same plugins and order might have a different result each time. Each specific plugin, and specific order the plugins were in, produced the same result every time I tried them.
|
Anderton
Max Output Level: 0 dBFS
- Total Posts : 14070
- Joined: 2003/11/06 14:02:03
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/28 19:13:17
(permalink)
Try taking a combination that didn't work in a bus and try it in an Aux track or an audio track. I'd try it myself but even using Channel Tools and Boost 11, I'm not able to duplicate. Another thought: What happens if you double the latency (e.g., 128 to 256 samples)? I'm not saying that's the problem, but it could give a clue from a diagnostic standpoint. Also, I assume you're not using ASIO4ALL...right?
|
Noel Borthwick [Cakewalk]
Cakewalk Staff
- Total Posts : 6475
- Joined: 2003/11/03 17:22:50
- Location: Boston, MA, USA
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/29 08:11:52
(permalink)
javahut The CWB file I sent to Cakewalk that has the problem on my system, has a bus containing Channel Tools > Breverb 2 Cakewalk > Boost 11.
Can you list the case number for this issue that you logged?
|
javahut
Max Output Level: -83 dBFS
- Total Posts : 361
- Joined: 2005/11/25 19:35:23
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/29 08:34:23
(permalink)
|
The Maillard Reaction
Max Output Level: 0 dBFS
- Total Posts : 31918
- Joined: 2004/07/09 20:02:20
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/29 12:08:08
(permalink)
Hi Noel, I have a test project that replicates the same problem. You can turn the master bus' reverb decay on and off by activating an instance of Boost 11 in one of the source tracks. I can send a .bun if it is helpful.
|
javahut
Max Output Level: -83 dBFS
- Total Posts : 361
- Joined: 2005/11/25 19:35:23
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/31 14:16:08
(permalink)
nothing yet? I guess not. bug report still says it's not been looked at by cakewalk staff. has cakewalk been able to duplicate the problem? or tried yet?
thanks.
|
javahut
Max Output Level: -83 dBFS
- Total Posts : 361
- Joined: 2005/11/25 19:35:23
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/08/31 19:48:15
(permalink)
FWIW... same series of plugins inserted directly in the track's effects bin also cuts off the tail of any effect that lasts longer than the clip. Don't know what's going on with this... but I wish they'd get it fixed... like... in a hurry. Or if it's not a bug... let me frickin' know so I can start looking elsewhere for the problem.
|
javahut
Max Output Level: -83 dBFS
- Total Posts : 361
- Joined: 2005/11/25 19:35:23
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/09/01 17:26:18
(permalink)
Day 4 of nothing... yes/no?... bug?... system problem?... anything?... hello. hello. is this thing on?
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/09/01 20:24:38
(permalink)
At best I think it must be a project/plug-in/system/config-specific bug, as I still cannot reproduce an issue with any of the reverbs bundled with SONAR. If you want to share a copy of a demo project using only bundled plugins somewhere, I'll check it out.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
javahut
Max Output Level: -83 dBFS
- Total Posts : 361
- Joined: 2005/11/25 19:35:23
- Status: offline
Re: Bug? - 1st and Last Plug-in in Bus Determines Length of Processed Bus Audio Output?
2016/09/02 14:37:54
(permalink)
brundleflyAt best I think it must be a project/plug-in/system/config-specific bug, as I still cannot reproduce an issue with any of the reverbs bundled with SONAR. If you want to share a copy of a demo project using only bundled plugins somewhere, I'll check it out. Thanks brundlefly. Sent you a PM with link to the CWB file.
|