Committing Melodyne ARA Tracks

[J-Hi]

Why do the newly committed tracks also have Melodyne instantiated on them? That's a bug. After committing, the new tracks should be free of processing.

Everyone's at NAMMBLA jerking off over Atmos but some of us still work.

[cwsand]

Originally Posted by J-Hi

Why do the newly committed tracks also have Melodyne instantiated on them? That's a bug. After committing, the new tracks should be free of processing.

Everyone's at NAMMBLA jerking off over Atmos but some of us still work.

I think it's by design - it does the same for Elastic Audio. It would be nice to change that behavior though.

[albee1952]

I'm confused. Can you describe in complete detail what you are doing? I wonder if a small change in your workflow is the solution. Example:
I just put Melodyne on a vocal track(in slot A where it should always be used), did tuning and then committed by 2 methods; Right-click on Melodyne and choose Commit up to this plugin(my usual method) and also by committing the entire track. In both cases, the resulting .cm track appeared without Melodyne inserted(the entire track commit appeared with no plugins). I'm not understanding how you are getting a result that has Melodyne on a committed track

As for Elastic Audio, do you have preferences set so new tracks default to Elastic Audio enabled?

[Bob Olhsson]

Dave, is that using ARA Melodyne?

[CarlosDanger]

I think I know what you are talking about, I noticed this behavior too and I think it is because your track is on ticks instead of samples in the timebase selector. This makes it analyze any audio on the track (even audio that was just rendered) so that it is always ready to react to your session changing tempo or whatever. I agree this is annoying and it should only analyze the track if a time stretch is actually needed

[J-Hi]

Originally Posted by albee1952

I'm confused. Can you describe in complete detail what you are doing? I wonder if a small change in your workflow is the solution. Example:
I just put Melodyne on a vocal track(in slot A where it should always be used), did tuning and then committed by 2 methods; Right-click on Melodyne and choose Commit up to this plugin(my usual method) and also by committing the entire track. In both cases, the resulting .cm track appeared without Melodyne inserted(the entire track commit appeared with no plugins). I'm not understanding how you are getting a result that has Melodyne on a committed track

As for Elastic Audio, do you have preferences set so new tracks default to Elastic Audio enabled?

I'm talking about using it in the Elastic Audio setting, not a plug-in. It's built-in now. No plug-in needed.

I have prefs set for Elastic Audio disabled on new tracks.

[J-Hi]

Originally Posted by CarlosDanger

I think I know what you are talking about, I noticed this behavior too and I think it is because your track is on ticks instead of samples in the timebase selector. This makes it analyze any audio on the track (even audio that was just rendered) so that it is always ready to react to your session changing tempo or whatever. I agree this is annoying and it should only analyze the track if a time stretch is actually needed

Next time I'll try the ticks/samples setting and see if that makes a difference, but I do believe you are mistaken about the default functions of tick-based tracks. It does no automatic analysis unless Elastic Audio is engaged. Tick-based track settings are used in case your clips are placed metrically and you would like to change tempo and have them scale accordingly. But they only scale the start time of the clip. They do not stretch the audio. That would be the preferred method if using drum samples as individual clips, for example. Sample-based tracks do not respond to tempo changes at all and stay locked to absolute time(code). Am I missing something?

[albee1952]

Originally Posted by Bob Olhsson

Dave, is that using ARA Melodyne?

If I am using ARA, I just commit the changes by removing Melodyne ARA and choosing Commit. I'm still not clear on where the issue is between EA and Melodyne ARA. It was my understanding that you could only enable one of these functions at a time(though ARA should allow adjusting timing, and might work better than EA, or at least with fewer artifacts). Sorry I couldn't help

[J-Hi]

Originally Posted by albee1952

If I am using ARA, I just commit the changes by removing Melodyne ARA and choosing Commit. I'm still not clear on where the issue is between EA and Melodyne ARA. It was my understanding that you could only enable one of these functions at a time(though ARA should allow adjusting timing, and might work better than EA, or at least with fewer artifacts). Sorry I couldn't help

Thing is, I don't want to remove the existing Melodyne processing on the tracks. I want to create new "committed" tracks without any processing, but leave the original MD'ed tracks alone. That's the whole point of committing. Otherwise I could just hit Freeze.

[albee1952]

Originally Posted by J-Hi

Thing is, I don't want to remove the existing Melodyne processing on the tracks. I want to create new "committed" tracks without any processing, but leave the original MD'ed tracks alone. That's the whole point of committing. Otherwise I could just hit Freeze.

Hmmm, still confused. When I commit a track with Melodyne edits, I get a new track without Melodyne on it. This does nothing to the original track, unless I choose to have the Commit function do something like Hide and Make Inactive. Do nothing(to the original track) is one of the options when you commit a track. I'm honestly trying to help, but am still unclear on what's going on.(maybe you are doing something I haven't considered)

As I reread your reply, maybe you do Melodyne edits in ARA and then Commit that track, and the new track appears with Melodyne ARA enabled? In that case, just disable Melodyne on the .com track(or does ARA have a problem that I am unaware of as I work differently?).