My only Roon issues occurred when I used a Windoze based music server between the NAS & my DAC.
Since I was sending the files from the NAS through the server (CAPS 3) which acted as my Roon Control Point and on to the McIntosh D100 pre/headphone amp/DAC it was if the server's OS was kicking out the McIntosh driver's needed with Windoze to process the signals through to the DAC. I was constantly having to retrieve the driver's and reload them to the music server.
When discussing the issue with the Roon community and McIntosh it became a finger pointing fight and I stopped trying to get a definitive answer from either. Don't get me wrong...both have been wonderful at supporting their products but this one just didn't seem to have an answer.
Then one day I got a call from a friend who had the same CAPS 3 server that I had. I know his was identical to mine as we had built our servers on the same day, on the same bench, in his aircraft hangar.
He had also experienced the same issues with the McIntosh drivers on the server. Anyway, his server started to overheat and he pulled it from service to test it on that very same bench he had built it on. He read about the Raspberry Pi and decided to get one to use as a Roon bridge between his NAS & DAC. He installed it and was very pleased with the results so he recommended I do the same.
I got one, the V4 unit, took the CAPS 3 server out of the system and plugged it in. I moved my Roon Endpoint to my laptop. That little piece of Pi worked great! So now my signal path is:
NAS ===USB===>Wyred 4 Sound reclocker ===USB===>RP4===USB===>DAC.
No more dropouts or control issues or finding the server down after a Windows upgrade which always kicked the McIntosh drivers right out the door. The system is rock solid and stable.
