I wanted to ensure that responses from the Roon team are easily accessible in one thread; it is hard to keep up to date on every topic/issue.
I am limiting the list to only show issues that are either being investigated by Roon, or are actively being resolved.
I will not be including issues that are effecting a minority of users which will require technical support specific to their control/core/endpoint/networking setup, but focusing on functionality/behaviour that could possibly effect all users that will either be restored or improved.
Please report issues or request new features in the appropriate forum category:
Making use of the forumās search functionality often avoids reposts of similar issues/requests.
Having a problem? Got a question about using Roon? Weāre here to help!
Post your suggestions for features here!
Please contribute as and when members of the Roon team post responses to issues not listed below. Thank you!
////////////////////////////////////////////////////////////////////////////////////////
An exception to the 1.8 scope limit, this bug existed pre-1.8:
Apologies for the continued trouble here, everyone. Iāve passed these reports along to our team for further investigation. We appreciate everyone reaching out with this feedback and weāll be sure to follow up here when we have more information.
Restoring functionality/resolving bugs
Hi @Jan_Terje_Hansen
Thanks for reaching out to us, we appreciate it! We have a ticket open for this issue and will be investigating further. You have our apologies for the trouble.
No need to escalate folks ā weāre investigating.
If youāre seeing this, please let us know which artist youāre having this issue with, exactly what youāre seeing on Overview vs Discography, and whether you use a streaming service.
Thanks all!
Hey @Serkan_Kuyumcu ,
Thanks so much for reporting what seems to be a bug. Our technicians will follow up on this.
In the meantime, could you please clarify if this happens for any track you ban, or just a specific one? Could you please share a few examples of tracks?
Thanks in advance
Thank you for the report, @Andreas_Philipp1 , we have an open ticket in about this issue.
ā
Ivan
Hello All,
Thank you again for the reports.
I wanted to touch base with some good news, which is that our technical team has been able to reproduce this behavior and weāve opened up a bug report with our developers.
While I canāt say for certain when this bug will be fixed, getting things reproduced in-house is a critical first step, and I will keep this thread up to date as the team passes along feedback and work begins to get this resolved.
Thanks again for the report!
Hey @bbrip ,
Thanks a whole lot for following up on this. Sorry for the delay in acknowledging - on the same day you posted this was brought up. Weāre looking into it and weāll follow up
Thanks for the feedback, @bbrip ā Iāve passed this along to our QA team for further investigation.
Hi everyone ,
I wish we would have seen and replied sooner to this thread - Iām sorry you are all affected by it. Iāve notified our team about this and weāre looking into it.
Please, bear with us while we get back to you with updates
Hi @bbrip ,
Thanks for raising awareness about this - and sorry about the trouble. Thanks @Weirdomusic , @Andre_Gosselin and @Juan_Piedrola for chiming in.
Iāve notified our team about your findings. Weāll follow up as soon as we have any insight to share
Composer tags:
Thanks for the further details here, @KML
Iāve passed this along to the QA team for further investigation.
Classical genre page:
Yeah, itās implied on the composer page but we should definitely be showing the composerās name when itās not part of the context.
Weāll get that fixed, thanks!
Artist page>Overview>Sort:
https://community.roonlabs.com/t/how-does-roon-1-8-sort-albums-with-the-same-release-date-in-overview/142466/5
iOS>Scrolling and App foregrounding issues:
https://community.roonlabs.com/t/jerky-scrolling-and-white-flash-for-sensitive-ones/144636/3
iOS (iPhone):
Wow! It looks like you have given this some thought. Thank you @SimplicityCompass . Iām at a point where I canāt not see things as you do.
Letās see what our team has to say about it
Android>Roon Radio>Skipped track feedback popup not appearing:
@RoonQA , please take a look. I would expect this on both platforms.
Limited offline functionality:
Hi @Vadim_Lvov
We appreciate the feedback here. I just wanted to let you know the team is looking into this.
Feature improvements:
We have some improvements planned in this area, to ensure we get the face properly centered in various views.
Not quite ready to say more, but weāre aware of the problem and have a plan. Stay tuned!
This is a feature that we are not too happy with. We built it very quick and dirty just before our launch in 2015 and never really revisited it. It returns some pretty weird results sometimes and is not on par with our other discovery features today.
We decided not to remove it from the product because we know there are fans of the screen, but we arenāt looking to attract new users to the feature, so we gave it less prominent billing than before.
I think at some point we will give it some realā¦
Artist>In Their Prime>include both local and streaming albums:
This is great example (qobuz + local content), we are looking into this now.
Thanks @Xekomi and others
I believe Valence driven recommendations are subject to ongoing improvements, but keeping these in the list:
Classical genres>āTop Composerā recommendations:
Classical compositions>āTop Performerā recommendations:
Just as one of many, many examples have a look at this:
Composition: 24 Preludes for piano Op. 28 by Chopin. I get a few pianists lsited as āTop Performersā. They are totally āat randomā. No idea who considered those as āTop performersā.
I also get a trumpet player !!! Now thats great. Never heard these preludes being performed on a trumpet. Do you need more examples? Could you pls fix this or just put this āfeatureā on hold until it really works. Many Thanks.
[IMG_0008.PNG]
Improving Roonās recommendations for artistsā top tracks:
Hey @GoldenSound @Martin_Zupancic ā it would be great if you guys could give me some examples of artists where youāre not getting the top tracks you expect. We did some analysis after these initial posts and I definitely agree that thereās room for improvement.
A few examples of where you feel like our lists are coming up short will be helpful as we work on improving these recommendations.
Thank you!
Housekeeping Tasksā¦>:
Check on Monday:
Release Notes
Hi all!
First, we just want to thank everyone for all the interest in Roon 1.8!
Weāve been overwhelmed by the positive response weāve heard from thousands of you, and weāve also been intently reading everyoneās suggestions for how we can improve Roon in the future.
Wide-ranging design changes to an application like Roon can be extremely complex, and our design team and developers spent countless hours working to ensure the changes didnāt affect critical functionality, or overwhelm the music tā¦
Hi all!
Weāre hard at work on our next round of improvements, but a few smaller bugs were resolved over the last couple of days, and we wanted to get these fixes out to everyone immediately.
Improvements to Focus and a few other areas are underway, so thanks again everyone for all the feedback and kind words about Roon 1.8!
The Team At Roon Labs
Roon 1.8 (Build 764) Release Notes
Roon Build 764 is now rolling out for macOS, Windows, Windows (64 Bit), Roon OS, and Linux.
Updated versions of ā¦
Hi all!
The last few weeks have been a whirlwind, with some of the best feedback (and sales) weāve seen in the history of the company. Not only are more people using Roon, but people are listening to more music every day, discovering more music than ever before, and participating in this community at never-before-seen levels.
In a user interface āredesignā release like 1.8, we are making thousands of changes at once. It can be very difficult to predict the handful of changes that will cause prā¦
4 Likes
The original topic is now closed, please post feedback from the Roon team in this continuation topic.
*After 30 days posts are no longer editable (this has effected the original topic), so I have created a new topic to continue the list.
All the listed issues in the original topic have been transfered to this topic.
Thanks to @andybob for helping.
1 Like
This one is missing from the list. Last update is some time ago. I guess the fix is still hanging somewhere in QA.
We have a fix in QA now, along with a lot of other post-1.8 changes/improvements. Once they have all been stabilized, we will ship it.
Update, fix is around the corner (finally)
Apologies for the delay here, everyone. As Brian mentioned, this issue was in QA along with a number of other changes. We know people have been waiting for this fix, and weāre feeling confident the next update of Roon will ship soon, with a fix for this issue. Thanks everyone for your patience!
⦠And fixed.
Thank you to everyone who has reached out about this issue, and for your patience as weāve worked to get this resolved as quickly as possible. We are happy to announce that Roon 1.8 (Build 778), which includes a fix for this issue, is now available.
Please update and if you have any issues donāt hesitate to let us know!
You can take a look at the release notes which includes many other fixes and improvements here:
1 Like
Thank you.
I am aware of this issue, but Iāve not added it to the list as, to my mind, the issue concerns a specific Roon configuration.
I realise the definition is somewhat blurry: for example, Iāve included issues effecting iOS and Android remotes. But options for types of remote devices are limited in number, and more than likely most users will have access to a smartphone or tablet.
However, your post itself serves to highlight Roonās response to the issue.
1 Like
Yeah, except the problem isnāt specific to ZFS. Just the majority of the people triggering that bug are using ZFS because it is the best way to handle big data storage in a reliable way.
If youāre going to build a list of major bugs for the current version, you should probably populate it with all of the major bugs. Just because your use case doesnāt involve you doing advanced data storage techniques doesnāt mean other people arenāt.
Just to be clear, āmy server canāt see local storage even though it has worked perfectly for multiple yearsā is in a wildly different class of bug than than āthe phone remote app is derpyā.
Edit: Sorry if I come off as harsh or jerkish. This particular bug has been pissing me off for 35+ days.
2 Likes
Hi, Dean.
The main purpose of this topic is to highlight the responses of Roon team members to issues with Roon 1.8. I created the topic over a month ago, when some users believed that Roon were not responding to issues, mainly because it was hard to keep up with the volume of posts/topics at that time.
The post linking to the support topic itself serves this purpose, and if just one user who is effected by this issue and who wasnāt aware of that specific topic, sees the post and understands that Roon is working on resolving the issue and posts their experience, then that is good in my book.
I have no intention of playing down the importance of the issue, nor the impact on effected users. I understand those effected have been waiting a long time for an update. I hope that it is resolved very soon.
The list isnāt meant to be a list of all major issues, but limited to the areas I roughly defined in my OP. I understand why you disagree with the issue being excluded from the list, but from my perspective, I am only aware of around 20 posters on that topic who are effected, plus one other who posted a seperate support topic, and was linked to the existing support topic.
Of course, more users will have been effected - I very likely have missed other topics on the issue, and not everyone effected will post to the forum.
The list, however badly you feel I have collated it, is not based on my own use-case.
As Iāve said, I totally understand your frustration, and I really hope you and all the effected users can get back to enjoying Roon as soon as possible.
1 Like
andybob
(Andrew Cox)
March 16, 2021, 11:20pm
9
Before posting in this thread, ask yourself the following question:
Does my post link a response by Roon staff to a 1.8 issue ?
If yes, post away. If not, donāt post in this thread, your post will be deleted.
3 Likes
bbrip
March 19, 2021, 5:02pm
11
@SimplicityCompass one to add to the list, please. this has now also received recognition by Roon staff.
Just as one of many, many examples have a look at this:
Composition: 24 Preludes for piano Op. 28 by Chopin. I get a few pianists lsited as āTop Performersā. They are totally āat randomā. No idea who considered those as āTop performersā.
I also get a trumpet player !!! Now thats great. Never heard these preludes being performed on a trumpet. Do you need more examples? Could you pls fix this or just put this āfeatureā on hold until it really works. Many Thanks.
[IMG_0008.PNG]
1 Like
Thanks @bbrip .
Added [tagged as: āreport is inā]:
Just as one of many, many examples have a look at this:
Composition: 24 Preludes for piano Op. 28 by Chopin. I get a few pianists lsited as āTop Performersā. They are totally āat randomā. No idea who considered those as āTop performersā.
I also get a trumpet player !!! Now thats great. Never heard these preludes being performed on a trumpet. Do you need more examples? Could you pls fix this or just put this āfeatureā on hold until it really works. Many Thanks.
[IMG_0008.PNG]
andybob
(Andrew Cox)
March 23, 2021, 12:53am
13
Build 778 has been released. The Software Release Notes describing changes are here:
Hi all!
The last few weeks have been a whirlwind, with some of the best feedback (and sales) weāve seen in the history of the company. Not only are more people using Roon, but people are listening to more music every day, discovering more music than ever before, and participating in this community at never-before-seen levels.
In a user interface āredesignā release like 1.8, we are making thousands of changes at once. It can be very difficult to predict the handful of changes that will cause prā¦
2 Likes
The nice part of maintaining this listā¦
Removed:
Good catch ā this used to be clearer. Weāll get it fixed.
Yup, we have a fix in testing but it wasnāt quite ready to ship this week.
But itās definitely coming ā thanks for your patience!
Weāre still working on Focus, so the latest changes havenāt gone live yet, but weāll have a look.
@RoonQA please have a look ā some of this is fixed, but Iām still seeing the Import Date heat map issues when comparing Albums vs Tracks.
Thanks for letting us know @Hazen !
Thatās reasonable feedback. Iāll make sure that the product team discusses it.
I think @Geoff_Coupe was talking about the Discography view on the Artist page.
If Iām understanding correctly youāre talking about the album page here:
This is good feedback and we appreciate it. The āselected discographyā feature was designed to give you a chronological overview of the artistās career, so you can see what they released right before or after the album youāre looking at, and get a sense of where the album fits into their career.
Itās designed to provide context, but weāveā¦
@Duckworp , I appreciate you putting that into words. It will now be taken into account by our technical and QA teams as they approach this issue.
Thanks, @Serkan_Kuyumcu ā Iāve passed this along to the QA team to investigate. Can you confirm what kind of device youāre seeing this on?
4 Likes
Iām also going to remove these issues:
We are looking into a quick fix for this. We have some ideas.
Improvements to handling of conductor/performer + composer:
I see some improvements possible with split-personalities like Bernstein. The missing ācomposersā filter criteria feels relatively simple to work out. Weāll take a look.
Artists like Bernstein are tricky to pick apart automatically. There are a lot of people that appear to meet the criteria of being both conductor/performer + composer as a result of one out-of-character recording or some inaccurate metadata, so there is a balance to be struck when defining data-driven rules. In any system like ā¦
But note that the new Match All/Any logic has highlighted inconsistent behaviour:
[image]
[image]
Look at these two screen shots⦠The selection criteria seem to look the same, right? But the results they give are very differentā¦
In the first case, both criteria are tags - one for albums by the label āBISā and the second for albums with āString Quartetā. Both tags combined are interpreted as a logical āORā⦠show me all albums tagged as āBISā OR albums tagged as āString Quartetā. I can see no option to comā¦
Added:
Hi @Jan_Terje_Hansen
Thanks for reaching out to us, we appreciate it! We have a ticket open for this issue and will be investigating further. You have our apologies for the trouble.
No need to escalate folks ā weāre investigating.
If youāre seeing this, please let us know which artist youāre having this issue with, exactly what youāre seeing on Overview vs Discography, and whether you use a streaming service.
Thanks all!
And linked to the most recent response from Roon re: the non persistent scrolling position:
Apologies for the continued trouble here, everyone. Iāve passed these reports along to our team for further investigation. We appreciate everyone reaching out with this feedback and weāll be sure to follow up here when we have more information.
2 Likes
The loss of the āhide albumā feature with the launch of 1.8 has been fixed with the March 21 update. Thanks
2 Likes
Already removed from the listing, but thank you for the secondary confirmation.
bbrip
March 24, 2021, 5:25pm
20
One to add to the list of recognized bugs:
Guys, / @support this shouldānt really be so hard to fix. I even provided you some code / logic before for this:
Again, it should take no more then a handful of lines of code to fix this:
If Tag = āComposerā, THEN >>> Composer!
If Tag = āTextā OR āPoetryā OR āLyricsā OR āLibrettoā THEN >>> NOT Composer !!
I still get Librettists listed as Top Composers for Opera. Could you please finally get this fixed once and for all.
Thank you
1 Like
bbrip
March 24, 2021, 5:53pm
21
And another one, addressing the malfunctioning āOnly complete recordingsā setting and missing counters for single albums in a library.
Thanks for the feedback, @bbrip ā Iāve passed this along to our QA team for further investigation.
1 Like
Removed:
Thanks, @jtnt ---- Iāve passed this along to the team to investigate further.
It seems from a recent post, Roon are regarding the back button appearing outside of the menu as a bug:
We are still working on this ā itās not being ignored but it wasnāt ready on the same timescale as a number of other fixes we didnāt want to hold up (like the ZFS storage fix).
The issue here was that a long translation string was pushing the back button off the screen. In other words, this was a bug fix not a design change.