OK, now one more device tested for the purpose. Potentially would be very promising, giving four optical inputs, small and less expensive:
On Windows, automatic rate switching works between 44.1k and 48k rate families. But not between 1x, 2x and 4x rate factors, this engages rate conversion. Driver control panel displays the actual rate though, so the needed hardware functionality is there. So this behaviour is just driver limitation.
If someone manages to convince RME to update the ASIO driver, this would be another potential input device. Less than half the price of current other options.
If you need just automatic switching between 44.1/48, or 88.2/96, or 176.4/192 rates, this can do it already and provides 4 optical inputs.
This one has functional S/PDIF inputs and also loopback from both WASAPI and ASIO to ASIO. But unfortunately like so many other pro audio devices, has only fixed rate manually set from the control panel. Even though it’s clock can be slaved to the external S/PDIF source as well. Any non-matching input rate will go through rate conversion to the current operating rate.
What I have is an ITX small case with intel 13900k windows PC for HQPD, but no way to add RME HDSPE AIO.
After reading the posts from you and @dabassgoesboomboom, I did an experiment try to avoid RME windows driver problem for automatic rate sampling switch, by trying ADI-2 DAC FS → NAA 4.40 (Pi4) → HQPD 5.0.2 (windows) → NAA ( try with Mac NAA 4.31 and pi 3B+ with Dietpi NAA 4.40) → Holo audio spring 3 DAC
But when I try to save the setting, HQPD always become application unresponsive.
Is there something I did wrong? or is this way theoretically dead end?
Depending on your settings, it may take a while. Leave it for 10 - 30 minutes before declaring it stuck. And in case it is stuck, check the HQPlayer log file what is going, what is the last entry there.
That is wrong, can you check what has been set in settings.xml? (you can open it with Notepad)
I will check this part of the settings dialog code next week to make sure there is no bug related to this combination.
You may need to flip between the Input/Output Settings tabs, because switching backends for either side will trigger device rediscovery. So please doublecheck that the devices are still correct for both.