Hi,
yesterday I have installed the newest snapshot of freevo and mmpython. This was my 
first "upgrade" of freevo. Here are my problems and solutions about that...

1. The startup script did not recognize that the runtime was present. (It complained 
about "import Image"...) It tried to find runapp in directory runtime. However, runapp 
resided directly in the freevo main directory. 
I have just copied runapp to runtime/runapp to make this work.

2. freevo won't work any more when started from console (without X)
   I have first tried to start freevo in KDE. Here (after ./freevo setup), this 
worked. But trying directly from console was not that a good idea. I have tried to set 
display in freevo.conf to 'vesa', 'sdl' and some others, but nothing really worked. 
With "vesa" freevo itself started, but mplayer won't play.
Then, I have deleted the following lines from osd.py (in init of class osd):
        # sometimes this fails
        if not os.environ.has_key('SDL_VIDEODRIVER') and \
               config.CONF.display == 'x11':
            os.environ['SDL_VIDEODRIVER'] = 'x11'
and I have deleted the display-line in freevo.conf. After that, I could run freevo 
incl. mplayer directly from console in framebuffer mode and in KDE.
I have no real clue why this is like it is, perhaps someone can clarify?

3. In ./src/tv/plugins/mplayer.py, the use of driver=v4l is fixed in the coding. I 
have changed that to driver=v4l2. 
What about having a config option for the tv driver?

4. I had some problems with mplayer, so I switched on MPLAYER_DEBUG. After doing so, 
mplayer.py (both the one in video/plugins and tv/plugins) tried to get 
$FREEVO_STARTDIR from the environment, but there was no FREEVO_STARTDIR set. I don't 
know why, but this seemed to lock up my system when started in framebuffer mode...
I have changed the coding so that the debug output goes directly to the current 
directory.

And just a last thing:
In my first freevo installation, I did some settings directly in freevo_config.py. 
This turned out to be a bad idea. Freevo_config.py is overriden by new snapshots, 
local_conf.py is not.
The version numbering of the config file is really a good thing. Freevo tells you the 
new features of the config automatically.

Regards,
        Thorsten
 


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users

Reply via email to