Help - Search - Members - Calendar
Full Version: ID3v1: Tracknumber should be an unsigned byte?
Hydrogenaudio Forums > Hosted Forums > foobar2000 > Support - (fb2k)
d0ggie
Hello,

It seems that Foobar2000 (0.9.4.2) interprets ID3v1 (v 1.1) tracknumber as a signed byte instead of unsigned byte. Therefore when no other tagging format is available any tracknumber larger than 127 will be displayed incorrectly. (Naturally tracknumber can't be any larger than 255, but that's not my point here.)

Eg. 0xC9 (<11001001>) becomes -55 even though it should be 201.

It also seems that when MP3 tag type is converted (using Tagging > MP3 Tag Types -function) from ID3v2/APEv2 to ID3v1 tracknumber disappers if it's larger than 127 (but less than 256). (Probably due this issue.)

Naturally ID3v1.1 isn't too well documented (unlike ID3v2), but I guess there are more usage for tracknumbers from 128 to 255 than tracknumbers from -1 to -127.
bit4bit
I've the same problem with tracknumbers >127 using ID3v2.4 Tags. Track 128 becomes -128, 129 -> -127, ..., 146 -> -110 and so on. This is not a major problem but should be fixed.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.