- Sep 30, 2016
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Sep 27, 2016
-
-
Tim-Philipp Müller authored
Not setting cdata here on purpose because of .. complications.
-
- Sep 26, 2016
-
-
Thibault Saunier authored
-
Thibault Saunier authored
-
Tim-Philipp Müller authored
Code was also checking the wrong define anyway.
-
Tim-Philipp Müller authored
Also, the valgrind bits weren't hooked up properly anyway, checking the wrong define.
-
- Sep 24, 2016
-
-
Tim-Philipp Müller authored
Need to include stddef.h for it, so this would've worked: if cc.has_type('ptrdiff_t', prefix: '#include <stddef.h>')
-
Tim-Philipp Müller authored
gst/gstprintf unit test would fail on 32-bit x86 with: gstprintf.c:83:printf_I32_I64:0: 'str' (64-bit x value = b5a6978f) is not equal to '"64-bit x value = f1e2d3c4b5a6978f"'
-
- Sep 22, 2016
-
-
Nirbheek Chauhan authored
This reverts commit cfc565e2. The commit was redundant since gst_gen_sources already contains gstenum_h. We're still investigating why some people are still seeing a racy build failure.
-
Nirbheek Chauhan authored
This forces gstenumtypes.h to be built whenever something uses gst_dep as a subproject dependency. This is needed since gst/gst.h includes gstenumtypes.h Closes https://github.com/mesonbuild/meson/issues/714 which is not actually a Meson bug.
-
- Sep 19, 2016
-
-
Sebastian Dröge authored
Need to cast away the const as g_queue_foreach() takes a non-const GQueue*
-
Otherwise both iterators share the same references, the second one usually resulting in a crash when being freed. https://bugzilla.gnome.org/show_bug.cgi?id=771649
-
- Sep 17, 2016
-
-
This carries over code for a similar test from multiqueue to ensure full control over the dataflow while testing. (The previous attempt was racy since the fill level changed without any thread sync with the test code.) https://bugzilla.gnome.org/show_bug.cgi?id=771210
-
- Sep 15, 2016
-
-
Arun Raghavan authored
Seems like there was some documentation left over from when this was gst_message_new_duration().
-
Sebastian Dröge authored
basesink: Remove unused fields and always use the buffer timestamp difference for calculating the QoS proportion The buffer timestamps are only hints and more often than not have nothing to do with reality. https://bugzilla.gnome.org/show_bug.cgi?id=771306
-
- Sep 13, 2016
-
-
Nirbheek Chauhan authored
Earlier we were only using __declspec(dllexport/import) when we were built with MSVC because when built with MinGW and linking with MinGW we don't need it (and we get linker errors because of it). However, when we're built with MinGW and someone wants to link to us with MSVC, we still need the prototypes to have __declspec(dllimport) since MSVC cannot do auto-import like GCC can. https://bugzilla.gnome.org/show_bug.cgi?id=771029
-
- Sep 12, 2016
-
-
Sebastian Dröge authored
Otherwise our bin might lose various flags that were explicitly set on it at arbitrary times.
-
- Sep 10, 2016
-
-
Thiago Sousa Santos authored
Some simple tests to make sure it keeps working
-
Suppress-flags is for preventing propagation of child element's specific flag when it is added to the bin. https://bugzilla.gnome.org/show_bug.cgi?id=770627
-
Jan Schmidt authored
From b18d820 to f980fd9
-
Otherwise GST_TYPE_FRACTION will work correctly in tags. https://bugzilla.gnome.org/show_bug.cgi?id=753922
-
Sebastian Dröge authored
When using seek_simple() in combination with other kinds of seeks, this becomes problematic. seek_simple() does not reset the stop position to GST_CLOCK_TIME_NONE but keeps whatever a previous seek did. So for example when doing a seek_simple() after a rate=-1 seek, we would usually get assertions that start>stop (and stop being the old stop from the rate=1 seek). https://bugzilla.gnome.org/show_bug.cgi?id=771104
-
- Sep 09, 2016
-
-
Jan Schmidt authored
From f49c55e to b18d820
-
Thibault Saunier authored
Basically we already have each test with a 20sec timeout, and testsuite can last more than the default 30secs from meson. 3 minutes is another arbitrary timeout but should be good enough.
-
- Sep 08, 2016
-
-
Sebastian Dröge authored
basesink: Use the average durations based on timestamps for the QoS proportion when doing trickmodes The durations of the buffers are (usually) assuming that no frames are being dropped and are just the durations coming from the stream. However if we do trickmodes, frames are being dropped regularly especially if only key units are supposed to be played. Fixes completely bogus QoS proportion values in the above case.
-
- Sep 05, 2016
-
-
Thibault Saunier authored
-
Thibault Saunier authored
And add a way to disable the introspection and bump version to 1.9.2
-
-
Wim Taymans authored
__ppc__ and __ppc64__ are non-standard defines, we should use __powerpc__ and __powerpc64__ instead because newer gcc doesn't know them anymore.
-
- Sep 04, 2016
-
-
Tim-Philipp Müller authored
Print GObject argument properly with pointer marker: "client-added" : void user_function (GstElement* object, GObject* arg0, gpointer user_data); instead of "client-added" : void user_function (GstElement* object, GObject arg0, gpointer user_data); for gst-inspect-1.0 tcpserversink.
-
- Sep 02, 2016
-
-
- Sep 01, 2016
-
-
Wim Taymans authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Aug 31, 2016
-
-
low/high-watermark are of type double, and given in range 0.0-1.0. This makes it possible to set low/high watermarks with greater resolution, which is useful with large multiqueue max sizes and watermarks like 0.5%. Also adding a test to check the fill and watermark level behavior. https://bugzilla.gnome.org/show_bug.cgi?id=770628
-
To make the code clearer, and to facilitate future improvements, introduce a distinction between the buffering level and the buffering percentage. Buffering level: the queue's current fill level. The low/high watermarks are in this range. Buffering percentage: percentage relative to the low/high watermarks (0% = low watermark, 100% = high watermark). To that end, get_percentage() is renamed to get_buffering_level(). Also, low/high_percent are renamed to low/high_watermark to avoid confusion. mq->buffering_percent values are now normalized in the 0..100 range for buffering messages inside update_buffering(), and not just before sending the buffering message. Finally the buffering level range is parameterized by adding a new constant called MAX_BUFFERING_LEVEL. https://bugzilla.gnome.org/show_bug.cgi?id=770628
-