diff options
author | Philip Langdale <philipl@overt.org> | 2019-10-23 18:11:37 -0700 |
---|---|---|
committer | Lynne <dev@lynne.ee> | 2020-02-04 23:19:48 +0000 |
commit | 88d2ccbe9384a1cba44a2909ef896aac50636d11 (patch) | |
tree | 8f137a7dde99b0f88cc79333b261a41d48b2ceb3 /doc | |
parent | a88449ffb2f249e31ecf98f84e7f8c338308e7e4 (diff) | |
download | ffmpeg-88d2ccbe9384a1cba44a2909ef896aac50636d11.tar.gz |
lavfi/vf_hwupload: Add support for HW -> HW transfers
As we find ourselves wanting a way to transfer frames between
HW devices (or more realistically, between APIs on the same device),
it's desirable to have a way to describe the relationship. While
we could imagine introducing a `hwtransfer` filter, there is
almost no difference from `hwupload`. The main new feature we need
is a way to specify the target device. Having a single device
for the filter chain is obviously insufficient if we're dealing
with two devices.
So let's add a way to specify the upload target device, and if none
is specified, continue with the existing behaviour.
We must also correctly preserve the sw_format on such a transfer.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/filters.texi | 13 |
1 files changed, 12 insertions, 1 deletions
diff --git a/doc/filters.texi b/doc/filters.texi index 9b5f4543b8..96dccc45be 100644 --- a/doc/filters.texi +++ b/doc/filters.texi @@ -11981,7 +11981,18 @@ Upload system memory frames to hardware surfaces. The device to upload to must be supplied when the filter is initialised. If using ffmpeg, select the appropriate device with the @option{-filter_hw_device} -option. +option or with the @option{derive_device} option. The input and output devices +must be of different types and compatible - the exact meaning of this is +system-dependent, but typically it means that they must refer to the same +underlying hardware context (for example, refer to the same graphics card). + +The following additional parameters are accepted: + +@table @option +@item derive_device @var{type} +Rather than using the device supplied at initialisation, instead derive a new +device of type @var{type} from the device the input frames exist on. +@end table @anchor{hwupload_cuda} @section hwupload_cuda |