TagReader: Track number from ID3v2 not read (1 Viewer)

[hwahrmann]

Area: Media Portal Program
MP Version: 0.2RC2
Skin: Project X
Windows Version: XP Professional SP2
CPU Type: Intel Pentium-M
Memory: 1GB
Motherboard Chipset: AOpen i915Ga-HFS
Video Card: Intel Onboard Graphics
Video Card Driver: Latest Intel Driver
Video Card Resolution: 1024 x 768
Video Render Type: VMR9
Video Codec Type & Version: InterVideo
Audio Codec Type & Version: InterVideo
TV Card: PVR500MCE
TV Card Type: hardware
TV Card Driver: Latest Hauppage Driver

Synopsis:

The track number from ID3v2 is not being read at all.
This has been reported in
https://forum.team-mediaportal.com/viewtopic.php?t=11029 and
http://mediaportal.elite-squad.net/forum/showthread.php?t=263

I haven't found anything in Mantis, so i report it again. Apologize if it is already in.

Scenario:
A mp3 file has both ID3v1 (1.0, 1.1) tags and ID3v2 tags.
The Track number in the v1 tags is empty, but is set in the v2 tags.
The Track as delivered by the TagReader is 0.

When you use an ID3 editor, ID3-Tagit in my case, to remove the v1 tags from the file, then the Track number from the v2 tag is taken.

One interesting thing is, that if v2 Tags are present for Artist or Album, they are taken, even if the v1 Tags are different.

Only for Track number it seems the v1 Tags are honored.

 

[Taipan]

I can confirm that this problem still exists in the CVS of February 13.

The workaround I have used is to make sure that all mp3 files have the same information in both the ID3v1 (1.0, 1.1) tags and the ID3v2 tags. Its a bit tedious, but it does solve the problem....

 

[hwahrmann]

yes, i'm currently doing this workaround as well, but sometimes i forget and then i have the files of an album out of order.
probably, if i find some time this weekend, i'll try to fix it.

 

[Taipan]

i'll try to fix it.

That would be great if you could create a fix for this issue....

 

[hwahrmann]

found the error and submitted patch 1435798 to sourceforge.
Now let's wait for someone of the devs to intergrate it in CVS.

 

[Taipan]

found the error and submitted patch 1435798 to sourceforge..

That's fantastic - thankyou....

Now let's wait for someone of the devs to intergrate it in CVS.

It might be worth logging in to IRC and let one of the devs there know of the patch, so they can integrate it asap...

 

[SteveV]

found the error and submitted patch 1435798 to sourceforge.
Now let's wait for someone of the devs to intergrate it in CVS.

Thanks. I have applied the patch. The change should be in the next cvs build.

Steve