Post by popmann on Dec 13, 2018 18:02:34 GMT -6
I'm not saying it will always be off....I'm saying that there is ALWAYS latency-all you can hope for is that the DAW properly compensates, which isn't semantics, because thinking you don't have any because the app gets it in and out properly compensated will bite you in the ass. People say things too often like "I don't have latency"....yes, you do--you mean you don't have a latency ISSUE....currently....with your use case and perception.
Plug ins with lookahead buffers or that need to go out to a DSP chip (like UAD) make the entire DAW compensation work TANGIBLY harder. Meaning LONGER. They change the scale of the compensation for a handful of milliseconds to 50 and 100... So, now you set your DAW on 128 but it feels like 1024 because there's UAD or other latent plug ins somewhere in the mixer it has to compensate for. You can set a Fabfilter to lookahead 20ms. So, it's not only UAD< but ALL UADs, by the nature of not being processed on the CPU are that level/scope of latent. I don't think they need to add disclaimers. That would just confuse people who apparently already don't know how native mixer compensation works.
If it helps, what you need is to not bother using hardware during the testing, because it will change the content....just take an analog cable, make a loopback....and get it to cancel. That's how you set this up or test it....there's no need to put in the variables of the actual hardware kit....which will change the tone and envelopes....making it harder to actually test. Just do an analog loopback. Same deal. Throw latent UAD and lookahead plug ins into the mixer all over....test again....take some of them out....test again....etc....different sample rates....change your buffers up and down.....if there are manual offsets, you'll need to document them.
Plug ins with lookahead buffers or that need to go out to a DSP chip (like UAD) make the entire DAW compensation work TANGIBLY harder. Meaning LONGER. They change the scale of the compensation for a handful of milliseconds to 50 and 100... So, now you set your DAW on 128 but it feels like 1024 because there's UAD or other latent plug ins somewhere in the mixer it has to compensate for. You can set a Fabfilter to lookahead 20ms. So, it's not only UAD< but ALL UADs, by the nature of not being processed on the CPU are that level/scope of latent. I don't think they need to add disclaimers. That would just confuse people who apparently already don't know how native mixer compensation works.
If it helps, what you need is to not bother using hardware during the testing, because it will change the content....just take an analog cable, make a loopback....and get it to cancel. That's how you set this up or test it....there's no need to put in the variables of the actual hardware kit....which will change the tone and envelopes....making it harder to actually test. Just do an analog loopback. Same deal. Throw latent UAD and lookahead plug ins into the mixer all over....test again....take some of them out....test again....etc....different sample rates....change your buffers up and down.....if there are manual offsets, you'll need to document them.
