[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 <http://epia.sf.net>, 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
