[MPlayer-dev-eng] x264 dimensions not set / float point exception

Fri Dec 24 22:44:42 CET 2010

On Fri, Dec 24, 2010 at 4:37 PM, compn <tempn at twmi.rr.com> wrote:
> On Fri, 24 Dec 2010 15:36:07 -0500, Joseph Miller wrote:
>>On Fri, Dec 24, 2010 at 2:43 PM, Joseph Miller <josephcmiller2 at gmail.com> wrote:
>>> On Fri, Dec 24, 2010 at 2:37 PM, Joseph Miller <josephcmiller2 at gmail.com> wrote:
>>>> On Fri, Dec 24, 2010 at 2:17 PM, Joseph Miller <josephcmiller2 at gmail.com> wrote:
>>>>> On Fri, Dec 24, 2010 at 1:44 PM, compn <tempn at twmi.rr.com> wrote:
>>>>>> On Fri, 24 Dec 2010 10:56:34 -0500, Joseph Miller wrote:
>>>>>>>On Thu, Dec 23, 2010 at 10:12 PM, compn <tempn at twmi.rr.com> wrote:
>>>>>>>> On Thu, 23 Dec 2010 10:38:31 -0500, Joseph Miller wrote:
>>>>>>>>>I keep getting floating point exceptions after doing the following.  I
>>>>>>>>>have attached mencoder output.
>>>>>>>>>
>>>>>>>>>/opt/mplayer/bin/mencoder -oac faac -ovc x264 -of lavf -o
>>>>>>>>>integra-reencode.mp4 integra-mp4box.mp4
>>>>>>>>>/opt/mplayer/bin/mencoder -oac faac -ovc x264 -of lavf -o
>>>>>>>>>integra-reencode.mp4 integra-lavf.mp4
>>>>>>>>>
>>>>>>>>>That last two give me Floating point exception.
>>>>>>>>>
>>>>>>>>>I have uploaded integra.mp4 and integra-lavf.mp4 and
>>>>>>>>>integra-mp4box.mp4 to the following location:
>>>>>>>>>http://www.calcmaster.net/downloads/fpx/
>>>>>>>>>
>>>>>>>>>I have had this happen on MP4Box files and other .mp4 files.  I'm not
>>>>>>
>>>>>> the problem with this bug is that its hard to reproduce. can you tell
>>>>>> us what cpu you are using ?
>>>>>>
>>>>>> try running your mencoder on a different box, another user with the
>>>>>> same fpe found he couldnt reproduce it on another box either.
>>>>>>
>>>>>> your samples work on my p4 1.5ghz:
>>>>>>
>>>>>
>>>>> Interesting.  I have tried with both a PhenomII quad core and my Intel
>>>>> Core i3.  I want to say that I had fewer problems with Ubuntu 10.04,
>>>>> but I'm unable to verify because all my boxes are 10.10 now.  I did
>>>>> try as far back as SVN 2010-01-01.
>>>>>
>>>>
>>>> The decvideo module shows the no picture:
>>>>
>>>> DECVIDEO: Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
>>>>  DECVIDEO: INFO: libavcodec init OK!
>>>>  DECVIDEO: Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
>>>>  CPLAYER: ==========================================================================
>>>>  DECVIDEO: vd_ffmpeg data: 1000000, 15006467, 6e534ac, 10017b42
>>>>  DECVIDEO: [h264 @ 0xd3bc60]no picture
>>>> STATUSLINE: Pos:   0.0s      1f ( 6%)  0.00fps Trem:   0min   0mb
>>>> A-V:0.000 [0:0]
>>>>  DECVIDEO: vd_ffmpeg data: 1000000, 1019a41, 1bf22b6, 85841830
>>>>  DECVIDEO: [h264 @ 0xd3bc60]no picture
>>>>  MENCODER:
>>>> 1 duplicate frame(s)!
>>>>    MUXER: VIDEO CODEC ID: 28
>>>>    MUXER: AUDIO CODEC ID: 15002, TAG: 0
>>>>    MUXER: Writing header...
>>>>   GLOBAL: [mp4 @ 0xcc8c40]dimensions not set
>>>> Floating point exception
>>>>
>>>>
>>>>
>>>> A working file produces:
>>>>
>>>>  DECVIDEO: Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
>>>>  DECVIDEO: INFO: libavcodec init OK!
>>>>  DECVIDEO: Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
>>>>  CPLAYER: ==========================================================================
>>>>  DECVIDEO: vd_ffmpeg data: 5061900, 24cb0a15, 3330fa13, 9cbda201
>>>>  DECVIDEO: [ffmpeg] aspect_ratio: 1.315789
>>>>  DECVIDEO: VDec: vo config request - 400 x 304 (preferred colorspace:
>>>> Planar YV12)
>>>>  DECVIDEO: Trying filter chain: expand x264
>>>>  CPLAYER: Movie-Aspect is 1.32:1 - prescaling to correct movie aspect.
>>>> x264 [info]: using SAR=1/1
>>>> x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2
>>>> x264 [info]: profile High, level 2.1
>>>>
>>>
>>> I guess I should include mplayer results too.  Here's the file that
>>> won't re-encode, but the output is from mplayer (which plays the
>>> file):
>>>
>>> DECVIDEO: Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
>>>  DECVIDEO: INFO: libavcodec init OK!
>>>  DECVIDEO: Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
>>>  CPLAYER: ==========================================================================
>>>  CPLAYER: ==========================================================================
>>>  DECAUDIO: Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
>>>  DECAUDIO: AUDIO: 44100 Hz, 2 ch, s16le, 48.0 kbit/3.40% (ratio: 6000->176400)
>>>  DECAUDIO: Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG
>>> layer-2, layer-3)
>>>  CPLAYER: ==========================================================================
>>>  CPLAYER: AO: [oss] 44100Hz 2ch s16le (2 bytes per sample)
>>>  CPLAYER: Starting playback...
>>>  DECVIDEO: vd_ffmpeg data: 1000000, 15006467, 6e534ac, 10017b42
>>>  DECVIDEO: [h264 @ 0xe87760]no picture
>>>  DECVIDEO: vd_ffmpeg data: 1000000, 1019a41, 1bf22b6, 85841830
>>>  DECVIDEO: [h264 @ 0xe87760]no picture
>>>  DECVIDEO: vd_ffmpeg data: 1000000, 1029e41, 2e7f453c, 45e08ee4
>>>  DECVIDEO: [ffmpeg] aspect_ratio: 1.315789
>>>  DECVIDEO: VDec: vo config request - 400 x 304 (preferred colorspace:
>>> Planar YV12)
>>>  DECVIDEO: Trying filter chain: vo
>>>  CPLAYER: Movie-Aspect is 1.32:1 - prescaling to correct movie aspect.
>>>  CPLAYER: VO: [xv] 400x304 => 400x304 Planar YV12
>>>  DECVIDEO: *** [vo] Exporting mp_image_t, 400x304x12bpp YUV planar, 182400 bytes
>>>  DECVIDEO: (imgfmt: 32315659, planes: (nil),(nil),(nil) strides:
>>> 0,0,0, chroma: 200x152, shift: h:1,v:1)
>>>
>>
>>OK some good news,
>>-demuxer h264es seems to allow the encoding to progress for the file
>>muxed with lavf, but it doesn't decode any sound.
>>-demuxer h264es causes segfault with MP4Box muxed file.
>
> yeah i'm guessing the demuxer/'no picture' is the cause, then
> the packets are passed onto mencoder lavf muxer and thats where it
> dies, as it has no dimensions for the first frame and screws itself.
>
> does -ss 1 make it work ?
>

No, this doesn't work.  There is definitely something wrong with the
way the demuxer reads this or something wrong with the lavf muxer that
created it.  Should I be contacting ffmpeg-devel?

-Joseph