suzuki123456789 / mplayer-for-windows

Automatically exported from code.google.com/p/mplayer-for-windows
0 stars 0 forks source link

Error while decoding frame! (stride changed) #4

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
Playing some h264 files in .mkv container.

MPlayer version: All recent builds.
Operating system: Windows 7 AMD CPU and Mobile AMD GPU.

What is the expected output? What do you see instead?
Generally get 1-2 frames decoded then frozen picture before the MPlayer process 
hangs, Windows has trouble ending the task.

Please provide any additional information below. Also, please attach the
complete verbose (using the -v switch) output of MPlayer in a text file
including the complete command used to run MPlayer. *Do not* copy and paste
the output, please use the attach feature.

In the simple log it spits out line after line of this.
Error while decoding frame!
[h264 @ 01197360]get_buffer() failed (stride changed)
[h264 @ 01197360]decode_slice_header error
[h264 @ 01197360]no frame!

The last build of MPlayer this file played fine on was Sherpya's latest. The 
earlier builds on here had choppy output but wouldn't hang the process, they 
all throw up the same error in the log.
Some have suggested that it is the newer FFmpeg not playing well with others.

Original issue reported on code.google.com by wrglee...@gmail.com on 11 Jan 2013 at 9:15

Attachments:

GoogleCodeExporter commented 8 years ago
I tried lots of H264/MKV files and none of them produce that error or had any 
playback problems now and before. Try a different video driver like 'direct3d' 
or 'directx' or playing it from a command line with no extra options:

"C:\Program Files (x86)\SMPlayer\mplayer\mplayer.exe" 
C:\Users\Bill\DOWNLO~1\Ecchi\_F90D6~1.MKV

If that doesn't work then possibly the files are badly encoded and FFmpeg has 
become less forgiving.

Original comment by redxii1...@gmail.com on 11 Jan 2013 at 6:15

GoogleCodeExporter commented 8 years ago
Tried D3D and Dx also from command line, had same errors in the logs.
Also tried playing the files on my old QX6700 Intel 8800GTX NVidia Vista system 
with same results.
I can understand they might have some bad encodes but less likely across 2 
different sub groups. Maybe FFMpeg is just a hater.

Here are some example files, only linking the forum not sure on the link policy 
here.
!WARNING NSFW Content in Files and on Site! Nothing too extreme, all censored 
hentai.
http://www.fakku.net/viewtopic.php?t=91823 <--This is the one with detailed log 
above
http://www.fakku.net/viewtopic.php?t=92707
http://www.fakku.net/viewtopic.php?t=93777

Other Sub group website is an Ad laden bit of mess so I wont link that.

Original comment by wrglee...@gmail.com on 12 Jan 2013 at 3:54

GoogleCodeExporter commented 8 years ago
It does appear the problem has gotten progressively worse for those files. I 
tried an older build of mine r34835 from April (way before I started uploading 
here) and it played perfectly, then r35425 from November was choppy but played 
and now it freezes in current builds. I've tried another build (not mine) and 
the same problem.

I have 100s of anime fansubs and this is the first time I encountered this 
problem. I'm not sure about it being an ffmpeg problem though because I just 
tried Zeranoe's ffmpeg (ffplay) compiled against the latest ffmpeg git and it 
didn't have any issue playing it.

mplayer2, an mplayer fork, uses libav (an ffmpeg fork) and it doesn't have that 
problem either. mplayer2 should be functionally on par with mplayer you're 
welcome to give that shot until it's fixed and works fine with smplayer: 
http://code.google.com/p/mplayer2-for-windows/downloads/list

Original comment by redxii1...@gmail.com on 12 Jan 2013 at 5:28

GoogleCodeExporter commented 8 years ago
It's a shame it doesn't work, and it is a strange error. I like the improved 
performance of the new builds and they handle sub streams way better, no more 
silly square chars. at the end of lines and no skewing on typesetting.
I guess I will give mplayer2 a run. Thanks for your help.

Original comment by wrglee...@gmail.com on 12 Jan 2013 at 5:49

GoogleCodeExporter commented 8 years ago
Fixed in r35908 upstream.

Original comment by redxii1...@gmail.com on 3 Feb 2013 at 7:12