The whole point is Roon evolves based on suggestions like this. If you come across an issue/idea, be part of the solution to make Roon better.
On the other hand, it’s hardly rocket science to work out what is going on.
My purpose for posting was just as you suggested in your first sentence.
Regarding your “hardly rocket science” statement. I agree once known, it’s not rocket science. In fact, once known, nothing including rocket science, is rocket science. That’s why this sort of issue needs to be viewed with neophyte eyes, not experienced ones.
So, we’re obviously in agreement that the Radio On isn’t rocket science. However, still there are posts here about the very thing that isn’t rocket science! What is the benefit of forcing a new user to expend their time to research or post about something we agree isn’t rocket science? How many newbies are startled and confused by the Radio? Why, because someone assumes the radio function is used more than it isn’t!? Even if this is a fact, rather than an anecdotal assumption, that’s still not a reason to keep it as a default.
Along with performing maintenance and adding new features, I would think that the ROON Team would be concerned with securing new clients. As I mentioned, defaulting software to perform something totally unexpected, is not a good introduction to ROON. It provides frustration for zero, nada, zilch benefit. Why frustrate a new user or any user for that matter with a default that shouldn’t be?
A satisfactory fix for ALL may be to provide not only an on/off Radio toggle (defaulted to OFF), but provide a 3rd. option to force the Radio to be on, no matter zone changes or anything else, until its again turned off. Wouldn’t that simultaneously satisfy Radio users and non-users alike; but more importantly, not irritate new users with a: “huh, what’s happening” moment, when unselected tracks begin playing? A “rocket science” level of knowledge is unneeded to conclude that any level of pissing-off potential customers is unacceptable.
Radio use vs non-use may be a variable that can be measured, I don’t know. But it’s impossible to measure the frustration level experienced by new users due to these sorts of (non-rocket science; read the manual) decisions.
Will, or does the Radio On frustration rise to the level of preventing a purchase, who knows, but why take that chance? What could possibly be the benefit of defaulting the Radio to on, compared to adding a level of frustration; with the potential result being the loss of a new ROON customer?