Created attachment 186378 [details] comparison of elisa, strawberry, amarok SUMMARY I have digitalised my CDs. One of them is "Vangelis - Blade Runner" Another is "Vangelis - Blade Runner: Blade Runner Trilogy, 25th Anniversary" which includes 3 CDs, one of them is the same in contents as "Vangelis - Blade Runner" The songs have been correctly tagged with MusicBrainz Picard, and show that they are different, one is CD1 out of 1 "Blade Runner", and the other is CD1 out of 3 "Blade Runner: Blade Runner Trilogy, 25th Anniversary" STEPS TO REPRODUCE 1. Scan the Local CDs 2. Display local collection "Album Artist / Year - Album" OBSERVED RESULT CD1 of Blade runner mixed up with CD1-3 of the Trilogy. EXPECTED RESULT Listed as separate albums SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 13 KDE Plasma Version: 6.5.0 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.16.12+deb14+1-amd64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Strawberry correctly shows them as separate CDs Elisa correctly shows them as separate CDs
Thank you for the report! This sounds quite surprising. I really can't figure right away why this would happen, but I'll try reproducing myself and inspecting at some point.
Created attachment 186804 [details] attachment-3564523-0.html Hi Tuomas, would it be useful to you if I provided those two digitalised CDs for the purpose of debugging? If so, please either let me know when you want to download it so I provide a time limited link, or a personal email address so I send the link just to you. Cheers, Marcos On Fri, 14 Nov 2025 at 22:01, Tuomas Nurmi <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=511453 > > Tuomas Nurmi <tuomas@norsumanageri.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |tuomas@norsumanageri.org > > --- Comment #1 from Tuomas Nurmi <tuomas@norsumanageri.org> --- > Thank you for the report! This sounds quite surprising. I really can't > figure > right away why this would happen, but I'll try reproducing myself and > inspecting at some point. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug.
Ah, my apologies, forgot to return to this one earlier. I tried building a scenario similar to the one you described, but didn't encounter the issue, so having known-to-be-problematic sample files would indeed be useful. So, yes please. You can send a link to tuomas@norsumanageri.org
Created attachment 188204 [details] attachment-694943-0.html Thanks, will do. On Sun, 4 Jan 2026 at 04:24, Tuomas Nurmi <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=511453 > > --- Comment #3 from Tuomas Nurmi <tuomas@norsumanageri.org> --- > Ah, my apologies, forgot to return to this one earlier. > > I tried building a scenario similar to the one you described, but didn't > encounter the issue, so having known-to-be-problematic sample files would > indeed be useful. So, yes please. You can send a link to > tuomas@norsumanageri.org > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug.
Thank you for the sample files! However, I am unable to reproduce the issue even with them (I tried on two systems, one with embedded database and one with a stand-alone mariadb server). Did you happen to have them earlier tagged under same album title? Amarok not picking up the (externally) changed tags and showing earlier ones from database/cache could be one explanation I can come up with. If that isn't the case, then I'm out of ideas. Anyhow, I guess you could try running amarokcollectionscanner -r . in terminal and seeing if the album info is ok in collection scanner output. If yes, then maybe try a full collection rescan (in settings -> database). If problem still persists, (this will reset the stats for the tracks, unfortunately) move the two albums away from collection, run a collection update (in tools menu), move albums back in place, and collection update.
Created attachment 188207 [details] attachment-841495-0.html Hi! Thanks for that. I run a full rescan under Collection Folders. It seems that that has fixed it. Thinking of what may have caused the issue, it is possible that I re-tagged the files with Picard MusicBrainz after the first time the collection was scanned. Do you think that's possible? In any case, thank you for your time, and thank you for Amarok :) Cheers, Marcos On Sun, 4 Jan 2026 at 17:54, Tuomas Nurmi <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=511453 > > --- Comment #5 from Tuomas Nurmi <tuomas@norsumanageri.org> --- > Thank you for the sample files! However, I am unable to reproduce the issue > even with them (I tried on two systems, one with embedded database and one > with > a stand-alone mariadb server). > Did you happen to have them earlier tagged under same album title? > Amarok not picking up the (externally) changed tags and showing earlier > ones > from database/cache could be one explanation I can come up with. > If that isn't the case, then I'm out of ideas. > > Anyhow, I guess you could try running > > amarokcollectionscanner -r . > > in terminal and seeing if the album info is ok in collection scanner > output. > If yes, then maybe try a full collection rescan (in settings -> database). > > > If problem still persists, (this will reset the stats for the tracks, > unfortunately) move the two albums away from collection, run a collection > update (in tools menu), move albums back in place, and collection update. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug.
Yeah, I think that's possible. Collection directories are monitored for changes (enabled as default), but reading the related documentation, there's probably many corner cases where especially changes in files (instead of creation/deletion) don't get noticed. But great to hear it's alright now! Closing this one. Happy listening!