It looks like you're new here. If you want to get involved, click one of these buttons!
Subscribe to our Patreon, and get image uploads with no ads on the site!
Base theme by DesignModo & ported to Powered by Vanilla by Chris Ireland, modified by the "theFB" team.
Comments
I hate it when tracking others, especially bands recording live where you need lots of individual cue mixing.
This is still where HDX rules- just one mixer to work with and it is just easy to work with.
UA Distressor is great- I've compared it against my hardware unit and it is so close you are down to 'component difference' levels of variation. Really, really close.
I love it on room mics.
Studio: https://www.voltperoctave.com
Music: https://www.euclideancircuits.com
Me: https://www.jamesrichmond.com
So in an empty project. One instance of Black76 in it. With the soundcard set to 32 samples buffer at 44.1khz, the PDC value as reported in Reaper is 64 samples.
So this seems correct. As long as the plugin itself is reporting it's latency to the host correctly. Which you can't always bank on.
The CLA76 reportedly doesn't require any PDC (the value is 0) because it's not adding any latency to the signal - again, if it's reporting correctly. Likewise with Native Instruments VC76.
Now here's the thing... just because Reaper is reporting that it's applying a 64sample plugin-delay-compensation does not mean the plugin itself actually has that amount of latency. What it means is that Reaper may be working in power of 2 block-sizes, and thus delaying by 32, 64, 128, etc.
IE: The host makes the decision about how much delay compensation to apply based on the amount of latency that the plugin causes. The plugin doesn't tell the host how much to apply. And this is why it is variable based on your soundcard buffer size. All hosts are going to treat this differently from what I can tell.
It's not true that only lookahead and convolution cause plugins to be latent, which causes hosts to apply PDC. Other factors can often come into play, oversampling being one of them. Oversampling can cause plugins to be latent, thus requiring the host to employ PDC.
Seems to me we're talking slightly at crossed purposes anyway. Because the original discussion point was about low latency or realtime monitoring. Something a plugin can affect, but is ultimately down to the host.
If I've got anything wrong there, feel free to clear it up!
Didn't monitor through the DAW at all.
Drew is correct regarding oversampling.
Fabfilter and Cytomic's 'The Glue' are two products that have variable oversampling.
Crank up the oversampling and watch the latency climb.
Studio: https://www.voltperoctave.com
Music: https://www.euclideancircuits.com
Me: https://www.jamesrichmond.com
I love The Glue, tis epic!
The UA version is even closer though.
Studio: https://www.voltperoctave.com
Music: https://www.euclideancircuits.com
Me: https://www.jamesrichmond.com
Studio: https://www.voltperoctave.com
Music: https://www.euclideancircuits.com
Me: https://www.jamesrichmond.com
I'd like to see him doing more products.
Studio: https://www.voltperoctave.com
Music: https://www.euclideancircuits.com
Me: https://www.jamesrichmond.com
The way I calculate latency in Pro Tools for Hardware Delay Compensation is pretty simple.
I send a kick drum out of two outputs- a loopback and a hardware output.
The amount of displacement between the loopback and the hardware output (in samples) is the delay compensation required.
You can do the same with plugins.
On the whole I just use PDC and get on with my life.
Studio: https://www.voltperoctave.com
Music: https://www.euclideancircuits.com
Me: https://www.jamesrichmond.com
Band Stuff: https://navigationofficial.bandcamp.com/album/silhouette-ep