Noel Borthwick

On 1/31/2025 at 9:02 PM, MIDInco said:

Upon checking the dump file, I found that the function m7_ippsLn_32f_A21 is causing the error.

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…

17 hours ago, Sal Sorice said:

I've been reading some good articles / tutorials about the Sonitus Suite of plugins that are (currently) still included with Sonar. Sound on Sound (SOS) magazine has some great articles. Groove3.com has wonderful content on them included in their (old but still very relevant) Sonar X1, X2, etc. tutorials. And, as always, Mike @Creative Sauce has some fabulous content about them (and about Cakewalk in general).

Of course, there are also many videos about them on Youtube as well.

I'm experimenting with the Sonitus Suite and must admit that, once you take the time to learn them, they are really powerful and sound great - sometimes rivaling other more "sophisticated" plugins.

Since they are DX plugins my question to the Bakers (and I am tagging @Noel Borthwick here, since he may have some good insight) I'm wondering if they will continue to be supported as Sonar evolves. Will they be updated? Will they be converted (or whatever the correct jargon is, as I'm no programmer) to VST? Will they be deprecated?

Comments please!!

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,

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.

52 minutes ago, dougalex said:

I turned off all Audio Drivers in Device Manager.
Rebooted.
Sonar (latest Beta) now asked me to set Audio driver (thankfully, instead of "Not responding")
I set to x32 (all 32 channels) and Sonar (not Cakewalk) seems to be working now.

However, in Cakewalk I do get further but there is a Steinberg I cannot uncheck (I never saw before). AND... it is not in Device manager.
So I have more battling to try get rid of that Steinberg driver and get Cakewalk working.

 

 

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.

Its literally explained in the first post on this thread. 
Generally if running the latest redist installer didn't resolve your issue then you have some other issue. Are you using an ASIO driver like ASIO4All or a variant of that? If so that is likely the cause for your hang.

2 hours ago, Sock Monkey said:

The bummer is that existing members can’t get the deals. 
Example. My membership runs out in July. So that’s another 7 months. 
It would have been nice to have Paid $1 to extend that for an extra 5 months! 

But I see they are only offering to new members only. 

 

Generally, most promo's tend to be for new customer acquisition. Also, it requires a bunch of backend work to implement promo's that extend existing customer subs , so most companies don't do it this way.

On 12/19/2024 at 6:05 AM, Will. said:

Weird prices. 

The countdown said $0.99, but It actually was $99 in the discription when the countdown was on 00:04:00:00 for me about 16 hours ago.

This is not an error. There were different tiers for the BandLab sale and indeed just a few licenses at $0.99 so that's not a typo. If you had bought in at the right time you would have got it at that price. Its important to note that this promo is a general Bandlab offer - its not directly targeting Cakewalk users.
It's very common marketing technique for companies to have holiday promo's like this. Google does volume limited promo's like this all the time as well. 
 

Rolling back is not going to solve anything if the problem is external. If you post a crash dump file we can tell you why its crashing.

9 hours ago, DCMG said:

There's enough activity on this issue to suggest CW might want to address this in a clean thread; maybe even delete this one for clarity.

There has already been a dedicated thread for redist issues for ages. We don't need more threads.
This is a Windows problem not a Cakewalk issue. Its happening to other apps as well. 
All we can do is guide users to solve the problem themselves. All our latest installers automatically attempt to repair the redist. There isn't anything further we can do. 
If anyone has problems beyond this I suggest contacting Microsoft support.
 

Although sonar can have very long projects in absolute time, there are limitations to musical time. This is an area that can be improved.

PS.  when we adopted wav64 as a wave file format back in Sonar 7 we tested really long projects. I remember testing files that were a month long and running test recordings for many days.

Have you actually tried the same project in cbb? If you can share a link to the project file with us we'll take a look.