- Dec 06, 2020
-
-
Tim-Philipp Müller authored
-
- Dec 04, 2020
-
-
It is possible there are no more pending clocks in the chain, in which case this function returns null. See also tests like test_single_shot_async_future that validate NULL returns. Part-of: <!716>
-
- Dec 02, 2020
-
-
It takes an enum and only the defined values are valid to pass in here as it's not extensible from the outside. Add a g_return_val_if_reached() for the unreachable case and return "invalid". Part-of: <!713>
-
- Nov 20, 2020
-
-
When compiling for 32bit architectures with 64bit time_t e.g. riscv32, the static assert that the GstClockEntryImpl smaller or equal to the struct _GstClockEntryImpl triggered. (they were 12bytes off). To fix this, the padding is increased by 8 bytes (on 32bit). Part-of: <!695>
-
identity should provide when sync=true. Don't provide when sync=false. Fixes gstreamer/gstreamer#630 Part-of: <gstreamer/gstreamer!697>
-
- Nov 16, 2020
- Nov 05, 2020
-
-
Part-of: <!699>
-
- Nov 04, 2020
- Nov 02, 2020
-
-
The PIDs on log lines were supposed to be colorized before, but the escape sequence was incorrect. With this change, the code uses the correct sequence to colorize those PIDs. E.g., instead of `\033[334m` (incorrect), use `\033[34m` (correct). This makes the log messages easier to read. It also reduces the chance that a buggy terminal will choke on the invalid escape sequence. #624 Part-of: <!691>
-
- Oct 30, 2020
- Oct 29, 2020
-
-
While we can fixe the upstream latency using the min-upstream-latency, we are now forced to use queues (hence more thread) in order to store the pending data whenever we have an upstream source that has lower latency. This fixes the issue by allowing to buffer the fixed upstream latency. This is particularly handy on single core systems were having too many threads can cause serious performance issues. Part-of: <!684>
-
- Oct 27, 2020
-
-
Tim-Philipp Müller authored
-
- Oct 26, 2020
-
-
Tim-Philipp Müller authored
-
- Oct 14, 2020
- Oct 13, 2020
- Oct 12, 2020
-
-
Most symbols in DbgHelp.h are not allowed for UWP Part-of: <!670>
-
- Oct 10, 2020
-
-
gstinfo.c(3086): error C2094: label 'done' was undefined Part-of: <!668>
-
e.g. on 32-bit arm, we may have armv6, armv7l, armv7hf, etc which all generally have the same layouts. cpu_family() groups all of these into just 'arm' that the ABI check table is expecting. Part-of: <!667>
-
The default implementation doesn't actually use its buffer parameters, but this error might have been the cause of some actual confusion in the plugins code. Part-of: <!666>
-
- Oct 03, 2020
-
-
Adds missing "transfer full" annotation for caps parameter in gst_pad_template_set_documentation_caps() Part-of: <!660>
-
Subsequent lookups in the hashtable are probably better done on memory we're confident is allocated to us :) It was easy to trigger invalid reads by calling gst_meta_register with dynamically allocated memory, freeing that memory, then calling gst_meta_get_info() Part-of: <!657>
-
... and update meson file so that enable it only using required headers. "dependency(...)" is unlikely successful for Windows SDK libraries since it doesn't ship pkg-config file. So it needs to be changed to "find_library()" to link corresponding .lib file. That would result to most MSVC build system will link dbghelp.dll. However, one drawback of the change is that gstreamer-1.0.dll will mandate dbghelp.dll although it should be optional. So g_module_open() way can be the most safe way in this case. Part-of: <!659>
-
The template itself is already marked as such and the caps, the documentation caps are a logical extension of those two. Part-of: <!658>
-
- Oct 02, 2020
- Oct 01, 2020
-
-
When going to PLAYING we will now have a clock and can stop waiting on the condition variable and instead start waiting on the clock if necessary for the current configuration. In the other direction when going to PAUSED the clock might have disappeared and we might need to wait on the condition variable again instead. Part-of: <!653>
-
- Sep 30, 2020
- Sep 08, 2020
-
-
Tim-Philipp Müller authored
-
- Sep 07, 2020
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
Part-of: <!618>
-
- Aug 25, 2020
-
-
Sebastian Dröge authored
Part-of: <gstreamer/gstreamer!607>
-
- Aug 24, 2020
-
-
On the first buffer the base class would update the segment position based on the start-time-selection. If the subclass provides its own segment this will caused unexpected behaviour and override segment information that was explicitly set by the subclass. Part-of: <gstreamer/gstreamer!600>
-
- Aug 20, 2020
-
-
Tim-Philipp Müller authored
-
- Aug 10, 2020
-
-
Mathieu Duponchelle authored
GI expects the instance parameter to be documented, omitting it leads to a msismatched output in the gir. Part-of: <gstreamer/gstreamer!592>
-
- Aug 07, 2020
-
-
Sebastian Dröge authored
Subclasses can use this to provide more information, for example audioaggregator could provide the offset into the output buffer where the next data is going to be filled. See gstreamer/gst-plugins-base#805 Part-of: <gstreamer/gstreamer!590>
-
- Aug 05, 2020
-
-
Mathieu Duponchelle authored
Part-of: <gstreamer/gstreamer!588>
-
- Aug 04, 2020
-
-
Part-of: <gstreamer/gstreamer!586>
-