Skip to content

Conversation

clemy
Copy link

@clemy clemy commented Sep 12, 2024

This change allows implementation to report VK_VIDEO_ENCODE_CAPABILITY_INSUFFICIENT_BITSTREAM_BUFFER_RANGE_DETECTION_BIT_KHR without causing a failed test dEQP-VK.video.capabilities.*_encode_capabilities_query.

Further this change sets dstBufferRange in VkVideoEncodeInfoKHR to valid values (instead of 0) so that implementations supporting insufficient bitstream buffer range detection do not report an error on video encode.

Tests dEQP-VK.video.capabilities.*_encode_capabilities_query failed
if the implementation supports
VK_VIDEO_ENCODE_CAPABILITY_INSUFFICIENT_BITSTREAM_BUFFER_RANGE_DETECTION_BIT_KHR.
This adds this as a valid flag.

Affects:
dEQP-VK.video.capabilities.h264_encode_capabilities_query
dEQP-VK.video.capabilities.h265_encode_capabilities_query
According spec:
"dstBufferRange is the maximum bitstream size in bytes that
can be written to dstBuffer, starting from dstBufferOffset."
This member was set to 0 and so no bitstream could be written.

Affects:
dEQP-VK.video.encode.*
@CLAassistant
Copy link

CLAassistant commented Sep 12, 2024

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants