Noel Borthwick

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.