Re: Trying to find out TotalMix Latency (not daw monitoring) 44K, 802, UFX
lol
You are not logged in. Please login or register.
RME User Forum → FireWire & USB series → Trying to find out TotalMix Latency (not daw monitoring) 44K, 802, UFX
lol
ramses wrote:Suggestions, ask your dealer. Get the two (802, UFX II), decide then. USB only is not a real reason to say no to an UFX II.
Finally, the new problem i may have discovered is that the combo jacks on the front of the ufx and 802 are XLR or unbalanced TS only for the line ins, so i presume for guitars or microphones.
Does this mean my synths won't work in those inputs?
The handbook mentions under 19.2 that the unsymmetric input at the front can be used for Keyboards, Samplers, CD-Players, Guitars.
Maybe also of interest for you driver stability and performance.
http://www.tonstudio-forum.de/blog/inde … cks-de-en/
TNM wrote:ramses wrote:Suggestions, ask your dealer. Get the two (802, UFX II), decide then. USB only is not a real reason to say no to an UFX II.
Finally, the new problem i may have discovered is that the combo jacks on the front of the ufx and 802 are XLR or unbalanced TS only for the line ins, so i presume for guitars or microphones.
Does this mean my synths won't work in those inputs?
The handbook mentions under 19.2 that the unsymmetric input at the front can be used for Keyboards, Samplers, CD-Players, Guitars.
Sounds great thank you!
I suppose 90% of my synths are unbalanced anyway, only the virus and integra are balanced.
I use the sound on sound pseudo balanced cables now to plug all my unbalanced stuff directly into the apollo balanced inputs and they work great, noise floor has been excellent.
So for those 2 remaining free at the front (one will be used for vocal and one guitar anyway), i will just use unbalanced cables. Should work fine.
It will be so nice to finally be able to work int he midi domain with low latency and everything having it's own channel, believe me. Apollo would have been ideal had this latency not existed.
I also want to take the opportunity to thank everyone, and especially MC for taking the measurements,and Ramse for being so helpful in so many areas. Cheers
Ahh I just read that link, i don't think you realise ramses, my imac is only usb 2, 2 usb2 busses on four ports, that i have turned into 22 ports with powered hubs.. This is why i said there's just not enough bandwidth for a high channel usb interface left.
The next model after mine got usb3, which obviously would have worked well with the RME.
IF i got a thunderbolt hub, like the OWC, it has 4 usb 3 ports.. and of course would be running on the thunderbolt bus not the usb bus already existing, then it would probably work great.... My mac has thunderbolt 1.. i believe it has it's advantages.. with thunderbolt 2, it's 20gb shared over one bus and 2 port.. With TB1, i have actually 2 independent thunderbolt busses in my imac with 10gb/s each. Yes unlike TB2 i can't get 20 from one port, but i've had nothing but success and it also means i can chain a couple hard drives (WD raptor with thunderbolt through then SSD at end of chain) to max out most of one bus, and leave the other entirely free for audio.
I love this imac as it makes no noise and just works, i will keep repairing it if anything happens till the point it's unsalvageable lol.
Ahh I just read that link, i don't think you realise ramses, my imac is only usb 2, 2 usb2 busses on four ports, that i have turned into 22 ports with powered hubs.. This is why i said there's just not enough bandwidth for a high channel usb interface left.
The intention was simply to make you aware of the RME driver quality and performance using a real world example, even if it is on a different RME interface than the one you intend to use.
I also wanted to underpin, that USB driver in the RME world are simply very good.
I was unsure whether your comment about why you want to have a RME recording interface which also supports firewire was really only based on your situation, that one of your machine has a limitation in terms of remaining USB bandwidth
or whether you dont fully trust USB.
Oh I can assure you i don't have anything against any protocol, i only judge things for my own situation. And look, if i get a new imac pro one day, or mac pro, i can then use the usb of the ufx i will buy anyway. I tried to haggle them down a bit today as they have had those 3 for ages, and see what their decision is tomorrow.
I have to also stay on my imac cause i love yosemite and pro tools 12 works the best on it.. and i will be forced to high sierra once the new macs are out... I also have a lot of old gear with drivers that stop at yosemite.
El capitan was a disaster for me, and sierra which is on my laptop, is ok, but PT still the best on 10.10.5. Weird glitches in sierra and things getting 'stuck', still, 1000x better than el capitan.
I am the type that likes to use what works. Believe me, i refused to move on from logic 9.1.8 and snow leopard for a long, long time (till yosemite came out)..mainly because of snow leopard which i STILL love.. such a lean fast OS..
I only left logic after 20 years cause i started heavily using uad plugins to mix, and logic's ADC does not correct automation for ANY plugin, even zero latency ones, when one is using latent plugins in the same signal path, i.e automation is always out by the time of the total latency of the latent plugins, so needs to be manually adjusted every single time you remove or change even a single UAD plugin! It was just too much after a while and I was sick of it...
Pro tools fixes all that completely, and now I am used to it like i have been using it forever.. If i wasn't using so many plugins with latency, i would have stayed on logicX but had to leave 2 years back, I still check every release out of curiosity but it's never fixed. I've reported it to apple 20 times LOL. I gave up as they obviously don't care.
I do need to ask one more question..
pro tools vanilla does not have a core audio recording negative/positive offset in audio settings like all other DAWs..can someone confirm to me that the RME ufx driver accurately reports the latency to PT, *including* the converter latency? I can test it during a loop back recording but too expensive to spend 2 grand to test lol.
Cheers -PS i think i'll get a S/H eleven rack for $300, problem solved by losing apollo for guitars, and it has aes/ebu out, so there is a perfect use for the UFX aes/ebu input
Thanks for clarification
>pro tools vanilla does not have a core audio recording negative/positive offset in audio settings like all other DAWs..
>can someone confirm to me that the RME ufx driver accurately reports the latency to PT, *including* the converter latency?
Maybe RME can help here.
> the RME ufx driver accurately reports the latency to PT, *including* the converter latency?
Under Mac no driver talks to an app. Our driver exposes the latency values including analog I/O to Core Audio. What ProTools then does with that information is not under our control.
that's fine.. that's all i meant. That it reports the absolute correct latency including a/d latency..
Many audio interfaces STILL don't do that properly.. they report the wrong latency.. this is a fact.
In TAFKAT's low latency audio database, most RME did report correctly, but that was on windows, which is why i am checking for mac. If it reports correctly, that means ANY daw can use them for sample accurate recordings without needing to put in an offset.
At 48 Khz, analog in to out via TotalMix FX, input and output channel have EQ, LC, Dynamics and AutoLevel active. Rev/Echo do not change these values:
48 kHz: 0.7 ms
96 kHz: 0.33 ms
192 kHz: 0.16 msThe manual says at 48 kHz AD 13 samples, DA 7 samples. One has to add some samples for the internal routing FPGA to/from DSP plus one sample TM FX, which results in about 33 samples at 48 kHz. Half and another half at 96 and 192. Please note that at 192 kHz the number of available FX channels is significanty reduced due to limited DSP power.
An old post but I tried to replicate the latency added by TotalMix FX on the UCX II by using the RTL Utility from Oblique Audio, Windows 10.
I in this case (SR 48kHz, samples 48 to 512) I got the same RTL, irrespective of enabling EQ, LC, Dynamics and AutoLevel on both channels. A cable was connecting output 7 with input 5.
So I wonder if I did something wrong in my test, or RME just has improved the latency. In TotalMix FX for the Dynamics graph I see that it's active during the test (a dot moving from lower left to upper right) for both input and output, so some work is done.
Edit: For 64 samples @ 48 kHz I got a measured RTL of 3.938 ms, with or without DSP enabled.
RME User Forum → FireWire & USB series → Trying to find out TotalMix Latency (not daw monitoring) 44K, 802, UFX
Powered by PunBB, supported by Informer Technologies, Inc.