Cakewalk Core Plugins Feedback

[Starship Krupa]

15 minutes ago, noynekker said:

If you can do this "addon takes seconds" in seconds . . . my hat is off to you:)

I guess I'm a member of the Naked Head Club then.

You shouldn't need to create the directory, the plug-in installer should do it for you, and since it's a subfolder of the standard VST3 path, it doesn't need to be added to Sonar's scan paths either.

The install under normal circumstances takes no longer than installing any other suite of lightweight VST3 fx. By "seconds," surely less than a minute. More like <10 seconds on my systems.

[noynekker]

13 minutes ago, Noel Borthwick said:

There is something messed up in your installation if you don't have common files/vst3 in your default vst scan path unless you manually removed it. 

Every clean installation of sonar includes that path because it is the standard vst3 location across it should never be removed. This is why it didn't work for you. All that is required is to install the latest version of sonar and then the core plugins add on without running through all the hoops you did 

No, that directory did not exist for me . . . perhaps I'm guilty of having every version of Sonar installed since Sonar 8 living on my 14 year old computer.

Edited 21 hours ago by noynekker

[noynekker]

3 minutes ago, Starship Krupa said:

I guess I'm a member of the Naked Head Club then.

You shouldn't need to create the directory, the plug-in installer should do it for you, and since it's a subfolder of the standard VST3 path, it doesn't need to be added to Sonar's scan paths either.

The install under normal circumstances takes no longer than installing any other suite of lightweight VST3 fx. By "seconds," surely less than a minute. More like <10 seconds on my systems.

Not familiar with Naked Head Clubs, more up on the Fuzzy Grey Club . . . but agreed, the install should create that directory . . . so, the question would be why it didn't after running the plugin install at least twice on my computer ? Maybe everyone else here has newer computers.

[Starship Krupa]

26 minutes ago, noynekker said:

Not familiar with Naked Head Clubs, more up on the Fuzzy Grey Club

You said you'd doff your hat if the process had taken him "seconds." I figured that you'd extend your pledge of cranial nudity to others who had such luck.😄

I'm a fuzzy grey myself.

As far as why you had to jump through extra hoops on your system....who knows. It's working now, and I bet it will work in the future.

Edited 21 hours ago by Starship Krupa

[matt]

This is more of an FYI, probably doesn't apply to a lot of people here who have already switched or planning to move forward in Sonar.

After installing the latest Sonar update and the new core plugins, none of my old projects would open in Cakewalk.  They just hang on the "prepping project" or "preparing project" (I forget) indefinitely.  Granted, every one of my projects for sure uses the Sonitus plugins, they are in my template... I assume that is the issue, trying to replace them.

Removing the new core plugins from my VST3 folder resolved the issue.  Just be aware if you install them there may not be any going back to Cakewalk, depending, your mileage may vary.

[Noel Borthwick]

This is bizarre. Did you install the latest sonar update successfully? If you disable the automatic VST3 migration this will prevent auto loading the new plugins.

You can change this  in Preferences > VST Settings > VST3 Migration and uncheck "Replace if Possible on Project Load"

Which version of windows are you running? Can you manually load these plugins? I suspect your problem is related to something else since nobody has reported this issue in months of testing. In any case if you can't resolve it send me a pm and we can do some further troubleshooting.

PS: installing the new plugins has no bearing on the old dx plugins. They can coexist and will not affect other apps.

[Shaan]

1 hour ago, Starship Krupa said:

The issue with the hard to see colored rings around the knobs could be solved by making the rings wider, too.

Yes, you are correct.  That is the first solution that I thought, but while I started typing I forgot that completely 😁🤭

Thank you for adding that 👍

[Mauro Gaspa]

Good morning everyone.
I'm trying out the new Cakewalk plugins (Sonitus) installed with the latest update.
At first glance, I like the new suite and congratulate the entire staff.
However, I note that it would be helpful to implement the ability to scale the graphic size of plugins by percentage, like those from other manufacturers.
For example, for Spectrasonics (Omnisphere, Keyscape, Trilian), the feature is called Magnify.
Having two 4K screens, I immediately noticed that the new Cakewalk plugins always appear a bit small even when optimized for high resolutions. Implementing Magnify would optimize the display even better.
I've attached the full print screen of my second monitor to illustrate how it displays in proportion to the screen.

 

Thanks

Mauro

[Salvatore Sorice]

10 hours ago, Starship Krupa said:

Yes, especially the knobs and text. Those are the elements I most want to have larger when I scale a plugin UI.

The issue with the hard to see colored rings around the knobs could be solved by making the rings wider, too.

Also, I'd really like for the unfortunately named Surround plug-in to be included in the new suite. For anyone who's thinking "nah, I don't do 5.1 mixing," that's not what Surround is for. What it actually is is a spatial effect to add depth and width to stereo material. Among other tricks, it can do the doppler effect when panning. Of course the Haas effect too.

If you've never tried it, open the Sonitus fx version and check the help file, try a few presets. You can set up modulation paths to have your source pan back and forth and in and out automatically. At extreme settings, it can even do scratch effects.

So it's got nothing to do with surround buses or any of that, what it is is a creative sound design tool. I so SO regret not checking it out before now due to its name. I suggest adding it to the Core suite and calling it Core Spatial.

If you're doing game audio or sound effects for film/TV, or you just (like me) like to put spatial ear candy FX in your music, check it out, and if you'd like to have it in the Core suite, post in this topic.

(Also mention if you never tried it because you thought it was for 5.1 mixing😆)

@Starship Krupa, glad you mentioned that Surround plugin - I totally forgot about it - and it is great! Lots of creative possibilities. I definitely vote for having it updated!

[Salvatore Sorice]

I'd like to see Midi Learn functionality in the new Core Plugins - anyone else? From what I've read (I'm not well versed in Midi) it is no trivial task to add it to a plugin, but it would be nice to have. Wonder if it is being considered for a future update?

[Noel Borthwick]

11 minutes ago, Salvatore Sorice said:

@Starship Krupa, glad you mentioned that Surround plugin - I totally forgot about it - and it is great! Lots of creative possibilities. I definitely vote for having it updated!

We're already on it and it will be released soon.

[Noel Borthwick]

7 minutes ago, Salvatore Sorice said:

I'd like to see Midi Learn functionality in the new Core Plugins - anyone else? From what I've read (I'm not well versed in Midi) it is no trivial task to add it to a plugin, but it would be nice to have. Wonder if it is being considered for a future update?

We can consider it but why not use standard parameter learn in the host application? That's the more modern way to do it.

[Noel Borthwick]

55 minutes ago, Mauro Gaspa said:

However, I note that it would be helpful to implement the ability to scale the graphic size of plugins by percentage, like those from other manufacturers.

See this reply. 

 

[matt]

10 hours ago, Noel Borthwick said:

This is bizarre. Did you install the latest sonar update successfully? If you disable the automatic VST3 migration this will prevent auto loading the new plugins.

You can change this  in Preferences > VST Settings > VST3 Migration and uncheck "Replace if Possible on Project Load"

Which version of windows are you running? Can you manually load these plugins? I suspect your problem is related to something else since nobody has reported this issue in months of testing. In any case if you can't resolve it send me a pm and we can do some further troubleshooting.

PS: installing the new plugins has no bearing on the old dx plugins. They can coexist and will not affect other apps.

Win 11 Pro.

Sorry I think you misunderstood my post... all my Cakewalk projects will open in Sonar, I was talking about going BACK to working in Cakewalk by Bandlab after installing the Core plugins.  And yes, of course unchecking "replace if possible on project load" fixed the problem, thanks for that I should have thought of  it, totally forgot that was an option.

I just thought you (and others) should know that backwards migration was not working, though I suspect compatibility issues in Cakewalk is not high priority anymore.  But, I'm still using it for another month!  Sonar is not working for me yet (see my other post in the Sonar forum).

I did reinstall Core plugins and recreated the hang, I made a dump file after 15 minutes of "not responding" (in Cakewalk) if you still want the dump file I can send a link but it's 2.5 GB.  Thanks!

[Noel Borthwick]

Hi @matt,

Aha I see what happened here. Backwards migration is indeed working fine in Sonar. The issue here is that CbB doesn't have the code needed to handle backwards compatibility with DX and therefore when it detects the new plugins it replaces the old plugins with the new ones, but since the migration from DX to VST is not implemented in CbB, that part fails and it throws this error.

I do not get any hang in CbB just this message.  Most likely what is happening is that you get a bunch of these messages that are behind the application window and it makes it look like it's hung. Please check.
The message is basically telling you that a plugin was replaced but the state couldn't be transferred. This logic is built into all Cakewalk applications from 2015 or so.
The resolution to this is to turn off automatic replacement in Cbb here.



PS: this is a classic example of why we cannot support old products in the field that are not updated anymore. 

Thanks for reporting this. We'll update the release notes for the plugins to tell people using CbB to disable automatic replacement.

[matt]

7 minutes ago, Noel Borthwick said:

I do not get any hang in CbB just this message.  Most likely what is happening is that you get a bunch of these messages that are behind the application window and it makes it look like it's hung. Please check.

No messages... it hangs for about 5 minutes and then goes into "not responding" mode.  It's possible it would eventually resolve but I've never let it go for more than 15 minutes.  All of my old projects have potentially 40-50 sonitus plugins on them as they don't take up much memory/cpu, I will have a sonitus eq and delay (disabled) on every audio track in my template.