<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang="ZH-CN" link="blue" vlink="purple"> <div class="WordSection1"> Yes, it should be like this, if you still have concern, you can map the surface out and dump to one bmp file to check.<o:p></o:p> <o:p> </o:p> From: Ratin [mailto:ratin3@gmail.com] Sent: Tuesday, January 29, 2013 11:40 AM To: Li, Xiaowei A Cc: Libva@lists.freedesktop.org Subject: Re: [Libva] VAConfigAttribRTFormat<o:p></o:p> <o:p> </o:p> <div> <div> <div> Awesome, the decoder I am working with does support it and when i create the surface with BGRA fourcc, the decoding still happens - so I am assuming if I get the decoded bistream, the data will already be packed in BGRA format - correct ? <o:p></o:p> </div> Thanks a bunch!<o:p></o:p> </div> Ratin<o:p></o:p> </div> <div> <o:p> </o:p> <div> On Mon, Jan 28, 2013 at 5:32 PM, Li, Xiaowei A <<a href="mailto:xiaowei.a.li@intel.com" target="_blank">xiaowei.a.li@intel.com</a>> wrote:<o:p></o:p> <div> <div> According to my understanding, VAConfigAttribRTFormat is used to describe the surface sample format, for example YUV420 , YUV422, RGB32, and VASurfaceAtrribPixelFormat aims to specify the detailed pixel storage layout, for example, one YUV420 surface can be stored with YV12/NV12/I420 pixel format and one RGB32 surface can be stored with RGBA/ARGB pixel format.<o:p></o:p> You can query whether VA_RT_FORMAT_RGB32 is supported as a render target format through “vaGetConfigAttributes()”, if supported, you can specify the BGRA fourcc when creating a render target surface.<o:p></o:p> Usually , video decoder only support YUV420 as decoding output, one color conversion is need to get BGRA surface.<o:p></o:p> <o:p></o:p> Thanks,<o:p></o:p> Xiaowei<o:p></o:p> <o:p></o:p> From: libva-bounces+<a href="http://xiaowei.a.li" target="_blank">xiaowei.a.li</a>=<a href="mailto:intel.com@lists.freedesktop.org" target="_blank">intel.com@lists.freedesktop.org</a> [mailto:<a href="mailto:libva-bounces%2Bxiaowei.a.li" target="_blank">libva-bounces+xiaowei.a.li</a>=<a href="mailto:intel.com@lists.freedesktop.org" target="_blank">intel.com@lists.freedesktop.org</a>] On Behalf Of Ratin Sent: Tuesday, January 29, 2013 6:19 AM To: <a href="mailto:Libva@lists.freedesktop.org" target="_blank">Libva@lists.freedesktop.org</a> Subject: [Libva] VAConfigAttribRTFormat<o:p></o:p> <div> <div> <o:p></o:p> <div> Hi got a question: I noticed that the #define values for for VAConfigAttribRTFormat in VAConfigAttrib does not include BGRA or ARGB formats (it does RGB 16 and RGB32), but the VASurfaceAttrib's VASurfaceAttribPixelFormat does allow it thru a four_cc value. Does that mean I can't decode the H.264 bitstream data directly to a BGRA surface, I have to convert explicitly? <o:p></o:p> <div> /* attribute value for VAConfigAttribRTFormat */ #define VA_RT_FORMAT_YUV420 0x00000001 #define VA_RT_FORMAT_YUV422 0x00000002 #define VA_RT_FORMAT_YUV444 0x00000004 #define VA_RT_FORMAT_YUV411 0x00000008 #define VA_RT_FORMAT_YUV400 0x00000010 #define VA_RT_FORMAT_RGB16 0x00010000 #define VA_RT_FORMAT_RGB32 0x00020000 #define VA_RT_FORMAT_PROTECTED 0x80000000<o:p></o:p> </div> <div> Thanks<o:p></o:p> </div> <div> Ratin<o:p></o:p> </div> </div> </div> </div> </div> </div> </div> <o:p> </o:p> </div> </div> </body> </html>