Jump to content

Cakewalk Sonar - Tempo Amendment Tips (getting existing audio tracks to fit new tempo changes)


Recommended Posts

Hi,

I looking for some tempo amendment tips regarding getting existing audio tracks to fit in time with new tempo changes.

I have added a tempo increase and decrease via the tempo track but would like to know the best way to get my audio tracks to fit in time with the tempo changes.

Especially with my vocal tracks which have an instance of Melodyne on each track (e.g. is it best to do my tempo changes before my vocals or is there a better way of doing things)?

Any ideas gratefully received.

Thanks in anticipation of your help.

 

Link to comment
Share on other sites

It's always better to let your audio guide your project tempo, recording the freely varying tempo that you want, and using the various methods available to fit the project timeline to it (Set Measure/Beat At Now being my prefered tool). But if you have an existing fixed-tempo recording that's matching the fixed tempo of the project and you want to add a tempo change after the fact, do the following:

 - With the audio clip(s) selected, expand the AudioSnap section of the Clip Properties tab in the Track Inspector.

- Check the 'Enable' box.

- Select 'Autostretch' from the 'Follow Options' pick list.

- Check the box to enable 'Follow Proj Tempo'.

The clip(s) will automatically conform to any tempo changes you make. See the documentation for information on stretching algorithms and using Bounce to Clip(s) to render the stretching permanent with an Offline algorithm.

Although it's all reversible, even after you render the stretching, it's generally advisable to work with a copy of the project to facilitate recovering the original state in case things don't go as expected for any reason.

 

  • Thanks 1
Link to comment
Share on other sites

I have tried several times to understand how to work with tempo in Melodyne  when it is inside a DAW. But I have failed to understand the logic (if it is there at all...).

If you have Studio, you can do multi-track tempo manipulations standalone. If material tempo is recognized/assign correctly, tempo changing of any kind is working predictable (including making tempo constant from free style playing).

But if Cakewalk way (AudioSnap) produce reasonable results, render Melodyne and then do tempo change in Cakewalk. It can happened that is working fine without Melodyne rendering these days, back in time that was not a good idea...

 

  • Thanks 1
Link to comment
Share on other sites

1 minute ago, azslow3 said:

But if Cakewalk way (AudioSnap) produce reasonable results, render Melodyne and then do tempo change in Cakewalk.

Yes, I intended to  mention that all the Melodyne (i.e. pitch correction) work should  probably be done first since it's optimized for working on raw audio and might be negatively affected by any stretching artifacts introduced by Audiosnap. And it should (and must) be rendered before Audiosnap can be enabled.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...