Yah, but some things are so core to the foundational principles of the team and the product, that we can be sure without a doubt.
Roon’s pedigree comes with a 21 year history of trying to create an experience that takes the files out of music and avoid the mess that arises from protocols that were designed to solve a technology/interop problem while ignoring the user experience.
@danny, I completely get that. It’s great what roon is trying to do. But it’s a monumental task I can see you have all pinned your careers to. In the meantime there seems to be a need to explore options that fall short of repeated red lines in the feature requests.
I am not a technical person so the unfortunate choice of the word “interoperability” seems to have pressed a button that wasn’t intended. Maybe “co-existance” would have been a better choice. There seems to be many interested in finding out and exchanging experiences that fall far short of a feature request for UPnP support. That should be carefully moderated.
My use case is business travel. I am not technical enough for raspberry pi’s and even if I was, carrying around a sackful of them in parts of the world I travel to is not practical. I am curious what others are doing and exchanging my work arounds and experiences. There would be a lot very useful that comes out of those types of discussions for roon as well I would imagine.
I think something has been lost in the translation. I don’t think it is particularly off topic. It’s a good example of clarifying what the boundaries of a fruitful discussion falling short of a pointless red-lined feature request could be.
What is a good example of that? This is an honest question.
The pointless feature request is UPnP support. So far the discussion has produced 3 solution options. Two of them are alternative suggestions and one is a work around from me. They all fall far short of a UPnP feature request.
IMO that is a good example of the boundaries of a discussion where no UPnP support is a given. Unfortunately, my case has a few complicating factors so the two suggestions do not improve on my work around. It is possible others have other ideas. It is possible refinements of my work around would help a lot. For example, support for library merging.
I’ve split out the second tranche of off topic posts to their own new topic, that discussion should continue there.
Let’s stick to this topic’s subject without having the distractions of getting bogged down in specific use cases.
For that please use an suitable existing topic or if not extant please create a new one in Roon Software area.
Maybe it’s obvious based on my OP, but I would like to think that users are free to discuss desired features, even if the Roon team has said they’re not on the road map. Certainly not to beat a dead horse – that would be pointless – but for the the benefit of sharing workarounds and tools that might substitute, and also, potentially, for the possibility that a compelling use case comes up - that could result in the Roon team changing its mind or maybe a better idea comes up and that better feature is implemented.
My point is that IMHO, as long as people remain civil, there should be a substantial level of freedom of expression here.
Hi all,
what is the purpose of the Roon forum? That’s a very complex question and I don’t really know how to answer it. But I do know what I like best about our forum:
It usually doesn’t take long until you get competent help if you let your fellow Rooners or the support team know that you need it. Thanks a lot, everyone!
I especially like the music related threads, e.g. “What are you listening to now?”. 6.5k replies! That says it all! There’re tons of great recommendations every day! The only negative thing is that this can become quite a burden on your wallet…
Which is why Tidal is great as an add-on! Of course, if Tidal fails, Roon will be printing me a very long list of album titles I have to seek out on the used market…