Skip to content
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

video encode: Fix tests for implementations with detection of insufficient bitstream buffer range #487

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

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
All committers have signed the CLA.

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