Delay compensation ignored on commit?

[Morten folmer]

connor@@vid i have a session i would like submit. where can i send it to?

thanks

[nigelpry]

Originally Posted by Eric Lambert

I strongly disagree and can't find any single reason why the two need to match. There should be an evolution of this technology, not an adherence to an unnecessary and antiquated limitation. What would be the practical point of that? When we make the decision to commit a track we've left real-time audio for good reason and we want audio in sync.

In fact, "commit" could become a NEW option for situations when a track is forced to cross the compensation threshold. I'd even argue that it makes zero sense to limit this function artificially IF ProTools is able to compensate for any delay when freezing tracks.

Out of curiosity, how does Logic deal with this?

More fundamentally .... Why, when doing a "ground up', "complete rewrite", of Pro Tools for 64bit, did Avid choose to perpetuate an archaic limit on maximum length of delay compensation?

Surely Avid must have known that there are commercially released plugins around that by their very nature generate long delays? Was this another piece of old code that was simply copied and pasted, warts and all, into the 64bit compiler?

[johnnymacvkguitar]

Originally Posted by dankin

No issues with Slate Trigger. Wonder if it's something to do with those plugins?

I was using Slate Trigger and after committing my snare tracks they moved in my session and I found out the hard way with a client remarking the snare flams that were happening where they shouldn't be. They were committed and the time stamp is of course off from the original. How can I report this to AVID?
:-(

[H-Musikk]

Originally Posted by johnnymacvkguitar

I was using Slate Trigger and after committing my snare tracks they moved in my session and I found out the hard way with a client remarking the snare flams that were happening where they shouldn't be. They were committed and the time stamp is of course off from the original. How can I report this to AVID?
:-(

I experience the same with Drumagog...

[Pyxis360]

Hello all

I'm on 2019.5 and Mojave, committing tracks with a hardware insert creates an audio track that is out of time.

If listening in realtime it's fine.

I've tried everything. An empty project with nothing but a single track and a hardware insert, tried turning compensation blue, etc. Nothing.

Has there been any update on this?

Thanks

[LoZion]

Bumping this old thread to see how commit is now with the new Hybrid engine and side chain compensation..

[JFreak]

Commit is working fine, wxcept if you use bad plugins like Waves and Slate.

[LoZion]

Originally Posted by JFreak

Commit is working fine, wxcept if you use bad plugins like Waves and Slate.

Txs Janne.
Any instances where the i/o plug is bypassed by hybrid, depending on plug order?

[JFreak]

Originally Posted by LoZion

Txs Janne.
Any instances where the i/o plug is bypassed by hybrid, depending on plug order?

You only need to have one bad plugin to be loaded into memory (not necessarily instantiated in session) to cause random trouble. Only fix is to get rid of it as in move to unused plugins folder.

[LoZion]

I meant approved plugs, so AAX DSP before or after the i/o plug in DSP mode will work but native in either order wont.. right?