On Wed, 2003-11-19 at 04:29, StormeRider wrote:
> I've actually been having a different issue. I just upgraded from
> Mandrake 9.1 to 9.2 (now that the ISOs are available, had to use
> BitTorrent to get them, but that's neither here nor there), and took the
> chance to upgrade tonight from 1.3.4 to 1.4rc4.
>
> (On a side note, please update the docs to reference PyXML 0.8.3 rather
> than 0.8.1-- .1 with python 2.3 causes an error about CHARSET, which .3
> handles fine.)
>
> Under 1.3.4, if I started freevo windowed, and played a movie, and then
> went to fullscreen, it would be blank. If I started it fullscreen, and
> played the movie, it would be fine, fullscreen. Hitting 'z' would bring
> it back to windowed, with the odd mplayer overlap. Hitting 'z' again
> would give the blank issue again.
>
> Under 1.4rc4, if I start freevo fullscreen, and play a movie, it
> _forces_ freevo out of fs mode into windowed.
>
> I'm not sure if this has something to do with freevo, or the OS update.
> (I didn't really test my 1.3.4 install under 9.2... just that it was
> recording last night.) Mplayer itself seems to be fine flipping in and
> out of FS mode, but it always was. I'm wondering if something in the way
> freevo interacts with mplayer changed, or if I need to recompile mplayer
> manually again.
>
> Any suggestions? 1.4r4 looks really nice, but the fs issue is something
> I do want to nail down as soon as possible. Otherwise I'll be using it
> mainly for the recording system rather than a client as well.
>
> --Morgan
>
Just spent some time tonight working on this. Apparently the mplayer
command issued to watch a movie is:
/usr/bin/mplayer -autosync 100 -nolirc -autoq 100
-screenw 800 -screenh 600 -fs -slave -ao oss:/dev/dsp
-v -vo xv,sdl,x11, -cache 5000
-idx /files/freevo/Movies/Recorded/blah.avi
If I run this on the CLI it limits the fullscreen to 800x600. By hitting
'f', it turns it to the res it was recorded at (640x480), and 'f' again
puts it back to 800x600.
I think what is happening is that when I full-screen freevo, and then
have it call mplayer, it isn't telling mplayer the same height / width
that freevo is running at, which dumps mplayer out of fullscreen to
display.
I checked local_conf.py and found:
MPLAYER_ARGS_DEF = (('-ac mad, -autosync 100 -nolirc
-autoq 100 -screenw %s -screenh %s -fs')
% (CONF.width, CONF.height))
It was commented out. Uncommenting it didn't change anything.
This led me to /etc/freevo/freevo.conf, where I found
geometry = 800x600
Changing it to 1600x1200 works for fullscreen playback, but freevo
itself is now too large until I fullscreen it within X. Setting it to
1200x900 looks clean in freevo, but mplayer once again breaks out when
it goes to play. Seems to need to match the resolution of the desktop to
not break out of freevo (when I say this, I mean that the monitor goes
black, I see warped pixels, and the resolution shifts, with mplayer
overlaid on my gnome desktop).
Any suggestions? 1.3.4 used to be fine with the 800x600 freevo
resolution without mplayer causing this issue when operating in
fullscreen mode.
At the moment I just have freevo starting in fullscreen mode itself, and
everything looks fine, but I don't need it that way for playing mp3s and
whatnot.
--Morgan
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users
