-
Notifications
You must be signed in to change notification settings - Fork 302
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
va: Add VAConfigAttribEncMaxTileRows and VAConfigAttribEncMaxTileCols #757
Conversation
2a51e1d
to
adf810f
Compare
adf810f
to
4c925b1
Compare
…leCols Requires: intel/libva#757 Signed-off-by: Sil Vilerino <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
4c925b1
to
a5b62cc
Compare
Currently there is no way of exposing the driver tile_rows and tile_cols limitations for encoding with tiles. For codecs like AV1 there is a cap specifying the max number of tiles, but without differentiating cols/rows. Different hardware may have restrictions which may need to be taken into account. More specifically, D3D12 encode exposes the maximum rows/cols and adding VAConfigAttribEncMaxTileRows/Cols allows for mapping that information to the VAOn12 driver. Signed-off-by: Sil Vilerino <[email protected]>
a5b62cc
to
e5758c4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one value is enough? 16 bit for each?
@XinfengZhang thanks for taking a look. We've discussed this previously with @dvrogozh . It may be easier for the user to have separate values instead of having to deal with bit manipulation, there are other caps like Do you think keeping the separate values would be okay for |
These attributes are not directly involved in bitstream packing. In such cases I think it's better to favor usability over compactness. |
@XinfengZhang kindly pinging on this MR :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, VA_ATTRIB_NOT_SUPPORTED represent " no limitation" "comply with codec spec" right?
…leCols Requires: intel/libva#757 Signed-off-by: Sil Vilerino <[email protected]>
…leCols Requires: intel/libva#757 Signed-off-by: Sil Vilerino <[email protected]>
Currently there is no way of exposing the driver tile_rows and tile_cols limitations for encoding with tiles. For codecs like AV1 there is a cap specifying the max number of tiles, but without differentiating cols/rows.
Different hardware may have restrictions which may need to be taken into account. More specifically, D3D12 encode exposes the maximum rows/cols and adding VAConfigAttribEncMaxTileRows/Cols allows for mapping that information to the VAOn12 driver.
Related vainfo change: intel/libva-utils#344
@dvrogozh @XinfengZhang