Created attachment 160732 [details] Screenshot of directory structure SUMMARY Albums with multiple discs, where each disc is its own sub-directory, e.g. `album/disc 1 - lorem ipsum/1.01 title.mp3` `album/disc 2 - dolor sit amet/2.01 title.mp3` etc. appear to be considered unrelated albums by Elisa and appear multiple times in album view, once for each disc in a sub-directory. The album artist tag seems to be ignored in this scenario. This becomes quite the problem the more discs an album has. No other music player on Linux exhibits this behavior; I compared this to Lollypop and GNOME Music, both consider it one album, despite each album being in its own sub-directory. STEPS TO REPRODUCE 1. Put a multi-disc album in the library folder of Elisa 2. Have each disc in its own sub-directory 3. The album appears multiple times in Elisa's album view OBSERVED RESULT Each disc appears as separate album entry in album view EXPECTED RESULT One album entry with multiple discs, no matter the underlying directory structure SOFTWARE/OS VERSIONS Linux/KDE Plasma: Tuxedo OS 2 (Kernel 6.2.0-10018-tuxedo) (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Putting all files into a single directory makes Elisa group them into one album. However, sub-directory structures shouldn't matter if the tags
Created attachment 160733 [details] Elisa splitting the album into multiple entries
Amendment because I derped on the description: SUMMARY [...] I compared this to Lollypop and GNOME Music, both consider it one album, despite each DISC* being in its own sub-directory. ADDITIONAL INFORMATION [...] However, sub-directory structures shouldn't matter if the tags for album artist are present and album name matches across tracks/discs
The issue still persists as of version 24.02.1
Thank you for the bug report! I think this is already being tracked in another issue, see the linked one. If you feel that the other report does not adequately capture your request, feel free to reopen this one. *** This bug has been marked as a duplicate of bug 422507 ***