Noel Borthwick

There is no problem. The single feedback thread is primarily to collect feedback on the most recently released version. If every issue found was posted in this thread it would be impossible to follow hence we ask for it to be specific only to features released in the latest version or actual regressions. All other questions should go in the main Sonar forum or in the feature request section. If you are a new user and need help about a problem you are encountering it should be posted in the main forum.

If you are unsure then make a new thread - don’t post it here since it creates unneecessary clutter for others to follow.

Just uncheck the realtek asio driver inputs and outputs in preferences and you should be able to select your other audio device.

This looks like a dupe of this issue which has been addressed for the next release. Check the workaround and see if it fixes your issue.

The realtek driver is very problematic so I doubt you will be able to get it working. It does some really expensive callbacks from what I remember. The best bet if you don't have a USB audio interface with an ASIO driver is to use WASAPI

Your settings in Sonar look fine. Did you try arming the track and recording? If you get no signal recorded into the track, then the problem is "out of the box". Obviously check if playback is working in Sonar through the Onyx output first. The first place I would check is the Mackie ASIO control panel (driver settings) and not the Windows sound settings that you are showing since that isn't relevant to ASIO mode in Sonar. Check if you are getting signal from the mic in the Volume / Input Volume tab. If it's a condenser mic you need to power the mic as well.

This is also fixed for next release.

So, because a faulty driver takes down the app its the apps fault? Would you prefer we invest our precious time in building useful features or rewriting our driver stack to avoid problems with broken drivers? Oh, and loading drivers has absolutely nothing to do with the "audio engine". It's the application initialization that loads and checks audio drivers that actually runs into this issue.

Are you absolutely sure you have the latest Focusrite drivers and are using the ASIO driver? Other users have had severe performance issues caused by an older version of the driver. See this thread. Also, if the app is disappearing from task manager it means that the process has been shut down by Windows due to a crash. I can't understand how it can be not in task manager and still visible on screen. Please post a video showing the problem in detail and also post pictures of your audio configuration in preferences. Its not possible to diagnose such issues remotely without extra information.

This is indeed a small regression and will be fixed in the next release. See this thread where its already reported.

Also, this thread is to report issues that are specific to THIS release. Please refrain from using this thread as a general bit bucket for random reports. Make separate threads if you have a different problem.

Its fixed for the next update. It was just a simple issue with the cursor hit point not being authored properly.

It was a regression caused by another bug fix for a more severe start up problem. For now if you see this issue, you can circumvent it by closing the start screen once after the app opens, then after that you can reopen it and the project should open without any issues.

So after loading completes, Sonar itself disappears? Can you post a video showing this. Also please clarify, are you loading your project via the start screen? If so, please try these steps to open your project: Launch Sonar. Now close start screen Reopen Start screen Now open your project.

Have you not seen the statement here? This has been discussed in many threads so there is no need to rehash it again.

It includes all the BandLab services yes.

I sent you a follow up PM

This may help you get started. Automation can be added to change track parameters like volume or pan, or actual effects parameters. https://help.cakewalk.com/hc/en-us/articles/47602806480665-Automation-in-Cakewalk-Sonar

Have you updated to our latest release which is 31.08.0.035?

@Art Penner is this reproducible for you consistently? I.e when you open Sonar the first project you open has tracks minimized? If so please contact me and we can try and troubleshoot it further. Anyone who has this issue, it would be useful to record a short video that shows the the sequence of operations from when you open Sonar to reproducing the issue.

Anyone experiencing problems and using Focusrite interfaces please first ensure that you contact their support for the newest drivers since there are known problems as discussed in this thread,

Glad you could get it sorted. Can you share what focusrite told you? Are their new drivers working? It's frustrating to go through this when all you want to do is make music so I get it. The DAW gets blamed for pretty much any problem known to man but the fact of the matter is that all it takes is one external moving part to fail and the entire system fails. 😀 A worse situation applies to plugins. These days some plugins are written by inexperienced developers who test one use case and call it a day. Plugins can cause crashes or bizarre behavior that is next to impossible to root cause. I've seen recording fail due to a plug-in interfering with the files on the system if you can believe that.

Not today but it is on the roadmap.

2 is the most likely culprit. There have been other reports of instability with their recent drivers. I recommend that you report it to them.

@Pathfinder I looked at your dump file. There was only one unique one. You uploaded the same file twice. I can see a lot of data since this is a full dump, so the full state is available. The dump file shows that you are loading the project file "H:\Audio_CW\Sittin on Dock of the Bay\Dock of the Bay_EXT-2023.cwp". The actual project file load succeeded with no issue. After the project loaded the then tries to initialize the engine to the project format. In doing so the engine tried to set your Audio driver to 48000 KHz which is the project sample rate. It calls the ASIO driver to do this via ASIOSetSampleRate. At that point the driver hangs. There is nothing else going on in Sonar so this is 100% a driver issue. If I were to guess, its most likely caused by the driver being in conflict with the sample rate due to something else using your audio device at a different sample rate. Besides that I have no further info about the hang since its not Sonar hanging. If the issue persists, you will have to talk to Focusrite. Ideally send them the same dump if their support has no idea why.