B
bizzybody
Guest
Every time I have a later release of an album that’s had tracks added, it puts the additional tracks into the correct release and all the original tracks into an earlier release.
IE, the original release had 14 tracks but a later release added 3 “bonus” tracks for 17. So it splits them and I have to drag them to the correct one.
Apparently Picard cannot count. Is there no way to have it count how many tracks are in a cluster and process it like “There are 20 tracks in this cluster. It matches two releases. One with 14 tracks and one with 20. I’ll add them all to the 20 track release.” But nooo, it acts like “Track 1 matches this release, track 2 also does, track n… Hmmm, I’ve hit 14 but there’s still more. Track 15 matches this other version so I’ll put it in that one”. With that way of “thinking” it should go back to the previous tracks and re-assign them to the correct release.
But even after manually re-arranging the tracks, if I scan them again, it screws them up again.
Another frequent issue is Picard not finding the newer release with additional tracks, leaving the ‘extra’ tracks unmatched. But then I’ll search on the barcode or other information and there it is in the database.
1 post - 1 participant
Read full topic
Continue reading...
IE, the original release had 14 tracks but a later release added 3 “bonus” tracks for 17. So it splits them and I have to drag them to the correct one.
Apparently Picard cannot count. Is there no way to have it count how many tracks are in a cluster and process it like “There are 20 tracks in this cluster. It matches two releases. One with 14 tracks and one with 20. I’ll add them all to the 20 track release.” But nooo, it acts like “Track 1 matches this release, track 2 also does, track n… Hmmm, I’ve hit 14 but there’s still more. Track 15 matches this other version so I’ll put it in that one”. With that way of “thinking” it should go back to the previous tracks and re-assign them to the correct release.
But even after manually re-arranging the tracks, if I scan them again, it screws them up again.
Another frequent issue is Picard not finding the newer release with additional tracks, leaving the ‘extra’ tracks unmatched. But then I’ll search on the barcode or other information and there it is in the database.
1 post - 1 participant
Read full topic
Continue reading...