diff options
author | Philip Langdale <philipl@overt.org> | 2022-03-25 11:16:21 -0700 |
---|---|---|
committer | Philip Langdale <github.philipl@overt.org> | 2022-09-21 09:39:34 -0700 |
commit | 7b84e6fa8988f31e297cbc3adcd8a81e18e63bc8 (patch) | |
tree | 82ce8166502b8b9d886c013315d3cd8a0f418b39 /filters/f_lavfi.c | |
parent | 989d873d6ec57171a55f432d6f87a9e5a61a706c (diff) | |
download | mpv-7b84e6fa8988f31e297cbc3adcd8a81e18e63bc8.tar.bz2 mpv-7b84e6fa8988f31e297cbc3adcd8a81e18e63bc8.tar.xz |
f_autoconvert: f_hwtransfer: support HW -> HW uploads
Historically, HW -> HW uploads did not exist, so the current code
assumes they will never happen. But as part of introducing Vulkan
support into ffmpeg, we added HW -> HW support to enable transfers
between Vulkan and CUDA.
Today, that means you can use the lavfi hwupload filter with the
correct configuration (and previous changes in this series) but it
would be more convenient to enable HW -> HW in the format filter so
that the transfers can be done more intuitively:
```
--vf=format=fmt=cuda
```
and
```
--vf=format=fmt=vulkan
```
Most of the work here is skipping logic that is specific to SW -> HW
uploads doing format conversion. There is no ability to do inline
conversion when moving between HW formats, so the format must be
mutually understood to begin with.
Additional work needs to be done to enable transfers between VAAPI
and Vulkan which uses mapping, rather than uploads. I'll tackle that
in the next change.
Diffstat (limited to 'filters/f_lavfi.c')
0 files changed, 0 insertions, 0 deletions