Protools basically invented their own hardware ecosystem so that all the problems we deal with today were handled by DSP processing and specialized drivers for their proprietary interfaces. It has a true RTL of .7ms. So for all intents and purposes, no discernable latency. For the most extreme cases, something in the 2.x camp of latency is more or less on the level of Protools. Without the specialized hardware and software, so you can do so "natively."What does “non protools latency” mean?I have a PreSonus interface with mediocre converters, but it has the lowest non protools latency you can find.
Curious how it would compare with my RME, as I’m a non protools user.
I would need to know which RME you have, but you can search "gearspace low latency thread" and there's a list that is constantly updated. But it's not arranged for absolute latency, and instead is something like "most efficient." The interfaces\cards in that thread are ranked in the order of how well they handle the load of a project, and the RME Aio Pro is at the top. But in terms of absolute latency, is bested by the Quantum 2632.
There are only a few edge cases where that extra ms plays any real part in anything which happens to fall into one of my usecases, but outside of that, RME's AIO Pro is an absolute beast.
Statistics: Posted by nickerz — Fri Feb 23, 2024 11:29 pm