aboutsummaryrefslogtreecommitdiffstats
path: root/doc/APIchanges
diff options
context:
space:
mode:
authorLynne <dev@lynne.ee>2024-12-24 13:29:42 +0900
committerLynne <dev@lynne.ee>2025-01-03 14:53:41 +0900
commit551041e384387d036bb9d92e619b2106c36394da (patch)
tree8f870fc5425199c7c8537d4136618faa550fedc6 /doc/APIchanges
parente7b474783c1f6ca11a040e9822358c618070a06b (diff)
downloadffmpeg-551041e384387d036bb9d92e619b2106c36394da.tar.gz
vulkan_decode: remove informative queries
We queried the decoder whether it was able to decode sucessfully, but since we operated asynchronously, we weren't able to do anything with this information but let the user know decoding failed for the previous frame(s). Since we parse the slice headers ourselves and we're reasonably sure we can decode before actually starting to decode, this was rarely triggered on corrupt data, and hardware's understanding of whether there was an error or not is vague. There's also a semantic problem with our use of the queries - if there's a seek, we flush, but what happens to the queries is vague according to the spec. Most hardware dealt fine, since queries are nothing more than GPU memory with integers stored. But with Intel, they seem to be more of a register to which a driver must keep track of, leading to issues if there's been a reset (seek) and we query the previous submission before the seek. Just get rid of them. The query code is still used in encoding. This fixes seeking with HEVC and AV1 on Intel.
Diffstat (limited to 'doc/APIchanges')
0 files changed, 0 insertions, 0 deletions