- Dec 06, 2020
-
-
Tim-Philipp Müller authored
-
- Oct 29, 2020
-
-
The check seems to be to present to verify that the decoded frame matches the format we expect. The actual check for the layout of the frame was being performed against the context instead. The check fails at least for avdec_aptx_hd, where the AVCodecContext has the sample format set to AV_SAMPLE_FMT_NONE. Part-of: <gstreamer/gst-libav!108>
-
- Oct 27, 2020
-
-
Tim-Philipp Müller authored
-
- Oct 26, 2020
-
-
Tim-Philipp Müller authored
-
- Oct 12, 2020
-
-
Since the commit https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/22b25b3ea5c, ffmpeg will not clear draning flag for encoder by avcodec_flush_buffers() API by default. Allowed case is only if encoder has AV_CODEC_CAP_ENCODER_FLUSH capability flag. If it's not supported, we should re-open encoding session, otherwise ffmpeg encoder will keep returning AVERROR_EOF Part-of: <gstreamer/gst-libav!102>
-
This is already done in all other codec elements. Part-of: <gstreamer/gst-libav!101>
-
Same behaviour as for avviddec now. FFmpeg will return AVERROR_EOF when it's completely drained but we should not return that here or otherwise upstream will receive EOS and not forward us more data. Part-of: <gstreamer/gst-libav!101>
-
- Sep 30, 2020
-
-
AVERROR_EOF means that it's fully drained, but it doesn't mean that that end of stream. Part-of: <gstreamer/gst-libav!96>
-
audiodecoder baseclass implementation is expecting that finish_subframe() is followed by finish_frame() in order clear its internal state related to subframe. Part-of: <gstreamer/gst-libav!96>
-
It might be useful for upstream to know that draining/finishing didn't succeed, and why. Part-of: <gstreamer/gst-libav!96>
-
It might be useful for upstream to know that draining/finishing didn't succeed, and why. Part-of: <gstreamer/gst-libav!96>
-
When sucessfully finishing out frames (or finishing configuration), we must make sure we don't override any failing GstFlowReturn that might have been detected previously. Failure to do this would result in not propagating not-linked, flushing, etc... Part-of: <gstreamer/gst-libav!96>
-
This now works with not so recent ffmpeg. Part-of: <gstreamer/gst-libav!95>
-
- Sep 08, 2020
-
-
Tim-Philipp Müller authored
-
- Sep 07, 2020
-
-
Tim-Philipp Müller authored
-
Sebastian Dröge authored
Part-of: <!89>
-
- Aug 20, 2020
-
-
Tim-Philipp Müller authored
-
- Aug 04, 2020
-
-
Jordan Petridіs authored
Part-of: <!86>
-
- Jul 23, 2020
-
-
Jordan Petridіs authored
This reverts commit d1b20eb6. See gst-ci!324 Part-of: <!85>
-
Part-of: <!80>
-
- Jul 08, 2020
-
-
Tim-Philipp Müller authored
Part-of: <gstreamer/gst-libav!84>
-
- Jul 06, 2020
-
-
Vivia Nikolaidou authored
We examined the output buffer, instead of the input buffer, for existence of cc meta. Part-of: <!83>
-
- Jul 03, 2020
-
-
Following discussion in gst-plugins-bad!1396 (comment 556068) While it is technically possible to store multiple closed caption metas in the same buffer, we don't currently do that anywhere and for H264/MPEG2 both parts have to be stored in the same packet, and also the number of CC bytes you can store per frame is rather limited. This restriction might be relaxed later once we figured out how to do it without breaking things. Part-of: <!82>
-
Tim-Philipp Müller authored
-
- Jul 02, 2020
-
-
Tim-Philipp Müller authored
-
- Jun 30, 2020
-
- Jun 26, 2020
-
-
Sebastian Dröge authored
Part-of: <!79>
-
- Jun 23, 2020
-
-
Mathieu Duponchelle authored
-
- Jun 22, 2020
-
-
Thibault Saunier authored
-
- Jun 20, 2020
-
-
Part-of: <!76>
-
- Jun 19, 2020
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Jun 10, 2020
-
-
Thibault Saunier authored
-
- Jun 08, 2020
-
-
Thibault Saunier authored
-
- Jun 05, 2020
-
-
Mathieu Duponchelle authored
-
- Jun 03, 2020
-
-
Thibault Saunier authored
-
- May 31, 2020
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- May 27, 2020
-
-
Mathieu Duponchelle authored
The discovered frame rate is only available on the AVStream itself. Updating the temporary context framerate before building caps from it seems like a pretty non-intrusive approach. Fixes #75 Part-of: <!74>
-