Audio Settings Error - 2 computers listed as same device

[xxx (Banned - toxicity)]

@Stephen_Dixon

Out of curiosity what “unique ids” is Roon Core using for each machine?

As was in the above link -

A Roon bridge/DietPi trap for the too clever (or lazy)

It creates a UniqueID which is stored at the server level. So if you cloned it, your server is seeing all endpoints with the same UniqueID. This also applies to copying RoonServers as well.

@Stephen_Dixon

When you say to de-install and “Make sure you get all the Roon pieces” are you aware of what those pieces are.

For the Core, everything that’s in these folders -
https://kb.roonlabs.com/Database_Location

@Stephen_Dixon

Will also do a complete un-install on the new iMac which is running Roon Core too to see if this helps

You shouldn’t need to do this, but as long as you have a Backup then it can’t hurt.

@Stephen_Dixon

Can anyone confirm if the Roon backup files will contain anything I would not want to have put back after re-installing in this instance?

Yes, a Restore will put everything that you want back to where it should be, without causing you your present difficulty. If you are going to Restore then I would do that first, before you deal with the endpoints. Out of superstition, I would disable the endpoints before you reinstall to them, just to be sure you’re generating and using a new UniqueId. Of course, before you do anything always Backup using Settings==>Backups.

Here;s a couple of useful links -
https://kb.roonlabs.com/Backup
https://kb.roonlabs.com/FAQ:_How_do_I_move_my_Roon_library_to_a_new_computer%3F

@Stephen_Dixon

Presumably this would lose album’s I’ve added to my library through Roon from Qobuz though would it?

Your Qobuz selections are in Qobuz Favorites and that will repopulate Roon.

In an above post, @nuwriy seemed to imply that this problem was caused by something that Roon Devs were working on to change and that you had to wait for that to fix your problem, as least that’s how I read it. I think that the reference to the Devs was that they were going to change the process so that one wouldn’t run into this problem. You should be able to fix the problem without waiting for the Devs to change something. Is that true, @nuwriy?