Core Machine (Operating system/System info/Roon build number)
Roon running on a dedicated Mac Mini.
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
REGA DAC via a HiFace 2.
Description Of Issue
Twice in the last week Roon has lost connection to the Zone it’s actually residing on.
I have to reboot computer to make Roon work. Tiresome.
Please advise.
Here are two screenshots. Please note that what has happened (twice) is that Roon loses the zone which contains the stereo. It still works thru SONOS. Also note that I have never had issues with the Hi Face 2. It is a very simple device. Rebooting the computer and Roon fixed the problem, but fearful it will continue.
If you are addressing me about this, the better way is a PM to the person who posted about the firmware.
I just supplied the link after doing a forum search on ‘HiFace’.
Also, it seems the OP of the link contacted M2TECH for the firmware update.
I would reach out to the HiFace manufacturer directly with regards to the firmware question. It seems like this could be device specific, so if you want to confirm that the DAC itself is operating as expected, I would try bypassing the HiFace and having the Core connected to the REGA DAC via a regular USB cable instead of the HiFace interface.
M2Tech got back to me and seems I already have 6.61, this means that firmware is already up to date. Happily the problem is not occurring frequently. Would be nice if a Roon rep added advice, although I do appreciate all the other users who have and will assist.
Thanks for checking the firmware version. The next step here would be to see what diagnostics say when this issue occurs. Can you let me know the exact local time + date when you next notice this behavior? E.g. 5:17PM on 9/26/19? Once I have this information I can enable diagnostics mode and check for any additional clues.
Thanks for letting me know the approximate timestamp.
I have activated diagnostics mode and what this action does is next time your Core is active, a set of logs will automatically be uploaded to our servers for analysis. I’ll take a look to see if there is any additional info contained on September 22/23 around 6:30PM.
If you experience this behavior again in the future, please do note the exact local time + date and let me know, as it would be good to be more precise when looking for timestamps. Thanks!