Re: Video Overlay on C3200

Tim Chick <[email protected]>
Newsgroups gmane.comp.handhelds.openzaurus.devel
Message-ID <[email protected]>
On Tuesday 27 February 2007 00:33, Tim Chick wrote:
> Hi List!
>
> Just a quick note to say I have YV12 overlays working on the C3200 with
> mplayer. I'm using the pxafb_overlay module from the 2.6.17 OE kernel.
>
> It still needs some more work, but it can play VCD (352 x 288) video
> properly without dropping frames, whilst playing audio.
>
> I still need to polish it quite a lot, speed it up, add rotation, more
> video formats, OSD and double buffering. I also hope to put at least some
> of the video buffer into SRAM to speed things up. Just a shame the PXA270
> does not support hardware scaling and rotation.
>
Ok, I have updated the source on my website.

It now includes OSD (using overlays), and fast rotation code. Also as far as I 
know all the bugs with the overlay persisting following close, and with 
suspend resume have now been fixed. (Actually, if you suspend then resume in 
full screen mode, you will end up in non-full screen mode following the 
resume, but that it is up to the kernel driver!)

It now does a pretty plausible job of being a video player!

Example command lines would be:

Not fullscreen mode:
mplayer -vo pxa -cache 2048 -double -framedrop [file]

Full screen mode (will auto rotate and crop so video best fits screen)
mplayer -vo pxa -vm -cache 2048 -double -framedrop [file]

In case anyone didn't know, if you press on the screen where the console icon 
would be, you reactive the console text input, and can use the mplayer 
controls. (By the way, is there a fix for this, it's really annoying!)

One thing I noticed is that mplayer by default was being compiled for arm  v3 
instruction set. This meant that ldrh and strh were missing, and all the 
pipeline optimisation done by the compiler was messed up. Compiling for 
xscale drops cpu usage of video decode by about 20%! I guess this is why 
there are armv5te packages on the feed browser, but it's not exactly clear 
that those are the ones which should be used. In fact, why do the arm-v3 ones 
even exist? arm v4 (strongarm) would be a better minimum? But why is there a 
minimum when allpackages are built for an xscale?

Thanks,
Tim


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.