ElastiquePro

[midnightrambler]

Here's another example of it not working right :

Running real-time : sounds fine https://duc.avid.com/attachment.php?...1&d=1685983384

Commit : what the hell is that spike and what is it doing in my audio? https://duc.avid.com/attachment.php?...1&d=1685983384

Commit using Poly instead : works as expected (i.e. good enough for this scenario) https://duc.avid.com/attachment.php?...1&d=1685983384

[albee1952]

Hmmm, maybe this is only happening on Mac? I have not seen it on Windows(yet). In any case, what happens if you bus the audio to a new track and record it in real time? I understand this takes extra time, but if it yields the desired result, at least that helps

[capt kirk]

They all sound like a picket fence, after a certain point......some sounds work better with these things than others.....if I could get one that could go 75% without crapping it out.....the one in PT now can get to about 81% before it renders it useless

[Sardi]

Has anyone logged this as a bug?

This can’t be expected behaviour and it would be beneficial to let AVID know if they’re not currently aware.


Sent from my iPhone using Tapatalk

[midnightrambler]

Originally Posted by Sardi

Has anyone logged this as a bug?

This can’t be expected behaviour and it would be beneficial to let AVID know if they’re not currently aware.


Sent from my iPhone using Tapatalk

As always with these things, they can be a pain to try and replicate consistently, and though I try and get to the bottom of these things when I have time, sometimes work gets in the way...

[Scotty Chops]

I found I had problem with it not timing correctly when I was using it on tracks with multiple comped clips, when I faded/consolidated the track first then started using Elastique it performed much better.

[Dizzi45Z]

This is under known issues for 2023.3

"Elastic Audio

élastique [Elastic Audio] warping is not working correctly if used on small selections. This is a design limitation. It is suggested to use this on entire songs or longer selections, or to use polyphonic instead. (PT-299616)

In my case, I thought my clips were still plenty long enough and it was still drifting. But maybe there can't be other shorter clips on the track? I'm not sure and I need to do more experimenting. I just stopped using it because it isn't reliable.

I sure hope this known issue can be resolved as it would be awesome if it could be used as reliably as the other elastic algorithms.

[JingleDjango]

Originally Posted by Dizzi45Z

This is under known issues for 2023.3

"Elastic Audio

élastique [Elastic Audio] warping is not working correctly if used on small selections. This is a design limitation. It is suggested to use this on entire songs or longer selections, or to use polyphonic instead. (PT-299616)

In my case, I thought my clips were still plenty long enough and it was still drifting. But maybe there can't be other shorter clips on the track? I'm not sure and I need to do more experimenting. I just stopped using it because it isn't reliable.

I sure hope this known issue can be resolved as it would be awesome if it could be used as reliably as the other elastic algorithms.

If this is a design limitation then perhaps they should have refrained from including the algorithm altogether. What constitutes a 'small' or 'longer' section? If these values are known then the software should warn the user. If the value isn't known then what were they thinking when they handed us an unpredictable new tool? Didn't this come up during testing? uuuuuugh.

[midnightrambler]

Originally Posted by JingleDjango

If this is a design limitation then perhaps they should have refrained from including the algorithm altogether. What constitutes a 'small' or 'longer' section? If these values are known then the software should warn the user. If the value isn't known then what were they thinking when they handed us an unpredictable new tool? Didn't this come up during testing? uuuuuugh.

I completely agree - if it doesn't work for a "small" section, and it's known that it doesn't work, then it shouldn't have been released. Or at least come with some sort of major health warning.

[Tweakhead]

none of my audio appears to be the "right length". pray tell, what is the right length ?

I wasted an entire day's work using this crap algorithm, before seeing others were getting the same predictably bad unusable results.

this is like the 1-tick-off grid edit bug . . . none of my sessions are at the "right tempo".
I think Avid have simply given up. That's why they're "for sale".