[MPlayer-users] Most annoying long-standing bugs in Mplayer

Vladimir Mosgalin mosgalin at VM10124.spb.edu
Fri Mar 25 00:14:54 CET 2011


Hi Reimar Döffinger!

 On 2011.03.24 at 23:48:10 +0100, Reimar Döffinger wrote next:

> > Now, the default: -key-fifo-size 2. I click right button as fast as
> > possible and it works *all the time*, without any lags, missed clicks
> > and messages to console. So I'd say that on my system, with
> > key-fifo-size other than 2 all mouse actions are broken, but with
> > key-fifo-size=2 at least 3 common buttons work..
> 
> With such a short fifo, the double-click events will throw out other events.
> Using "-doubleclick-time 0" should avoid it.
> I think the other issues are also fixed from r33106 on.

Oh wow a great option indeed! It helps for "fast scrolling" case with
large fifo for sure, thanks!
It eases problem with low fifo, doesn't fix completely in my version,
but I see that you made changes to mplayer to solve that, I'll try it
out when I have time.

As a matter or fact, without doubleclick-time 0 even fifo of size 100
doesn't allow you to seek fast by rotating wheel; I suppose that's
because the idea of mplayer thinking that rotating wheel is like double
click is strange by itself. I mean, I can see where that comes from but
it's probably confusing to users, because no one expects it to behave
like this. Can't see how it can be useful.


Oh wait I lied; right as I was about to send mail I imagined how it can
be used (though it requires user to understand concept of fast wheel
rotate = "double clicking" in wheel direction, which is confusing). Kind
of "progressive" scroll can be created with that (not sure it's the
right word), by binding smaller "seek" to MOUSE_BTN3, bigger seek to
MOUSE_BTN3_DBL, even bigger to MOUSE_BTN3 + MOUSE_BTN3_DBL: the faster
you rotate wheel, the faster it seeks. Through it's, well, hackish and
I'd rather stick to small key-fifo myself which won't allow this anyway.

PS manpage stats that "doubleclick-time 0" is supported only by directx
vo?  Or something. Or that behaviour is different with directx?

-- 

Vladimir


More information about the MPlayer-users mailing list