Closed z0Kng closed 2 months ago
Auto Created VSMGWL-75618 for further analysis.
Hi@z0Kng, Current scaling/iscaling enum value cannot be reported as caps. The value cannot be updated to avoid backward compatible issue. you can use flag definition directly in document documentation instead of call vaQueryVideoProcPipelineCaps().
Hi @VincentCheungKokomo thanks for the detailed answer. I had already hardcoded it, I just wanted to check if the hardware supports the different interpolation methods. So is it safe to assume that all hardware supports all interpolation and scaling methods?
Hi @VincentCheungKokomo thanks for the detailed answer. I had already hardcoded it, I just wanted to check if the hardware supports the different interpolation methods. So is it safe to assume that all hardware supports all interpolation and scaling methods?
Yes, hardware supports all interpolation and scaling methods.
Which component impacted?
Video Processing
Is it regression? Good in old configuration?
No, this issue exist a long time
What happened?
Shouldn't it be possible, as described in the documentation, to query the supported filter_flags from the driver with vaQueryVideoProcPipelineCaps?
However, filter_flags is always 0: https://github.com/intel/media-driver/blob/5641059bea7098ab0abd40dc9f3d13f1c7797013/media_driver/linux/common/ddi/media_libva.cpp#L6675
What's the usage scenario when you are seeing the problem?
Others
What impacted?
Its needed for the gstreamer va plugin implementation of interpolation methods, see: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/7301
Debug Information
No response
Do you want to contribute a patch to fix the issue?
None