Hi  Randall,
 
I got your PM and checked out the project. I was able to repro the problem, and after some poking around, it seems to be related specifically to having Channel Tools and/or CA-2A directly in front of the Reverb. I couldn't repro with any other single plugin in front of the reverb, and having any other plugin in between either of those two and the reverb also seemed to work.
 
But I felt that the results were a little unpredictable, depending on what order the FX were inserted/enabled/disabled, and in which combinations, which may be why I couldn't initially repro the problem.
 
In any case, assuming the Bakers are able to repro with your project right out of the box as I was, they should be able to get to the bottom of it.
 

As I have been saying, I was able to reproduce the problem about 30 seconds after creating a test project and have subsequently come to realize that the cause seems unpredictable while somehow being related to simply making use of items in the fx bins.

Caa2
As I have been saying, I was able to reproduce the problem about 30 seconds after reading the op and have subsequently come to realize that the cause seems unpredictable while somehow being related to simply making use of items in the fx bins.

Yes, same here. After playing a little more with it... the same effects that cause the problem in the track to bus send, also cause it in an Aux track, and also simply by putting the affected effects (pun intended) in the FX bin on a track.
 
Wish/hope this gets attention and a fix soon!!! It seems like a relatively serious problem for a full featured DAW to have.

Just for the record, the reason i was not able to repro originally was that I misinterpreted this:
 

javahut
I also have noticed so far the Channel Tools, Boost 11 before and after cause bus output to be cut off...

I thought I was supposed to put both Channel Tools and Boost 11 before the reverb; that's what's in my original test project, and that will not repro the problem.

So... problem still not fixed with the latest update. Too soon for a fix? Too hard to fix? Seems like such a simple issue for a purportedly premier DAW to have, yet zero acknowledgement from Cakewalk that it even exists. Support ticket still indicates "New", so apparently hasn't been even looked at by Cakewalk yet.

It hasn't been investigated yet. We'll escalate it for the next release. So your test project only uses Cakewalk plugins?

Noel Borthwick [Cakewalk]
It hasn't been investigated yet. We'll escalate it for the next release. So your test project only uses Cakewalk plugins?

Yes, that is correct. Thanks.

We fixed this issue today. Its a symptom of the zero buffer optimizations for VST plugins that we introduced recently.
The fix will be in the October release since its too late for regression testing for this release. However if you are interested in testing this fix earlier send me a note and I'll try and get you a build.

Noel Borthwick [Cakewalk]
We fixed this issue today. Its a symptom of the zero buffer optimizations for VST plugins that we introduced recently.
The fix will be in the October release since its too late for regression testing for this release. However if you are interested in testing this fix earlier send me a note and I'll try and get you a build.

Great!
 
For the projects I'm working currently, now that I know about the bug, I've found a workaround to get by. If you guys NEED testing, be glad to help. But I trust you guys know your stuff better than I do, and know you have it fixed. So I can wait until the October release for the fix for now.
 
Glad you guys were able to find it relatively quickly, though! Thanks.
 

Happy to report... this bug quashed in latest Sonar Platinum version 2016.10!