Sorry Uwe I didn’t get your point.
I don’t want to install 2 instances of the Roon Server, it’s a non sense from my point of view.
That’s why Roon Bridge was designed (as I understood), to expose local audio devices to the Roon Client.
That’s right, but if the bridge it does not work, the server or core with everything would be a try, the 2nd server must never be activated and always remain only the one selected. It’s just more functionality and flexibility on all machines for later tasks or current problem workarounds.
It would be good if the team comments, but there is a lot to solve and queues.
Yes, indeed that is why RoonBridge was developed. While not official support, there are some other points of information that might be useful for support when they engage.
If you enable any of the other non-Meridian outputs on the PC, like system output, do they enable and produce audio. That will let Support know if the issue is limited to only the Meridian device.
Roon can fail to engage/enable a device that might already be engaged by a different program. Is there any other software on that PC that might be grabbing the device prior to Roon? This can be other audio programs, streaming applications, HQPlayer, etc.
I noticed the Encore ASIO driver, what device is that for?
I would also add these exceptions to any Antivirus or other Firewall blocking applications you may have and ensure that you connected to your network via a Private network, not a Public one, see this guide for more information.