01-Jan-2017, 23:00
(This post was last modified: 01-Jan-2017, 23:07 by Hifi_swlon.)
(01-Jan-2017, 21:56)GuillaumeB Wrote: With all the new functionality coming with 1.3 I do wonder if my sT will be able to cope with it. Sometimes it can be a little sluggish with searches.
My Roon is up for renewal in April, and as much as I love the interface (I really do) I'm not sure if I will commit to another year.
What would really suit me would be Roon integration with Qobuz but I realise this isn't going to happen soon since Qobuz have designs of their own, in terms of owning the desktop. I find myself listening to Qobuz over 70% of the time and it is growing. Superb sound quality and wonderful music selections and suggestions.
I do find it terribly frustrating that these companies won't link up properly and ironically I suffer more dropouts with Roon than, say, AIR.
Happy New Year everyone!
Guillaume
Its not easy to troubleshoot these kinds of issues, but it would be a real shame if you had to lose Roon if you really like it.
My suggestion, would be to systematically isolate each component to see what it might be. My hunch is networking but whether it's the ST or totaldac or the remaining network is hard to isolate without doing it bit by bit. If you had another machine you could temporarily use as the rooncore server, that would at least hopefully tell you whether the ST is to blame and then it would be up to SGC to help you. If not do you have any other zones you could try in place of the total DAC? Since it's RoonReady and should've been tested thoroughly youd hope the issue wouldn't be there but in any case it means the Roon guys have it to test so I'd definitely contact Roon support.
I had some occasional Roon dropouts that were hard to diagnose but I had a hunch about the cause - it just took ages to get round to doing it. My hunch was partly right, and it was an OS X update I did (plus a funky thing going on with a raspberry pi which I hadn't guessed). Doing a fresh install of the OS cleared it up in general, bar one zone. And a reinstall of the pi fixed it there. I'm guessing the OS update had adjusted some networking thing somewhere but I never worked out what it was really. All I knew was I had a stable system for a year and then it went downhill shortly after I updated (which I never do usually - ironically I only did it to try AIR on a different OS to see if it fixed the issues there, which I didnt, it just broke a Roon). This isn't specifically helping you I know, but just saying it's worth going through the motions if you want to keep Roon.
1.3 round the corner has a lot of nice new features so it would be a shame to lose it now.
The Qobuz issue is annoying. I worked pretty hard rallying support to get Qobuz to do it (and to get Roon keener on the ideainitially) but it fell on deaf ears at the Qobuz end. I hope Roon work round it, there's always hope for 1.4.....
HNY by the way!
Just as an after thought have you tried adjusting the buffer for RAAT?
[actually that option doesn't seem to appear in my RoonReady settings on the rendu whereas it does on the raspberry pi's. Maybe this is hardware dependent for RoonReady? That's a shame. I might ask them if this can be exposed. ]
>>> 1st Place Award: Devialet, last decades most disappointing technology purchase. <<<