[MPlayer-dev-eng] machine lockup due to xv driver
Felix Buenemann
atmosfear at users.sourceforge.net
Wed Jul 24 17:24:50 CEST 2002
On Wednesday 24 July 2002 16:58, D Richard Felker III wrote:
> On Wed, Jul 24, 2002 at 04:08:25PM +0200, Diego Biurrun wrote:
> > On Wed, Jul 24, 2002 at 03:56:29PM +0200, Felix Buenemann wrote:
> > > I have another problem, with current mplayer cvs, mplayer always shows
> > > the saturation OSD bar for two seconds, which is annoying. I also have
> > > savage, althoug it's Savage/MX chip.Note: this happens, no matter what
> > > vo is used.
> >
> > Yep, I also had this in the last 2 weeks or so. It disappeared, but now
> > it is apparently back.
>
> Yes, this is very annoying. It happens with mga_vid too.
And on GeForce with nvidia binary driver, too.
Btw. for those interested, here is the xvinfo output from the geforce:
number of attributes: 8
"XV_DOUBLE_BUFFER" (range 0 to 1)
client settable attribute
client gettable attribute (current value is 1)
"XV_COLORKEY" (range 0 to 16777215)
client settable attribute
client gettable attribute (current value is 66046)
"XV_AUTOPAINT_COLORKEY" (range 0 to 1)
client settable attribute
client gettable attribute (current value is 1)
"XV_SET_DEFAULTS" (range 0 to 0)
client settable attribute
"XV_BRIGHTNESS" (range -512 to 511)
client settable attribute
client gettable attribute (current value is 0)
"XV_CONTRAST" (range 0 to 8191)
client settable attribute
client gettable attribute (current value is 4096)
"XV_SATURATION" (range 0 to 8191)
client settable attribute
client gettable attribute (current value is 4096)
"XV_HUE" (range 0 to 360)
client settable attribute
client gettable attribute (current value is 0)
> Rich
--
Best Regards,
Atmos
____________________________________________
- MPlayer Developer - http://mplayerhq.hu/ -
____________________________________________
More information about the MPlayer-dev-eng
mailing list