Jack Hawk

Thank You gmp... When I do this, I still get the error or warning that it's an old theme, but I tell it I want to use it and it loads, and all appears to be well. I tried this several times with the same result. Instead of switching folders, I simply renamed it, thus retaining the original, but I get the error every time. So far this has cost me several hours in time spent debugging the latest fix, and it still isn't right. I should probably just give in and use the default, but I rather liked what I had and hoped I could work around this easily... not so, for some reason. I downloaded and installed the latest Theme editor yesterday, Time stamps on both edited files are today. One thing I noticed is the original file is slightly larger that the edited versions 3872kb for the original, 3865kb for both edited files. Not sure if that is a problem... I open the file in the editor, and tell it to save as... it really shouldn't be this difficult. Jackson Hawk

I got the Waveform Outline issue resolved, thanks. As far as the theme issue, I opened the theme in the latest editor, applied a save as new name, attempted to select that theme, but still get the incompatibility error. I had thought that saving using the new editor would be what I needed to do, but apparently there's more that needs to happen? has anyone been able to get their current custom theme to work?

Thanks for this information. I believe this is the waveform issue I was noticing... I'll try doing an edit/save later today and see if it helps with the errors and such...

For the time being, I reverted back to 2021.01. As well as the theme not loading, I am having issues with the waves themselves looking different, too contrasty perhaps is a good description, and I really don't want to mess with this anymore right now. Question... if I open the theme in the editor, and manage to save it, will that fix the issue? Why in the name of God, did someone decide to mess with this?

So it seems to have removed the theme I was using. More time now to spend fixing something that wasn't broken... nice...

Gentlemen, Thank you so much for the replies. I think I have a handle on it now. The tutorial is excellent. I was able to pull up one of my songs and edit so I'm all set. I appreciate all your help and assistance, as this has been driving me crazy. Jackson

I'm thinking perhaps Melodyne is highlighting and accentuating them John, so yes, I need to better understand what's happening. Thanks for the video Salvatore, I'll check it out later today. Part of the issue is I don't want to delete them all as the words will still need s's and t's. Thanks for the replies everyone!!! Jackson

I began our latest Project last summer, and not long after starting Melodyne 5 was released. I know it handles sibilant detection differently and wonder if it may be causing loud sibilants on project vocals. I cannot seem to make them go away. De-essing has no effect with half a dozen different De-essing plug ins. adding compression during mastering seems to make the problem much worse. I never had the issue before using Melodyne 4, though I am not sure that is the problem. Looking for anyone having similar issues that may have found a solution? Does anyone have any suggestions to help. Thank You Jackson

Found a work around on one track that involved exporting the track and importing it back and everything was a-ok. triee the same thing on a second track with no change, still two full measures difference... no idea what might be happening...

I just came across another track recorded last week that does the same thing... It is recorded correctly, and plays correctly, but the curser in Melodyne moves almost 2 measures before The DAW starts moving putting Melodyne 2 measures ahead... pretty crazy.

henkejs is correct about selected blobs stopping scrolling. Took me a long time to figure that out... One of my issues may be compatibility with Melodyne 4, but I certainly have issues with one song I am working on. As I find work arounds I'll post back. Have not had a response from Celemony in over a week...

Lynn, When I hit play, you can see the cursor jumps ahead in Melodyne, When I stop it appears to be lined up correctly, but it jumps again when I hit play.

I upgraded to Melodyne 5 a few weeks back. I am in the middle of a new recording, and had been using melodyne 4 studio. The improvements looked good enough to warrant the cost, so I went to 5. What I am seeing is an issue similar to the problems with 4.2 about 2 years back in that the editor window, and the track window are not in sync. Track view is correct, but Melodyne is in a different position, so the blob it's passing is not what I'm hearing, making it difficult to edit. Not all tracks are affected. I definitely have one that I know was edited in 4 previously that's problematic. I also have a new track that's a problem, but do not recall if it was recorded and edited first before the upgrade. The brand new tracks I've worked on seem to be okay so far, so I am looking for a common denominator. Celomony claimed that 5 was fully compatible with 4. Celomony has reached the point where they aren't bothering to respond to questions. I am using Melodyne 5 Studio With CbB and I also see the issue in Studio One 4. I just wonder if I am the only one with issues, or if others have seen this behavior. As I recall, last time I went back to 4.1 until they fixed the problem. (It took months), but with money spent I don't want to revert back to 4. Anyone else see problems??? Thanks

I am running into an issue I saw with Melodyne a few years back where the Editor view and track view are not in sync. Latest version of Cakewalk and Melodyne 5. I also see it in Studio One as well, so I'm guessing it's something in Melodyne. I have reported it to them and am waiting for a response. This is all since updating to Melodyne 5

Thank you both for the response. I learned a few things. CJ, It would be the peak. I wouldn't normally work this way, but had completed the tracks, and then decided to go back and alter. In the future I'll go back and export an unmastered wav file to work on. Thank you both Jackson

Working on cleaning up some tunes I released awhile ago and had a question or two. I remixed and mastered some tracks. After the export I decided to change the tempo and imported the finished track, sped it up, and exported again. Would/should I remaster the altered track. I am not sure what the ramifications are. I did note that even though the tracks were mastered with a limiter, when I exported the finished track, after modifying the tempo, if was showing over the -.1 limit I set prior to mastering. I did the tempo mods in another DAW, but wouldn't think it should matter once it's mastered and exported to a wav. am I missing something here? I'll admit I'm in over my head on some of this and learning as I go. Thanks for any and all help. Jackson

I appreciate the feedback. I'm not using ASIO on the on board card. While I'm not likely to change my method just now, I do like hearing how others work and do make adaptive changes in my methods when I run across an idea that really strikes me, and works for me. Thanks for your input.

Thanks Jeremy, I actually am using this as my sound device for everything except the drum programs. Not a huge midi person, so I run EZ drummer and Addictive Drums out through my onboard sound card, and back in through the SoundCraft. Then I lay down a drum track with my rhythm track. When I have a drummer available, I can have them over dub drums, but if not my drum track is finished. I have spent hours trying to finesse a drum track into a finished piece and prefer to work this way...

scook, thank you, that got me going... is this something that changed in CbB? i.e. was it on by default in previous versions, because I never had this issue before, and likely noticed it right around the time things changed, but wasn't working as much as I have been lately until recently. anyway, thank you, that was the tweak I was missing...

Update: it seems nothing is getting through the master bus when I am in record mode. I can record, but can only hear on playback. to monitor I must listen st the mixer. Weird, because as I say, it works as expected in Studio One

I am using EZ Drummer running stand alone. I have the output going through my sound card, and feeding into the only RCA in on my Soundcraft Signature 12MTK. EZ Drummer tracks are getting to the input and recording, but not getting back to the master output, although they are setup to do so. I can only monitor at the mixer and must disengage the USB return to do so. Another note... this setup works fine in Studio One and behaves the way I expect. am I missing a setting somewhere in Cakewalk? Is the fact it's sharing a bus the issue. So far I am stumped as to why the signal never gets to the master out. Thoughts??? Thank You Jackson

Prior to updating CbB, I copy and rename the c:/Program Files/Cakewalk/ Cakewalk Core folder to reflect the version number of that version. Then if I need to rollback I can rename the Cakewalk Core folder to the version number, and rename the version number to Cakewalk Core. I have copies of previous versions, but I'm not sure how to get one to you. Others here also do the same, that's how I learned the trick. What version were you running?

I meant 4.2, must have fat fingered that... Thanks for the input...

I apologize for not responding sooner. I've been out of commission for most of the winter, and had a small project in April I was working on, which is when I had the issue. I'm just now back to actually spending time in the studio... When all this transpired, what I found was my output device had somehow removed itself from the DAW. not only that, but once I found and fixed, (I had to completely reinstall), I had to go through and reconfigure everything. It was an easier process to do the initial install than it was to find and fix this snafu. I run a Soundcraft Signature 12 multi track mixer, fed into the DAW via USB. I have no idea what caused everything to belly up, but once I reinstalled and reconfigured It's been fine.

Hello all, last fall there were issues with Melodyne 4.2 and CbB. at the time, Melodyne claimed they couldn't reproduce the error, and to keep working I reinstalled version 4.1, which has been working. I since finished the project I was working on, and due to health issues I've been off the radar since January. just getting back to things now and wondered if Melodyne 4.3 is working properly these days with the CbB 2019.5, which I just installed... can anyone update me please??? Thank you