If I have a video stream that is 352x480 and I play it on DirectFB's CRTC2 output using MPlayer with "-fs", it gets scaled up to 720x480, and MPlayer tells me:
VDec: vo config request - 352 x 480 (preferred csp: Planar YV12) VDec: using Planar YV12 as output csp (no 0) sh->aspect=1.333333 Movie-Aspect is 1.33:1 - prescaling to correct movie aspect. VO: [dfbmga] 352x480 => 640x480 Planar YV12 [fs] using crtc2 without doublebuffering vo_dfbmga: CRTC2 surface 720x480 YV12 vo_dfbmga: Video surface 352x480 YV12 (offscreen) vo_dfbmga: Sub-picture surface 720x480 LUT8 (Sub-picture layer) Selected video codec: [mpeg12] vfm:libmpeg2 (MPEG 1 or 2 (libmpeg2)) I also noticed that "StretchBlit()" is being called rather than Blit(). Is this scaling being done in software by MPlayer or in hardware on the G400 using the BES? If in software, will using the ":bes" sub-option to "-vo dfbmga" enable use of the BES to scale the image before outputting it on CRTC2? If yes to this question, and this is not the default, why would we not want to make it the default action? Does StretchBlit scale in hardware (using the BES) regardless of whether a BES surface was requested or not? Just trying to squeeze every last drop out of the hardware facilities that I can. :-) b. -- Brian J. Murrell
msg01322/pgp00000.pgp
Description: PGP signature
