FFmpeg

Commit Graph

Author	SHA1	Message	Date
Anton Khirnov	3f63685c35	fftools/ffmpeg: supply hw_device_ctx to filters before initializing them This is more correct, but was not possible before the recently-added filtergraph parsing API. Also, only pass hw devices to filters that are flagged as capable of using them. Tested-by: Niklas Haas	2 years ago
Anton Khirnov	d0f767f81f	fftools/ffmpeg: drop OutputStream.enc It is either equal to OutputStream.enc_ctx->codec, or NULL when enc_ctx is NULL. Replace the use of enc with enc_ctx->codec, or the equivalent enc_ctx->codec_* fields where more convenient.	2 years ago
Anton Khirnov	04b340e6b8	fftools/ffmpeg_hw: stop logging to the decoder context Only the decoder itself should do that. Use NULL as is done by all other logging code in ffmpeg.	2 years ago
Haihao Xiang	6803d8b440	ffmpeg_hw: make hardware selection for filters more user friendly When a device is derived from a source device, there are at least 2 devices, and usually the derived device is the expected device, so let's pick the last device if user doesn't specify the filter device with filter_hw_device option After applying this patch, the command below can work: $> ffmpeg -init_hw_device vaapi=va:/dev/dri/renderD128 -init_hw_device qsv=hw@va -f lavfi -i yuvtestsrc -vf format=nv12,hwupload=extra_hw_frames=64 -c:v h264_qsv -y out.h264 Reviewed-by: Soft Works <softworkz@hotmail.com> Signed-off-by: James Almer <jamrial@gmail.com>	3 years ago
Haihao Xiang	51a80aacce	ffmpeg_hw: Don't ignore key parameters when initializing a hw device Currently user may use '-init_hw_device type=name' to initialize a hw device, however the key parameter is ignored when use '-init_hw_device type=name,key=value'. After applying this patch, user may set key parameter if needed. Reviewed-by: Soft Works <softworkz@hotmail.com> Signed-off-by: James Almer <jamrial@gmail.com>	3 years ago
Haihao Xiang	ecee3b07cd	qsvdec: add support for HW_DEVICE_CTX method This allows user set hw_device_ctx instead of hw_frames_ctx for QSV decoders, hence we may remove the ad-hoc libmfx setup code from FFmpeg. "-hwaccel_output_format format" is applied to QSV decoders after removing the ad-hoc libmfx code. In order to keep compatibility with old commandlines, the default format is set to AV_PIX_FMT_QSV, but this behavior will be removed in the future. Please set "-hwaccel_output_format qsv" explicitly if AV_PIX_FMT_QSV is expected. The normal device stuff works for QSV decoders now, user may use "-init_hw_device args" to initialise device and "-hwaccel_device devicename" to select a device for QSV decoders. "-qsv_device device" which was added for workarounding device selection in the ad-hoc libmfx code still works For example: $> ffmpeg -init_hw_device qsv=qsv:hw_any,child_device=/dev/dri/card0 -hwaccel qsv -c:v h264_qsv -i input.h264 -f null - /dev/dri/renderD128 is actually open for h264_qsv decoder in the above command without this patch. After applying this patch, /dev/dri/card0 is used. $> ffmpeg -init_hw_device vaapi=va:/dev/dri/card0 -init_hw_device qsv=hw@va -hwaccel_device hw -hwaccel qsv -c:v h264_qsv -i input.h264 -f null - device hw of type qsv is not usable in the above command without this patch. After applying this patch, this command works as expected. Reviewed-by: Soft Works <softworkz@hotmail.com> Signed-off-by: James Almer <jamrial@gmail.com>	3 years ago
Mark Thompson	706ed34ce7	ffmpeg: Don't require a known device to pass a frames context to an encoder The previous code here did not handle passing a frames context when ffmpeg itself did not know about the device it came from (for example, because it was created by device derivation inside a filter graph), which would break encoders requiring that input. Fix that by checking for HW frames and device context methods independently, and prefer to use a frames context method if possible. At the same time, revert the encoding additions to the device matching function because the additional complexity was not relevant to decoding. Also fixes #8637, which is the same case but with the device creation hidden in the ad-hoc libmfx setup code.	5 years ago
Mark Thompson	8abd3b2028	ffmpeg: Use hardware config metadata with encoders This can support encoders which want frames and/or device contexts. For the device case, it currently picks the first initialised device of the desired type to give to the encoder - a new option would be needed if it were necessary to choose between multiple devices of the same type.	5 years ago
Mark Thompson	e254212405	ffmpeg: Make filter hardware device selection clearer Also move it into a dedicated function in the hardware file.	5 years ago
Mark Thompson	a444863738	ffmpeg_hw: Treat empty device string as no device setting The implementation will use some default in this case. The empty string is not a meaningful device for any existing hardware type, and indeed OpenCL treats it identically to no device already to work around the lack of this setting on the command line.	6 years ago
Mark Thompson	1f8b36329f	ffmpeg_hw: Mark some strings as const	6 years ago
Mark Thompson	b0cd14fb1d	ffmpeg: Use codec hardware config to configure hwaccels Removes specific support for all hwaccels supported by the generic code (DXVA2, D3D11VA, NVDEC, VAAPI and VDPAU).	7 years ago

13 Commits (fd980b261536fbd30f2c8df42779ecb09bf1b240)