Mistakes of this nature, which appear to be widespread, should not make it through. That is my point.
Roon donât need to reinvent the wheel, options exist already. Either effectively sift through the EA sub category, which seems incredibly inefficient and prone to error or have a more robust process, such as in app reporting with the option to attach logs.
That method does not need the user to know which version theyâre on, it should be reported.
Anyone who can send an email can generate a report of that nature.
I canât add any more to this thread, itâs in Roon labs court to resolve this. Itâs premium software, with a premium cost, the basics should be in place.
This is the crux of the issue. Itâs early access not aplha or beta testing, so attracts the wrong audience. IMO, alpha was a more considered and managed forum, that wasnât visible to the entire community. Evidently, this didnât work for Roon.
Furthermore, donât underestimate the pressure from the corporate gods and marketing on developers release updates and new features. Usually, theyâre tone deaf to âI told you soâ.
I donât know if they are all that widespread, but as I had already said before, it may well be too often. This LL one isnât exactly catastrophic, but we have seen worse (like the destroyed queue) that were really problematic and shouldnât have happened.
My point, though, is that everybody knows that it shouldnât happen, but everybody also knows that murders shouldnât happen and yet they do.
Itâs easy to agree on obvious basic stuff, but not as easy to find solutions that take the actual, practical scenarios into account, i.e., solutions that donât assume resources that donât exist and rely on user abilities that donât exist in big numbers.
I mean, you donât even want to take part in the easy EA stuff, which is fine, but then you suggest hardcore methods like the Debian Bugzilla.
Yes, but it still needs the user to provide a coherent and ideally reproducible case.
True. Small groups always suffer from limited coverage.
Several steps with increasingly bigger groups are good, but tend to make everything slower, and if itâs too show, users migrate to the EA- like channels and the problem is only moved any not solved.
Of course it does. We seem to have circled round to make obvious points. Some people will write gibberish and some will report an issue effectively, that will obviously happen in any scenario.
I donât know why this was even brought up.
Iâm done anyway, this has ran itâs course.
I no longer participate in EA as like @Grasshopper I find the process to be completely broken and feedback seemingly ignored. But I appreciate the pain others put yourself through to get things a few weeks earlier .
But I would be happy to have read only access to the EA threads/Category to keep up my reading and not being able to post, as I agree that it should be more focused. Seems a very reasonable idea to me at least.
But until we get it; I click the song in Shazam library, then click on Share Song, then Copy Without Link, then paste to Roon Search, go to desired result (if any) and finally add to Listen Later.
It doesnât take too long, but a direct feature in Roon would sure make it simple.
I have been using Listen Later daily. I stopped creating new release playlists every week and instead add new releases to Listen Later. I adore this new feature and thank you Roon team for implementing it!
Hello,
something different on this topic. I have my language set to German, can I get âListen Laterâ translated in some way so that it is consistent? Currently it looks like it was somehow âplantedâ.
Ok, thanks for the quick information.
I thought I had overlooked something because I assumed that the existing languages ââwould also be implemented with the rollout.
So Iâll hide it for nowâŠ
Translations are contributed by the community, so they are independent from software updates (canât delay an update until all participants have sent in their translations). I think they are updated online.
.