- Feb 19, 2016
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Feb 18, 2016
-
-
Julien Isorce authored
Currently the .la path is provided which requires to use libtool as mentioned in the GStreamer manual section-helloworld-compilerun.html. It is fine as long as the application is built using libtool. So currently it is not possible to compile a GStreamer application within gst-uninstalled with CMake or other build system different than autotools. This patch allows to do the following in gst-uninstalled env: gcc test.c -o test $(pkg-config --cflags --libs gstreamer-1.0) Previously it required to prepend libtool --mode=link https://bugzilla.gnome.org/show_bug.cgi?id=720778
-
Sebastian Dröge authored
Revert "pad: PULL probes are called without a buffer so don't require any of the data flags to be set" This reverts commit b89fa478. The changes break various tests.
-
Sebastian Dröge authored
This reverts commit 17d30e94. The PULL probe changes break various tests.
-
-
-
- Feb 17, 2016
-
-
Sebastian Dröge authored
This reverts commit b4279971. It breaks things that used to work before, even if the change by itself is correct and the previous code is just working around deeper bugs in the async state change code. Let's go back to what previously worked and then fix async state changes in general. https://bugzilla.gnome.org/show_bug.cgi?id=760532
-
Edward Hervey authored
That commit would break scheduling reconfiguration with ghostpads This reverts commit ab55ad7e.
-
Showcases the regression introduced by this commit: Commit: ab55ad7e Author: Stian Selnes <stian@pexip.com> Date: Wed Jan 27 13:20:23 2016 +0100 ghostpad: Do nothing in _internal_activate_push_default
-
When calling gst_pad_activate_mode() on a ghostpad gst_ghost_pad_activate_push_default() will be called. This will call gst_pad_activate_mode() on the proxypad (which is internal of the ghostpad), calling gst_ghost_pad_internal_activate_push_default(), which again will call gst_pad_activate_mode() on the original ghostpad. By simply returning TRUE in gst_ghost_pad_internal_activate_push_default() the redundant call to gst_pad_activate_mode() (for the same pad) is avoided. https://bugzilla.gnome.org/show_bug.cgi?id=761913
-
- Feb 16, 2016
-
-
Thiago Santos authored
macro was added in 2011 and isn't used anymore
-
Sebastian Dröge authored
This reverts commit 8ae8b272. It's not used anymore by anything and was considered a bad idea in general.
-
- Feb 15, 2016
-
-
Thiago Santos authored
tracerserialize.c:117:1: error: control reaches end of non-void function [-Werror=return-type]
-
Thiago Santos authored
C90 compilers complain about it error: ‘for’ loop initial declarations are only allowed in C99 or C11 mode Also run gst-indent on systemclock tests.
-
The integration is already so tight, there is no reason to not further formalize it! https://bugzilla.gnome.org/show_bug.cgi?id=761914
- Feb 13, 2016
-
-
Tim-Philipp Müller authored
Was supposed to be squashed with 336c7bb6 https://bugzilla.gnome.org/show_bug.cgi?id=761910
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
And remove egl which no longer exists.
-
- Feb 12, 2016
-
-
Similar to the stress test functions for buffers that has a callback to create the buffer to be pushed, it's useful to have functions that use a callback to create the event to be pushed. API: gst_harness_stress_push_event_with_cb_start() API: gst_harness_stress_push_event_with_cb_start_full() API: gst_harness_stress_send_upstream_event_with_cb_start() API: gst_harness_stress_push_upstream_event_with_cb_start_full() https://bugzilla.gnome.org/show_bug.cgi?id=761932
-
And use it inside GstHarness API: gst_test_clock_crank() https://bugzilla.gnome.org/show_bug.cgi?id=761906
-
Also make the testclock a member of the harness, allowing some more interactions with the clock prior to adding elements. https://bugzilla.gnome.org/show_bug.cgi?id=761905
-
Depending on when gst_harness_pull was called - before the buffer reached gst_harness_chain or after we can get different behaviors of the test with enabled blocking push mode. The fix makes the behavior always the same. In pull function we get the buffer first, thus making sure gst_harness_chain waits for the signal, and emitting the signal after. https://bugzilla.gnome.org/show_bug.cgi?id=761931
-
notify is not called per buffer, but when the thread is freed. Comment about serialized events and OOB does not make sense for upstream events. https://bugzilla.gnome.org/show_bug.cgi?id=761909
-
Set the sink_forward_pad to NULL before tearing down sink_harness to avoid that the harness tries to forward events/queries to it while it's tearing down. https://bugzilla.gnome.org/show_bug.cgi?id=761904
- Feb 11, 2016
-
-
When allocating a new buffer in the pool, both the do_alloc_buffer() and the vmethod, alloc_buffer(), receive the parameter GstBufferPoolAcquireParams. Nonetheless, when default_acquire_buffer() calls the do_alloc_buffer() it does not pass the received GstBufferPoolAcquireParams, so when the user pass those parameters they are ignored by alloc_buffer() vmethod. This one-liner patch pass the received acquire params to do_alloc_buffer(). https://bugzilla.gnome.org/show_bug.cgi?id=761824
-
- Feb 10, 2016
-
-
Stian Selnes authored
Fixes a race where an entry is set to BUSY in gst_system_clock_id_wait_jitter() and is UNSCHEDULED before gst_system_clock_id_wait_jitter_unlocked() starts processing it. The wakeup added by gst_system_clock_id_unschedule() must be cleaned up. Two stress tests are added. One test that triggers the specific issue described above. The second stresses the code path where a wait is rescheduled because the poll returned early. https://bugzilla.gnome.org/show_bug.cgi?id=761586
-
Thiago Santos authored
If the clockentry is too late and is unscheduled before it gets a change to detect its lateness the wakeup count and the poll are used but never properly cleaned up. This leaves it in a dirty state that is going to mess with the next clock entry waiting requests. https://bugzilla.gnome.org/show_bug.cgi?id=761586
-
- Feb 05, 2016
-
-
Thiago Santos authored
To get the CK_DEFAULT_TIMEOUT defined for all tests https://bugzilla.gnome.org/show_bug.cgi?id=761472
-
Thiago Santos authored
From 86e4663 to b64f03f
-
- Feb 04, 2016
-
-
Tim-Philipp Müller authored
We have no guarantees about what flags are set on buffers we take out of the GstAdapter. If we push out multiple buffers from the first input buffer (which will have discont set), only the first buffer we push out should be flagged as discont, not all of the buffers produced from that first initial input buffer. Fixes issue where the first few mp3 frames/seconds of data in push mode were skipped or garbled in some cases, and the discont flags would also trip up decoders which were getting drained/flushed for every buffer. This was a regression introduced in 1.6 apparently.
-
- Feb 02, 2016
-
-
Thibault Saunier authored
In case the property was not interpollable we might never initialize the GValue, we should thus never unset it.
-