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.

Thanks, Neil. Issue was completely resolved in this latest release (2022.02 build 029)!

So sorry about that! I'll be sure to test out the newest one! Thanks for the quick response!

However, my prior complaint stands. This new Early Release messes up Auto-tune Pro, causing a distortion effect on stereo tracks. I just rolled back to the current release and the problem is gone. So this is indeed a bug in this Early Release.

Literally just found it now right when you posted. Thanks!

*sigh* My God I'm having a lot of problems I really don't have time for. OK, so I uninstalled Cakewalk by Bandlab and now I can't re-install it, because my Bandlab Assistant under Cakewalk keeps saying "Update" and not "Install". But I uninstalled Cakewalk. So I click "Update" and it just sits there forever at "Downloading (0/0)". Is anybody else experiencing this issue? It seems that Bandlab Assistant still thinks Cakewalk by Bandlab is installed on my computer when it isn't. I restarted my computer and I'm running into the same issue. I uninstalled and then re-installed Bandlab Assistant. Same issue. I can't possibly be the only one having this issue.

Is anybody else's Bandlab Assistant screwing up? Is it down or something? I uninstalled Cakewalk to re-install the current release (sorry but this Early Release ain't it) but now it's not letting me install Cakewalk at all. It's stuck at 0/0 Downloading.

Show-stopping bug, here. Auto-tune Pro on a Stereo track does not work properly anymore. It creates a weird chorus effect or it distorts the sound entirely.

I do want to be clear I still think Cakewalk is awesome and I love it. Trust me, I have FAR more scathing things to say on the Ableton forum, and they never listen to me...

Still my favorite DAW but at this point I've just resigned to the fact this will always be a buggy and crash-prone DAW. Pro tip: ALWAYS have auto-save ON, saving at least every 2 minutes. It crashes, far, far more often than any other DAW I use. Ableton for instance, it's like night and day as far as stability. Cakewalk crashes at least once or twice every time I use it. Something as simple as moving or transposing an audio clip can cause it to randomly hang or crash for no apparent reason. It's never really the same predictable thing (transposing audio makes it crash A LOT). It's just a capricious, rickety, buggy program and always will be. I would imagine it's probably built on a lot of bad and buggy code and it would take way too much time to rewrite a lot of it. It's still a very good program, but people just have to know that going in. ALWAYS have Auto-save on. Although to be fair Cakewalk will sometimes crash while trying to Auto-save, which at our studio we call "Cakewalk tripping and falling again". That said, I know and appreciate the fact the Bakers are trying very hard to make the program more stable.

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.