Sean Aitken

That's good to know! In this case, the clip export feature is ideal, as it eliminates the silence, and with broadcast WAV, when I go through the import process in Cubase (through the media pool), I can add them back as tracks, with the clips in their original location (and it seems to also preserve the slight overlaps, where I can quickly re-create fades). I'll play with the settings some more on the next project I need to do the export. Maybe one of the devs can take a quick look, or someone can see "oh, this it what you're doing wrong" based on the same exact scenario. Thanks a ton!!

Here's a video demonstrating the issue. I start with the track routing through a stereo buss ("Vocals"), then opening the resulting export in WaveLab, clearly showing the clipping. Then I switch to Main Out, and no clipping. Simple.

I'm not sure that's it. It's the "export clips" preset, which does seem to use the hardware output. I have 28 tracks in this project. Many are sent to a stereo buss, such as "Vocals", "Instruments", "Drums". I was going to create a video, but didn't have the time. The solution I found was to select all tracks, then using "Control+Click" on the output, set all to "Main Mix". Now when I export all clips, they are fine. I just checked, and I have no additional sends on any of the affected tracks. It's like because they are being sent to the stereo BUSS before routing to the main out, that the problem occurs. The routing was simple. Track -> Stereo Buss track (or whatever it's called now) -> Main Out. No additional gain was added, or FX. I triple checked. It seems like a legitimate bug. I'm going to do with with a few projects soon, and will try to create a video showing what's going on. Note: The only reason I'm doing this is because export to OMF crashes Cakewalk, so this was the next best option. I've used Cakewalk / SONAR for many MANY years... I'm still a fan (although I've kinda moved on to Cubase - mainly because it's cross-platform).. As a software engineer myself, this is the type of bug I would want to squash!

I was noticing that when I exported clips from an old project that the resulting WAV was clipping. The original audio on the track had plenty of headroom. After a lot of trial and error, I discovered that it was because I had the track routing through another BUSS (in this case vocals). No additional gain was applied. When I changed the track to route directly to my main outs (audio interface channels 1/2), and then exported clips, the problem was gone. No more clipping. I would expect that if I'm routing to another send, then to mains, that the volume would remain the same. I'll work out more details tomorrow, but it's definitely a problem.

Thanks for the reply! Great detail... good theories on the crash! (I've written many a lines of C/C++ code and spent countless hours in WinDbg, so I appreciate the thoughtfulness. ) Well, TBH, I uninstalled Sonar as I just recently invested heavily in Cubase Pro, and entire NI Komplete and Spitfire BBC Orchestra. I'm loving it (although Cubase friggin' annoys me so far, although it has some clever tools. Just a different animal. Can't say (yet) that it's better than Sonar... I really do like the MIDI editing stuff.. :)) My idea was: Cakewalk by BandLab seems just as powerful as Sonar, as you mentioned, all the plugs work. I spent a good amount of time also rearranging my VST's, keeping the "Cakewalk-only" ones in the Cakewalk folder. I was also trying to reclaim some of my drive space on my SSD to make room for the sample libraries. In hindsight I should have just left it. I wound up ultimately investing into a new 2TB SSD. Problems solved! Regarding the crash, it still happens with the 2020.05 update. I'll send the minidump file to Cakewalk... er... bandLab... Cheers! - Sean

I'm trying to export a rather large project to OMF. When I do so, Cakewalk crashes. Cakewalk Version: 2020.04 (or whatever the latest is) I can send the dump file to someone for further debugging. (I'm not comfortable attaching publicly, as it does contain some private info) According to '!analyze' in WinDbg, this is the culprit: I recently uninstalled Sonar, so I can't test it to see if it's a new or old bug. I'll also look at other export options and maybe start deleting things to find the cause. Also, I was able to successfully export another project, but it only had 5 tracks. This one has 28. Cheers! - Sean

Wow. I spent a lot of time trying to understand what was going on until I found this thread. I love the footnotes. How absurd. It's like "it's okay for our customers not to be able to use stereo effects on mono tracks... They won't care..." Thanks for finding this release note! At least provide a feasible workaround! But dear god... what about existing projects where there's a bunch of tracks with existing plugins.... with precisely tuned settings.. I mean, nah... nobody would ever encounter that. ? Absolutely a massive production issue. I've used Cakewalk and Sonar for many many many years. For this type of regression to occur and for them to let the software ship is a huge quality issue. This can wreck havoc on existing projects and for anyone who isn't familiar with this bug. This type of thing will completely shut down a studio if they rely on Waves plugins for their daily work. This is a very very very common use case!! Would ProTools, Fruity Loops, Logic Pro or Ableton let this garbage ship? I've been working in Ableton more lately and only popped into Cakewalk to check out some older projects. I immediately thought I started losing my mind since I couldn't figure out what I thought I was doing wrong. This is an embarrassing disaster... definitely not good for the reputation. BandLab (or whoever the product owner is)... FIX THIS! Totally unacceptable and unprofessional to leave a bug in like this. Just friggin' open-source Cakewalk/Sonar and let us fix the issue. This is the type of thing I would drop what I'm doing to chase down. Sorry if I sound angry, but this truly is astonishing to still be an issue months later.