- This topic has 2 replies, 2 voices, and was last updated 15 years, 7 months ago by
.
-
Posts
-
An album I added to my library this week (and only this album) has the song lengths stored in the database WAY higher than they’re supposed to be.
e.g. one track is 2147483647 in the DB, which is nearly 600 hours long!
How would it have worked this out wrong, and how do I fix it?
The tracks are playing and playing through fine on clients (Soundbridge, Fireplay) but the track length on the display is being reported as some massive figure which makes the display a bit confusing.
Thats related to invalid or outdated ID3v2 tags iirc. When you actually play the file, the correct length is reported, isn’t it?
No, it still comes out wrong on the SB or Fireplay.
Ah, here we go – I just made an arbitrary change to the tag using id3v2 and that seems to have sorted them out.
Cheers!
- The forum ‘General Discussion’ is closed to new topics and replies.