David Teirney <[email protected]> added the comment: @reimar, the following appears in the ffmpeg logging:
> [NULL @ 0xaadab80]start time is not set in av_estimate_timings_from_pts > Input #0, mpegts, from '1002_20100221172800.mpg': > Duration: 01:50:47.23, start: 58149.813867, bitrate: 4161 kb/s I don't know what is actually setting the start time but it does not appear to be setting it correctly. When that error appears in the log, the start time and duration consistently appear to be off by about 44 minutes. For example, the actual playback duration of the full mpegts file is ~1:05:00. And, for the -trimmed file, the duration is only a few seconds: > [mpegts @ 0xa95a850]max_analyze_duration reached > [NULL @ 0xa967d50]start time is not set in av_estimate_timings_from_pts > Input #0, mpegts, from '1002_20100221172800-trimmed.mpg': > Duration: 00:44:04.19, start: 58149.813867, bitrate: 30 kb/s For every DVB-T recording from a specific channel the duration presented is always ~44 minutes too long and every file has the same error. > [NULL @ 0x8df8b60]start time is not set in av_estimate_timings_from_pts Perhaps the ticket title should be "start time is incorrectly set if start time is not set in av_estimate_timings_from_pts" @bcoudurier: the patch that I am using for LATM AAC playback is the one that Paul Kendall put together and submitted some time ago. Unfortunately it has already been rejected. There are number of people in the OSS community now using that patch, e.g. XBMC Media Center, MythTV. ________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/issue1959> ________________________________________________
