-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[gstreamer-vaapi][ICL] vaQuerySurfaceAttributes doesn't support YUY2/UYVY VASurfaceAttribPixelFormat. #322
Comments
which context? VP, ENCODE,DECODE? |
Hi @XinfengZhang , Encode. |
@feiwan1 @XinfengZhang I submitted one PR for this previously. Could you please review it? Thanks. |
Hi @wangyan42164 , Did you mean PR #323? It should be the fix of issue #318, not the fix of this issue. |
@feiwan1 Sure. I can check it. |
@feiwan1 How should I reproduce this issue? What profile do you use? VAProfileHEVCMain? |
Hi @wangyan42164 , I used gst-vaapi cmdline to reproduce this issue: gst-launch-1.0 videotestsrc num-buffers=100 ! video/x-raw,format=YUY2 ! vaapih265enc ! fakesinkThe default profile is VAProfileHEVCMain, does this profile support YUY2 in driver side? Or I need to use |
@feiwan1 I did some initial checking on my KBL(Gen9) platform because I have not ICL (Gen11). But I think they are similar in this issue.
It seems cannot support YUY2 based on the following log: If necessary, I can submit PR for adding YUY2 and UYVY surface support in media driver. |
@wangyan42164 , please add YUY2/UYVY surface support in meida-driver. I will take a look at gst-vaapi side. |
Fixes intel#322. Signed-off-by: Yan Wang <yan.wang@linux.intel.com>
@feiwan1 Added. Thanks. |
I read the whole thread, it is related to codec context. @XinfengZhang to check it. |
Based on @Maggieie's comments, we don't support it. |
Now, vaQuerySurfaceAttributes only return NV12 format with attrib type of VASurfaceAttribPixelFormat.
Need your help to also support YUY2/UYVY to meet Iotg requirement.
The text was updated successfully, but these errors were encountered: