It depends on the specific application whether the RTL is relevant.
The values for RTL are stored in the ASIO driver for all analog interfaces on the recording interface (e.g. in Windows) so that the DAW can perform correct latency compensation. RME is known for entering correct values here.
Specifically: 1. the converter latency depends on the sample rate and is much, much lower than the RTL.
2. the RTL depends to a lesser extent on the sample rate, but above all on the selected ASIO buffersize.

What I don't understand about your and your friend's explanations is what should be variable or change after a reboot. The times are fixed and depend on the sample rate and asio buffersize. There is no variance. Even the differences in RTL between USB, TB and PCI/PCIe based interfaces is very small with RME.

At the moment I have no idea what you are getting at. Never heard of R&DL. But maybe you can be so kind to explain it.

I haven't tested, but I guess latency might vary if one uses more RME interfaces that use the same driver. Say FF UC and FF UFX III. And once one uses the both, and other time former or latter.

I am just guessing..... Latencies may be different for each interface and if one connects FF UC driver reports its latency, if one connects FF UFX driver reports its latency. And if one connects the both? Probably the value of those two that is bigger....

Thank you for your replies ramses and Kubrak

Use case:
For parallel processing (so DAW wave file + 20% mix of heavy hardware distortion for example) this latency should be exactly the same everytime since other wise you have to ping all your FX hardware every time you restart your machine or (perhaps) your DAW/session. MIDI synths is something different btw, since MIDI is sloppy as hell. So we leave that out for now.

I believe this can manifest itself with just one interface already and with hardware FX. So for example Output 3-4 to input 3-4 to add a hardware stereo distortion in parallel. So if you use 2 convertors via ADAT and 1 via MADI - It could be even worse perhaps. But I am not sure. I am also if other RME users have run into these issues or not or if they have best practices to work around this behaviour (if RME has this ofcourse).

So if the claims are true then you need to reping the latency every boot if you are unlucky. Otherwise you end up with phase issues and you need to do a lot of manual editting for example. Anyway I have to test this myself as well and am just curious if this is really the case.

RME would know... If they have solved it with or over USB for OSX and Windows then they should use this in their marketing, as a lot of pros would love this. Perhaps I missed something, but didn't hear a lot about this term and just found out.

So it seems that only PCIe PCI and TB (which is PCIe) are capable of this repeatable and determinstic latency. Again, I am just curious if this is really the case since AVB isn't working like you want to and for Dante you have the same as well etc. Perhaps Ravenna is better - something that is being used by Merging as well and perhaps not without reason. But once again, would love to know more about this.

I had planned testing this, but so far it is - well - what I expected from RME - solid like a rock! I still wonder how RME has solved this then tbh. Could someone tell some more about it?

Reported RTL    Measured RTL    Measured RTL (ms)    Return Level    Noise Floor    Correlation Factor    Valid        Notes
332        333    6.938    -7.7    -116.4    20.5     True [RME analog o8 to  analog i11 RME]
332        333    6.938    -7.7    -116.5    20.5     True [RME analog o8 to  analog i11 RME] Reboot
332        333    6.938    -7.7    -116.4    20.5     True [RME analog o8 to  analog i11 RME] Reboot
332        333    6.938    -7.7    -116.5    20.5     True [RME analog o8 to  analog i11 RME] On/Off of UFX+
332        355    7.396    0.8    -99.2    54.7     True [RME via ADAT to Alesis AI3 -> o3 to RME i11]
332        355    7.396    0.8    -99.2    54.8     True [RME via ADAT to Alesis AI3 -> o3 to RME i11] Reboot
332        355    7.396    0.8    -99.2    54.7     True [RME via ADAT to Alesis AI3 -> o3 to RME i11] On/Off of UFX+

Some-more-added-details-edit:
Buffer: 128 Samples
Samplerate: 48K

Now where you delivered data, I also do

Patch cable on UFX III between AN3 IN and OUT, these are three RTL measurements using RTL Utility.
3x, then reboot of Windows 10 PC and again 3x measuring after reboot.

Result: always "static" values of 132 samples RTL and the same RTL of 2,993 which is being reported by my DAW (Cubase) as reported by the RME ASIO driver which contains these correct values so that a proper latency compensation can be performed by the DAW.

BTW this matches with the values from the RME driver which he reports to the DAW, from which I compiled this table below,
see also this blog article which I wrote to that topic:
https://www.tonstudio-forum.de/blog/ent … cts-en-de/

No need to thank me. I regard the guy highly as he has mixed countless hit records and really knows his stuff. But perhaps he never used RME.

edit: I was away for lunch and see that you guys have added important stuff as well. Many thanks ramses and mlprod!