This is a shame as I am trying to patch mplayer.py so I can set a different vo device and vo options depending on the suffix. Why? Well I have a VIA EPIA MII board and by now mplayer has HW accelleration for mpegs via the xvmc vo device and HW accelleration for other movies via the xvidix vo device, both with their own options and they do not play nice together when put in the .mplayer/config. DOH!
So is there a way to patch this in freevo (have tried some things but to no avail) or is this a bug in mplayer?
Paul
Paul Sijben wrote:
it is one 'xvidix -colorkey 0x000000'
The def in local_conf.py is: MPLAYER_VO_DEV = "xvidix" MPLAYER_VO_DEV_OPTS = ' -colorkey 0x000000'
so now you mention it it is odd that these are in one. Well spotted!
I'll try and put the colorkey in the .mplayer/config .
Paul
Dirk Meyer wrote:
Paul Sijben wrote:
right getting debugging more organized:
/var/log/freevo/mplayer-stderr.log sais
'-autosync' '100' '-nolirc' '-autoq' '100' '-screenw' '720' '-screenh' '576' '-fs' '-slave' '-ao' 'alsa' '-v' '-vo' 'xvidix -colorkey 0x000000' '-cache' '5000' '-loop' '1' '//media/films/Vlamboog.mpg'
Can you check, is it 'xvidix -colorkey 0x000000' like you posted or 'xvidix' '-colorkey 0x000000'? The difference? Each quote is one argument and 'xvidix -colorkey 0x000000' is a bad video device, sure.
Dischi
-- Paul Sijben mailto:[EMAIL PROTECTED] Amersfoort, NL http://www.sijben.net tel:+31 334557522 fax:+31 33 4557523
------------------------------------------------------- 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
