On 10/10/2008 10:04, Alberto Hernando said the following: > El Viernes, 10 de Octubre de 2008 09:25, Scott Serr escribió: >> twm -> freevo -> mplayer >> only xv = no video / black >> only sdl = no video / black >> only x11 = no video / black >> >> Now, I decided to do the same test with freevo -fs from console >> only xv = no video / black >> only sdl = no video / black >> only x11 = no video / black >> >> BUT... "xv,x11" works in the freevo -fs case but with high CPU. > > > Interesting. > Could you add vesa to your tests? It only uses cpu power, so if you get your > 50% with vesa, it could mean that freevo uses it as a fallback method for > some reason. Another thing you could try is to upgrade to the lastest freevo. > I don't know if something regarding this has changed, but... > Anyway, it looks like a serious bug. Consider reporting it when you have a > clear idea of what's going on.
Indeed this is interesting. Clearly the xv driver is not working when you start freevo -fs, it is typical of the x11 driver to use a high level CPU and jerky play back. The main difference is that with the -fs option X starts without a window manager. I think that you need to check your xorg.conf. It is possible that your normal window manager loads drivers/modules when it starts. Duncan ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Freevo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-users
