On Mon, Mar 24, 2003 at 05:14:15AM +0200, Ville Syrj�l� wrote: > > I'm not sure if they are mentioned in the API docs since I've never really > read them. Instead I just read idirectfbdisplaylayer.c ;)
:-) I am not sure if I have enough of an understanding that idirectfbdisplaylayer.c would make sense to me. Oh well. > The real solution is reference counting. Still only FIXMEs. OK. I have no problem hacking MPlayer to not do it, but I just thought if there were a supported way to do it, I would do it while I am rebuilding all of this stuff. > You could call SetOpacity from the launhcer. I wondered about that. > The screen will blink but > then again it would blink anyway when the pixelformat is changed back to > RGB32. Right. Is there any pixelformat that would be compatible between GTK and MPlayer to avoid the flicker? > Not sure if that's any better than patching mplayer though. Only, I guess, if I can get a compatible pixelformat. So the field parity looks good with the triple buffering patch. I did notice the setting of the flag to tell mplayer that vo_dfbmga.c does it's own frame timing is gone. Was that an oversight? I thought we had it so that MPlayer would sync on the output framerate and (hopefully) reduce the "out-of-sync timers" judder. b. -- Brian J. Murrell
pgp00000.pgp
Description: PGP signature
