[Freevo-users] Re: EPIA and Framebuffer: Not playing full screen

[Jason Lunz]

[EMAIL PROTECTED] said:
> (I have the VESA framebuffer working fine)

btw, i boot with vga=0x315, if that helps anything. other resolutions
probably work.

> First question: when I compile MPlayer, I don't see
> 'vidix' os one fo the output options.  I see 'xvidix',
> but no 'vidix'.

I don't have 'vidix' in the configure output either, but it works. I
think they both use the same backend drivers, but the two methods differ
in how the common vidix infrastructure sets up the drivers (i.e. the
xvidix variant gets screen or window size from the X server, while vidix
uses the framebuffer console. or something like that).

The goal is to use the vidix/drivers/cyberblade_vid.c driver, if you're
curious.

>   Optimizing for: i586 mmx 3dnow mtrr

According to an lkml alan cox post, the instruction scheduling for the
via C3 chips is most similar to i486, so that's what you want to
optimize for. I pass "-target=i486-linux --enable-mmx --enable-3dnow
--disable-mmx2 --disable-3dnowex --disable-sse --disable-sse2" to
mplayer's configure.

> Also, when you say you have MPlayer run eith '-vo
> fbdev:vidix', is that what is entered on the 'display'
> line in freevo.conf?  I.e.:
> 
> display = fbdev:xvidix

close... no x. "display = fbdev:vidix"

> And for the scaling options you mentioned, I assume those are added to
> the appropriate video playing .PY file?

I have this in local_conf.py:

OVERSCAN_X = 24
OVERSCAN_Y = 40

MPLAYER_ARGS_DEF = '-ac mad, -autosync 100 -autoq 100 -zoom -x %s -y %s' %
(CONF.width - 16, CONF.height - 40)

You can also use -fs, but with my config (an 800x600 fbdev) that
actually scales to 800x546 for some reason. The above config gets you
784x560, which seems to fit my TV better.

Jason



---
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users

Re: [Freevo-users] Re: EPIA and Framebuffer: Not playing full screen

[Alan Murrell]

Hey Jason,

Quick question or two regarding fbdev:vidix...

(I have the VESA framebuffer working fine)

> you use mplayer with -vo fbdev:vidix.

First question: when I compile MPlayer, I don't see
'vidix' os one fo the output options.  I see 'xvidix',
but no 'vidix'.  Here is my "summary" output from just
runnig './configure':

--- BEGIN ---
  Install prefix: /usr/local
  Data directory: /usr/local/share/mplayer
  Config direct.: /usr/local/etc/mplayer

  Byte order: Little Endian
  Optimizing for: i586 mmx 3dnow mtrr

  Enabled optional drivers:
Input: streaming edl tv cdda mpdvdkit2 vcd
Codecs: libdv libavcodec libvorbis libmad liblzo
Audio output: alsa9 esd arts oss nas sdl
mpegpes(file)
Video output: xvidix dxr3 sdl vesa jpeg png
mpegpes(file) fbdev aa ggi opengl dga xv x11
  Disabled optional drivers:
Input: tv-v4l tv-bsdbt848 dvdnav dvdread dvdcss
Codecs: qtx opendivx xvid real xanim dshow/dmo
win32 gif
Audio output: sgi sun dxr2 win32
Video output: bl zr dxr2 directx gif89a svga xmga
mga directfb tdfxfb 3dfx
--- END ---

There's 'xvidix' but no simple, plain 'vidix'.  I
tried FB mode + 'xvidix', but no go (I didn;t thin
there would be, but I had to try :-) )

Also, when you say you have MPlayer run eith '-vo
fbdev:vidix', is that what is entered on the 'display'
line in freevo.conf?  I.e.:

display = fbdev:xvidix

And for the scaling options you mentioned, I assume
those are added to the appropriate video playing .PY
file?

Thanks for you enlightenment! :-)

Alan



__ 
Post your free ad now! http://personals.yahoo.ca


---
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users

[Freevo-users] Re: EPIA and Framebuffer: Not playing full screen

[Jason Lunz]

[EMAIL PROTECTED] said:
>>  - use the standard kernel vesa framebuffer (not an accelerated one)
> 
> Hrm, how does this affect playback of DivX, etc.?  I heard it's fairly
> slow on this platform.

the framebuffer is slow, but it doesn't matter when you use mplayer with
-vo fbdev:vidix.

> I think this is only required with the epiafb module, since when it is
> inserted, it makes the display go all wonky until you specify the '-b
> ntsc' with the tvout tool (I think the epiafb uses PAL by default)

I haven't tried epiafb.

> I'm wondering if tools compiled specifically for the
> epia (MPlayer, etc.) would help performance any?

The epia vidix support in mplayer is the _only_ epia-specific thing I
use, and it's fine. But I don't use X.

Let me know what config you settle on. I'd like to know what else works
well.

Jason



---
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users

[Freevo-users] Re: EPIA and Framebuffer: Not playing full screen

[Alan Murrell]

Hi Jason,

Thank you for your response.

> I have the same problem with an Epia 800. (a Trident
> CyberBlade-based board).

Actually, I think that's the same board I have :-)  I
actually bought it to play with, and once satisifed
with the results, will likely upgrade to one of the
other models, and perhaps give this one as an Xmas
gift or something to a friend :-)

>  - set overscan/ntsc in the bios

I think I've done that.

>  - use the standard kernel vesa framebuffer (not an
> accelerated one)

Hrm, how does this affect playback of DivX, etc.?  I
heard it's fairly slow on this platform.  Actually,
one thing I have noticed is when playing an MP3 in
framebuffer, if I press FFWD or some other key,
everything freezes :-(

>  - don't use any tvtool or tvout to set anything (It
> automatically uses tvout if no monitor is attached)

I think this is only required with the epiafb module,
since when it is inserted, it makes the display go all
wonky until you specify the '-b ntsc' with the tvout
tool (I think the epiafb uses PAL by default)

>  - use -vo fbdev:vidix with mplayer. It has built-in
> support for the hardware.

Hrm, I will have to give that a try.  It may even
correct the problem I just mentioned regarding the
MP3's, if there's built-in support :-)

> X seemed slow to me too. I didn't try freevo under X
> on the epia, but mplayer was far slower under X.

Actually, I was playing with Freevo + X (on the epia)
this morning (output to a monitor, since I still
haven't been able to X to display ont he TV screen
yet), and there was no window manager running (I
figured out how to do it).  It seemed pretty okay,
actually.  We'll see when I actually get it outputting
to my TV screen (I want to have both framebuffer and X
support)

I'm wondering if tools compiled specifically for the
epia (MPlayer, etc.) would help performance any?

> X driver, so that's not really a good test. Did you
> try it?

Actually, no, I plum forgot about it.  Perhaps rather
than smack my head against the wall, I should give it
a go :-)

> That sounds nice, I may have to experiment with X
> again. The color of the epia 800 tv out leaves 
> something to be desired.

Actually, when I think about it, I am not sure that
the "vibrant blue" will come out through X even on the
TV screen, or at least, prolly not on my TV, since the
colour palette is prolly fairly limited.

Alan


__ 
Post your free ad now! http://personals.yahoo.ca



---
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users

[Freevo-users] Re: EPIA and Framebuffer: Not playing full screen

[Jason Lunz]

[EMAIL PROTECTED] said:
> I have everything pretty much working (Freevo menu, 800x600 screen
> size, etc.), except when I play video files, they are not played full
> screen.  Instead, they are played in a small window that is centered
> in the middle of the TV screen.

I have the same problem with an Epia 800. (a Trident CyberBlade-based
board).

> Would this be an issue with the framebuffer driver (I am using the
> epiafb.o module from , although I am running under
> 'fbdev' in Freevo.  My frambuffer lines (the ones I use to get into
> framebuffer mode) look like this:
> 
>   modprobe fbgen
>   modprobe epiafb
>   fbset -g 800 600 800 600 32
>   /usr/local/epifb/tvout -b ntsc

I've experimented a bit, and it turns out that the best thing for me has
been to:

 - set overscan/ntsc in the bios
 - use the standard kernel vesa framebuffer (not an accelerated one)
 - don't use any tvtool or tvout to set anything (It automatically uses
   tvout if no monitor is attached)
 - use -vo fbdev:vidix with mplayer. It has built-in support for the
   hardware.

The epia doesn't seem to do hardware scaling (that or mplayer doesn't
support it), so I've been doing it in software. You'd think that would
be too slow, but for most tv caps it's fast enough. To get the overscan
right, I've been using:

mplayer -vo fbdev:vidix -zoom -x 784 -y 560

> The Freevo main menu itself looks pretty good (there's just a small
> black strip across the top.  It's only whne playing video files that I
> have an issue.

Once you have video-out displayed on the tv with overscan, you can
compensate for it with OVERSCAN_X and OVERSCAN_Y in local_conf.py. I use
X=24 and Y=40.

> It's more to do with the fact that Freevo responds much quicker in
> framebuffer mode than X Windows (from what I could test when I was
> running it on the monitor)

X seemed slow to me too. I didn't try freevo under X on the epia, but
mplayer was far slower under X. Though I didn't use the proprietary epia
X driver, so that's not really a good test. Did you try it?

> However, the skin colouring is *so* much more vibrant in X than from
> frambuffer (in framebuffer, it looks kinda aqua-coloured, and in X, it
> looks like a really awesome blue!)

That sounds nice, I may have to experiment with X again. The color of
the epia 800 tv out leaves something to be desired.

> Out of curiousity, would performance under X be more a function of CPU
> or RAM?  There's not much I can do about the CPU, but I can add more
> RAM to the 128MB already in there.

RAM won't speed it up.

Jason



---
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
___
Freevo-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freevo-users