Conversation
Signed-off-by: Zhang <furong.zhang@intel.com>
FurongZhang
force-pushed
the
3dlut_interpolation
branch
from
05f467e to
21cae44
Compare
| uint32_t va_reserved1 : 28; | ||
| uint32_t va_reserved[VA_PADDING_HIGH - 1]; | ||
| } VAProcFilterParameterBuffer3DLUT; | ||
|
|
There was a problem hiding this comment.
For HDR10， If app needs to enable 3DLut TETRAHEDRAL interpolation, besides VAProcFilterHighDynamicRangeToneMapping filter type, they also need to add VAProcFilter3DLUT filter type because we only add this parameter in VAProcFilterParameterBuffer3DLUT. right?
There was a problem hiding this comment.
App either use VAProcFilterHighDynamicRangeToneMapping with HDR10 metadata, or use VAProcFilterParameterBuffer3DLUT by using their own 3DLUT. Those 2 filters are usually not combined to use.
There was a problem hiding this comment.
App either use VAProcFilterHighDynamicRangeToneMapping with HDR10 metadata, or use VAProcFilterParameterBuffer3DLUT by using their own 3DLUT. Those 2 filters are usually not combined to use.
Thanks for your answer. For VAProcFilterHighDynamicRangeToneMapping with HDR10 METADATA, do we only control 3DLut interpolation method in our internal driver?
NOW, App only could control interpolation mode by VAProcFilterParameterBuffer3DLUT.
2 participants
No description provided.