shloyer / gnome-mplayer

Automatically exported from code.google.com/p/gnome-mplayer
GNU General Public License v2.0
0 stars 0 forks source link

Video output stops under a few seconds #114

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
When I start any video file in gnome-mplayer the output stops after a few 
seconds, I get simply a black screen. I see the following in the xterm 
from which I have launched gnome-mplayer:

(gnome-mplayer:31516): Gtk-CRITICAL **: gtk_socket_get_id: assertion 
`GTK_IS_SOCKET (socket)' failed
(gnome-mplayer:31516): Gtk-CRITICAL **: gtk_fixed_move_internal: assertion 
`widget->parent == GTK_WIDGET (fixed)' failed

It happens to me both with 0.9.2 and svn version. I am on archlinux. Many 
others archlinux users reported analog issues in the distro forums.

Mplayer and other mplayer frontends (I have tried smplayer and kmplayer) 
work fine. I have tried to change the video output from xv to x11 or gl, 
but to no avail.

Original issue reported on code.google.com by patroc...@gmail.com on 23 Dec 2008 at 10:51

GoogleCodeExporter commented 8 years ago
I guess the first question is what window manager are you using? KDE/Gnome 
something
else?

What that error looks like to me is that the window has not been fully created 
yet
and that is what is causing the error. I put a little workaround into the code 
to
flush the gtk event buffer right before that is requested so perhaps that will 
help. 

I do have to admit that this part of the code has been in there over a year and 
this
is the first I have heard of any problems with it.

But give SVN a try and let me know if it helps.

Original comment by kdeko...@gmail.com on 23 Dec 2008 at 1:48

GoogleCodeExporter commented 8 years ago
I have tried svn but there is no difference.
It happens to me with the following WM (I do not use a Desktop Environment):
1) openbox;
2) awesome;
3) ratpoison.
I was suspecting that it is connected to the tiling window managers, and I have 
tried openbox to exclude this hypothesis, and actually the problem happens also 
in 
openbox.

I am not 100% sure that the errors I get in xterm are the cause/symptom of the 
fact 
that the video output stops. But they seem approximately contemporary.

Also note that the amount of seconds elapsed when the video output stops is 
variable 
(in my experiments from 2 seconds up to 30 seconds); the variation does not 
seem to 
depend on the file opened (it varies also if I open several times the same 
file).

Original comment by patroc...@gmail.com on 23 Dec 2008 at 2:05

GoogleCodeExporter commented 8 years ago
Well I am running under openbox right now and it seems to be working fine and I 
don't
get the assertion. Can you please post a full run of gnome-mplayer with the -v 
option
so I can see what the problem may be. Also have you tried turning off 
deinterlace
frames and turning on frame drop in the preferences?

Original comment by kdeko...@gmail.com on 23 Dec 2008 at 2:25

GoogleCodeExporter commented 8 years ago
I have set the options as you said, but to no avail. I attach the output of 
gnome-
mplayer -v where I launch gnome-mplayer, I open a film, the video output starts 
fine 
and disappears after 5 secs and I finally quit gnome-mplayer with Ctrl + q.

Original comment by patroc...@gmail.com on 23 Dec 2008 at 2:31

Attachments:

GoogleCodeExporter commented 8 years ago
Perhaps it is relevant that I am using xorg-server 1.5.3

Original comment by patroc...@gmail.com on 23 Dec 2008 at 2:33

GoogleCodeExporter commented 8 years ago
Your version of mplayer is really old. I can tell by some of the messages in the
output. The X11 errors are worrisome. I have a feeling that something is wrong 
with
your install of X. But I didn't see the assertion so that is good. But the bad
drawable means that the window that mplayer is drawing frames to, has been 
destroyed.
That really should never happen. I do suggest updating mplayer as a first step 
and
see if that helps. 

Original comment by kdeko...@gmail.com on 23 Dec 2008 at 2:51

GoogleCodeExporter commented 8 years ago
Isn't 1.0-rc2 the latest release? Should I upgrade to latest development 
version? I 
will try this (but note that mplayer, gmplayer and smplayer works fine here, 
and for 
this reason I thought that the problem was in gnome-mplayer).

Original comment by patroc...@gmail.com on 23 Dec 2008 at 3:01

GoogleCodeExporter commented 8 years ago
mplayer does not do releases or has not do so for over two years. They recommend
using SVN. 

Original comment by kdeko...@gmail.com on 23 Dec 2008 at 3:38

GoogleCodeExporter commented 8 years ago
I compiled the latest mplayer from svn, but I get the same problem. I attach 
the 
output of gnome-mplayer -v, but it looks similar to what I attached above

Original comment by patroc...@gmail.com on 23 Dec 2008 at 10:00

Attachments:

GoogleCodeExporter commented 8 years ago
So I have taken from the output above the way in which gnome-mplayer runs 
mplayer:

mplayer -profile gnome-mplayer -quiet -slave -identify -framedrop 
-noconsolecontrols 
-osdlevel 0 -nomouseinput -nocache -wid 0x1a001ae -ass -embeddedfonts -ass-font-
scale 1,0 -ass-force-style FontName=Sans -ass-color ffffff00 -vf-add screenshot 
/
home/patroclo7/documenti/multimedia/film/\[DivX\ \-\ ITA\]\ Stanley\ Kubrick\ 
\-\ 
Arancia\ Meccanica\ \(completo\)\.avi

If I run this on the CLI I get the same x11 errors. But if I remove "-wid 
0x1a001ae", then the video is executed properly. What does that option do? Does 
gnome-mplayer need it?

Original comment by patroc...@gmail.com on 23 Dec 2008 at 11:18

GoogleCodeExporter commented 8 years ago
The -wid option is required. It is the command that tells mplayer where to put 
the
video. This is the X-window that it is drawing to, which is a drawing area 
supplied
by gnome-mplayer. So if that does not work there is a possible bug in your 
setup. And
you get this same exact error when you use x11 as the vo?

Original comment by kdeko...@gmail.com on 24 Dec 2008 at 12:14

GoogleCodeExporter commented 8 years ago
Yes, I tried with x11, xv and gl. Nothing changes (except obviously the 
resource id 
of the window where mplayer tries to draw).
When I use that command line with -wid <id> above I do not see any video output 
(and 
this is right, since there is no window with that id). On the contrary in gnome-
mplayer I see some seconds of video output; so it seems that mplayer is able to 
contact the window and draw in it, but then something goes wrong. Is this 
related to 
a change of attributes? I ask because I see the following line:
ERROR:   Major opcode of failed request:  2 (X_ChangeWindowAttributes)

If so, which attributes of the window are changed only after some seconds?

Original comment by patroc...@gmail.com on 24 Dec 2008 at 4:16

GoogleCodeExporter commented 8 years ago
As far as I know, no attributes of the window are changed after it is resized 
and the
resize only happens on the first video. 

I think your window manager might be doing something here. Can you please test 
with
gnome to see if it works there.

Original comment by kdeko...@gmail.com on 24 Dec 2008 at 5:06

GoogleCodeExporter commented 8 years ago
Sorry for the delay, I was out of town. 
Installed gnome and I get the same issue, with the same debuf output.

Original comment by patroc...@gmail.com on 30 Dec 2008 at 12:04

GoogleCodeExporter commented 8 years ago
Another odd behaviour: if, when the video output already stopped, I open 
another 
video file through the menu, then the video output seems to be sent to the root 
window (it is displayed in all virtual desktops instead of my wallpaper) and 
actually runs fine.

Original comment by patroc...@gmail.com on 30 Dec 2008 at 1:30

GoogleCodeExporter commented 8 years ago
Something just doesn't seem right with your setup.
I'm running xserver 1.5.3 on Fedora 10 and everything is working as expected. 
I'm
using an ATI card with the radeon driver. Which driver are you using?

Original comment by kdeko...@gmail.com on 30 Dec 2008 at 1:49

GoogleCodeExporter commented 8 years ago
The intel driver with an intel i945 integrated. The version of the driver is 
2.4.3.

Original comment by patroc...@gmail.com on 30 Dec 2008 at 2:31

GoogleCodeExporter commented 8 years ago
Can you test with the vesa driver and the x11 vo in mplayer. I used to run the 
intel
driver and found it to be really buggy. 

The reason I'm asking you to do this, is that you are the first person I have 
seen
with this issue and have never seen this problem myself so I'm trying to figure 
out
where the problem is.

Original comment by kdeko...@gmail.com on 30 Dec 2008 at 2:43

GoogleCodeExporter commented 8 years ago
Also, have you ever run an earlier version of gnome-mplayer and did the problems
happen with it?

Original comment by kdeko...@gmail.com on 30 Dec 2008 at 2:47

GoogleCodeExporter commented 8 years ago
Tried vesa driver with x11 output, but there is no difference. Since mplayer 
works 
fine and the problem concerns the embedding in the gnome-mplayer window (but is 
wm 
independent), the peculiarity o my setup concerns probably not the driver but 
something in the xserver configuration.
Bu I do not know what can be; usually I run without any xorg.conf at all.

Original comment by patroc...@gmail.com on 30 Dec 2008 at 2:53

GoogleCodeExporter commented 8 years ago
No I can remember that in the past gnome-mplayer worked fine, but I am not able 
to 
say exactly when the problem appeared.

Original comment by patroc...@gmail.com on 30 Dec 2008 at 2:55

GoogleCodeExporter commented 8 years ago
Tried some old releases (0.6.3, 0.5.2), but no difference.
A thing which I have not mentioned is that I am on x86_64

Original comment by patroc...@gmail.com on 30 Dec 2008 at 3:05

GoogleCodeExporter commented 8 years ago
I run on x86_64 as well. In fact I use a 32bit mplayer and a 64bit 
gnome-mplayer and
that works quite well. 

I compile mplayer in 32 bit mode with this command (I have have PKG_CONFIG 
point to
the 32bit include files, so that may vary for you).

export PKG_CONFIG_PATH=/usr/lib/pkgconfig
./configure --target=i386-linux --cc="gcc -m32" --as="as --32"
--with-extralibdir=/usr/lib  --prefix=/usr --disable-dvdread-internal 
--disable-nemesi

Interesting about the old releases doing the same thing. The error message you 
are
giving really is odd and doesn't really tell me much. Can you tell me what 
version of
gtk/glib you have installed. I'm am surprised that smplayer works since it 
should be
using the same method that gnome-mplayer does. But the usage of QT by it may 
affect that.

I have gtk 2.14.5 and glib2 2.18.3

Original comment by kdeko...@gmail.com on 30 Dec 2008 at 3:16

GoogleCodeExporter commented 8 years ago
same glib2, gtk 2.14.6

Original comment by patroc...@gmail.com on 30 Dec 2008 at 3:32

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Any update on this? Also have you check your .xsession-errors file and seen 
anything
unusual. 

I was reading back over your comments and the part where you sayd the first 
window
doesn't work, but the second one goes to the root... that is really weird. 
Never seen
that. 

Original comment by kdeko...@gmail.com on 3 Jan 2009 at 12:01

GoogleCodeExporter commented 8 years ago
The only error from gnome-mplayer in .xsession-errors is:

Resizing to 624 x 332 
Changing window size to 624 x 332 
ERROR: Failed to get value of property 'sub_demux'.

which was also in the above output. What is sub_demux?

About the second window in the root, it happens with openbox, ratpoison, 
awesome, 
but not with gnome (in gnome with the second file I see no video output at 
all), 
perhaps because in gnome there is a daemon controlling the root window (while 
in the 
others I set the wallpaper with a one-time command such as xsetroot or feh). 

Original comment by patroc...@gmail.com on 3 Jan 2009 at 10:07

GoogleCodeExporter commented 8 years ago
Oh, it concerns subtitles, there is no subtitle in the files I am playing, so 
this 
is probably unrelevant.

Original comment by patroc...@gmail.com on 3 Jan 2009 at 10:13

GoogleCodeExporter commented 8 years ago
I am experiencing the same issue, and it has occurred on 2 systems so far.  
Using it
as a firefox plugin, it will work without issue until it randomly starts only 
playing
3 seconds of video.  Seeking within the video being streamed will not shake it 
from
the 3 second problem.  I've been running Ubuntu Hardy, and installing from the
repository.  I have not tried SVN.  The main machine this pops up on is my 
Thinkpad
X32 laptop.  What's even stranger, is if I close firefox, do "sudo aptitude 
purge",
and then do a reinstall, it will work fine until it creeps up again.  I've 
noticed it
has something to do with closing tabs in firefox before a video finishes.  I've 
also
seen it occur when I've quit the player while a video is streaming in.  I'm 
thinking
its more of an mplayer issue because i've had problems before watching WMV 
streams
with the regular mplayer plugin.  Something gets goofed up and kills the plugin 
until
its purged and reinstalled.

Original comment by killerbe...@gmail.com on 6 Jan 2009 at 2:39

GoogleCodeExporter commented 8 years ago
most likely mplayer is hanging on the machine. Check your version of mplayer, 
if it
is 1.0rc2 then that version is quite old and may be causing the problem. 
Instead of
reinstalling does a reboot also correct it?

Original comment by kdeko...@gmail.com on 6 Jan 2009 at 4:54

GoogleCodeExporter commented 8 years ago
I have made some changes to SVN on how the original window is setup, can you 
please
test that and see if it helps any. I'm not sure it will, but just curious.

Original comment by kdeko...@gmail.com on 23 Jan 2009 at 2:28

GoogleCodeExporter commented 8 years ago
Tried it, but no difference.

Original comment by patroc...@gmail.com on 23 Jan 2009 at 3:52

GoogleCodeExporter commented 8 years ago
Does passing the --sync option to gnome-mplayer help any?

Original comment by kdeko...@gmail.com on 23 Jan 2009 at 4:03

GoogleCodeExporter commented 8 years ago
No difference. By the way, thanks for your extensive help.
In these weeks I have tried to look for something peculiar in my X server 
setup, but
I did not find anything relevant.
However I have verified that in the same machine, using zenwalk (so a different
kernel, a different xorg version, a different gtk version), gnome-mplayer works
flawlessly, so the problem is somewhere in my archlinux setup (but seems to 
affect
only gnome-mplayer).

Original comment by patroc...@gmail.com on 23 Jan 2009 at 4:10

GoogleCodeExporter commented 8 years ago
That is interesting. I do know that people are using gnome-mplayer with arch 
linux,
so hopefully there is a fix out there. Do you know who the maintainer of
gnome-mplayer on arch is?

Original comment by kdeko...@gmail.com on 23 Jan 2009 at 4:45

GoogleCodeExporter commented 8 years ago
gnome-mplayer is in the archlinux binary community repo, so it is maintained by 
a
so-called Trusted User. His name is allan and his email is mcrae_allan at 
hotmail dot
com.
The page of the package is http://aur.archlinux.org/packages.php?ID=9498.
I have discussed my issue in the following thread in the archlinux forum, but I 
guess
that some of the people in the thread were actually discussing a different 
issue:
http://bbs.archlinux.org/viewtopic.php?id=58213

Original comment by patroc...@gmail.com on 23 Jan 2009 at 4:57

GoogleCodeExporter commented 8 years ago
I've have the same problem for a long time on two different machines, a laptop 
and a
desktop. Basically every time a video is supposed to play in Firefox (3.0.5) and
gecko-mediaplayer 0.6.0 is called to do the job, the plugin properly launches 
but the
video will never actually get around to playing: it just keeps loading and 
loading
with only black in the video screen. Here's my mplayer info for my desktop:

MPlayer 1.0rc2-4.2.3 (C) 2000-2007 MPlayer Team
CPU: Intel(R) Pentium(R) D CPU 3.40GHz (Family: 15, Model: 6, Stepping: 4)
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.

Running fully up-to-date Ubuntus (8.04 on desktop) and (8.10 on laptop). I have
compiz going too with the free drivers.

Original comment by jason.le...@gmail.com on 30 Jan 2009 at 3:09

GoogleCodeExporter commented 8 years ago
please upgrade gnome-mplayer and gecko-mediaplayer to current releases and then 
see
if you can get a video to play normally in gnome-mplayer. Once you get 
gnome-mplayer
working, gecko-mediaplayer should work correctly.

Original comment by kdeko...@gmail.com on 30 Jan 2009 at 3:39