This is for Roon to deal with if that is a problem as I think it is not a problem that users should worry about in terms of describing how they may like the system to work (I havnt hit this, but if its a bug - its a bug). If Roon think this FR has merit, I am sure they would make the underlying mechanisms support the usage better if required, or find another mechanism that can. That’s their responsibility that I trust them to own - not ours
I only mention tags as a concept that we are already familiar with, but please don’t take it literally to mean must use tags system - really - just whatever N:1 concept works. It is not our place to say how the internals of Roon should work, just ask for how we might like the external observed behavior to work.
I think you are also taking a single phrase out of the post as a means of dismiss it all My point is the existing behaviour is still desirable, but I also agree with the original feature request concept of having some means of separating the experience for each user in terms of what portion of a whole that they interact with (physically separate libraries is an implementation detail that is maybe not for us to care about).
And you are right - as a work around for those who wish to do so right now - to libraries, two cores, two account etc is the way to go today. That is not a reason to dismiss they way it could work (if licensing issues allow for this - which they may not). However, that is a hard separation, and I dont think that is an ideal for a family either.
Anyway - my post was intended an illustration of external behaviour to give segregation for users in the context of some other related issues that could be solved by a single approach. It is not intended as a dictate for how it should be implemented. As such, I think it belongs here, not as a separate FR, or maybe you think this FR is only asking for a means of hard segregation? If so, then maybe this is different and more general? Thinking about it - maybe I don’t have a view either way
Maybe if you moved this part of the thread - it would end up without context and thus be hard to read.
I would suggest the FR is renamed as N libraries (for a family) rather than two (for a couple), but I think we can understand that the concept equally applies.