Is committing EA impossible to do accurately?
 

I can't figure out a way to commit a track with Elastic Audio.

I've tried:

1. None - Disable Elastic Audio
2. Rendered Processing
3. Route track to new audio track and record in real time
4. Commit (offline and in real time)
5. Bounce (offline and in real time)

In all of the above cases, notes in the new audio clip are delayed by around 10 milliseconds.

But the delay isn't consistently that same amount. Some notes are a little less delayed than than others, which means I can't just nudge the whole thing earlier to compensate.

I've searched this topic exhaustively and it seems that a lot of people have this problem. Some say that if you record in real time that you will get an exact copy of the original, but that's not working for me. I've tried it with Delay Compensation both on and off, plugins active or all deactivated (for the entire session), etc. Every time, the new audio is delayed.

Does anyone have any other ideas I can try? Or is it not possible to get a sample-accurate copy of the EA track with the adjustments committed? I guess I can just roll with the EA on there for this project, but what if I need to send a committed version to a collaborator in the future? Also, isn't the audio being delayed anyway if I bounce down the session to a stereo mix?

Re: Is committing EA impossible to do accurately?
 

Why not simply turn EA off on the track and choose COMMIT from the pop-up? That has worked for me for the past year or more(but I almost always use X-Form for timing edits):o

Re: Is committing EA impossible to do accurately?
 

I've tried that--it's labeled 1. in my list, if I understand you correctly.

It ends up with delayed audio just like the other choices.

Re: Is committing EA impossible to do accurately?
 

So if you turn EA off and commit, the audio moves on the track? I've never seen that here. Say I move some warp markers to a grid line and commit. The audio stays ion the grid here. Routing or bouncing to a new track can net some audio offset for a few reasons;
A bug in PT(seen this myself)
Latency caused by plugins(especially on the master track)
Latency caused by a large buffer setting(which PT should compensate for).
These reasons are why I generally just turn EA off and commit where it is:o

Re: Is committing EA impossible to do accurately?
 

Yep, it moves even when I turn off and commit. Please see the screenshots I've attached. I duplicated the track and turned EA off to commit the bottom one. Neither track has plugins on it.

As I noted in my original post, I've tried all these options with and without Delay Compensation on. I've also tried them all with zero plugins in the session--are you saying that I should be getting almost 500 samples of delay @ 44.1 kHz on a routed and recorded track even with absolutely no plugins in the entire session? I know that PT adds a small latency when routing, around seven samples or so from what I've heard, but this goes far beyond that.

I've tried the commit at both a 64-sample and 512-sample H/W buffer size, makes no difference in the size of the delay.

So I guess the only possibility is a bug, then?

Re: Is committing EA impossible to do accurately?
 

Here's a test I did on the same track, but without EA (I committed it to get rid of it).

The top track was routed to the bottom track and recorded. Might be hard to see from this image, but there is about a 30 sample delay. I assume this is the bus routing delay in Pro Tools, and is small enough to be neglible in terms of musical timing.

So to me, this test proves that there is something wrong with the way Elastic Audio works, since I am not getting a significant delay in the same session with the same track if EA is not part of the equation.

Anyone have a line to an Avid engineer that could shed some light on this?

Is committing EA impossible to do accurately?
 

Curious why you don't file a case with Avid?


Sent from my iPhone using Tapatalk Pro

Re: Is committing EA impossible to do accurately?
 

That's my next step. I first wanted to see if anyone else had this problem, but apparently not.

Re: Is committing EA impossible to do accurately?
 

isn't what you are experiencing a known issue with avid?

From the readme.....(12.8)

Elastic Audio
Maintaining phase coherency with Elastic Audio pitch processing (PTSW-20602)
When there is Elastic Audio Pitch processing enabled on a track, switching from Polyphonic, Rhythmic, or X-Form to Monophonic or
Varispeed can disrupt phase coherency. To preserve phase coherency in this case, be sure to clear all Elastic Audio Pitch processing
from the track before switching to the Monophonic or Varispeed algorithm.

Drift in an audio file may occur when using Elastic Audio and the Monophonic or X-Form algorithms (PTSW-33768)
Drift in an audio clip may occur when using elastic audio depending on how much the clips is expanded or compressed when using the
Monophonic algorithm. If you are using elastic audio with material that contains transient information in it that you would like to keep
from drifting, you should use the Polyphonic or Rhythmic algorithms.

Re: Is committing EA impossible to do accurately?
 

YYR123,

You are right, nice catch. I switched to Polyphonic and while the committed track is still slightly delayed, it's within a reasonable tolerance (50-100 samples or so).

Quite interesting that the bug (can we call it that?) occurs with X-Form too, which is often touted as being the most accurate. Or maybe it just has the least artifacts. At any rate, it depends on the source material.

I'll stay away from Monophonic and X-Form then. Lately I've found Polyphonic to be the overall best for me anyway--it doesn't smear cymbal tails nearly as much. But now I can finally commit all these Nebula instances and reclaim my CPU. Many thanks to everyone who responded.