View Single Post
Old 05-24-2016, 04:02 AM
nigelpry's Avatar
nigelpry nigelpry is offline
Join Date: Dec 2008
Location: Home
Posts: 2,154
Default Re: Delay compensation ignored on commit?

Originally Posted by Eric Lambert View Post
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?
Mac Pro 2009 with 2010 firmware, 12-Core 3.46ghz, 64gb RAM & working Thunderbolt, OS 10.13.6 and Windows 10
Macbook Pro 2011 17", 2.2ghz i7, 16gb RAM OS 10.12.6
Digi 003 Console, Focusrite Octopre and MOTU Traveler for extra analog-ADAT conversion, UAD Apollo Quad with Thunderbolt card, Apollo Twin mk11 and pci-e Octo, Adam A77X monitors.
Pro Tools 2018, Media Composer 8.9, Sibelius 8.7, Cubase Pro 10, Wavelab Pro 9.5, Logic Pro X, Mainstage 3.
Various apps, soft synths, FX plugins.
Plenty of hardware synths, rack gear, microphones etc.
And then there's the studio ;-)
Reply With Quote