- Jun 07, 2015
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Jun 02, 2015
-
-
Makes source code smaller, and ensures we go through common initialization path (like the one that sets up XML unit test output ...)
-
- May 26, 2015
-
-
Tim-Philipp Müller authored
In auto mode it will happily chose much higher values anyway, and a limit of 4 seems a bit low these days.
-
- May 12, 2015
-
-
Jan Schmidt authored
Make the initial chapter seek work across reuse. https://bugzilla.gnome.org/show_bug.cgi?id=453322
-
Jan Schmidt authored
Ignore the initial seek basesrc sends, as it breaks starting from another chapter by immediately seeking back to the start of the title
-
- May 10, 2015
-
-
Tim-Philipp Müller authored
Mostly gst-launch -> gst-launch-1.0, but also use autoaudiosink/autovideosink in more places and update pipelines a little or flesh out descriptions.
-
- Apr 27, 2015
-
-
Luis de Bethencourt authored
Property enum items should be nameed PROP_ for consistency and readability.
-
- Apr 26, 2015
-
-
Tim-Philipp Müller authored
This is not needed any longer.
-
- Apr 24, 2015
-
-
Luis de Bethencourt authored
-
- Apr 23, 2015
-
-
Tim-Philipp Müller authored
Make sure the test environment is set up. https://bugzilla.gnome.org//show_bug.cgi?id=747624
-
Tim-Philipp Müller authored
This is only required for builds from git, people can still build tarballs if they only have older autotools. https://bugzilla.gnome.org//show_bug.cgi?id=747624
-
Tim-Philipp Müller authored
-
- Apr 22, 2015
-
-
Sebastian Dröge authored
It's completely outdated and just confusing, better if people are forced to look at the actual code in question than trusting this file.
-
Sebastian Dröge authored
autotools automatically generate this, and when using different versions for autogen.sh there will always be changes to a file tracked by git.
-
- Apr 20, 2015
-
-
A seek in push mode failed for big offsets which are beyond the range of guint32. https://bugzilla.gnome.org/show_bug.cgi?id=748162
-
- Apr 08, 2015
-
-
Needed by the new automake test runner
-
- Apr 03, 2015
-
-
Tim-Philipp Müller authored
From bc76a8b to c8fb372
-
Vincent Penquerc'h authored
a52_init initializes the IMDCT global state as well as creating a new state. When two A52 decoders are created (eg, when two AC3 tracks are contained in a video), calls to a52_init may happen at the same time, and the IMDCT initialization is not reentrant. https://bugzilla.gnome.org/show_bug.cgi?id=746781
-
- Mar 30, 2015
-
-
gst_buffer_pool_acquire_buffer() gives us a new owned buffer while gst_buffer_replace() reffed it as well so we were one reference extra. https://bugzilla.gnome.org/show_bug.cgi?id=746887
-
- Mar 28, 2015
-
-
- Mar 24, 2015
-
-
Luis de Bethencourt authored
CID #1291630
-
Luis de Bethencourt authored
Buffer needs to be null before passing it to gst_buffer_pool_acquire_buffer() CID #1291634
-
- Mar 13, 2015
-
-
Nicolas Dufresne authored
This allow using external pools that have different strides from the default. These strides need to respect certain rules, which we check and if these are not met, we fallback to generic pool. https://bugzilla.gnome.org/show_bug.cgi?id=735379
-
Nicolas Dufresne authored
This is a rewrite of the pool negotiation and configuration. Direct to output decoding is now achieved by configuring the pool using video-alignment. This removes copies when dealing with any elements that supports VideoAlignment, and enable usage of generic video buffer pool, XVImagePool and GLPool. It drops the crop meta implementation for now. https://bugzilla.gnome.org/show_bug.cgi?id=735379
-
- Mar 10, 2015
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Mar 09, 2015
-
-
Nicolas Dufresne authored
This reverts commit f3e8dcb9.
-
Nicolas Dufresne authored
This reverts commit 63b43d3b.
-
Nicolas Dufresne authored
-
- Feb 15, 2015
-
-
A pipeline like: gst-launch-1.0 filesrc location=file.ts ! tsdemux ! mpegvideoparse ! mpeg2dec ! vaapisink would look bad when file.ts contains 704x576 video, because vaapisink would give you buffers of stride 768, but libmpeg2 was not told about this and used a stride of 704. Tell libmpeg2 about the stride from downstream; in the process, teach it to reject buffer pools that don't meet libmpeg2's chroma stride requirements Signed-off-by: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
-
- Feb 11, 2015
-
-
Sebastian Dröge authored
This now follows the design docs everywhere, especially the maximum latency handling. https://bugzilla.gnome.org/show_bug.cgi?id=744106
-
- Feb 06, 2015
-
-
Sebastian Dröge authored
The meaning of the max latency is *not* the maximum latency this element will introduce. It is the maximum latency this element can endure without overflowing any buffers, which is infinite for x264enc. Fixes latency configuration in zero latency mode, where max latency was becoming 0... which usually won't work well if something else introduces latency as then max < min in the end, and latency configuration just fails.
-
- Feb 02, 2015
-
-
Vincent Penquerc'h authored
This matches what is done when downstream caps are not ANY, and fixes prerolling in byte stream mode when typefind is downstream.
-
- Jan 21, 2015
-
-
Sebastian Dröge authored
-
- Jan 18, 2015
-
-
Tim-Philipp Müller authored
It's not needed any longer, all plugins in -ugly have been ported.
-
Nicolas Dufresne authored
There is no reason x264enc should enforce a maximum allocation size. The maximum is normally set by buffer pool which cannot grow, but we don't offer a buffer pool. This would lead to stall when used with element that don't implement allocation query. Related to: https://bugzilla.gnome.org/show_bug.cgi?id=738302
-
- Jan 12, 2015
-
-
Stefan Sauer authored
From f2c6b95 to bc76a8b
-