Discography view truncates album titles making them indistinguishable (ref#K8UXK3)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· App interface looks or behaves oddly

Tell us what's going on

· The discography view truncates long album titles in a way that makes them indistinguishable when multiple albums share the same long prefix.

In these cases, the differentiating part of the album title appears at the end, but it is not visible due to truncation, so several distinct albums appear identical in the list. This makes it impossible to reliably identify or select the correct album. The issue is especially pronounced for series-style album names with shared prefixes, where the suffix is the only meaningful identifier.

Tell us about your home network

· this is a ui issue, not a networking issue

The names of the albums in the screenshot are:
At Home with Martin & Sylvia - Bonus
At Home with Martin & Sylvia - Fall
At Home with Martin & Sylvia - Spring
At Home with Martin & Sylvia - Summer
At Home with Martin & Sylvia - Winter

Hello @Casey_Link ,

Thanks for reaching out with your report. Can we kindly ask that you send us at least two of these albums so htat e can take a look at the text spacing from our end? You can upload to the below link and let us know once uploaded, thanks!

https://workdrive.zohoexternal.com/collection/nqcgjac23027d90a441bda2c314de49d7958a/external

I have uploaded it!

Hey @Casey_Link,

Thanks for sharing a few examples! After looking into this, we want to clarify that there isn’t a specific ‘bug’ at play here; rather, this is the standard behavior for title displays in this view.

We realize that while this works for most standard albums, it creates a challenge for edge-case content like audiobooks, short stories, and massive box sets where the titles are long and repetitive. It’s a fair point that the current truncation makes these items indistinguishable at a glance.

I’ve passed this thread over to our product team so they can keep this use case in mind for future design discussions. We appreciate you pointing this out!