Track Number 0 Glitch

Due to a bug, the tagger can return a TrackNumber of 0. This is a CurrentProblem.

Cause of the Bug

The bug is triggered if more than one TRM match is found on an album. This is most probably caused by LazyUsers MisTaggingTRMs, and usually happens on very popular albums.

There are no known cases of TrmCollisions occurring on an album, though if they did, it would also trigger this bug.

Fixing the Glitch

The glitch can be fixed in the following way:

• LookupTheTrack in the tagger, and check whether more than one track is high-lighted on any given album.

  • If they are, delete the incorrect TRMs using RemoveTRMIDEdit.

  • If you are sure of the name of the track you are looking up, this should be easy.

  • If you are unsure of the correct name of the track you are looking up, compare the track times on the album with the length of your file.

• Lookup the file again, and the tagger should now return the correct TrackNumber.

• If it doesn't, check for more incorrect hits on the same album.

• If there are no more incorrect hits & you're still getting track number 0, please tell us, either by added a comment to bug number 834541, or via the MailingList.

Discussion of the Bug

This bug has been brought up several times on the mailing list, and is logged as bug number 834541.

The bug has apparently been fixed in an unreleased (as of Tagger 0.10.5) version of the client library.

CategoryTerminology Author: ZeroGravitas