Doh, forgot to RTFM. I have been ab-using the VO_DEV_OPTS
Now that I have it working I realize what I have been doing wrong.
I have made a small patch to mplayer.py so it now uses the right (for
me) vo device per movie type
the diff
-
183,188d182
#XXX PS
I replied yesterday but I don't see the message on the list, here
again :
I guess you are using anlogue tv card. the mplayer tv plugin is loaded
by default. If you wan't to use the tvtime plugin, you have to remove it
and load the tvtime plugin, see the wiki, tv plugins how to do that.
To see
I've been attempting to set up directfb for my G400-DH. Like a lot of
people on this list, I've run into a few problems along the way.
I'm running a 2.4.29 kernel and i2c 2.9.0 on debian/sarge. using
directfb 0.9.21, mplayer 1.0pre6a
First thing i ran into was where the matrox
Don't load the matroxfb_maven module - it blocks DirectFB from accessing
the maven registers.
Try again and post an updated log.
Also, I use primary-layer=2 (not 02 - not sure if that makes a
difference) - I've never needed to set bg-color or no-cursor either.
- Chris
On Thu, 24 Feb 2005
I gotta say that the wiki is not as informative to a novice as an experienced
user might think.
Maybe you are right, but it is a wiki, so feel free to improve it
mplayer works fine on my system. I can use it to view TV directly with
`mplayer /dev/cxm0` ... I just can't change
Christoph Kaminski wrote:
Hi!
I have a Problem with MAME and freevo...
If I start it, freevo crashes and I see these errors:
Traceback (most recent call last):
File /usr/lib/python2.3/site-packages/freevo/main.py, line 315, in
eventhandler
app.eventhandler(event)
File
