Force Core or Satellite PC to re-scan Audio devices for hardware changes in satellite PC

Good morning,

I am facing a common problem, and I believe this should not happen on a software as robust as Roon.

I have a machine running the CORE and several “satellite” endpoints, one of which is a Windows 11 machine.

I had to reinstall the “satellite” machine, precisely because if have new hardware, including a new Audio Interface.

When I installed Roon on that machine, the Audio preferences of the Roon Server still lists my OLD Audio devices, including ASIO Drivers which are no longer installed on the machine.

I’m assuming that this spawns from the fact that I have fixed IPs on my network, an my Machine has been assigned the same IP, but the hardware infrastructure is COMPLETELY different. Clicking on the “scan for devices” button on the Audio preferences page takes a fraction of a second and does absolutely nothing.

This has happened to me before, can’t really remember how I fixed this, but this shouldn’t be such a difficult task. I’m assuming this happens often. Roon needs to do a better job at “knowing” which devices it has available.

How do I “force” either the core or the satellite PCs to detect the new ASIO drivers correctly?

Thanks for any input,
Rafa.

Hi @Rafael_Polit,
Thanks for letting us know about this issue. I will bring this to the rest of the team to look into. In the meantime can you upload a screenshot of your audio settings in Roon?


The NuPrime ASIO Driver was from the previous installation, it is no longer installed in the system.

Hi all, we’re going to put in a ticket for this with the team. However, I cannot comment on any timelines.