[mythtv-users] [UK] BBC HD and BBC ONE HD - recording length incorrect

[belcampo]

Taylor Ralph wrote:
> On Wed, Dec 22, 2010 at 6:13 AM, David Knight <dlknight at sdf.lonestar.org> wrote:
>> On Mon, November 29, 2010 8:19 pm, Taylor Ralph wrote:
>>> On Mon, Nov 29, 2010 at 3:11 PM, David Knight <dlknight at sdf.lonestar.org>
>>> wrote:
>>>> On Sun, November 28, 2010 12:43 pm, Richard Morton wrote:
>>>>> I have seen this on one recording as well (last weekend I think). i
>>>>> was waiting for it to reoccur before reporting it - but I havent
>>>>> watched any BBC HD since that occurance.
>>>>> R
>>>>>
>>>>>
>>>> Thanks for confirming Richard, I will check to see if there is an open
>>>> ticket on the weekend as this was also mentioned in another recent
>>>> thread.
>>>> Just need to get the playback log output and a sample then :)
>>>>
>>>> Suppose I should try mplayer to see if it is an issue with some library
>>>> e.g. ffmpeg.
>>>>
>>>> Dave
>>>>
>>> What does ffmpeg -i report for the recording? A change was committed
>>> to trunk recently that hopefully fixes this issue.
>>>
>>> Regards.
>>> --
>>> Taylor
>>>
>>>
>> FFmpeg version SVN-r25557-snapshot, Copyright (c) 2000-2010 the FFmpeg
>> developers
>>  built on Oct 24 2010 07:32:30 with gcc 4.4.4 20100630 (Red Hat 4.4.4-10)
>>  configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64
>> --mandir=/usr/share/man --enable-shared --enable-gpl --enable-version3
>> --enable-nonfree --enable-postproc --enable-avfilter --enable-pthreads
>> --enable-x11grab --enable-vdpau --disable-avisynth --enable-libdc1394
>> --enable-libdirac --enable-libfaac --enable-libgsm --enable-libmp3lame
>> --enable-libnut --enable-libopencore-amrnb --enable-libopencore-amrwb
>> --enable-libopenjpeg --enable-libschroedinger --enable-libspeex
>> --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid
>> --extra-cflags='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
>> -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fPIC'
>> --disable-stripping
>>  libavutil     50.32. 3 / 50.32. 3
>>  libavcore      0. 9. 1 /  0. 9. 1
>>  libavcodec    52.93. 0 / 52.93. 0
>>  libavformat   52.84. 0 / 52.84. 0
>>  libavdevice   52. 2. 2 / 52. 2. 2
>>  libavfilter    1.53. 0 /  1.53. 0
>>  libswscale     0.12. 0 /  0.12. 0
>>  libpostproc   51. 2. 0 / 51. 2. 0
>> [h264 @ 0x1e1c490] non-existing SPS 0 referenced in buffering period
>> [h264 @ 0x1e1c490] non-existing PPS referenced
>> [h264 @ 0x1e1c490] non-existing SPS 0 referenced in buffering period
>> [h264 @ 0x1e1c490] non-existing PPS 0 referenced
>> [h264 @ 0x1e1c490] decode_slice_header error
>> [h264 @ 0x1e1c490] non-existing PPS 0 referenced
>> [h264 @ 0x1e1c490] decode_slice_header error
>> [h264 @ 0x1e1c490] non-existing PPS 0 referenced
>> [h264 @ 0x1e1c490] decode_slice_header error
>> [h264 @ 0x1e1c490] non-existing PPS 0 referenced
>> [h264 @ 0x1e1c490] decode_slice_header error
>> [h264 @ 0x1e1c490] non-existing PPS 0 referenced
>> [h264 @ 0x1e1c490] decode_slice_header error
>> [h264 @ 0x1e1c490] non-existing PPS 0 referenced
>> [h264 @ 0x1e1c490] decode_slice_header error
>> [h264 @ 0x1e1c490] no frame!
>>
>> Above errors repeated for couple of pages.
>>
>> [mpegts @ 0x1e166e0] max_analyze_duration reached
>> [NULL @ 0x1e3a630] start time is not set in av_estimate_timings_from_pts
>> Input #0, mpegts, from '/video/default/8941_20101127194500.mpg':
>>  Duration: 00:46:26.00, start: 5649.660133, bitrate: 7424 kb/s
>>  Program 1
>>    Stream #0.0[0x1518]: Video: h264, yuv420p, 1440x1080 [PAR 4:3 DAR
>> 16:9], 27.53 fps, 25 tbr, 90k tbn, 50 tbc
>>    Stream #0.1[0x151a](NAR): Audio: mp2, 48000 Hz, 2 channels, s16, 256 kb/s
>>    Stream #0.2[0x151b](eng): Subtitle: [6][0][0][0] / 0x0006
>>    Stream #0.3[0x151c](eng): Subtitle: dvbsub
>>    Stream #0.4[0x1519](eng): Audio: ac3, 48000 Hz, stereo, s16, 192 kb/s
>> At least one output file must be specified
>>
>> Dave K.
>>
> 
> Is 00:46:26.00 the correct duration? What does MythTV show for the
> duration? We now use the ffmpeg duration so if it's correct then the
> next release will contain the fix.
FYI I reported several issues on this on ffmpeg issue-tracker
issue 2020 2144 1472-although a very old issue it still holds.
> 
> Regards.
> --
> Taylor
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users