19-May-2016, 13:30
(19-May-2016, 12:45)SwissBear Wrote:(19-May-2016, 12:31)Hifi_swlon Wrote:(19-May-2016, 12:28)hk6230 Wrote: Now that's not good, getting another device to solve one device's problem.
You read my mind.
Although technically it would be getting a device to solve another devices problem which was bought to solve another devices problem.
Plus I could have just bought a Mutec in the first place!
Well, the Mutec could have done it, although Antoine seems to like his µRendu + Mutec combination better than the Mutec alone. But Mutec is pro-audio, not designed by Jesus, not that much fun and buzz as your µRendu. So if you want the fun and the stability, there is only one way to go
Steve - I did respond to your post on this over on CA. I honestly have not experienced this and I know I've started Roon playing only then realizing I forgot to wake up the Dev and set it to USB source. Is USB your default on the Dev? Mine is not. I simply had to stop and start Roon playing after getting Roon to wake up and set to USB source - it would then play fine.
Does the problem ever occur if the Dev is awakened before starting Roon or only when the Dev is asleep with Roon starts playing? I think any solution that requires rebooting the uRendu each time is a bad one and having to buy yet another piece of hardware seems like a pricey bandaide.
Out of town until next week so I can't dig deeper until then.
Devialet 440 Pro (two 220s)- Oracle CD transport - Kuzma Stabi S/Stogi S turntable - Von Schweikert VR-35 speakers - JPS SC3 SCs - PI Audio power conditioning -
Triode Wire Labs ICs and PCs - Roon on NUC 8i7beh running ROCK
Triode Wire Labs ICs and PCs - Roon on NUC 8i7beh running ROCK
Durham, NC USA