Craig Reeves

I have a feeling it may be Ozone, because it just seems that once I started using it, I began having problems when I leave the 64-bit Engine checked.

That's certainly within the realm of possibility. I have 128 GB of RAM, which is the maximum amount of RAM my motherboard can handle. Although I don't know exactly how FAST that RAM is.

It looks like it was the 64-bit Engine after all that was the culprit. I believe that Ozone 9 may have its own audio processing that it does that doesn't jive with the 64-bit engine. As soon as I unchecked it, my projects are bouncing perfectly. If anyone else has this problem, we'll now know what to tell them. Thanks guys!

I'll try to reproduce the bug when I get home.

I suspect the issue is related to a plugin, possibly Ozone 9 but I can't be certain of that. I'll try to troubleshoot some more once I get some downtime.

I thought that was the case too, so I turned the master bus down to where there was no digital clipping (there wasn't to begin with) and the problem still persisted. I finally got a clean bounce but I had to slow-bounce along with the audio bounce.

Quick question. Does anybody else have issues sometimes with bounced audio containing pops and artifacts, particularly on big transients? I've noticed this problem consistently with a lot of projects but it doesn't happen all the time so it's not the easiest problem to reproduce. Anybody else having this issue or had it before? Pops, clicks and artifacts tend to persist whether I slow-bounce or fast-bounce.

Will do!

I'm aware. But Legato.cal doesn't work very well and very often fails to do what it is supposed to do.

LOL that last line. Yeah I feel you. There have been times where I have unfairly blamed Cakewalk myself, sometimes on here for all to see. Anytime that happens, I will usually make sure to indicate where I'm wrong. For instance, I was under the impression that Cakewalk's audio engine was slow because while using it, I found my CPU usage was higher than it should have been for a similar project I had open in Ableton Live. Well, it turns out what was slowing things down was that I had Streamlabs open and forgot to close it. As soon as I did, Cakewalk ran perfectly.

Basically, a process that achieves the same functionality as the Legato.cal script, but actually works on a consistent basis. Pretty common in other DAWs and I don't believe would be a difficult feature to add. I use Legato all the time and I'm sure others do as well. Hell, we have Retrograde, I think we can include Legato, lol.

I've never been told by any of the staff people on this forum that my videos are unclear. My videos aren't unclear to the people that actually watch them.

Well people do very often feel like they can't bring up problems with CbB without being vilified for it. It's a serious problem and has been for a long time. As I said I've used Cakewalk for 21 years. I don't need to prove my sincerity to nobody...

There are specific instructions in the videos on how to reproduce the bugs. It isn't just "this isn't working", but I'm pointing out exactly what one can do to bring about the bug himself. Again, you keep mentioning "why" but knowing WHY a bug exists is the developer's job once they go through the code and find the bug. Everything starts with REPRODUCING the bug, THEN you pinpoint the cause. You're putting the cart before the horse, Tim. And @bdickens was literally accusing me of just coming on here and whining and not reporting bugs, when I literally put videos up SHOWING exactly what the bug is and how to reproduce it. The Bakers have fixed bugs I've reported in this manner and have never had an issue with the way I report bugs. He clearly did not watch the videos, so there is no point in you defending what he said. And it is indeed true that the Bakers have addressed many bugs. I acknowledge that. I wouldn't be here if they just didn't care at all. As I mentioned before, I left other DAWs to come here for a reason and I would not have posted what I did in the OP if I didn't think anyone cared. I have WAY, WAY, WAY more issues with Ableton but you don't see me over there now do you?

As I mentioned before, that's not necessary if the developers can reproduce the error themselves. That means it isn't specific to one's system. Stuff like that only really needs to be done if others can't reproduce the problem. If everybody no matter what system they're on can reproduce the error, that means it doesn't matter what system they're on. Noel nor any of the developers have ever asked me to provide details on my system. But they have asked me to provide instructions on how to reproduce the problem, which I provide. It is generally poor form to ask someone to provide their system specs before even trying to reproduce the problem yourself.