12.5 Elastic Sound Quality

[metalmixer]

Elastic Audio on 12.5 is broken - Totally glitchy audio - turn off elastic audio glitches go away. Even tried my Apollo.
The audio sounds like clock jitter - but its' not because disabling elastic audio removes the glitches.
Tried realtime rendered/Poly/Mono/XForm - they all do it mono is better than poly but its' still unusable.
Mac Pro 2013 12 Core 32GB RAM
OSX 10.10.5
12.5 HD

FWIW I have never had issues with Elastic Audio or Elastic Pitch ever....

[john1192]

Have you Opened a Support Case for this ???

this sounds very bad ...

Originally Posted by metalmixer

Elastic Audio on 12.5 is broken - Totally glitchy audio - turn off elastic audio glitches go away. Even tried my Apollo.
The audio sounds like clock jitter - but its' not because disabling elastic audio removes the glitches.
Tried realtime rendered/Poly/Mono/XForm - they all do it mono is better than poly but its' still unusable.
Mac Pro 2013 12 Core 32GB RAM
OSX 10.10.5
12.5 HD

FWIW I have never had issues with Elastic Audio or Elastic Pitch ever....

[jchan]

There's also some graphical bugs in elastic audio (x-form rendered) where the waveform isn't drawn in some cases, though the sound remains intact.
Can't say I have any glitches with rendered x-form though...

[longname]

Originally Posted by jchan

There's also some graphical bugs in elastic audio (x-form rendered) where the waveform isn't drawn in some cases, though the sound remains intact.
Can't say I have any glitches with rendered x-form though...

I gotta say Pro tools Elastic audio sounds the worse compare to other DAWs. Today I use pro tools 12.5 to stretch time using Elastic Audio, and it's so glitchy (Unusable) I tried it on Adobe Audition, and the problem went away.

AVID, you take money from us, and we ask you just a stable and usable version of pro tools (12.5 is a trash version). What are you doing with the world standard DAW???? WAKE UP.

[Niilo Nuori]

Don't get your hopes up - this one has been on the Avid "fix it" list for 5 years : http://protools.ideascale.com/a/dtd/...a-tab-comments

[AlexLakis]

Don't get me started...I'll try to stay as on topic as possible for this one...

Ahem--Elastic Audio gives me random glitches/blips on playback in Pro Tools 12 constantly. Its very easy to replicate (just use it, lol). Thankfully, these glitches are not present when you commit the EA.

Metalmixer, what version of Pro Tools are you upgrading from? The X-Form algorithms are best in 7.4, so if you are upgrading from that particular version, be prepared to be disappointed in X-Form's quality.

[EdwardG]

I remember Izotope showing up around DUC explaining why 7.4 was better and later worst, it was his algorithm back then it seems.

[nigelpry]

Originally Posted by EdwardG

I remember Izotope showing up around DUC explaining why 7.4 was better and later worst, it was his algorithm back then it seems.

What's worse, from what I recall of the thread, is that it was diagnosed and confirmed to be a settings preference that is simply set to '0' or '1' in the original isotope/radium version. But in Avid's implementation in X-form they hard coded that setting the wrong way.

Perhaps they no longer have anyone capable of finding the '1' in the code and changing it to a '0'? Or the other way around ... I'd have to track down the original thread to confirm high way it SHOULD be set. I'll try to find it later.

[nigelpry]

Ok so this is the thread ...

http://duc.avid.com/showthread.php?t...t=Xform&page=2

Post 47 in the thread is when it gets really interesting. It's by Alexey Lukin of Izotope.

If you don't make the effort to read posts prior to #47, then you should read everything after, as it explains what we think has gone on very well.

Also, importantly, post #55 includes this link ...

http://protools.ideascale.com/a/dtd/81879-3779

in which the relevant details have been used to create an ideascale item on the subject to persuading Avid to fix x-form.

[Niilo Nuori]

Good work! Now let's hope Avid, one of these days, will act on this. Unless PT is total spaghetti code with no documentation, it should be very easy to find and change the API call(s) to iZotope algorithms/DLLs even by a new programmer. It is a question of priorities...