IME the requirement for a GUI software on a headless server is quite common. E.g. I needed to convert LyX files to PDF automatically on a headless server. I have always used Xvnc (part of TightVNC, debian package tightvncserver) with good results. If access to the GUI is actually needed, any...
The exclusive mode bypasses any volume control done by windows mixer. If its ouput has lower level than non-excl mode, then the windows mixer boosts the signal. It may do other things, depending on your DSP chain in the mixer.
Exclusive WASAPI goes directly to your soundcard, while shared WASAPI goes through the windows audio mixer with all its features and DSP, whatever is configured. Including volume control.
UAC2 is a protocol used by almost all modern USB audio devices which offer high resolution. The actual driver is the key. I do not know what driver miniDSP devices use - whether some Thesycon build, or their own make. They are large enough to afford their own driver.
The issue I was talking about was handled in linux - setting the cpufreq governor to "performance" (i.e. running at fixed maximum frequency), and setting the max frequency to something small. No idea if windows allow that. If yes, then likely in the Power Plan configuration.
Sync or async is unlikely to make any difference, async means the driver justs adjusts the number of samples per USB packet, based on feedback sent by the device. In fact async is slightly more work for the driver.
But the actual driver for Tascam & Focusrite could be the culprit, or with some...
Nice. Issues with latency when switching between power/frequency levels are quite common. E.g. on RPi switching to another CPU frequency has been measured to block the CPU for up to 4ms which is killing for low-latency audio. Therefore it is recommended there to run at full performance cpufreq...
That's a hugely powerful machine. It looks like some HW+SW issue with the USB controller. It will be interesting if Asus come up with something useful.
Well, 1.5ms DPC latency is still rather high, on such a powerful machine. Maybe some modern power management issue, something not waking up...
If that "exclusive" mode means wasapi exclusive, IMO there should be no clicks caused by separate clocks for each direction. But the clock difference could still be too large for REW, exceeding some inner hard-coded limit in REW.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.