gmp

I've been using a theme since 2017 and it's worked fine until 2021.04. I went ahead and installed the new theme editor and opened my Theme in it and then saved it. This was supposed to work, but doesn't. Currently the only problem is with ProChannel showing up correctly in Inspector. I'm just concerned that there will be more problems in the future. Has anyone found out a solution to this? I see many are posting new Themes and that's great. So maybe those persons can give some insight on this. Will there be a fix for my Theme or will I have to just scrap it and go to a new Theme? If so, i sure would be nice if the new Themes were all saved on a website where we could check them out. Instead of finding each individual post in this Forum. Many years ago when we were really into the Themes when they first came out around 2016 there was a website link like I described

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.

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

I would be nice if our cut, copy, and paste function had this feature that Arranger has: "set the Overlap Threshold to 1/16 and copy a section with overlapping notes by using Ctrl+Shift+Mouse drag,"

Man it's good it was a test project. If I ever try to use it, I'll rename the cwp, so I don't lose anything. Either Arranger is buggy or we need help in understanding how to use it

I love the ripple editing. It's a huge addition. I guess using the 1/16 or 1/32 before the spot it'll be good especially if I set the nudge to 1/32. Then it's easier to find the beginning spot and find the target. I think I'll try that next time. I just installed the new 2021.01 update last night, it lists several improvement to the Arranger. Maybe it'll work better for you. I hope some one else replies that has had success with it.

I saw this feature in 2021.01 "Arranger section inclusion of outlying MIDI notes. When dragging sections or committing arrangements, Cakewalk has logic for dealing with leading/trailing MIDI notes that overlap section boundaries." Sometimes I want to copy a midi piano from Verse 2 to Verse 1. If it starts on or near the downbeat of the selection, I quantize beat 1 so the piano is exactly on beat 1, because if I don't and the piano starts even 1 click before beat 1 it won't copy. Apparently the Arranger feature solves this. I've never used the Arranger, so I'm not sure if I should try to use this in this situation or if there's a way to copy a piano track with leading/trailing MIDI notes that overlap the selection boundaries and paste it to Verse 1.

When I found out I couldn't use an ISO file I thought like you that Nero could problem do it and I could send the client my free copy of Nero for him to install along with the Nero file. I noticed your file was a NRA file. That sounds more like audio. Here's maybe part of the problem, I used CD Architect to create my original CD I then uploaded it to Oasis CD Duplicator and created a test CD. I first put the test CD in Nero and chose "Copy CD" it then created an .NRG file in my E:\My Documents folder. I then copied the NRG file to a different computer in E:\My Documents folder. I Opened the NRG file in Nero and everything looked ok until I hit "Burn" then instead of prompting for a CD I got this "Save Image As" window. My situation is different from what you outlined, because I'm forced to burn the test CD from Oasis. Weird things can happen with an upload due to the internet and various computer problems, so I felt he needed to check out the test CD not my original. I do have a 2nd CD to do with him, so do you think Nero would work in my situation?

I was certain that exactly how I could do it, until I tried and then started reading articles saying that an audio CD is different from a data CD and the ISO image won't work. If you've successfully done this let me know. Maybe there is a specialized ISO that will work with audio.

I'm not wanting him to get separate wav files from a zip file, I wanted to send him 1 file like a ISO that he could easily burn an exact copy of the audio test CD from the upload I did to the CD duplicator

I sent him the wav files with wetransfer and walked him through the upload and he burned the test CD. I'm surprised there's no ISO type file for audio CDs. DDP is what the duplicator uses, but they didn't have any solutions for getting the client a file to burn the test CD

I've done a CD project for a client and we're trying to save time by uploading to the duplicator. I uploaded it and made a test CD of the upload and thought I could just make an ISO copy of it, send it to him and he could burn an audio CD from that. But ISO files don't work for audio CD's. Does anyone know how I can send him the exact copy of the test CD?