Sound quality of Roon

Having read countless threads discussing digital sound quality, can anyone corroborate or counter what @blisshifi is saying? It seems to me the dac and speakers are the key factors in resolution not really anything else assuming bandwidth is flowing and adequate.

What do you mean by "bandwidth is flowing"?

And @sonicfanatic what exactly do you need corroborated? That the quality of a streamer / server will advance the quality of the final sonic outcome?

@jji666 wrote: Sorry but I couldn’t disagree more with this.  Roon is great but those who post saying they’ve never had a problem are just lucky.  Plenty of power users have had issues too.  If it’s a network issue, why does restarting the software resolve it temporarily?

Network issues can be very complicated.  I will admit, far more complicated than my networking smarts allow for.  Issues with TCP, UPnP, router IP conflicts and on and on.  As I was on the steep learning curve, I was having plenty of issues too.  I even had the guys at SGC try to figure out why I couldn't run their software consistently in the opticalRendu and we eventually gave up and I returned everything.  And they really know their stuff - far more than the average Joe, so that should tell you a lot.  I've since rebuilt my LAN with fiber optic, added managed fiber switches, new fiber router, PSU's, etc, etc.  And now Roon is ROCK solid (pun intended as I run ROCK via a NUC).  It doesn't disconnect, doesn't cut off the ends of songs, doesn't skip a beat or anything else unpredictable.

I *think* restarting Roon software/device temporarily refreshes the IP addresses and something (another device most likely) borks it down the road (it becomes conflicted).  But it's too complicated to have any certainty.

@audiom3 wrote:

Network issues can be very complicated. I will admit, far more complicated than my networking smarts allow for. Issues with TCP, UPnP, router IP conflicts and on and on. As I was on the steep learning curve, I was having plenty of issues too. I even had the guys at SGC try to figure out why I couldn’t run their software consistently in the opticalRendu and we eventually gave up and I returned everything. And they really know their stuff - far more than the average Joe, so that should tell you a lot. I’ve since rebuilt my LAN with fiber optic, added managed fiber switches, new fiber router, PSU’s, etc, etc. And now Roon is ROCK solid (pun intended as I run ROCK via a NUC). It doesn’t disconnect, doesn’t cut off the ends of songs, doesn’t skip a beat or anything else unpredictable.

I *think* restarting Roon software/device temporarily refreshes the IP addresses and something (another device most likely) borks it down the road (it becomes conflicted). But it’s too complicated to have any certainty.

I definitely agree that trouble-shooting Roon is a highly complex process. But it’s just not fair to say that nearly all problems with Roon are the user’s fault and usually due to their crappy network. True: many users that complain of problems have crappy networks (many are powerline! Yuck!). False: Roon is stable if your network is.

There are many ways in the way of ordinary use of Roon that cause it to tax itself to the point it piddles. Just do 15-20 searches in a row, adding tags to your search findings in between, then bring up a large tag and try to use focus on some of the tag results. It’s gonna choke.

Someone mentioned that having many open remotes also seemed to tax Roon. I’ve had my eye on that as a potential cause as well and there does seem to be some correlation.

I’m definitely not kicking Roon from a software design standpoint. I couldn’t do what I do with my music room without Roon. It’s brilliant in many respects. But that doesn’t make it stable.

AND, if it were the case that a restart of the core software temporarily refreshes IPs and other data that were causing problems, why doesn’t Roon just do that every so often?