mplayer unable to initialise when reading .m2ts video file

[GoogleCodeExporter]

if I try to play the main feature .m2ts file from a ripped blueray disk I
get the following:

==========================================================================
Opening video decoder: [dshowserver] DirectShowServer video codecs

MPlayer interrupted by signal 11 in module: init_video_codec
ID_SIGNAL=11
- MPlayer crashed by bad usage of CPU/FPU/RAM.

this is with a patched svn mplayer that works fine otherwise (on a 64bit
install).

a svn version of mplayer without the coreavc patch plays the .m2ts video
fine (other than jerkiness because my cpu is not fast enough).

this would seem to indicate that the problem is in the coreavc/dshowserver
area.

Original issue reported on code.google.com by allan.mi...@zetnet.co.uk on 19 Aug 2008 at 1:28

[GoogleCodeExporter]

Try -demuxer lavf, that fixed it for me.

Original comment by stevo3...@gmail.com on 18 Oct 2008 at 7:11

[GoogleCodeExporter]

I tried your suggestion but what happened was that mplayer started reading the 
file
and quickly consumed all my memory and swap space.

Original comment by allan.mi...@zetnet.co.uk on 21 Oct 2008 at 12:58

[GoogleCodeExporter]

can you get it to work at all using ffh264?  even if it is really slow, it 
would be
helpful to know whether this is a demuxer or codec problem.

Original comment by alannis...@gmail.com on 21 Oct 2008 at 7:02

• Changed state: WaitingForResponse

[GoogleCodeExporter]

using r74 dshowserver, svn 27809 mplayer, 1.8.5 coreavc on a 32 bit Gentoo 
install:

1. with -vc coreserve I get the original reported problem

1. plays OK (other than jerkiness) with -vc ffh264

2. if I specify -demuxer lavf with/without ffh264 I get this memory consumption

(The disk I am playing is blueray Stargate)

Original comment by allan.mi...@zetnet.co.uk on 22 Oct 2008 at 11:49

[GoogleCodeExporter]

Sorry, I wasn't clear.  If you use '-demuxer lavf -vc ffh264' do you get the 
memory
consumption issue?

The problem in teh original ticket is that teh default demuxer doesn't provide 
enough
info for CoreAVC to run.  This is basically a 'WontFix' because there is 
nothing I
can do about it.  So the hope is to find a demuxer that does provide enough 
info to
CoreAVC that actually works with the stream.  IN general, the lavf demuxer does
provide the right info, but it may not work with all inputs.

You might just give up and try xine.  Xine seems to do a better job with its 
demuxer
providing the right headers without overrides than mplayer does.

Original comment by alannis...@gmail.com on 22 Oct 2008 at 1:22

[GoogleCodeExporter]

Yes, I get the memory consumption with lavf and ffh264.

Thanks for explaining what the problem was.

Xine won't/can't handle m2ts files, it comes back with a message saying there 
is no
demuxer plugin available for that file type. I am using xine-lib-1.1.15, should 
I be
using the 1.2 branch?

Original comment by allan.mi...@zetnet.co.uk on 22 Oct 2008 at 6:36

[GoogleCodeExporter]

Original comment by alannis...@gmail.com on 12 Mar 2010 at 4:12

• Changed state: WontFix