diff options
author | Lynne <dev@lynne.ee> | 2024-08-30 22:02:39 +0000 |
---|---|---|
committer | Lynne <dev@lynne.ee> | 2024-09-09 07:05:42 +0200 |
commit | 3de73f1262732a70f10e3d60a4f0951fd322fcfa (patch) | |
tree | 179255c06980df8dc7a0d156a0ee6c1eabe84368 /tests/ref/fate/h264-conformance-mr1_mw_a | |
parent | e6019ed075d6d2557dc834a09c92102055837d73 (diff) | |
download | ffmpeg-3de73f1262732a70f10e3d60a4f0951fd322fcfa.tar.gz |
hw_base_encode: make recon_frames_ref optional
Vulkan supports some stupidly odd hardware, that unfortunately,
most modern GPUs happen to be.
The DPB images for encoders may be required to be preallocated
all at once, and rather than be individual frames, be layers of
a single frame.
As the hw_base_encode code is written with the thought that either
the driver or the device itself supports sane image allocation,
Vulkan does not leave us with this option.
So, in the case that the hardware does not support individual
frames to be used as DPBs, make the DBP frames context optional,
and let the subsystem manage this.
Diffstat (limited to 'tests/ref/fate/h264-conformance-mr1_mw_a')
0 files changed, 0 insertions, 0 deletions