It works now, so you can skip to the ending if you wish. I will leave the individual talking points in for posterity.
>Can you link to the mainboard and the boards manual please?
https://www.gigabyte.com/Motherboard/Z3 … -rev-10#kf
https://download.gigabyte.com/FileList/ … 0219_e.pdf
>The GPU should better be placed into a PCIe 3.0 socket with 16 PCIe lanes (not 8).
I have done this now, still same problem.
>As long as you do not get audio drops too early, ok, but quite high.
>Did you measure an IDLE system and did you use High Performance energy profile?
I did measure an idle system, unsure of energy profile, will check now. Assume this is a windows control panel setting and not BIOS?
I did not have High Performance enabled, but it is enabled now. new measurements:
It seems that both moving the GPU to the correct PCI slot, and choosing the high perfomance energy profile has helped slightly.
>Your numbers are too high, wondering about your setup / settings.
>Are you sure that you choose the proper RME ASIO driver for the HDSPe RayDAT?
I have the HDSPe ASIO (Hammerfall DSP it is called specifically) drivers chosen in Ableton, however it seems i still have the Fireface UC drivers installed. Is this relevant in some way? Or perhaps i have installed the wrong drivers in my eagerness?
>I measured the input and output latency of RayDAT to be 2.2ms.
>Then maybe 1.05ms for AD/DA of the Behringer, then you have approximately 3,25 at 44.1 kHz.
That seems about right with regards to audio into the Raydat, but alas I measure 70ms when i send audio out and then back in from the 8200's
>On Windows and macOS you can measure with RTL Utility.
>https://oblique-audio.com/rtl-utility.php
This is interesting, RTL seems to imply that you are correct and there is something in the analog signal chain introducing the latency. Will investigate.
>Really wondering about your setup and how you measure, the values are IMHO far too high.
>So I have doubts that you use valid settings.
>You can compare with my numbers here for different products:
>https://www.tonstudio-forum.de/blog/ent … cts-en-de/
>Maybe you have FX in between (insert or send)?
The only thing in between is a Soundcraft GB4 mixer, it has no on board effects that can manipulate time or otherwise introduce latency.
1 of the Behringer units (ch 25-32) has a broken door (labelled out), could that be the culprit?
Another option is that Ableton introduces the latency. But as far as i can see all the relevant settings are correct. There is no driver error compensation and all the channels have 0 latency compensation as well.
However, there is a new button (i just updated to Ableton 12) I am unfamiliar with labelled "keep latency" that is enabled. AHA! I just disabled it on BOTH the relevant tracks (in & out) and now its is WORKING! 2ms latency! Sorry to trouble you for a stupid user error like this
Very happy i got to the bottom of this, as always RME is rocksolid. I wonder what that "keep latency" button actually does, will go read up on that.
Ableton says very early in the section about the "keep latency" toggle, that the correct setting for most use cases is to have it toggled off, i wonder why it is on by default then? Good job Ableton. As a final aside, i kept having trouble with just incoming audio not being on time, but after disabling "delay compensation" entirely in the options drop down now everything is smooth.
Only thing i wonder about now is whether or not my BIOS settings could be optimized, would appreciate any help in this regard as well if its not too much trouble. Thank you for guiding me through this Ramses, much appreciated!