![]() M +1 -1 tests/core-impl/collections/db/sql/TestSqlTrack. Was dropped should avoid surprising "Duplicate Tracks Found" errors. M +1 -1 tests/core-impl/collections/db/sql/TestSqlTrack.cpp M +0 -5 src/services/lastfm/ScrobblerAdapter.cpp M +0 -2 src/musicbrainz/MusicBrainzFinder.cpp M +0 -7 shared/tag_helpers/VorbisCommentTagHelper.cpp M +0 -6 shared/tag_helpers/MP4TagHelper.cpp M +0 -6 shared/tag_helpers/ID3v2TagHelper.cpp M +0 -6 shared/tag_helpers/ASFTagHelper.cpp M +0 -6 shared/tag_helpers/APETagHelper.cpp In various documentation need to be removed GUI: Mentions of MusicBrainz ids being useful for AFT (Amarok File Tracking) Was dropped should avoid surprising "Duplicate Tracks Found" you'll probably need to rebase your patch as I've touched * Problematic support for treating MusicBrainz ids as track unique ids The SqlScanResultProcessor should cope with changed track ids just fine. No comments on my mail inquiry, which I treat as a consent. Git commit 216c18bdaf18acf28e9ca98b115623934c9b4401 by Matěj Laitl.ĭrop support for treating MusicBrainz ids as track unique ids So I did the -newid on one of the tracks, and after it's done amarok shows me the same dialog box again, but it now only gives the mysql errors about duplicate entry when inserting into urls and tracks. I think the "loog" there should be "look". > perform the suggested investigation/remedy. > I've significantly improved that answer, please have a look at it now and > information, like it's the same album/track. I can perfectly understand if the files have identical > TroubleshootingAndCommonProblems#Duplicate_Tracks, but I think that's not They have the same musicbrainz_trackid (and musicbrainz_artistid), but different musicbrainz_albumid > This may be the cause of the problem - perhaps the same musicbrainz id is > I have several tracks that I have on multiple albums. After all the duplicate warnings it also gives a bunch of mysql errors about updates that fail, and I'm guessing that the tracks that are currently already in the database cause the problem. ![]() In my case, the problem remains: in mp3 files ID2. If I then do a full rescan of my collection, it gives me all thos errors. This is a big step towards compatibility between applications. I was using 2.6.0 which perfectly imported those tracks. Picard supports the majority of audio file formats, is capable of using audio fingerprints (AcoustIDs), performing CD lookups and disc ID submissions, and it has excellent Unicode support. But in this case the albums are different. MusicBrainz Picard is a cross-platform (Linux, macOS, Windows) audio tagging application. I can perfectly understand if the files have identical information, like it's the same album/track. It then points you to, but I think that's not really useful. This means that if I want to play an album it doesn't have all the tracks for that album anymore. Since 2.7.0 it now seems to only want to import one of those tracks. So you can see that it's the same recording, because that's in the metadata. They are all tagged using information from musicbrainz. I have several tracks that I have on multiple albums.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |