spurious double 'pause' or double 'play' states

[GoogleCodeExporter]

What is the expected output? What do you see instead?
For two releases now I very often get spurious double 'pause' or
 double 'play' states. For example, I am now playing an .flv file and
 if playing is paused and I hit the 'space' key, then this is what I
 get in the console:
 GMLIB-Message: in media state change with state = play dontplaynext = 0
 GMLIB-Message: in media state change with state = pause dontplaynext = 0
 GMLIB-Message: in media state change with state = play dontplaynext = 0

 If I do the reverse, the movie is playing and I hit space:
 GMLIB-Message: in media state change with state = pause dontplaynext = 0
 GMLIB-Message: in media state change with state = play dontplaynext = 0
 GMLIB-Message: in media state change with state = pause dontplaynext = 0

 This makes for a very jerky play/pause experience. Is this issue
 known? I'm using 1.0.8.

What version of the product are you using? On what operating system?
I'm see this with 1.0.8 or 1.0.9a, and mplayer or mplayer2.

Please provide any additional information below.
This is a follow-up from the ML discussion: 
https://groups.google.com/d/msg/gnome-mplayer/cQ4GEGn6ssQ/TH7ky3335ZgJ .

Original issue reported on code.google.com by landroni...@gmail.com on 24 Nov 2013 at 8:15

[GoogleCodeExporter]

Can you please run gnome-mplayer from a terminal with the -v option set so that 
I can look at the output. I am not seeing this behavior on my machine.

Original comment by kdeko...@gmail.com on 24 Nov 2013 at 2:54

[GoogleCodeExporter]

Here's what I see. The movie was playing and I hit pause: 
GMLIB-Message: Posting Event TimeChanged
GMLIB-Message: old: position=231.100 length=1284.660 start_time=0.000 
run_time=0.000 volume=1.00 player=running media=play 
uri=file:///proc/16120/fd/36
GMLIB-Message: in media state change with state = pause dontplaynext = 0
GMLIB-Message: trying to enable screensaver
GMLIB-Message: Posting Event MediaPaused
GMLIB-Message: new: position=231.100 length=1284.660 start_time=0.000 
run_time=0.000 volume=1.00 player=running media=pause 
uri=file:///proc/16120/fd/36
GMLIB-Message: old: position=231.100 length=1284.660 start_time=0.000 
run_time=0.000 volume=1.00 player=running media=pause 
uri=file:///proc/16120/fd/36
GMLIB-Message: in media state change with state = play dontplaynext = 0
GMLIB-Message: trying to disable screensaver
GMLIB-Message: Posting Event MediaPlaying
GMLIB-Message: new: position=231.100 length=1284.660 start_time=0.000 
run_time=0.000 volume=1.00 player=running media=play 
uri=file:///proc/16120/fd/36
GMLIB-Message: old: position=231.100 length=1284.660 start_time=0.000 
run_time=0.000 volume=1.00 player=running media=play 
uri=file:///proc/16120/fd/36
GMLIB-Message: in media state change with state = pause dontplaynext = 0
GMLIB-Message: trying to enable screensaver
GMLIB-Message: Posting Event MediaPaused
GMLIB-Message: new: position=231.100 length=1284.660 start_time=0.000 
run_time=0.000 volume=1.00 player=running media=pause 
uri=file:///proc/16120/fd/36
GMLIB-Message: Posting Event LeaveWindow

The pause/play/pause sequence happens in about a quarter of a second, 
generating this "jerky" behaviour. Using 1.0.9a and mplayer. 

Original comment by landroni...@gmail.com on 26 Nov 2013 at 8:12

[GoogleCodeExporter]

Please post the whole log and do not cut anything out. Also that URI is pretty 
unusual, can you tell me why you are doing things that way?

Original comment by kdeko...@gmail.com on 27 Nov 2013 at 3:49

[GoogleCodeExporter]

See attached. The issue happens towards the end of the log. This time the URI 
is more standard: a local video file. 

Original comment by landroni...@gmail.com on 27 Nov 2013 at 5:10

Attachments:

• gnome-mplayer-spurious-play-pause.log

[GoogleCodeExporter]

Ok, the log looks ok from what I can tell except from the part where you says 
is fails. So I have another question for you. If you just use mplayer to play 
the file do you have this problem.

mplayer [video file]

Also, it looks like you have force cache enabled, can you turn that off.

Original comment by kdeko...@gmail.com on 28 Nov 2013 at 1:51

[GoogleCodeExporter]

Ok, I did some test with gmtk 1.0.9a, gnome-mplayer 1.0.9a and mplayer  SVN 
r36171 with some mkv files I have here and was unable to duplicate the problem.

Original comment by kdeko...@gmail.com on 28 Nov 2013 at 2:59

[GoogleCodeExporter]

Here's a log with gnome-mplayer and cache disabled. The issue occurs at the end.

Original comment by landroni...@gmail.com on 30 Nov 2013 at 7:58

Attachments:

• gnome-mplayer-spurious-play-pause-nocache.log

[GoogleCodeExporter]

I have to test it a bit more, but I haven't encountered this issue when simply 
using mplayer sofar. Just in case I attach the log. 

As far as I can see something wrong is going on in gnome-mplayer. Also, as far 
as I can remember this issue appeared in gnome-mplayer a couple of releases 
ago, so it would seem to be a regression. 

Original comment by landroni...@gmail.com on 30 Nov 2013 at 7:51

Attachments:

• mplayer.log

[GoogleCodeExporter]

For what it's worth, I keep encountering this bug with r2469. With both mplayer 
and mplayer2. 

Is there any other info about my system that could help you track down this 
issue? 

Original comment by landroni...@gmail.com on 12 Jan 2015 at 1:01