-
Posts
447 -
Joined
-
Last visited
Everything posted by gmp
-
I'm going to maintain my Logic theme myself. So here's what I'm doing: Open my Theme in theme editor. Double click on TungstenTheme.fth in Cakewalk Core to open a 2nd theme editor. It says untitled but I assume this is Tungsten. I looked at Morten's guide to the changes here https://discuss.cakewalk.com/index.php?/topic/13621-psa-theme-changes-updated-17-may-2021/ I see under "Inspectors" Clip tab as one of the changes. In the theme editor for Tungsten I see a folder on the left named Inspectors and see Clip tab, so I right clicked on it and hit copy. If I go back to the theme editor of my Logic theme and right click on Clip tab I can choose to remove or import but not paste. What's the best way to proceed forward? Or do I simply choose remove and assume that it will now be the default Clip tab without me having to import or paste it? I also tried the Views and selected Modified, Images, and Toggle filter (on), so I can see what images have been modified and need to be replaced with the default ones. Am I doing this right so far?
-
Very good investigative work. You found the original post by the creator of the Logic Theme - RFLint. I even see my posts in the thread and how others were commenting on what a good theme it was
-
Ok here are my theme files https://onedrive.live.com/?id=C256E2DAE26B22A5!105&cid=C256E2DAE26B22A5 logic GP 21 old.sth - I used this one since 2017 until 2021.04 and then saved it in the new Theme editor to this: logic GP 21.sth the oldest version or the themes I have is named: logical.sth I'm not sure why this name is slightly different from the old Sonar Themes website that I downloaded logic.sth But all 4 of these theme files are about the same size, so they must all be the same theme.
-
Thanks Colin you link was very good and in it someone gave a download link to the old Sonar themes almost all were created by Elffin. I wonder if he's still around? I found the logic theme that I use in the downloads https://app.box.com/s/jcaqb2lpcpi9f16uq99b1zvo9fmatnje?page=1
-
Is there a link we can click on that will take us to the new updated themes? Right now it seems you just have to go through all the posts in this Forum and find ones that say Themes and hope that the person actually gave a link to it. Does Cakewalk have a [public upload section for users to upload Presets, Themes, etc
-
This overlay idea you have sounds promising. Keep us updated on your progress. Maybe Cakewalk can help you develop this, since it would be good for them to have a simpler solution to this problem
-
Yes you are remembering the post. I do have some experience with tweaking themes, but this was back in 2017. scook told me to fix some elements but was very vague about exactly what to do. Even opening my Theme and saving it in the new Theme Editor was a quirky process and I was trying to help this other guy through it. So you're right I haven't made any tweaks to my Theme to fix this current problem. Like you I have zero experience designing themes, but I have made tweaks. I hope Cakewalk can give us better guidance, especially when we start running into more serious problems than just the ProChannel Inspector problem. Every time I made tweaks to my theme I renamed it, so i have 21 versions of it. That's a lot of work to redo.
-
I'm using Logical.sth, which tried to copy what it looks like when using Logic as a DAW. I made lots of changes to it. I'm not sure what's involved in me making changes to update my customized Logic theme, but I'd like to know what's involved.
-
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,
-
Updated several utilities for CbB v2.0.10 2023-05-06
gmp replied to scook's topic in Cakewalk by BandLab
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? -
Updated several utilities for CbB v2.0.10 2023-05-06
gmp replied to scook's topic in Cakewalk by BandLab
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 -
Updated several utilities for CbB v2.0.10 2023-05-06
gmp replied to scook's topic in Cakewalk by BandLab
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. -
Updated several utilities for CbB v2.0.10 2023-05-06
gmp replied to scook's topic in Cakewalk by BandLab
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
-
Can I copy leading or trailing MIDI notes that overlap the selection?
gmp replied to gmp's topic in Cakewalk by BandLab
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,"