When I add a Qobuz entry to my library, and then click on the star rating, the pop up window shows an incorrect value for my personal rating. It should be blank, but it shows the last value I assigned to any other entry.
Note the same problem happens when I go to change my personal rating for an existing Qobuz entry in my library. The pop up window does not reflect the current value of my personal rating for this entry, but rather the last value I previously assigned to any entry.
It feels like the pop up window, at display, does not pick up the current value of the star rating of the current item, but just shows the value the window was last used with.
I too tried to reproduce this behavior on my end but have not been able to do so. Is there any pattern to the affected albums? I tried to use 96khz Qobuz albums as per your screenshot, but no luck.
I assume you have also tried to close/reopen the Roon UI app, not just the server?
Strange! Therefore I have retested. It happens on my ipad for each and every entry in the library (that i have tested).
But on my Android phone (smaller screen) it does not happen . Due to the smaller screen the access to the star score pop up screen is different (thru the info screen). There the pop up screen is initiated with the correct (previous, library) star score.
Thank you for the thorough and diligent report @Jan_Stes. We’ll escalate these steps to development and notify you here if the ticket is confirmed in the pipeline.
Hi @Jan_Stes,
Unfortunately, we haven’t been able to reproduce this issue in-house. As @connor mentioned, we’ve escalated the investigation to our development team so they can take a closer look. While I can’t provide an exact timeline, please know that we’ll update you here as soon as we have next steps or more information to share.
Thank you for your continued patience and understanding while we work through this!
It doesn’t matter if this topic gets closed automatically - an internal ticket has been raised with development. If there is any news,@daniel will update you here in this thread as he promised he would.
Hi @Jan_Stes,
I wanted to share an update on your case. Our QA team has successfully reproduced the issue and documented clear steps for doing so—an important milestone toward resolving it. With this progress, our developers are now actively working on a fix. While I can’t give an exact timeline just yet, please rest assured that we’ll keep you informed as soon as there’s any news to share.
As @Geoff_Coupe mentioned, even if the thread auto-closes, your issue is safely tracked in our internal system and won’t be overlooked. Thanks again for your patience and continued support!
We’ll post here when the fix goes into testing, but you’ll also see the fix announced in Software Release Notes when it’s released into a public update.