Noel Borthwick

Recording at a higher depth that the interfaces provides is just padding silence.

You can't assume that necessarily. Its not that abnormal to have an issue which is driver or system related that only shows up with one DAW. Not saying that that is the case here but there is some environmental issue that triggers this that obviously most users never see. So you stop recording, the recording appears and then spontaneously disappears shortly afterwards? If you watch the wave data folder in file explorer while recording, do you see the file get created and then removed shortly after? Another thing to check is your recording drive. Check for disk errors and also check if you have any software (such as one drive) monitoring the folder where audio is recorded. If a program locks the file it can fail recording. Most of the times where people have encountered such issues it has been related to problems like this.

It most certainly doesn't force you to sign in via Facebook. The sign in process is identical for Sonar as well as Cbb or even the Bandlab web for that matter. It prompts you to sign in a very industry standard SSO (single sign on) page where you can sign in using whatever mechanism you chose when you created your BandLab account. This is what I see. You can use your username and password (assuming you create your account that way) or you can use Google, Facebook, Apple, or potentially SMS to sign in.

CbB has not been in development for over 2 years other than receiving a few updates for breaking issues. Please try this in Sonar and if you encounter the issue contact us.

You are free to draw whatever (incorrect) conclusions you may. There is no "campaign" to force anyone to update. You use old OS's at your own risk. We don't have the bandwidth to chase down obscure bugs that only affect certain systems on unsupported OS's. Our dev spent days if not weeks trying to fix issues that ended up being specific to your machine. Old versions of Sonar used completely different Microsoft tools so if it coincidentally worked for you there is nothing we can do to solve that. Upgrade to stick to old versions if you insist on running an old OS.

We cannot indefinitely support breaking changes to older operating systems. Windows 10 and Sonar work perfectly for 99% of users. Beyond that there isn't much we can do to support this. Changes caused by mismatched components or bugs in Windows itself are completely beyond our control.

Unless you have the symbols the function name will be meaningless. If you have a repeatable crash from a recent build of Sonar send me a link to the dump and I can check the cause of the crash. Sometimes dumps don’t give us the full picture…

The sonitus plugins will definitely be supported going forward. We're in fact currently working on some updates to the suite so stay tuned.

You are reading an ancient thread! There is no problem to solve unless you have a project that exhibits the problem. Also note that CbB is not being maintained other than for the most essential issues. If you have a problem in Sonar submit a ticket with a repro project in the Sonar forum.

Exactly. It makes no sense using melodyne in an effects bin in any ARA capable host because it won't use ara at all.

If you have a project in that state that still crashes with the latest version of Sonar then send me a link. The one you sent support doesn’t crash here. If its TTS1 crashing there isn’t anything I can do. There are latent bugs in that plugin that can never be fixed since its not in production and we don’t distribute it anymore.

Uncheck both inputs and outputs for the current driver, and then the spark will become available to select.

Check what driver mode you are using and what the buffer size set in preferences is. WASAPI shared mode introduces a fixed latency. If changing the buffer size has no effect on latency heard, the problem isn’t inside Sonar, its in your monitoring path. This is not a CPU issue so power settings etc will not affect anything. Always test latency with an empty project by adding a single track and input monitoring that without any plugins. Ensure that you are getting the lowest latency there by setting your buffer size accordingly.

Attach a project file so we can look at why this may be happening. Also have you tried this project in the new Cakewalk Sonar?

This was a backend issue that has since been resolved. Should be working now.

This issue should be fixed in the latest release. Can you confirm?

ARA will make it into Next at some point but we can’t give you a timeline. There are some more pressing features that have more general use that are needed prior to that.

The settings should be saved as part of your project. However if you are overriding it with a workspace then it will revert to whatever is in the workspace. To verify don’t use a workspace and save and reload your project,

This isn’t a bug. Feature requests should be posted in the feature requests channel.

I like to fix a bug for Christmas - glad it’s sorted. Merry Christmas Since nobody was able to reproduce it I suspect it’s something within your project. I’ve seen some bizarre issues in the past where certain plugin copy protection schemes were locking project files intermittently. Not impossible that your issue was similar. Auto save is now deferred by a few seconds after the change is detected.

I sent you a build to evaluate.

It would appear that somehow autosave is trying to sneak in and save before the bounce fully completed. What are your autosave settings? I can't say with certainty since I cannot reproduce this, but I've made some changes that may prevent this from happening. Also made some improvements to auto save for next version.

This is your exact problem. Irrespective of whether you use it or not ASIO4All and similar variants like this "built in" driver, cause complex problems and interfere with other drivers loading at startup because they lead to sample rates being changed abnormally. If you don't use those wrapper drivers just find and delete them (or rename them so that Sonar never sees them). You have 3 of them installed - god help you with that! Getting rid of them will also speed up startup of Sonar. In the drivers page you must unselect both inputs and outputs before you can select a different driver.

Alternatively, you can force switch to WASAPI. With Sonar closed open regedit and double click and change the "Core" value listed below to 3d On next restart Sonar will use WASAPI shared mode. If that opens fine, the issue is one of your ASIO drivers that get enumerated at startup. Nothing has changed in this area in 5 years so if the issue just started, its exposing the incompatibility now. We have not supported non-native ASIO drivers for years because they have problems with switching sample rates and interfere with other devices being enumerated as well. Contact your vendor for a native ASIO driver if you aren't sure how to resolve it.

This is an audio driver issue not a redist problem. If you are using a non native asio driver that is your problem. Use WASAPI shared mode and not ASIO mode if the driver hangs when starting Sonar. We don't support ASIO4All and its variants.