Noel Borthwick

CbB will soon stop accepting new activating but will not stop working tomorrow so dont worry, Regarding the export its almost surely some plugin blocking the export. Have you tried turning off flushing plugin buffers? If Sonar appears hung then capture a dump file and send me a link. There are lots of notes in the FAQ on how to capture a minidump from a hung process. Try setting this value to 0 and retest.

Solved for next release.

The full set of features of Sonar is listed here.

Fixed for next release

Yes its been logged and will be fixed soon. I don’t believe its new to this build. Its a preexisting issue.

Yes I get that while recording with clients you want to be offline to avoid notifications or other distractions - no different from mobile devices. For general use however being online doesn’t cause any issues for the most part these days since network drivers typically are much better. If your machine can go online periodically there is no need to use offline activation since it will acquire a license intermittently as well.

This issue has been fixed for the next update.

It's not so much a nag as an informative message to tell you that online features aren't available. No different from when you attempt to open a web page on a browser with no Internet connection. Sonar is fully functional without an Internet connection besides online features. Please note however that if your machine is permanently offline it will require periodic monthly offline activation to be done. This is no different from how CBB was.

Crash dumps are invaluable to developers to pinpoint the source of crashes. Even when a crash isn't specifically DAW related, the dump file can sometimes provide information on the nature of the problem for further investigation. Cakewalk products automatically intercept crashes and capture a minidump file whenever possible. However, in certain rare circumstances, a dump may not be saved if the crash happened very early in the startup process. If asked by support or development, you can manually capture a crash dump using the Microsoft WinDebug tool using the steps below. Install Windbg from the Windows Store. https://apps.microsoft.com/detail/9PGJGD53TN86 Find the location of your desktop in File explorer and copy the full path to the desktop from file explorer. (you will need this path below). We'll call this path <desktop-path> You can right click on the word "Desktop" and choose "Copy Address" to get the full path to the desktop. It should look something like this "C:\Users\yourname\Desktop" Open Windbg and choose File | Start Debugging | Launch Executable. Navigate to the Sonar exe file and open it. This will load the executable into the Windows debugger. You will typically see a window like this: In Windbg, now press F5 to run Sonar once it has loaded or press the Go button. If it starts running successfully, you will see something like this. After Sonar starts executing you may now perform the steps needed to reproduce your crash (or hang) If the application crashes in WinDbg before the UI opens, then the crash is caused early during startup. If WinDbg intercepts the crash, you will see a message in the WinDbg Command Window indicating the crash. If the app is hung then proceed directly to the next step. Find the command prompt of Windbg at the bottom of the Command window and type this in the command prompt. .dump /ma "<desktop-path>\sonar.dmp" Replace desktop-path with the path you saved in step 2 above. Note the period before the dump command and also the quotes around the path. Press Enter when you are ready. See example below If you entered the command correctly, WinDbg will save a dump file to the specified file on your desktop. Finally, you may now zip the minidump file and send it to Cakewalk

Im not sure what you are doing wrong but the operation as shown in the video works perfectly in Sonar here. New empty project Go to Metronome bus and assign output to New Aux track Arm aux track and start recording Metronome records fine here.

Its much better to default to only having one project open because people forget and open multiple projects when they dont intend to. If you end up opening 10 or 20 large projects then It will start paging to virtual memory and slow things down, potentially cause playback glitches etc.

This is fixed for the next release. It only impacted bus envelopes.

@Andrey_rbk I downloaded your project and cannot reproduce the crash following your steps. I don't have all the plugins however. Your dump file was not very useful unfortunately. It also references an older build. Please retest this in the latest build which is 109. Dump files should always be submitted using the latest version of the Program since the bug could already be fixed. If you can still reproduce it submit a new dump file.

Fixed for next release.

If you log a crash send the ticket number or PM it to me.

We’ll fix it. Thanks for reporting it.

most likely the save as dialog was hidden by something else. There is no way it won't launch - its a simple system dialog.

Its not that we select the device. Sonar enumerates all ASIO devices and these devices cause problems simply as part of being enumerated. Its unfortunately how these wrapper devices work. I think the driver vendors have coded them only testing it with apps like Cubase so never see the problems. That is really the root problem here. The only solution is to not use them for now.

No its not related to "graphics". We'll have to investigate but its likely something related to the mouse tool handling.

My response was to the OP. That error is a generic message and can be caused by different issues. It may not be related to disk space but something failed while writing the file. Did you try writing to a different drive?

I can reproduce this. It does seem to be an unexpected side effect of bypassing the rack. Its losing the assigned edit filter. No envelope data is lost just the selection. We'll investigate it.

@profwacko Can you try this? First keep a backup of your project before saving or save to a new name afterwards. Select the clips you edited and open the AudioSnap palette. Right click on the power button Choose "Clear all audiosnap markers" Now save the project and see if it rectifies the problem You can also select all clips in the project (CTRL-A) and do this operation. NOTE: This will delete all user edited audio snap markers. Sometimes after an error or with many edits the number of audiosnap markers can get huge in the hundreds of thousands. Clearing them like this will allow you to start over.

Its possible. We'll investigate it. If you change the folder to a non Chinese name does it work ok?

I've PMed Mark and Max a build with this fix to try.

Even though we're had a lot of changes to the UI code in Sonar I'd still be surprised if this is an issue thats entirely new to Sonar. I expect Cbb would have similar issues if its indeed Windows shuffling things around.