- Feb 08, 2014
-
-
Sebastian Dröge authored
-
- Feb 04, 2014
-
-
libavformat only supports muxing 16bit, 48kHz stereo into DV containers. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=722672
-
Sebastian Dröge authored
- Jan 15, 2014
-
-
A AVCodecContext needs cleaning up before being freed. Go through all of the allocations/setups to ensure none of them can leak a context or its contents.
-
- Jan 11, 2014
-
-
Tim-Philipp Müller authored
This reverts commit fcf09aff. This broke the build. In theory the problem might occur with libav 9 too, but it seems in practice it doesn't, unless you link against ffmpeg 2.x, but then you're on your own anyway. https://bugzilla.gnome.org/show_bug.cgi?id=721077
-
New libav will not call the release_buffer callback anymore when avcodec_default_get_buffer() is called from get_buffer. Releasing of the memory in a picture should now be done by registering a callback to the avbuffer objects in the picture. There is some compatibility code to wrap the memory we provide in get_buffer in avbuffer with a callback to release_buffer but that is not done when avcodec_default_get_buffer() is called. Work around this by adding a dummy avbuffer object to the picture that will release the frame. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=721077
-
- Jan 06, 2014
-
-
The VC-1 decoder should handle that. Before avdec_wmv3 handled it, but then we added format=WMV3 to its sink pad template caps, at which point nothing handled WMVA any longer. https://bugzilla.gnome.org/show_bug.cgi?id=697665
-
- Dec 27, 2013
-
-
Sebastian Dröge authored
Nowadays libav has proper releases and API/ABI guarantees. We're not living in last decade.
-
- Dec 26, 2013
-
-
Sebastian Dröge authored
-
- Dec 17, 2013
-
-
... so as to focus on providing *a* buffer rather than one (too) tied to a frame, in particular allowing multiple allocations related to a frame. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=697806
-
- Dec 13, 2013
-
-
... to avoid these piling up in list of pending frames. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=693772
-
... by also removing it from the pending list of frames, where it may still be in if it has never been submitted to _finish. This could happen if is a decode-only frame, or in skipped decoding situation, ... Fixes https://bugzilla.gnome.org/show_bug.cgi?id=693772
-
-
- Dec 04, 2013
- Nov 11, 2013
-
-
-
Add a new property to GstFFMpegVidEnc and GstFFMpegAudEnc to supply the "strict compliance" value to AVCodecContext https://bugzilla.gnome.org/show_bug.cgi?id=691617
- Nov 09, 2013
-
-
Sebastian Dröge authored
-
-
- Oct 15, 2013
-
-
Sebastian Dröge authored
-
- Oct 04, 2013
-
-
Sebastian Dröge authored
Check for uniqueness differently now.
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
It can happen that negotiation fails during get_buffer(), but then we don't retry later and never return NOT_NEGOTIATED upstream... and instead run into assertions.
-
Sebastian Dröge authored
It can happen that negotiation fails during get_buffer(), but then we don't retry later and never return NOT_NEGOTIATED upstream... and instead run into assertions. https://bugzilla.gnome.org/show_bug.cgi?id=708769
-
Sebastian Dröge authored
Some encoders require a non-zero framerate to be configured properly and just choosing something will make them not fail completely at least. https://bugzilla.gnome.org/show_bug.cgi?id=708732
-
Actually avdec_mjpeg does not deal well with incomplete buffers and try to decode incomplete frames. A parser which will also acts as an accumulator needs to be inserted before it. https://bugzilla.gnome.org/show_bug.cgi?id=709352
-
- Sep 30, 2013
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Sep 24, 2013
-
-
Tim-Philipp Müller authored
From 6b03ba7 to 7412249
-
Sebastian Dröge authored
-
- Sep 20, 2013
-
-
Edward Hervey authored
From b613661 to 6b03ba7
-
- Sep 19, 2013
-
-
Tim-Philipp Müller authored
From 74a6857 to b613661
-
Tim-Philipp Müller authored
From 12af105 to 74a6857
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Sep 12, 2013
-
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
During get_buffer() it can happen that the main context is not updated yet and only the context passed here has the correct width, height, etc.
-