Login at Kodi Home

tkgafs · (This post was last modified: 2016-02-04, 10:43 by zag.)

Having now tried this out, I am puzzled as to where the track length is obtained from

I have at least two tracks where the displayed length is greatly in excess of the actual track length see attached pictures

they are 320kbs mp3 files

**DaveBlake** · 2016-01-30, 12:06

@zag, or any other mods, could you split the above and this reply into a new thread in Support/OS Independant forum with title
"Music Song duration displayed is wrong". I'd rather not clutter up this node examples thread with discussion of what looks like a bug, or at least a tagging funny.

@tkgafs how duration of these tracks display in say the Song Info Dialog? Same large number I presume? How long do the files play? I believe duration is taken from file properties (not tags exactly), but I could be wrong. Happy to persue this, just in a better place.

**zag** · 2016-01-30, 14:37

Topic split. I'm not sure i've even seen the wrong duration myself. Maybe its just a corrupt mp3?

**DaveBlake** · 2016-01-30, 17:16

Thanks for the split zag. I know year comes out as garbage when not set (another fix to do), but thought duration was file data. One reason I want to check this out and learn.

tkgafs · 2016-01-30, 17:32

They play for the correct length of time without any issue

as you'll see from this screenshot it appears to be only these two tracks which display the incorrect length of time

the song information from the context menu does not seem to display the track length, is there somewhere else I should be looking

**DaveBlake** · 2016-01-30, 17:47

Sorry, I must have been dreaming duration in Song Info Dialog.

They play OK, but does the player show the right time? Probably does, but may as well check.

Could you have a look at the tags for these songs in your favorite tagging software, and give me a screen shot please. Probably the quickest way to do it.

tkgafs · 2016-01-30, 18:01

Yes they play correctly and finish at the correct time. I am currently playing both tracks with debugging turned on and will upload log file shortly

here is a screenshot of mp3tag with some columns hidden

tkgafs · 2016-01-30, 18:16

here is the kodi log if I have hopefully done it correctly

Kodi Debug Log

you'll notice that the first track seems to start playing at 15:36:25 until 15:49:50 a duration of 13:25

next track starts at 15:49:50 and seems to finish at 16:00:50 a duration of 11:00

both pretty much spot on for track length reported both by mp3tag and windows file properties

tkgafs · 2016-01-30, 19:19

(2016-01-30, 17:47)DaveBlake Wrote: Sorry, I must have been dreaming duration in Song Info Dialog.

They play OK, but does the player show the right time? Probably does, but may as well check.

Could you have a look at the tags for these songs in your favorite tagging software, and give me a screen shot please. Probably the quickest way to do it.

Actually to clarify the player shows the wrong time but finishes the tracks at the correct time,

ie when playing the track lemmings it displays 1:18.24 but only plays up till 13:25

and sleepwalkers display 36:08 but only plays up till 11:01

and on both tracks you cannot try and skip past the correct actual time

**DaveBlake** · 2016-01-30, 20:16

Well the debug shows ffmpeg seeing the track as that long.... so I am thinking it is a ffmpeg issue with those files. It isn't tags, but file properties. The music library just stores the file data for sorting etc. Here even the player is seeing a long files, so it is not a library thing.

Wrong file properties, anyone know anything about that kind of thing?

**DaveBlake** · 2016-02-01, 13:03

The key debug log part is

Code:
36:24 T:6812   DEBUG: ffmpeg[1A9C]: [mp3] filesize and duration do not match (growing file?)

36:24 T:6812    INFO: ffmpeg[1A9C]: [mp3] Skipping 0 bytes of junk at 5140.

36:24 T:6812   DEBUG: CDVDDemuxFFmpeg::Open - avformat_find_stream_info starting

36:25 T:6812   DEBUG: CDVDDemuxFFmpeg::Open - av_find_stream_info finished

36:25 T:6812    INFO: ffmpeg[1A9C]: Input #0, mp3, musicdb://albums/1396/18651.mp3?albumid=139':

36:25 T:6812    INFO: ffmpeg[1A9C]:   Metadata:

36:25 T:6812    INFO: ffmpeg[1A9C]:     album           : Paradiso, Amsterdam

36:25 T:6812    INFO: ffmpeg[1A9C]:     artist          : Van Der Graaf Generator

36:25 T:6812    INFO: ffmpeg[1A9C]:     genre           : Rock

36:25 T:6812    INFO: ffmpeg[1A9C]:     title           : Lemmings

36:25 T:6812    INFO: ffmpeg[1A9C]:     track           : 01

36:25 T:6812    INFO: ffmpeg[1A9C]:     TYER            : 2007-04-14

36:25 T:6812    INFO: ffmpeg[1A9C]:   Duration: 01:18:24.99, start: 0.025057, bitrate: 54 kb/s

36:25 T:6812    INFO: ffmpeg[1A9C]:     Stream #0:0: Audio: mp3, 44100 Hz, stereo, s16p, 320 kb/s

36:25 T:6812    INFO: ffmpeg[1A9C]:     Metadata:

36:25 T:6812    INFO: ffmpeg[1A9C]:       encoder         : LAME3.96r

36:25 T:6812   DEBUG: CDVDDemuxFFmpeg::AddStream(0, ...) -> 0

36:25 T:6812   DEBUG: FactoryCodec - Audio: passthrough - Opening

36:25 T:6812   DEBUG: FactoryCodec - Audio: passthrough - Failed

36:25 T:6812   DEBUG: FactoryCodec - Audio: FFmpeg - Opening

36:25 T:6812   DEBUG: FactoryCodec - Audio: FFmpeg - Opened

36:25 T:6812   DEBUG: ffmpeg[1A9C]: [mp3] Could not update timestamps for skipped samples.

36:25 T:6812   DEBUG: CDVDDemuxFFmpeg::SeekTime - seek ended up on time 0

36:25 T:6812   DEBUG: Previous line repeats 1 times.

36:25 T:6812   DEBUG: ffmpeg[1A9C]: [mp3] Could not update timestamps for skipped samples.

Maybe Windows uses filesize, but ffmpeg passes Kodi duration (the long time)?

**zag** · (This post was last modified: 2016-02-01, 13:10 by zag.)

If ffmpeg isn't reading the time correctly then there is not much we can do other than report it to them.

I still suspect it may be an error with the file as I have never seen this issue(although I do use FLAC exclusively these days).

**scott967** · (This post was last modified: 2016-02-02, 04:51 by scott967.)

If the file was LAME3 encoded in variable bit rate (VBR) it should have the LAME header (or Xing header) and from that get duration in secs as

frame count * 1152 (for Mpeg-1 Layer III) / sample rate (eg 44100). If you don't have LAME or Xing header, then I guess you need to open each frame and get the bitrate to calculate the average bitrate (obviously not needed for CBR).

You might hunt down a program mp3diags which can decode headers and display them for you (also ID3 tags, but for this I think TLEN which could contain this info is ignored by ffmpeg).

scott s.
.

tkgafs · 2016-02-03, 11:52

Thanks for that

Mp3diags shows a mismatched Xing header for the two problem tracks, quite why those 2 were wrong and the rest ok will remain a mystery though

but mp3diags happily fixed them

**scott967** · 2016-02-04, 01:33

Interesting finding.

scott s.
.