You are not logged in.

#1 2008-11-22 21:11:30

Perre
Member
Registered: 2008-01-22
Posts: 189

[Solved]Wierd difference between running '# freevo' vs. '#sudo freevo'

Hi!

I'm using freevo as a media center and with that, mplayer, as main media player. Since I have a old computer I'm also using CoreAVC to play my HD material. But
now I'm experiencing a wierd problem. hmm

When I start freevo by typing '# freevo' and not '# sudo freevo', mplayer seems to be responsive to it's config file in ~/.mplayer/conf. This means
that for example the subtitle size can be adjusted etc. The problem is that at the same time, mplayer seems to be ignoring it's configurement in local_conf.py (the
config file for freevo). So it won't run movies with the CoreAVC codec cause it invoked from the local_conf.py by adding -vc coreserve to movie format config.

On the other hand when typing '# sudo freevo' mplayer seems to ignore it's own config file (meaning my subs are HUGE), but it uses CoreAVC. If I don't run freevo
as root it also crashes after a short while.


What is causing these problems? I've just done a format and reinstall and freevo never acted like this before. How can I get mplayer to follow both it's config file
statements and the config from the freevo conf?

Last edited by Perre (2008-11-22 22:25:42)

Offline

Board footer

Powered by FluxBB