Search results

This is fully normal behaviour. The drivers need dampening. In open space they are undamped and swing out too much. Yes, others don't do that, but others also don't sound like they do.

From the manual: Note: Loudness works best in Auto Ref Level mode due to the seamless dBr scale of the volume control. Without Auto Ref Level active, manually changing the Ref Level will change the volume without changing the VOLume value (dB). As Loudness is referenced to a 'Low Vol Ref'...

The ADI-2 DAC does not use the 'PLL settings' you refer to. It has a dedicated SPDIF receiver and clock section (SteadyClock FS) that is the only relevant thing when receiving SPDIF signals, and works very different to ESS own SPDIF receiver (which we don't use).

The Hz increments follow usability and necessity. No one needs to dial in 10001 or 10002 Hz. And without bigger steps in the higher frequencies the knob must be turned endlessly to get to the desired frequency. Regarding PEQ gain - they are all identical at 0.5 dB steps. Where did you see 0.1?

The main difference between v1.3 and 2.0/2.1 is that the 2.x versions load the formerly (auto) saved state on startup. The files to load are C:\ProgramData\ADI2Remote\rme.adi2remote.main.xml and C:\Users\UserName\AppData\Local\ADI2Remote\ADI-xxxxx The first is about 1kB, the second about 46...

You wrote same problem on Windows 11. That is a dual-boot machine, or a different computer then? I wonder if there is any background task or service that causes this. It could be that if your Windows 11 is a copy of the Windows 10 install, with same tools, apps etc, and the same computer hardware.

Is that '3 to 4 seconds'? What about AV?

I like to hear that :) Ok, that the problem is solved too ;)

On the unit check that the MIDI port is enabled (Setup - Options - Device Mode / DSD, scroll down to MIDI Control). The firmware update might have reset this to off.

No way. Especially as we can't reproduce this nor know why it behaves like that on your system. You could temporarily disable the AV to check if that is related. Otherwise you need to post all driver and firmware versions in use, the exact model and OS that you use etc.

You are the only one to report this. I expect foul play from your Antivirus.

Begs the question - what is wrong with 2.1?

No plan. We are not the company that spits out changed units every 6 months. Instead you know what you get and often enough get some more even after years ;)

See here: https://www.avermetrics.com/averlab-specifications/

+1

For @weme.

@MC_RME will just point to the manual where we clearly made our point about power supplies. ;) Ground issues, a ground loop, or no ground aka leakage current issues, or leakage with wrong grounding - all this could be cured by a linear power supply. But this is noise that shouldn't be there and...

Never imagined our Bit Test could be useful for something like that :)

IMHO THD deeply buried into the noise (means in the FFT plot you can't identify the harmonics visually) should not give 'valid' THD results. For example lower level parts of the yellow curve could be dashed, so it becomes clear the shown value is whatever, but not clearly identified THD.

The 'Nihtila' does not have this usse, the (all) AKM ADC has. That is standard behaviour, very different to the ESS ADC.