FFmpeg

Commit Graph

Author	SHA1	Message	Date
Timo Rothenpieler	f85e0673c3	fftools: add DPI awareness manifest Some filters, like gdigrab, rely on this to be set to see and report proper dimensions.	2 years ago
Anton Khirnov	7b6622705e	fftools/ffmpeg: move the input thread into its own file It will contain more demuxing-specific code in the future.	2 years ago
Anton Khirnov	37c764df67	fftools: add a multistream thread-safe queue It is similar to AVThreadMessageQueue, but supports multiple streams, each with its own EOF state.	2 years ago
Anton Khirnov	4740fea7dd	fftools/ffmpeg: rework -shortest implementation The -shortest option (which finishes the output file at the time the shortest stream ends) is currently implemented by faking the -t option when an output stream ends. This approach is fragile, since it depends on the frames/packets being processed in a specific order. E.g. there are currently some situations in which the output file length will depend unpredictably on unrelated factors like encoder delay. More importantly, the present work aiming at splitting various ffmpeg components into different threads will make this approach completely unworkable, since the frames/packets will arrive in effectively random order. This commit introduces a "sync queue", which is essentially a collection of FIFOs, one per stream. Frames/packets are submitted to these FIFOs and are then released for further processing (encoding or muxing) when it is ensured that the frame in question will not cause its stream to get ahead of the other streams (the logic is similar to libavformat's interleaving queue). These sync queues are then used for encoding and/or muxing when the -shortest option is specified. A new option – -shortest_buf_duration – controls the maximum number of queued packets, to avoid runaway memory usage. This commit changes the results of the following tests: - copy-shortest[12]: the last audio frame is now gone. This is correct, since it actually outlasts the last video frame. - shortest-sub: the video packets following the last subtitle packet are now gone. This is also correct.	2 years ago
Anton Khirnov	288aa37387	fftools/ffmpeg: move some muxing-related code into a separate file This is a first step towards making muxers more independent from the rest of the code.	3 years ago
Anton Khirnov	a545cb2b9d	fftools/cmdutils: split common option handlers into their own file	3 years ago
rcombs	4b54818981	ffmpeg: remove ffmpeg_videotoolbox This was almost completely redundant. The only functionality that's no longer available after this removal is the videotoolbox_pixfmt arg, which has been obsolete for several years.	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
James Almer	60b1f85b67	ffmpeg: remove superfluous custom cuvid hwaccel It's a duplicate of the properly implemented nvdec libavcodec hwaccel Reviewed-by: Timo Rothenpieler <timo@rothenpieler.org> Signed-off-by: James Almer <jamrial@gmail.com>	5 years ago
Rostislav Pehlivanov	6b35a83214	Remove the ffserver program Signed-off-by: Rostislav Pehlivanov <atomnuker@gmail.com>	7 years ago
Mark Thompson	3650cb2dfa	lavu,lavfi,ffmpeg: Remove experimental OpenCL API This was added in early 2013 and abandoned several months later; as far as I can tell, there are no external users. Future OpenCL use will be via hwcontext, which requires neither special OpenCL-only API nor global state in libavutil. All internal users are also deleted - this is just the unsharp filter (replaced by unsharp_opencl, which is more flexible) and the deshake filter (no replacement).	7 years ago
James Almer	3e6829a8aa	build: fix compilation of tools with OpenCL enabled Signed-off-by: James Almer <jamrial@gmail.com>	7 years ago

14 Commits (c8c4a162fc18c0fd99bada66d9ea3b48c64b2450)