gmp

I'm getting a new computer possibly next week and have been using Cakewalk actually since 1992, so I have accumulated a lot of plugins and soft synths. I still have all the old install CD's and install files. Which versions have the plugins and soft synths? Is there a list?

No problems with authorization, every once and a while I have to log into bandlab

V-Vocal was a Roland product when Roland owned cakewalk, so it hasn't been updated for a very long time. Did you find a way to update it or is this the last version we got from a Sonar version many years ago? A frozen synth is much like a disconnected synth, no more RAM involved, so V-Vocal won't crash in a project with a frozen synth or disconnected synth. Does V-Vocal crash with unfrozen or connected soft synths for you?

What is v1.5.2.5 (2011)? I'm using CbB 2024.07. As long as I have no soft synths loaded it won't crash. Are you using soft synths. Ivory is pretty RAM intensive

I'm getting a new computer from Jim Roseberry. I've been using V-Vocal for many years successfully as long as I disconnect all soft synths and close and reopen the file. With this new computer and WIN 11 Pro, has anyone been successful with it not crashing? I can get extra RAM if it will work

>>The only version of CbB that will authorise will be the latest version of the day.>> I've been using 2023.09 up until a few weeks ago. I didn't have any problems with authorization. 2024 02 was problematic for me

Before I update to a new version, from the beginning I always renamed Cakewalk Core with it's version number at the end of the name and then installed the new version. If I ever need to rollback I can simply change the name of Cakewalk core. scook found out that this can cause problems unless we put the correct CW130Auto.dll file into C:\Program Files\Cakewalk\Shared Utilities\ So I can do a Manuel rollback like this. I assume I still have to use the correct CW130Auto.dll. scook hasn't posted in about a year and Launchpad which did all this rollback stuff automatically, doesn't work with the new versions. It seems strange that cakewalk got rid of the rollbacks.

If I need to rollback to a previous version, it used to be easy with Launchpad, which doesn't work with the newer versions. Do we still have the rollback to a previous version? I've never done it like that before. I just manually did what Launchpad does. You have to correctly put the CW130Auto.dll file into C:\Program Files\Cakewalk\Shared Utilities\. Is this even necessary with the newer versions?

Every evening I run Vice Versa, which is a backup program that backups 3 of my computers to a 7T USB backup HD. Then after it's done I click on Backblaze, which is an online backup, in case something really crazy like a fire happens. Vice Versa also does something interesting, if I have a file like a CWP file that has the same name and I overwrite it, it will save the original file in a deleted files folder. This has come in handy a few times.

It seems like scook the creator of CbB tools and Launchpad is no longer in this forum. From what I can see he left last summer. I've been using 2023 09 and recently updated to 2024 07, since I was having issues with 2024 02. Launchpad doesn't recognize 2023 09. I can manually do what launchpad does by copying the Cakewalk Core folder and fixing the C:\Program Files\Cakewalk\Shared Utilities\CW130Auto.dll Maybe there's an easier way to roll back to the previous version Any thoughts?

I've been using Launchpad since it's been out and hadn't run into this problem before. When I open it I get this message Fatal error caught in destructor 2023.09 not known. 2023.09 is the version i'm currently using In this folder \CbB Tools2-0-10\CbB Tools\sub I see CW130Auto-29.9.0.75.dll Which is the version and build I'm currently using. 2024.02 was problematic so I didn't use that for very long, so I want to update to 2024.07 It seems that scook, the creator of launchpad, isn't in this forum since a year ago. Am I mistaken?

I've been using Launchpad since it's been out and hadn't run into this problem before. When I open it I get this message Fatal error caught in destructor 2023.09 not known. 2023.09 is the version i'm currently using In this folder \CbB Tools2-0-10\CbB Tools\sub I see CW130Auto-29.9.0.75.dll Which is the version and build I'm currently using. 2024.02 was problematic so I didn't use that for very long, so I want to update to 2024.07

Control bar was gone completely. I disabled many of the shortcuts like C, since I never want to hide it. In about a week when I'm back in town, I'll for sure report if I get that happening again

In the Workspace window I chose "save workspace" Maybe that will fix it. Nothing happened when I hit C, maybe I have that shortcut disabled. What does it do? I also went back to my template and unchecked Views / Control bar and then rechecked it and reselected my custom Workspace and resaved my Template. Lets see if those things make it work

This bug has been around a while, but since I just resumed using Workspaces, I hope it can be fixed. Sometimes when I open a CWP file, the Control bar is gone. The workaround is for me to click on the little arrow on the right side of Workspaces and select my custom workspace. The Control bar then shows back up. I have a custom Workspace in my Template, so every song I do has this. In the workspace window I have checked "Apply workspace on project load". Under "Views" I have Control bar checked in my template and when I open my template it's fine, the Control bar is there. But when I save a new song and later open it, sometimes the Control bar is not there. When I open CbB I have it always load my Template. I can't find a recipe to make this happen, it's erratic. Has anyone else noticed this?

Thank you msmcleod for the detailed explanation. I've been using Cakewalk since 1992, so no doubt I'll be happy to buy the paid version of Sonar and by what you said I feel confident I won't run into any problems.

So once they go to the paid version of CbB, and once we pay them, will we be able to activate old versions again?

Whenever I install a new CbB I always save the installation file and as soon as I install it, I also then do all the Win 10 updates, then I save an Acronis image file. This way I can revert my C HD to that version. I wonder how long an activation lasts and why Banklab is doing this. It's fairly rare but sometimes there's a show stopper bug that forces me to use an older version. I also use Launchpad, but I did forget to use it to save all the info for 2022.11 before installing. After I installed 2023.09 I realized I forgot this and went ahead and copied Cakewalk Core for 2022.11 on my backup HD back to the Cakewalk folder, renaming it to "Cakewalk Core 2022 11" I also have the CW130Auto.dll file from the 2022.11. So I can manually do what launch pad does and open 2022.11 from the Cakewalk.exe in the "Cakewalk Core 2022 11" folder My big question is what does the future hold. Is Bandlab going to let us use an old version of CbB? I heard someone mention that CbB will soon be a paid version. maybe once I've paid, I can revert to an old version. If anyone knows the answers to any of these questions, please chime in

I see in 2023.09 there's no rollback installer available for the 2023.09 release. Occasionally I find a bug in a new release that makes it necessary for me to use the previous version. In this case 2022.11. I see there's some activation issue that may prevent this. What options are there for this?

You nailed it. When Workspaces first were introduced, I set up some of my own, but ended up just using the same one in my template and then really forgot about them until you reminded me. I'm pretty sure they didn't have as many features years ago. This looks like it'll solve my problem. Thanks for your great help and advise.

I never have liked using Screensets and have tried all sorts of ways to disable them. I have my Keyboard shortcuts set up where if I hit any Screenset shortcut key like 1-9, it opens Smart Tool, which I have permanently open any way, so it does nothing. This works right after I import my custom keyboard Shortcuts, but once I close the CWP and reopen it, Screensets are back. It seems they are hotwired as a keyboard shortcut. Any clues how to fix this or is it a bug?

Here's an easier way that never crashes. Disconnect all soft synths, save and close CbB and reopen. Use V-vocal. Or if you need to hear the soft synths you can either export an audio mix of the music track and import it back in or bounce all the soft synths

I checked it and it is 4 Gigs of RAM. I wasn't planning on running CbB, just a standalone Keyscape for an electric piano sound. I wouldn't record it in the laptop, only playback in the studio, like a live gig. If needed, I could do a fresh install of WIN 11 to get rid of any extra background programs and things in the Startup in Task Manager

I have a fairly old laptop. It's not too old because MS upgraded WIN 10 to WIN 11. It's probably 4 GIGS of RAM. I'm wondering if it's good enough to trigger a soft synth, one at a time, for a live session. Probably KeyScape. I do have an very good MOTU AVB Ultralite USB audio/midi interface that I can use. I can use the soft synths as standalones. I never done this before, so any advise is appreciated.

I installed it. Is the comments section the best place to add the ISRC code? What do you do?