I don’t care about the higher figures as they can only be lower, but the one i have to be happy with is the 44k figure.Īpollo console is 2.3ms at 44k without any effects. I want to know the latency through the dsp mixer… not going through the daw at all… No you are indeed misunderstanding, but thanks anyway… Your post is a perfect example, as you also had no idea on the truth about console latency. So to achieve that in console i have to avoid using all the uad fx i paid thousands of dollars for… what a waste!! I really don’t think many people realise… 3 to 3.5 ms is my absolute total RTL cutoff for me… can not stand any higher. If i was steinberg, RME, etc, i would really attack UAD on this, make it known… draw attention to their products instead. This is all because of console’s crappy latency when using any of the good plugins. I have 32 midi synth inputs going into it from hardware synths… unless i record everything to audio, leaving all the midi stuff to play through console with plugins, in other words, using console as an analog desk replacement which is what i bought it for, actually causes timing issues with the rest of the project playing back in your daw, especially against virtual synths playing back… the hardware synths are out of time. This is why i am trying to find out what the steinberg dsp fx latency is, as i am very unsatisfied with console… i loved it in every way, except for the terrible latency. Once again native wins, besides cpu use… as we have hundreds of zero latency native plugins. It’s the same with avid HDX… you get 1.9ms RTL at 44.1 or 0.7 at 96, but each and every aax dsp plugin adds latency, some 60 samples or more… before you know it, a 4 or 5 plugin monitoring chain and you are at 10ms. well two reasons… low console latency is not one of them. The whole thing has been a sham and many have been fooled for years… there is only one reason to go apollo, to save cpu for old computers, and unison. To put it in simple terms… the UAD marketing of zero latency console and 4 plugins is a LIE, as, unless you read the manual, you’d have NO idea that only very few UA manufactured plugins did not add additional latency. Now, if anyone can tell me whether steinberg DSP suffers from this issue, and what the actual monitoring latency through the DSP mixer is, we can get back on topic… I am just waiting for 10 demos to be reset, to finish it off, but 95% are already done. In the meantime, i spent many hours making a chart of every uad plugin latency, IN CONSOLE.
#Uad dsp chart manual#
Read the UAD plug in manual “additional latency” section if you need to further understand it, and IDC. In fact, console latency gets so high, that at some point you would get lower latency using apollo as a normal thunderbolt interface THROUGH the daw, and using native plugins to monitor at 32 or 64 sample buffer… where you would get around 3 and 5ms RTL… Console goes much higher than that when using multiple new plugins.įor example, just ONE instance of the new fender amp, adds almost 2 and a half milliseconds to CONSOLE’s round trip latency… this is without using ANY other effects yet… so we are already almost at 5ms at 44k just for one guitar input and one guitar amp… through CONSOLE… capish? Using any of the GOOD NEW plugins like fairchild, fender amp, la2amk2, 1176 etc… adds compounding latency… This has NOTHING to do with the daw… i am talking about console…
You can keep it at 2.23 ms if you use a handful of very old, decade old UAD 1st gen fx… this is how UAD claim the 4 inserts per channel with no latency lie. All the good UAD plugins have latency in console… what do you think the input delay compensation is for?Īlso, what on earth did that have to do with my question? I know EXACTLY what apollo CONSOLE latency is at 44k, 2.23 ms without any FX…
0 kommentar(er)
