Craig Reeves

It's been really bad with regard to the crashes. Just about any and everything will make this DAW crash, particular copying and pasting large amounts of clips. It is a productivity killer. Significantly less table than Cakewalk by Bandlab. I have no idea what they did to this but these recent updates have made this DAW so much less stable. Even the simplest things will cause the DAW to crash. I literally am at a standstill in a project because I cannot copy and paste anything without it crashing. It is not justifiable in my view that a DAW so much more unstable than its competition should be priced the same or more than its competition. It's just broken. Simple and plain. Held to gether by duct-tape and bubble-gum. Bandlab just isn't putting enough money into the development to give us a DAW that works. The devs they have I'm sure are doing the best they can so it's not their fault. Check this video out. This is a simple copy and paste and Cakewalk crashes EVERY TIME I try to perform this simple task. This is problematic. And the worst thing is that it's difficult to report bugs because the crashes are random and unpredictable. A lot of the times moving clips, copying, and pasting clips is something Cakewalk has trouble with. They seriously need to tighten up the code in that area but the thing is, it doesn't happen all the time. Again it's fussy and unpredictable so you just have to be saving all the time. This is not the case in any other DAW but Cakewalk sadly. It's just way, way behind. Again, I blame Bandlab for just not putting enough money into it. It's possible it's just a lot of old code. I believe Cakewalk will eventually face the same fate as Finale. I've been using Cakewalk for over 25 years so I say all of this with great sadness.

With the new vector-based UI, does this mean vertical zoom could show more tracks without scrolling? I've always envied how Logic, PT, Cubase, Studio One and all the other major DAWs could vertical zoom so much you could literally see 100+ tracks without scrolling. This would really help with people who do film scoring where they're working with templates of 200+ tracks or more.

BIG TIP: When using Opus, make sure to choose as your MIDI Input MIDI Ch. 1 of the MIDI controller. Leaving it at MIDI Omni will cause your MIDI to triple-record.

That did it! I will send over the crash dump to Cakewalk's support team! Thanks!

No dump was produced in either that folder or the Plugins subfolder.

IK Hammond B-3X does not open in Cakewalk by Bandlab. Opening it crashes the program. Anyone else able to reproduce this? It opens fine in Ableton and Studio One.

I've requested this before but the only MIDI legato is by running CAL, which is buggy and doesn't work very well. It's one of those features I really miss when coming back from Ableton.

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.

Which is exactly why I post videos on how to reproduce the bug. Notice that I never actually say that I am CERTAIN it is a bug. That's the whole point of providing instructions on how to reproduce the error. Because if others are unable to reproduce the bug, then it is something local to my system or user error that is the cause. For instance, the bug with quick-group latch automation I have tried on four different systems and multiple different versions of Cakewalk. I was able to reproduce the problem. But you cannot dismiss the problem I'm having as specific to something I'm doing wrong until it is demonstrated that others cannot reproduce the error. And as far as finding out why a bug exists, you don't do that until you have tried reproducing the error. And I honestly can't believe you're defending @bdickens either. Dismissing someone expressing legitimate concerns about Cakewalk as "bitching" is toxic. And he was "getting at" anything but being an a-hole. I've seen some of his past posts. He's like that toward others, not just me.

Yes I have. Where do you think those videos came from? I didn't just make them today. Had you actually watched them you'd know they were dated in the past. And as I'm sure you already know, anyone could watch those videos and reproduce the bugs, whether the person is a developer or not.

I provide videos specifically showing how to reproduce the bugs. I really do not know how much clearer I can be in that regard because I'm literally showing you all step by step how to reproduce the bugs. I can't do anything about it if you all choose not to watch them.