On Sunday 13 March 2005 02:25, Daniel Phillips wrote: > It should be pretty easy to make that decision now. The hardware budget > doesn't leave any room for extras that can already be accomplished with > the existing 3D pipeline. MPlayer et al know how to convert YUV, so > the card doesn't need to. Host CPU overhead is unlikely to be an issue > here.
Time for me 2eurocents.. Hardware RGB->YUV is, imho, a must for the card to be usable in, for example, a home entertainment system. It's already difficult to find a quiet CPU that can power that without having MC in hardware, let alone without having colourspace transform in hardware. It's not only CPU usage, also double bandwidth (if outputting to RGB24) over the bus. A few figures from my computer for DVD: Accelerated colourtransform: 35% CPU Software colourtransform and no scaling. Scaling is software in this mode, but I did not disabled scaling in attempt to only measure transform: 75% CPU Output to mga400 HW GL: ~400% CPU However, if the video is ~QCIF resolution, CPU usage drops enough to make it watchable, and maximizing the window does not noticeably increase CPU usage, thanks to the HW scaling. Did I mention that I dislike QCIF resolution? I would really hope for YUV->RGB transform in hardware. _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
