- 14 Jan, 2020 1 commit
-
-
Alicia Boya García authored
In theory, `dispose()` functions should be idempotent and should be prepared not to crash or cause a double-free if an unref done from inside caused a recursive call to `dispose()` of the same object. https://developer.gnome.org/gobject/stable/howto-gobject-destruction.html This patch modifies the `dispose()` method to honor these constraints. Since the double `dispose()` call won't actually occur in qtdemux (there is no cycle detection mechanism that could invoke it to work that way), this is more of a code cleanup than a user-facing problem fix.
-
- 13 Jan, 2020 2 commits
-
-
The channel position is an enum but the conversion code assumed it's a mask. Convert accordingly.
-
Kristofer Björkström authored
A typo bug: | instead of & resulted in TID alwasy being set to 7 for the aggregated NALU of type 48
-
- 11 Jan, 2020 1 commit
-
-
By default imagefreeze will still reject new buffers after the first one and immediately return GST_FLOW_EOS but the new allow-replace property allows to change this. Whenever updating the buffer we now also keep track of the configured caps of the buffer and from the source pad task negotiate correctly based on the potentially updated caps. Only the very first time negotiation of a framerate with downstream is performed, afterwards only the caps themselves apart from the framerate are updated.
-
- 09 Jan, 2020 1 commit
-
-
Elements emitting frames through several srcpads should use a flow combiner to aggregate the chain returns and therefore only return GST_FLOW_NOT_LINKED to upstream when all the downstream pads have received GST_FLOW_NOT_LINKED. In addition to that, in order to handle pads being relinked downstream, the flow combiner should be reset in response to RECONFIGURE events. This ensures that a both srcpads process a chain operation before a GST_FLOW_NOT_LINKED can be propagated upstream (which would usually stop the pipeline). Otherwise, in a configuration with two srcpads, only one linked at a time, after the relink the element could chain data through the now unlinked pad and the flow combiner would resolve as GST_FLOW_NOT_LINKED (stopping the pipeline) just because the now linked pad has not been chained yet to update the flow combiner. This patch adds handling of RECONFIGURE events to qtdemux. Also, since this event handling causes the flow combiner to be used from a thread other than the qtdemux streaming thread, usages of the flow combiner has been guarded by the object lock.
-
- 06 Jan, 2020 1 commit
-
-
Seungha Yang authored
GValue might have null object. (gst-inspect-1.0:10304): GStreamer-CRITICAL ... gst_object_ref_sink: assertion 'object != NULL' failed
-
- 03 Jan, 2020 1 commit
-
-
Daniel Molkentin authored
-
- 30 Dec, 2019 2 commits
-
-
Also, `control_url` variable has been renamed to `control_path`, as it is actually a path.
-
Appending control string to end of query changes meaning of query string Fixes #650
-
- 28 Dec, 2019 2 commits
-
-
Add transform filter capabilities to aasink and cacasink in the form of new elements aatv and cacatv.
-
We started depending on GLib 2.44, so we can clean up all the GObject boilerplate macros.
-
- 20 Dec, 2019 2 commits
-
-
Use helper method to get string from GValue.
-
The key is to make sure the jitterbuffer is set to NULL *before* the ptdemux. The race that existed would basically happen when ptdemux had reached READY, and the jitterbuffer would then push a buffer, triggering a new pad with a new payloadtype being added and ghosted to the rtpbin itself. However, the srcpad of the ptdemux would now be inactive, and all the sticky-event pushed on it would be swallowed, not allowing any to reach the ghost-pad. Then the buffer in-flight would come to the ghostpad, and we would assert that a buffer arrived before the necessary events. By simply re-ordering the state-changes, we ensure that there will be no buffer racing into the ptdemux while its state is being changed, and the problem disappears completely. Notice also that there is not point in disconnecting the signals on the ptdemux before this point, since we need the push-thread to settle down before we can do this in a non-racy way.
-
- 19 Dec, 2019 1 commit
-
-
Not setting DISCONT avoids a noticable delay when seeking with only rate changing, in the same direction as current rate.
-
- 18 Dec, 2019 4 commits
-
-
GTimeVal won't work past 2038
-
-
avidemux already handles this correctly.
-
avidemux already handles this.
-
- 16 Dec, 2019 4 commits
-
-
Vivia Nikolaidou authored
Receiving a pixel-aspect-ratio should trigger a caps change, but not replace the existing video codec tag
-
-
-
Joakim Johansson authored
Otherwise is it possible to get a crash in gst_rtspsrc_set_parameter.
-
- 13 Dec, 2019 1 commit
-
-
Applications might handle locations and generally configuration of the sink by themselves instead of having splitmuxsink set the location on the sink. Nonetheless it makes sense to increment the fragment_id that is passed to the signal so that applications know which fragment is requested.
-
- 12 Dec, 2019 1 commit
-
-
Jan Alexander Steffens authored
This avoids creating a timestamp regression during a stream. gstreamer/gst-plugins-good!429
-
- 11 Dec, 2019 1 commit
-
-
The logic is taken straight from matroskademux, see 77403d0a
-
- 10 Dec, 2019 1 commit
-
-
Seungha Yang authored
gmtime on *nix is not thread-safe.
-
- 05 Dec, 2019 1 commit
-
-
Allow to change the fragment-id start index.
-
- 04 Dec, 2019 2 commits
-
-
If Mesa is built without X11 headers, building against Mesa EGL headers requires a dependency on egl.pc, to define MESA_EGL_NO_X11_HEADERS. This fixes a build error when compiling ext/qt/gstqtglutility.cc: In file included from /usr/include/EGL/egl.h:39, from /usr/include/gstreamer-1.0/gst/gl/egl/gstegl.h:44, from ../gst-plugins-good-1.16.1/ext/qt/gstqtglutility.cc:43: /usr/include/EGL/eglplatform.h:124:10: fatal error: X11/Xlib.h: No such file or directory
-
Add parsed=true to output caps, as we always output whole frames, timestamped and all. Means also that the output can be decoded by avdec_mjpeg wihout plugging an extra parser (which has no rank).
-
- 03 Dec, 2019 3 commits
-
-
Jan Alexander Steffens authored
In file mode, only push one onMetaData at the start of the stream. In stream mode, always push complete onMetaData. They get replaced, not merged. gstreamer/gst-plugins-good!418
-
Jan Alexander Steffens authored
There's no header to rewrite, so the duration is left unused. gstreamer/gst-plugins-good!418
-
-
- 02 Dec, 2019 3 commits
-
-
Tim-Philipp Müller authored
This was never installed and it was only used by the uninstalled autotools dev environment to locate the -good plugins for use in unit tests in gstreamer modules higher up the stack. It is no longer needed now that we no longer have an autotools build.
-
So that "/" are correct on Windows.
-
That way we get some of the meta -> rtp-extension goodies.
-
- 29 Nov, 2019 4 commits
-
-
VPX_IMG_FMT_I444 pixel format with sRGB colorspace means GBR data. Fixes: gstreamer/gst-plugins-good#651
-
-
-
Håvard Graff authored
...or it will segfault from time to time...
-
- 25 Nov, 2019 1 commit
-
-
Linus Svensson authored
Add a property that makes it possible for an application to set the DateUTC header field in matroska files. This is useful for live feeds, where the DateUTC header can be set to a UTC timestamp, matching the beginning of the file. Needs gstreamer!323 Fixes gstreamer/gst-plugins-good#481
-