Opened 9 years ago

Last modified 8 years ago

#1767 new defect

mplayer doesn't play mpeg4 video file correctly on arm

Reported by: kaijun61@… Owned by: reimar
Priority: normal Component: demuxer
Version: unspecified Severity: critical
Keywords: Cc: compn
Blocked By: Blocking:
Reproduced by developer: Analyzed by developer:

Description

I tested mpeg4 video (.m4v) file on mplayer rev. 31956 on arm, it doesn't play correctly. I found it gives wrong image size in mpeg_hdr.c. But rev. 30165 can work properly.

Change History (2)

comment:1 Changed 9 years ago by compn

  • Cc patriotact@… added

can you paste mplayer output?

is it an h263/h261 in mp4 ?
if so, its a known problem with container res not matching video res

comment:2 Changed 8 years ago by kaijun61@…

(In reply to comment #1)

can you paste mplayer output?

is it an h263/h261 in mp4 ?
if so, its a known problem with container res not matching video res

It could be h263. Here is output for mpeg4.

MPlayer SVN-r4-4.3.3 (C) 2000-2010 MPlayer Team

Playing /media/sda1/davincieffect_ntsc_1_50s.m4v.
MPEG-ES file format detected.
FPS seems to be: 29.979414
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
[IMGUTILS @ 0x8fd2c0]Picture size 0x16 is invalid
Could not open codec.
VDecoder init failed :(
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
Cannot find codec 'mpeg4_vdpau' in libavcodec...
VDecoder init failed :(
Requested video codec family [xvid] (vfm=xvid) not available.
Enable it at compilation.
Cannot find codec matching selected -vo and video format 0x10000004.
==========================================================================

MPlayer interrupted by signal 11 in module: uninit_vo

  • MPlayer crashed by bad usage of CPU/FPU/RAM. Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
  • MPlayer crashed. This shouldn't happen. It can be a bug in the MPlayer code _or_ in your drivers _or_ in your gcc version. If you think it's MPlayer's fault, please read DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and won't help unless you provide this information when reporting a possible bug.
Note: See TracTickets for help on using tickets.