A lifetime of audio players have trained me to think that exiting the app will also stop music playback. With Roon it doesn’t, so I often the exit/re-launch/hit pause/exit dance. (No, I am not learning with repetition!).
Suggestion: have an option in the Roon GUI for the close button to stop playback and close.
What would you expect Roon to do if it is playing music to multiple zones or if someone else in your household was playing music on another zone? Stop playback in all zones?
It should stop playback in the selected zone(s), if enabled.
I am the only Roon user in my home so I don’t know how it works in multi-user environments.
Even as a single user, you can play different music to different systems in your house with Roon. You can play different music to each system, or you can simulcast (group) multiple systems to hear the same music throughout your house.
So, what you are saying is that you see no need for the option I have suggested. That’s ok.
I do.
I think @DDPS is probably saying that such a kill option is unlikely to be adopted.
He’s just asking about your expectations because these are all valid use cases that need to be solved if your suggestion is adopted
Indeed. /10char
Nothing much needs to be solved. The option is set to “on” if it fits the use case for that end user, otherwise behaviour stays as is.
One can simply state “I see too many differing use cases for this work” without wasting time on tangents. Any feature request is, on average, unlikely to be adopted. Pointless pursuit of detail is irrelevant at this stage.
In my professional software development experience, one should get as much information as possible from the user at the time when they make a request. It may be impossible to do so later when the feature is chosen for implementation.
And that’s precisely an interesting expectation. You might just as well have said „the feature should be deactivated and the music should keep playing if there is more than one active zone“ for instance.
And there is your problem. A Roon system is not just and ‘audio player’, it is a client/server application. What you do with the client (Remote/Control or whatever Roon call it these days) doesn’t shut down activity of the server. It carries on doing whatever you told it to do. I, in common with many Roon users have a multi room multi user system. Roon’s behaviour is designed for just this type of use case. If you want just an ‘audio player’ then there are many that will behave exactly as you expect.
With all respect due to @Patrick_Morley I think this is something that makes Roon different.
A helpful analogy might be that you are running an email server in your home. You quit your email program, and you aren’t seeing new email anymore, but mail keeps coming in, and other people running other email programs in our house can still get theirs. Roon is like that; it allows for it.
I believe that @Patrick_Morley would like an option that enables him to quit a Roon Desktop application and to stop playing whatever the currently selected zone is in that UI when quitting. That might be the way to request it so that the Roon developers have everything they need to consider this sort of feature request.
Note that mobile apps are designed without quit menus, so there probably would not be an option on those platforms.
FYI @Patrick_Morley you do need to add your vote for your own feature request in the Discourse forums, even though that sounds somewhat brain dead. But don’t blame Roon for that! 