Elastic Audio Commits and Bounces are out of time

[ralphonz]

Hi everyone,

So I've come across what appears to be a catastrophic, show-stopper of a bug with elastic audio.

It seems that "sometimes" for no reason that I can find, various warp modes won't render, bounce or commit in time.

Yesterday I realised that some drums I'd warped in ElastiquePro mode had gone nuts when they were committed. Indeed there is no pattern to what is output by either committing, bouncing or recording to another track other than it is not the same as the actual warped track and many hits are out of time. I tried other warp modes and the only one that rendered correctly was Rhythmic.

So I found (in the same session) the same thing happening with the bass track. For that none of the modes except rhythmic would output correctly either, however, rhythmic sounds awful on the bass...

Before I go through the lengthly process of putting together evidence and testing everything in multiple projects etc I would like to know if anyone else has had this issue or is it a known bug?

[midnightrambler]

Elastique Pro definitely had issues (e.g. https://duc.avid.com/showpost.php?p=2669221&postcount=6). I thought these were ironed out but I haven't really used it since I got my fingers seriously burnt with it last year.

Personally I can't think of any issues with real-time processing vs rendered/committed for the other algorithms.

[ralphonz]

Further, yesterday I found timing issues when committing melodyne too. Completely different when committed or bounced, but at least melodyne is okay when recorded back in, though the recording still doesn't null with the original melodyne track so the result is still different from what I'm hearing at least it's in time when recorded rather than committed. Also there was a strange blip in a vocal track when committing or rendering melodyne which isn't there in a recorded version or on playback of the edited melodyne track.