gmp

I changed to the Mercury theme, closed and reopened CbB and it worked. I then tried the cakewalk.ini entry EnablePluginMenuFix=1 I entered it correctly, then changed to my custom GP Logic 21 theme, closed and reopened CbB and still have the seam problem. I double checked the Preferences and they're done right. At least I have a workaround of undocking the Inspector. IS this something that will be fixed in a new version of CbB, or do I need to edit my theme and fix it? It's been right at 4 years since I messed with Themes. When I installed 2021.04 it said my Theme needed to be updated. I did that and it now has worked fine, but now I have this problem. If I need to update my Theme, any guidance would be appreciated. Any more suggestions?

The addition of the arranger inspector Tempo inspector seemed to have affected whether we can see Pro Channel in Inspector. I have some Pro Channel EQ and FX on one of my busses by default and the only way I can view Pro Channel now is by undocking the Inspector. It seems part of the problem is not enough space at the top of the Inspector Show/Hide Arranger Inspector, etc. Because if I undock the Inspector, I can then see the Pro Channel tab at the top right. With it docked, you can't see that tab There's also a check box for Pro Channel - compact EQ module. That doesn't affect this problem. I did a search for Inspector and didn't find any other posts about this. So has this been reported yet?

Who's post are you referring to?

Hey Toy, I'm unsure from your post if this Tempo crash bug and quirky behavior you outlined was fixed in build 175 or is it still being worked on. I haven't been having any crashes with the tiny amount o tempo change work I do. I very rarely ever have more than 1 tempo in a song and never have a series of tempo changes like a ritard. The only problem, which is more of an inconvenience is that the default setting has changed in the tempo box and I have to retrain myself to remember that. It sounds like the whole Tempo box and Tempo view were broken and got buggy. I hope they fix the default behavior too, if they're still working on it. Let me know if the problem you wee having is fixed and if this is all again working the way it was for you.

I'm using the latest build 175. Since 2021.04 the Tempo change box defaults have changed. I prefer the previous way it's been done for decades. First go to any bar from bar 2 on up and hit stop. Go to Project - insert tempo change. Hit the mouse on "click here to tap tempo". I do that then quickly start tapping the spacebar which is far more accurate. In the past the default selection was "Change the most recent tempo". Now the selection is "Insert a new tempo". If I leave the default like I used to and I hit Ok and go back to bar 1. The new tempo won't kick in until I get to the bar I was at when I did the tempo change. Most of the time when I need to change the tempo it's because I'm trying to match the tempo of a prerecorded rough demo track that I imported into CbB. Many times I go to near the middle of the track, since if the writer was playing with no click track they may speed up. So I listen there and then bring up the tempo change box and change the tempo. Since I'm not at bar 1 the tempo change is inserted at whatever bar I'm at. Whereas in the past I didn't have to change the selection to "Change the most recent tempo", I just hit ok. Are there any others out there like me that prefer the old default in this box? I don't change tempos every day otherwise I'd remember this change. I hope we can return to the old default selection. I've been using Cakewalk since 1992 and it's always been like this even back then - why change?

Good post, Terry. I did forget to say that I always work with small clips, one or two vocal phrases and I immediately "bounce to clip". Then move to the next spot. I, as a habit, only have 1 project open at a time. I assume most V-Vocal users are already doing this. I'm a pianist so my template always has Ivory, Superior Drums and Kontakt synths connected. So my RAM is about 3.5 gigs. About a month ago I did forget to close and reopen CbB and I got a crash right away - oops. My method has been working 100% for a year or 2.

You've come up with a good method, but you're right it's a lot of extra work. The method I've come up with is easier and I never get a V-Vocal crash. I do have Melodyne Assistant (found a great sale) and have learned how to use it, but prefer V-Vocal. You're right there is some conflict with the VSTi's that causes it to crash. Once you export the music only tracks Don't delete the soft synths, just disconnect each one. Then you can just import that music only track back into the same project and also not worry about bouncing the vocal tracks so that they're one seamless wav file. Maybe this works because I close CbB right before I start using V-Vocal and then I reopen it by double clicking the file. This seems to be the key. Don't ever try to go from one project to the next, you have to close CbB and then reopen it with the file you want to use V-Vocal on. Maybe deleting the VSTi"s does the same thing as closing CbB and reopening. No need to create a new fresh CWP or do any bouncing. Try it - it's easy and works, never a crash.

I've used Kontakt for years with CbB and Sonar. I have 3 instances of Kontakt in the synth rack of my template, so every song has Kontakt. I only have 1 of those 3 connected in my template. The other 2 I need to choose "synth connected" to use them. For the last several months I've noticed that sometimes when I go to the Synth Rack open the Kontakt Synth properties, I get a message at the very top of the window saying "not responding" this lasts for about 10 sec and then it's ok. This only happens for 1 or the 3 instances of Kontakt in my synth rack and it's the one that is "synth connected" by default in my template. It is a multi with 3 synths I've tried reinstalling Kontakt to fix this to no avail. I'm not sure if this is related to the crashes, but I thought I'd post it in case it would be helpful. I'm not getting crashes.

Glad I asked. That fixed it - thanks, man. You're the best

You're so right. The update checker was wrong, so now I've updated t build 147 and it fixed the problem i had. So thanks again scook, you're on top of it What do you think of this error screen that came up about the automation version being build 144. Am I ok to use it like this?

David, I checked out the post and I justed installed for the first time on Saturday, so I just double checked. Cakewalk update says I have the latest build. Apparently this timing issue is more widespread into other areas like what I've experienced. Should I email Cakewalk support with this bug? Or will this thread suffice?

16 msec delay in recoding audio 2021.04 has a problem with a 16 msec delay in recording that is only in this version of CbB. I have a midi track that triggers an 8th note high hat from an external AKAI sampler. I go to an audio track, arm it for record and hit record. The hat plays and the audio output of my analog mixer goes to the audio track in CbB.I stop it after a bar and then select the audio clip and then paste it 99x checking the box "align to measures. I now have an audio track that serves as an audio click track This has worked fine with all version of CbB except this one. What happens is after I record 1 bar and select the clip the start point of the click is not 01:01:000 (0 sec), it's now always 01:01:018 (16 msec). I just opened 2021.11 and did the same test and the clip starts at 01:01:000 (o sec). So there's a delay in recording the audio using 2021.04

Hey Jackson, yes strange indeed. Like you, I spent a long time trying to figure this out and I hope this post saves others from the frustration we went through. I hope Cakewalk makes this easier in the future for long time users like us. Once would think the renamed file would work, but no, you can't trick it into thinking this is a different file. It's weird, no doubt. Glad it worked, man.

Hey Jackson, I ran into the same problem. I know it seems crazy but load the old theme in the new theme editor, choose save as and look at which folder it's being saved to, but don't save it yet. Mine is like this: new theme editor and CbB use this folder for themes C:\Cakewalk Content\Cakewalk Themes - there's only 1 theme in there - logic GP 21.sth (this is my custom theme) here are old Sonar themes - which have all the old themes, which need to be updated if you want to use them C:\Cakewalk Content\SONAR Themes Once you're sure of the folder, then open the old theme in Theme Editor and go to that folder and just move that old theme file temporarily to any folder , now choose save as and this time you'll notice it has today's date not something in 2017 Ike mine was. It's not updated until you have the current date. There really should be an error message pop up so others don't go through this. You can't just rename it old, like I did. That didn't work for me either, move it out of that folder. You can do this, I'll help you. I wasted a lot of time to. I hope this post saves others all this frustration.

yes when you hit save, notice the date on the theme, it hasn't changed to today's date. I wish there was an error message. Once the theme is open in the theme editor, move the theme file to a different folder, then when you hit save as it will have today's date and be correct. It won't overwrite the old theme

Thanks that explains what I was seeing - makes sense

I'd like anyone that reads this thread to know that I had a hard time having the theme editor saving the file. It doesn't seem to want to save it as the same name. I had to move the file from the folder and rename it "old" and then it saved it fine. The Theme editor apparently doesn't want to overwrite the old file in case we use an old version of CbB that's expecting the old file.

I installed 2021.04 and it says Custom Theme incompatibility. The Theme I have is old and needs to be updated. I assume I need to download the new Theme Editor. I've searched all over and can't find it. Any clues on what I need to do Thanks,

This is great info I just did an experiment, I'm using 2020.11 and I chose to download the update, after it downloaded I opened the folder and saw that this is a different path from the way Bandlab did it. I chose not to run the file and closed Cakewalk. The file was deleted. In the future should i immediately save that file to a different folder, because Cakewalk will delete the file after install? Or is that file saved?

You said installers downloaded using CbB are stored on disk - can you tell me where? I used to open the downloads folder and if I was fast I could select it and copy it to a different folder before it was deleted, in case I need it later. But I stopped doing that and don't see the download >>Without the 2021.01 installer, one way to re-install the current version is rollback to the previous version. Then BA and CbB will both make the update available.<< thank you this is a great idea and would have prevented my debacle. At that time I was not aware of the rollback feature - live and learn - ha ha. >>Links to the rollback installers are provided in the release announcement.<< cool, I saw it and now know how to do all this better next time

I agree totally in order to keep multiple versions of Cakewalk installed and switch between them, that the safest way is always run Cakewalk from Launchpad. The thing is for me I only ever run old versions when I run into a bug in the current version. When I ran into this bug (that I've reported already to Cakewalk email support) I did some testing and used launchpad to test other versions. When I ran into this problem I posted the bug under 2011.01 Feedback. You saw this post and Noel said my mini-dumps were caused by the wrong CW130Auto.dll. For some reason the check mark on restoring the current version of CW130Auto.dll didn't work in my case and caused the crashes. He suggested I reinstall 2021.01 Since the install files are not saved, the only way I saw of doing this was first uninstalling CbB and then reinstalling 2021.01 Well that turned out to be a big mishap, because then my export presets were gone. I didn't hear of any way to restore them, so I used the rollback installer and after that CbB would not open at all saying there was an error in with ttslame.dll not found. This is when I decided to just revert my C drive to the image file I made right after installing 2020.11 So in retrospect I think I should have instead put the 2020.11 CW130Auto.dll into Shared Utilities and only run it and not run 2021.01 anymore.

Need some clarification on Launchpad I've had a problem with 2021.01 so I wanted to only use 2020.11. I can use launchpad to run 2020.11 and if I understand correctly the only thing Launchpad does it to place the correct CW130Auto.dll into this folder. C:\Program Files\Cakewalk\Shared Utilities\CW130Auto.dll Is that correct? if so then once I'm 100% sure which CW130Auto.dll is correct for 2020.11, I can even manually place that file in that folder and as long as I only run 2020.11 from it's shortcut, I'll be fine. Yet if I try to run a different version from it's shortcut without running launchpad then I'll be using the wrong CW130Auto.dll Is that correct? If all of this is correct then I could also run 2020.11 using launchpad and then the correct CW130Auto.dll would be in place and I could then run 2020.11 from it's shortcut and it would be fine as long as I didn't run any other version from it's shortcut only.

I was having problems with 2021.01, so I decided to use the Cakewalk rollback. it didn't work. I got this error message while trying to open CbB, which never opened cakewalk.exe system error code execution can't be found ttslame.dll not found reinstalling program may fix I assume it means to reinstall Lame and not reinstall 2020.11, which I was trying to rollback to. The setup files for 2020.11 are never saved, so I can't reinstall that version. if it's referring to Lame. I don't use the old Cakewalk MP3 converter from about a decade ago, I use a custom version of Lame that's integrated into CbB when I export files.

Noel suggested to always use the official rollback installer if I need to go to a prior build. I've looked all over and can't find it. Any suggestions?

While trying to test a bug in 2021.01, It was suggested that I reinstall CbB since I may have a faulty install. I didn't see an obvious way of doing this without first uninstllling 2021.01 and then reinstalling it. When I did this, somehow it deleted all my Export Audio presets and Bounce to clips presets. Where are these files stored? I can revert to a previous image file of my C drive to find them or I can look in my Deleted files folder that saves all files that were deleted. I also have quite a few older versions of CbB that I can run using Launchpad, but those older versions don't have these lost presets either. I wondering what else I may have lost by uninstalling. Any help will be appreciated