Registered Member
|
I have a problem since upgrading to v2.2.0 ... I can't remeber I've had the same problem with the previous release version.
I have an album (album A) with many tracks that are scanned but these tracks are not shown in the collectionlist because an other file (file B) is scanned first. This file B is shown in the collectionlist under album A, but when I look in the track details of this file, the album field is empty. I've read about issues with MusicBrainz identifiers, but I thought this is fixed in v2.2.0 ... I'm using v2.2.0 right now. Some things I've found out: - file B is a track that may've been ripped from the same album; - removing file B will make the collectionlist show all the tracks in album A again; - file B has an empty album field (not unknown, just empty) in track details; - changing the album field will make the collectionlist show all the tracks again; - scanning the collection when running "amarok --debug", I saw something with "[ERROR!] GREPME MySQL query failed! Duplicate entry". |
Registered users: Baidu [Spider], Bing [Bot], Google [Bot]