MPlayer V MPlayer-gui

[DaveQB]

Is it just me and my system, but MPlayer is must more 'sturdier' then MPlayer-gui ??

often playing a file through a simple double click and MPlayer-gui, it will freeze and need to be killed. Yet the same files launched with the bash shell and MPlayer work just fine.

I would of thought their performance would be identical as they are essentially the same when talking bout the 'motor' or core of it.
:confused:

[Penguin Man]

I haven't really noticed that actually, but I almost always use gmplayer launched from the command-line, not a graphical file manager or regular mplayer.

[mikeX]

Does the freezing happen immediately or after the file has played for a while? If it's the first case, you should check your gmplayer's audio output configuration, you may have selected a module that conflicts with a sound server or something. If you launch gmplayer from the command line you should see it freezing at the 'initializing audio ..' or whatever part.

[Sujao]

I experience the same. I think gmplayer conflicts with some graphical windows and crashed pretty often. Its usually if the video output window crosses another window that is being generated dynamically. I think I could solve the problem by checking the conf file but I just use mplayer without the gui.

[DaveQB]

thanx guys

I guess i should of explained that better. Its right at the start of the playback and i have to kill the window with Xkill or the like. Today it was one particular file that kept doing it (and it was encoded with mencoder on this very machine!!)

Good idea on launching mplayer-gui from a shell. Might get some more feedback.

As for sound, i use software mixing now that mplayer and xmms for instance work with nicely. This problem has existed before and after going to software mixing though.


BTW MikeX love the sig link :D

[frodoontop]

Now where do we need a gui for? All you need is to type mplayer <filename> . With TAB this goes even faster.

[DaveQB]

ok i finally got another file that had this same behaviour

gmplayer launched from a shell and it gives these errors


Dec: using Planar YV12 as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
VO: [x11] 512x384 => 512x384 Planar YV12 [zoom]
SwScaler: using unscaled Planar YV12 -> BGRA special converter
[mpeg4 @ 0x860c1a8]warning: first frame is no keyframe
[mpeg4 @ 0x860c1a8]ac-tex damaged at 10 3
[mpeg4 @ 0x860c1a8]Error at MB: 109
[mpeg4 @ 0x860c1a8]concealing 2147483647 errors
alsa-space: xrun of at least 1.910 msecs. resetting stream?,?% 0 3 0%
Marker bit missing before vop_coded
[mpeg4 @ 0x860c1a8]ac-tex damaged at 3 4
[mpeg4 @ 0x860c1a8]Error at MB: 135
[mpeg4 @ 0x860c1a8]concealing 2147483647 errors
Marker bit missing before vop_coded0.002 2/ 2 ??% ??% ??,?% 0 3 0%
[mpeg4 @ 0x860c1a8]concealing 969 errors



Heaps more of the same sort and then stops playing altogether


mplayer just plays it fine.

It did give this though


VO: [xv] 512x384 => 512x384 Planar YV12 [zoom]
alsa-space: xrun of at least 2.809 msecs. resetting stream?,?% 0 0 2%
alsa-space: xrun of at least 0.069 msecs. resetting stream0.1% 1 0 82%





interesting

[mikeX]

Well you are using different Video Outputs for gmplayer. While mplayer uses XV, gmplayer uses X11, and because of that it has to use the Software Scaler to make a YV12 -> BGRA color space conversion. It appears that this is responsible for the crash.
Gmplayer uses an extra configuration file, ~/.mplayer/gui.conf which overrides all others, whereas mplayer reads it's configuration from ~/.mplayer/config and /etc/mplayer/mplayer.conf.

[DaveQB]

Ahh i see.

Here's the top bit of my gui.conf


enable_audio_equ = "no"
vo_driver = "x11"
vo_panscan = "0.000000"
vo_doublebuffering = "no"
vo_direct_render = "yes"
vo_dxr3_device = "/dev/em8300-0"


Simply change the vo_driver line ???

[mikeX]

Well yes, you could just change "x11" to "xv", but you don't really have to change the configuration file manually. These options -and a lot more- are available from the GUI when you right-click and select "Preferences", in the 'Video' section.

[DaveQB]

oh of course.

i think i need to look into what the xv and x11 are exactly in regards to mplayer.

[joeljkp]

Just as a layman's higher-level view, the x11 driver simply uses unaccelerated X calls to play the video, while the xv driver uses your video card's accelerated video playback functions.

Both nvidia and ATI cards have xv acceleration if you're using their official drivers.

That's what I've gathered from reading things on the 'net, anyway. Correct me if I'm mistaken.

[shevegen]

gosh... way more than i knew
but thanks for making things clear

[DaveQB]

ahhh blah same error ..



VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
VO: [xv] 512x384 => 512x384 Planar YV12 [zoom]
[mpeg4 @ 0x860c1a8]warning: first frame is no keyframe
[mpeg4 @ 0x860c1a8]ac-tex damaged at 10 3
[mpeg4 @ 0x860c1a8]Error at MB: 109
[mpeg4 @ 0x860c1a8]concealing 2147483647 errors
alsa-space: xrun of at least 1.925 msecs. resetting stream?,?% 0 3 0%
Marker bit missing before vop_coded
[mpeg4 @ 0x860c1a8]ac-tex damaged at 3 4
[mpeg4 @ 0x860c1a8]Error at MB: 135
[mpeg4 @ 0x860c1a8]concealing 2147483647 errors

[mikeX]

sorry if this sounds kinda stupid, but are you using the same clip to compare? If so, is there any case that you 're using different decoders? You can control that with the -vfm option,
e.g.
(g)mplayer -vfm xvid your_clip
(g)mplayer -vfm ffmpeg your_clip

[DaveQB]

Yes of course same file.

Those commands launched with gmplayer on rthe file result in the same error and output.

[bennettp]

Final words in regards to "x11" vs "xv":

Everyone should use xv.

For the vast majority, x11 and xv will both work perfectly well; however full-screen video will be much faster with xv, since it uses hardware accelerated scaling and colourspace conversion. If you're unfortunate enough to have a card that doesn't support xv, then should you use x11.

(back on topic...)
Originally posted by DaveQB
ahhh blah same error ..

VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
VO: [xv] 512x384 => 512x384 Planar YV12 [zoom]
[mpeg4 @ 0x860c1a8]warning: first frame is no keyframe
[mpeg4 @ 0x860c1a8]ac-tex damaged at 10 3
[mpeg4 @ 0x860c1a8]Error at MB: 109
[mpeg4 @ 0x860c1a8]concealing 2147483647 errors
alsa-space: xrun of at least 1.925 msecs. resetting stream?,?% 0 3 0%
Marker bit missing before vop_coded
[mpeg4 @ 0x860c1a8]ac-tex damaged at 3 4
[mpeg4 @ 0x860c1a8]Error at MB: 135
[mpeg4 @ 0x860c1a8]concealing 2147483647 errors

I get the same errors when playing back damaged or incomplete mpeg4 streams. It also happens when I try to seek past the end of an incomplete xvid encode.

(back off topic again...) ;)
I rarely use the mplayer gui, simply becuase it's not very good. MPlayer is primarily a command-line movie player, and it does an excellent job at that.

[DaveQB]

Would i be right in assuming if you haven't drivers for your VGa install and thus using software rendering that xv wouldn't be an advantage to you over x11 ???

I just would of though gmplayer would be the same in what files it can and can't play as mplayer as i thoguht they used the same engine.

[mikeX]

Like bennettp said, the message seems to come from a damaged/incomplete file, but it is really weird that mplayer doesn't display a similar one, while gmplayer does... The only reasonalble explanation I could think of was that different settings are used, but I can't think of any more settings that can change the outcome that much...
I think you should let the mplayer devs know about it, e.g. file a bug report, or ask on #mplayer (irc.freenode.net), although I still think it has to do with some setting, gmplayer should be using the same 'engine' as mplayer does, unless of course you somehow have 2 different versions of mplayer installed (e.g. a precompiled binary and one you compiled yourself), and only one of them is compiled with GUI support, which could explain why a different mplayer is used in each case.
If you choose to bug the devs though, make sure this is not the case, and that if you are using a precompiled binary it's not related to that certain binary (try other binaries, try compiling it yourself from cvs, etc).