Yeah, from this point of view you are right, but OTOH I plugged my ROCK into my network 6 years ago and it worked since then.
That’s because I kept things simple (simpler than the limit of my knowledge) and consistent with how much effort I want to spend. I don’t have a complex, segmented mesh network beyond my understanding like so many do.
Again you are digging into TECH……..most routers will do DHCP out of the box - i mean do you really think that everyone that owns a smart TV knows how to do DHCP?!??! - I dont.
And it said no networking skills…..straight from the Roon page - DHCP is …networking..
Anyway - I feel we are going back and forth just for fun now.
Just know I agree with the original posts sentiments. (and you dont)
Exactly. And as long as this is not messed with, it just works, and there is not need to know anything in a simple network.
The problems with DHCP start only where people have two routers with both having DCHP enabled, or they apply static IPs on devices because they read this in an “audiophile” post without taking the necessary measures with the DHCP.
How do you think this can be avoided?
Like I said, sure it would be nice if everything just worked whatever people do, I just don’t think it’s a realistic proposition and nobody is proposing how to achieve it.
But Roon is not made for just people with nucleus + , its made for a wide range of servers and systems. Same with remotes and endpoints, they can be run on so many different systems.
To have this all work the system needs to be fairly complex and flexible.
Tidal (or any pure streaming service) have a much easier job with just pulling one stream from a sentralized server. Its not really comparable for what Roon is doing.