"Commit" or "Bounce" Non ARA 2 Melodyne Track?

[Sparky1]

Hello

Using Melodyne (Non ARA 2 Version) as an insert on a track.

Does "Commit" and "Bounce" the track give the same processed result?

Thanks,

Sparky

[nednednerb]

IF

Melodyne is last insert, NO automation on fader or panners,

THEN THEORETICALLY

Commit makes what gets bounced.

HOWEVER

When the fader is moved after the melodyne, commit would have the audio only up to that point.

So if no changes to the signal occur after the point where commit occurs, then it's the same. Have to consider for instance any BUS or Master processing.

In other words, yes and no it depends.

[albee1952]

Methods vary, but mine(for non-ARA) is to always use Melodyne in the first insert slot>make edits as desired>right-click on the Melodyne Plugin and select "Commit up to this Plugin" and select "Do Nothing" to the original track. Once the commit finishes and creates its new ".cm" track, I move the printed audio back to the original track, but to a new Playlist(so the original un-edited audio is kept handy, but hidden)and make the Melodyne Plugin inactive(or remove). Delete the (now empty) ".cm" track and get on with whatever's next

[Sparky1]

Originally Posted by nednednerb

IF

Melodyne is last insert, NO automation on fader or panners,

THEN THEORETICALLY

Commit makes what gets bounced.

HOWEVER

When the fader is moved after the melodyne, commit would have the audio only up to that point.

So if no changes to the signal occur after the point where commit occurs, then it's the same. Have to consider for instance any BUS or Master processing.

In other words, yes and no it depends.

Interesting... I did not know most of this...


Thank you...


Sparky

[Sparky1]

Originally Posted by albee1952

Methods vary, but mine(for non-ARA) is to always use Melodyne in the first insert slot>make edits as desired>right-click on the Melodyne Plugin and select "Commit up to this Plugin" and select "Do Nothing" to the original track. Once the commit finishes and creates its new ".cm" track, I move the printed audio back to the original track, but to a new Playlist(so the original un-edited audio is kept handy, but hidden)and make the Melodyne Plugin inactive(or remove). Delete the (now empty) ".cm" track and get on with whatever's next

I typically place Melodyne on my first insert as well...

I like the idea of "commit up to this plugin"

I think I'll start moving the committed track up to the original track in a new playlist... good idea!

Thanks,


Sparky

[Dizzi45Z]

Originally Posted by albee1952

Methods vary, but mine(for non-ARA) is to always use Melodyne in the first insert slot>make edits as desired>right-click on the Melodyne Plugin and select "Commit up to this Plugin" and select "Do Nothing" to the original track. Once the commit finishes and creates its new ".cm" track, I move the printed audio back to the original track, but to a new Playlist(so the original un-edited audio is kept handy, but hidden)and make the Melodyne Plugin inactive(or remove). Delete the (now empty) ".cm" track and get on with whatever's next

This is exactly what I do. I really wish there was an option to "commit to new playlist." In this case, it would make inactive all plugins up to the point you commit to, make a new playlist and put the processed audio on the playlist.

[nednednerb]

Originally Posted by Dizzi45Z

This is exactly what I do. I really wish there was an option to "commit to new playlist." In this case, it would make inactive all plugins up to the point you commit to, make a new playlist and put the processed audio on the playlist.

Maybe this is a case where SoundFlow automation would be useful... I'm more and more interested in my own macros for features that ARE there for one button after encoding the specific keyboard shortcuts in sequence, first..!