"FeNiX" wrote:
Hi!
Hi, I meant to reply to this yesterday. :)
I am running freevo 2.0 cvs. I have g400dh connected to tv. I am using
directfb for output. Everything that works works fine, there is no
window flickering like in 1.5.3.
Really? I would like to have your config please, Mplayer and df_xine
looked ok, but Freevo is a mess.
But it seems to me that mevas engine is a bit slow. I like new
mplayer freevo osd that is blended with bmovl, but then cpu usage of
mplayer is huge.
So it's no mevas problem, it is a problem with mplayer showing the
osd.
Without bmovl i get around 30% but with bmovl it gets up to 80%!
It should be possible in future versions to turn the bmovl code
off. No nice osd on mplayer, but works with slower cpu.
A while back I set self.use_bmovl = False in the mplayer video plugin because of this and other instability at the time. I've been meaning to turn it back on and test it some more.
I am suggesting to implement more directfb in mevas engine. For
example, when fading why not use directfb method SetOpacity? When
making fade in - fade out transition from one image to another why
not use two directfb windows and on one increasing opacity and on
the other decreasing it.
Yes, a real dfb imagelib in mevas would be great. But we need more man power to do all the cool stuff.
I have one started. I was pretty hot on it a few weeks ago but then Dischi went and made some things perform faster so there's been less need. :)
To replace bmovl for freevo osd in mplayer, xine or other external programs why not use directfb windows? In one window is mplayer, xine or whatever and in other window, that is on top, freevo osd.
I have been thinking about using this model for quite some time. I have an old directfb_osd plugin that does just this. Also the main Freevo screen is a directfb window. I will revive this plugin asap.
IIRC this is not possible, both mplayer and xine are running in fullscreen mode and don't like other dfb applications.
I had this working over mplayer but I might have been using force-windowed in /etc/directfbrc. It is also very possible to modify mplayer and df_xine to display onto an existing window's surface, still using the BES. This way Freevo could startup and maintain several windows - for main screen, OSD, picture in picture, video previews, and full video.
Best solution would be to build new display engine (based on directfb) that should be written in c. I am willing to work on this.
Great. But you don't need a new display engine. The display engine is not the problem, we need a dfb based imagelib for mevas. Maybe you can work together with Rob, he is maintaining pydirectfb. Maybe you need to expand something in the c part of pydirectfb to make it faster.
I don't think we need a new display engine either. I will commit the directfb imagelib by Saturday, then we can experiment with some different approaches.
Dischi, on a related note, I was wondering if you could add a get_ method to the src/gui/displays/ code that returns a list of (or active) canvas. I'd like to play with a dfb_osd plugin that gets the dfb canvas then uses that dfb instance to create a new window (or use an existing one) - instead of having to create a new / reinit directfb.
-Rob
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Freevo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-users
