Jump to content

PSA: If you are a Sonar Premium customer and using CbB with the new Cakewalk Core Plugins


Recommended Posts

The Cakewalk Core plugins will work in any host including CbB as long as you have an active BandLab membership and sign in to activate via the plugins.

However, while Sonar can seamlessly migrate the Cakewalk Core Plugins suite from the old legacy Sonitus plugins at project load time the automatic migration will not work in prior Cakewalk hosts or other hosts. In CbB or SONAR Platinum you must disable the VST Migration settings before loading old projects containing Sonitus plugins, since it may lead to errors on loading these projects otherwise and cause plugin settings to be lost.

To disable automatic migration turn off  "Replace if possible on Project Load".
 

image.png

  • Like 4
  • Thanks 1
Link to comment
Share on other sites

Thanks for the information.

Re:  The Cakewalk Core plugins will work in any host including CbB as long as you have an active BandLab membership
Is it correct to assume then that if my Bandlab membership lapses that these VST3 plugins will stop working?
Not complaining about or bashing subscription just want to be sure I understand things properly.

Edited by TheSteven
Link to comment
Share on other sites

I just saw the notices regarding CbB going away and that I need To migrate to your new version of Sonar. I was a Sonar Platinum member and I am wondering  how closely will the free version match the capabilities of Sonar Platinum, or for that matter the CbB I've been using. I'm sorry if this isn't a good place to ask, but I've been offline for a bit and want to get some info before I switch to Sonar again.

Many Thanks

Link to comment
Share on other sites

2 hours ago, Jack Hawk said:

. . . I was a Sonar Platinum member and I am wondering  how closely will the free version match the capabilities of Sonar Platinum, or for that matter the CbB I've been using. . . . .

If you are asking specifically about compatibility with regard to opening projects created and saved on older software (Sonar Platinum, CbB, etc.), I defer to others.  If you are asking more generally about features, workflow comparison, etc. I suggest the "Current Release . . . " Topic in the General > Product Release Info section might be helpful to you.   

Hope this helps.

  • Like 1
Link to comment
Share on other sites

I had this problem recently - I bought Sonar X2 Producer decades ago, and used CbB.
Recently I've given the new Sonar a go- Seemed fine until they updated all my Sonitus inserts to Sonar Core inserts irreversibly- Core inserts require Bandlab membership which is not free, so be aware that activating Sonar will change your inserts and music without asking.

Bit disappointed that Bandlab/ Cakewalk felt the need to hold my paid for inserts (On Sonar X2, when it was Roland) to ransom to try and get my membership.
Working on a workaround now.
CbB won't even open, since the updates.

And the suggested fix in the opening post just leads to multiple crashes, when attempting to open recent projects.Screenshot2025-09-16143823.png.4c846f1ebc5e2edfaf79bdce668aeb7c.png

Edited by RKK
Link to comment
Share on other sites

So at the moment, I'm runningthe free version of Sonar. I'm considering trying the subscription for a year to see what it's like. Reading this I'm suspecting that's not a good idea if I want to be able to open older projects that may have used the Sonitus plugins? I currently have my original sonitus plugs. Can I simply not install the new plugs? This looks possible with the new Sonar Product Center.  I don't need/want TH-U or Melodyne (Own them both) but wanted to check out Session Drummer.  I did disable auto migration per Noel's suggestion.  Also wondering if CbB will stop working come 9/30 or will it still be available after that.  BTW, this new version looks nice...

Thanks guys

Jack

Edited by Jack Hawk
added info
Link to comment
Share on other sites

It seems to me, so far, that the only way to test new plug-ins is to allow VS3 migration and pay for membership, which automatically reassigns Sonitus inserts when you open projects and if you want to save projects makes that reassignment irriversible- Unless you 'Save as' and spend time opening projects manually, with  or without VST3 migration. Always the risk of of sudden crashes or forgetfulness erasing your settings.
It's a case of 'Eithier Sonitus' or '(Untested & paid for) Core'. I can't open CbB now, but did find that my Sonar X2 doesn't accept the newer Cakewalk plug-ins, let alone the newest Sonar Core ones, so older projects seem to be fully intact- I can painstakingly collect the original Sonitus settings and reappropriate them so that Sonitus and Core plug-ins are both available in one project.
Still getting a lot of crashes  on Sonar now, so I'm not sure if I'll be diving down the membership path yet- Even though the crash-dump appears to work far better than CbB ever did, which,  in my experience,  it rarely did.

Link to comment
Share on other sites

We're going to make the core plugins available to demo soon. Note that if you turn off migration it won't replace the older plugins on your project. It also warns you when it replaced the plugins. In the next release we're also migrating any old plug-in presets you may have saved to make the process painless.

But it's fairly easy to save a copy of your project with the new plugins.

Link to comment
Share on other sites

18 hours ago, RKK said:

Recently I've given the new Sonar a go- Seemed fine until they updated all my Sonitus inserts to Sonar Core inserts irreversibly- Core inserts require Bandlab membership which is not free, so be aware that activating Sonar will change your inserts and music without asking.

It won't if you follow the instructions in the first post in this topic.

The point of this topic is to warn about this and inform users how to avoid it.

It isn't irreversible.

Don't overwrite your old SONAR or CbB projects after opening them in $onar or SoFT.

When trialing new software, it's never a good idea to overwrite the projects you've created in the older version. Always keep a backup copy.

Link to comment
Share on other sites

52 minutes ago, Starship Krupa said:

It won't if you follow the instructions in the first post in this topic.

The point of this topic is to warn about this and inform users how to avoid it.

It isn't irreversible.

Don't overwrite your old SONAR or CbB projects after opening them in $onar or SoFT.

When trialing new software, it's never a good idea to overwrite the projects you've created in the older version. Always keep a backup copy.

My posts were purely based on my experience, and people are free to dismiss them as they see fit.
Sonar regularly crashes if I switch off VS3 migration. I am currently unable to use CbB after this issue arose.
You can't trial Sonar Core plug-ins yet, so it seems needless to have them as an opt out option on the trial version of Sonar until they can be used safely, as they can, and in my case, do, affect older versions- Also stated in the first post.
 
Screenshot2025-09-17092307.png.552ee6ef90579899ca89117a6aa27e2b.png

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...