aboutsummaryrefslogtreecommitdiffstats
path: root/libavfilter/vf_chromaber_vulkan.c
diff options
context:
space:
mode:
authorLynne <dev@lynne.ee>2023-05-29 03:50:25 +0200
committerLynne <dev@lynne.ee>2023-05-29 05:12:27 +0200
commite71cd1804920b846757adcd45da22b3958f58f83 (patch)
tree196d0b7349ebf0074925bbacf398316288f6daa4 /libavfilter/vf_chromaber_vulkan.c
parent246bec23a9225ffe9e6ad247ba26073a201a1be8 (diff)
downloadffmpeg-e71cd1804920b846757adcd45da22b3958f58f83.tar.gz
vulkan_decode: do not align the image dimensions
According to Dave Airlie: > <airlied> but I think ignoring it should be fine, I can't see any > other way to get the imaeg extents correct for other usage > <Lynne> what width/height should be used for the images? > the final presentable dimensions, or the coded dimensions? > <airlied> if you don't want noise I think the presentable dims > <airlied> the driver should round up the allocations internally, > but if you are going to sample from the images then w/h have to be > the bounds of the image you want > <airlied> since otherwise there's no way to stop the sampler from > going outside the edges Apparently, the alignment values are informative, rather than mandatory, but the spec's wording makes it sound as if they're mandatory.
Diffstat (limited to 'libavfilter/vf_chromaber_vulkan.c')
0 files changed, 0 insertions, 0 deletions