• SONAR
  • Melodyne / tempo issue
2016/04/30 10:26:18
MacFurse
Hi Guys.
 
Today I was fixing a bass part right at the end of a song which has a massive tempo slow down to the finish. I'd done a really good job with all tracks during recording, and everything was almost perfect, but today I decided to tighten the bass, and my first real use of Melodyne since upgrading from 2 to 4 studio. About 10 various guitar tracks, vocals, and AD2.
 
I selected only the last 4 bars of the bass track, created my region and started work. The first thing I did was select the timing tool and just slid up the bar, just to see what Melodyne thought of the existing timing. It was in the auto position. I observed the suggestions and then cancelled out, and started some manual correction just to tighten up the individual notes. Everything was playing and sounding good, so I saved, got out, bounced to clip, and replayed, just to double check things.
 
The entire timing of everything else changed, including AD2. Nothing was in sync. No amount of undo has fixed it. The audio tracks have been stretched for the last 4 bars, and the drums completely out of whack. A few problems over the last couple of days had me turn auto save back on for the first time in years. So, it did it's job, and I can't revert !! It's back off again!!!
 
I have the project saved elsewhere, but it's a few days behind this current version. I can cut back and start again, but I have lost a fair bit of work.
 
I have never come across anything like this before. Anyone have any ideas what I either did wrong, or shouldn't have done ? (apart from the auto save)....I've done stuff like this hundreds of times before. Can't figure it out.
 
Cheers. Dave.
2016/04/30 10:34:31
MacFurse
I should clarify. The first 2 bars of the 4 were still at the song tempo, the last 2 slow down, so I was checking for the song tempo initially against the individual notes. I am already thinking I should have done 2 bars at a time, but it still shouldn't have changed the global tempo.
2016/04/30 11:26:54
paradoxx@optonline.net
If you haven't already, try closing Sonar, restarting the computer, and listen again. Sometimes that works for me!
2016/04/30 11:29:12
MacFurse
Yup. Tried that too. thanks ..
2016/04/30 13:34:05
VariousArtist
If you bounced the clip(s) it's still possible that the previous un-bounced clips are still in the audio folder. Maybe you can import those back in?
2016/04/30 13:41:42
mettelus
Can also try looking at the tempo list for the project and delete the last 4 bars worth. This will give you a starting point, then can use Shift-M (Set Measure/Beat at Time Now) to reinsert tempo map points.

Rather than Shift-M, you may also be able to split the last 4 bars of a track that was correct and drag that to the timeline, but I cannot verify if that works.

Regardless... Once reconstructed, save the project as a new name and tackle the bass again.
2016/05/04 19:44:57
MacFurse
mettelus
Can also try looking at the tempo list for the project and delete the last 4 bars worth. This will give you a starting point, then can use Shift-M (Set Measure/Beat at Time Now) to reinsert tempo map points.

Rather than Shift-M, you may also be able to split the last 4 bars of a track that was correct and drag that to the timeline, but I cannot verify if that works.

Regardless... Once reconstructed, save the project as a new name and tackle the bass again.

Thanks mettelus. I tried to recover the original tempo's, but it didn't work. It really did a good job. I've reverted and started again. I havn't had time to examine this, but a couple of simple experiments indicate to me Melodyne is not behaving as it did under certain circumstances. Re-timing a clip CAN change global tempo it would seem. Thanks for your help.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account