- 23 Sep, 2021 1 commit
-
-
Tim-Philipp Müller authored
-
- 02 Sep, 2021 1 commit
-
-
Thibault Saunier authored
Instead of opt-out. Part-of: <!264>
-
- 19 Aug, 2021 3 commits
-
-
Mathieu Duponchelle authored
Part-of: <!265>
-
Mathieu Duponchelle authored
Part-of: <!265>
-
Mathieu Duponchelle authored
This includes both topology and profile Part-of: <!265>
-
- 14 Aug, 2021 3 commits
-
-
Mathieu Duponchelle authored
Since 70e3b8ae the CommandLineFormatter also emit "loaded" so we ended up doing this twice, once as before in `run_pipeline` and another time in the `project:loaded` callback. Part-of: <!265>
-
Mathieu Duponchelle authored
Part-of: <!265>
-
Piotrek Brzeziński authored
Part-of: <!260>
-
- 13 Aug, 2021 2 commits
-
-
Piotrek Brzeziński authored
Part-of: <!260>
-
Piotrek Brzeziński authored
Part-of: <!260>
-
- 06 Aug, 2021 1 commit
- 05 Aug, 2021 1 commit
-
-
Piotrek Brzeziński authored
Part-of: <!263>
-
- 04 Jul, 2021 1 commit
-
-
Piotrek Brzeziński authored
Part-of: <!259>
-
- 16 Jun, 2021 1 commit
-
-
François Laignel authored
Part-of: <!258>
-
- 02 Jun, 2021 1 commit
-
-
Size is constant here, so no problem in any case, but g_memdup() is now deprecated and we don't want deprecation warnings. Part-of: <!257>
-
- 01 Jun, 2021 1 commit
-
-
Tim-Philipp Müller authored
-
- 31 May, 2021 1 commit
-
-
Tim-Philipp Müller authored
-
- 21 May, 2021 6 commits
-
-
Part-of: <!252>
-
Part-of: <!252>
-
We shouldn't show assets usage in the simplest example we have as it is useful for more advanced use cases. Part-of: <!252>
-
Thibault Saunier authored
-
Philippe Normand authored
The tests already depend on -bad, so this should be OK. Part-of: <!254>
-
Philippe Normand authored
Simplifies the code a bit, though introducing runtime dependency on -bad. Part-of: <!254>
-
- 19 May, 2021 2 commits
-
-
Thibault Saunier authored
Since 60922c02 we force string in the command line parser which broke setting layers on clips for example Part-of: <!253>
-
Thibault Saunier authored
And recursively Part-of: <!253>
-
- 14 May, 2021 2 commits
-
-
Seungha Yang authored
Some hardware compositor elements (d3d11compositor and glvideomixer) consist of wrapper bin with internal mixer element. So, we need special handling for such elements. Part-of: <!242>
-
Seungha Yang authored
Other compositor/mixer elements might not have the property. For instance, d3d11compositor and glvideomixer define graphics API specific blending properties, instead of simple "operator" one. Part-of: <!242>
-
- 12 May, 2021 1 commit
-
-
Doug Nazar authored
Skip allocation of temp buffer (which was undersized). Part-of: <!250>
-
- 10 May, 2021 1 commit
-
-
It's not needed for the tests and fixes an occasional issue where the terminal is left in -echo mode. Part-of: <!248>
-
- 05 May, 2021 3 commits
- 27 Apr, 2021 1 commit
-
-
Seungha Yang authored
Sync with gst-launch, as g_print* will print broken string on Windows. See also gstreamer!258 Part-of: <!245>
-
- 23 Apr, 2021 2 commits
-
-
framepositioner will not touch raw video data and therefore should be able to accept ANY caps features Part-of: <!243>
-
Reed Lawrence authored
In gst_frame_positioner_init, there was the magic number 1 when assigning the default value of the operator. Now it has the default value for the operator pulled from the compositor. Part-of: <!241>
-
- 21 Apr, 2021 1 commit
-
-
Reed Lawrence authored
The 'operator' property was added to gstframepositioner so that blending modes in the compositor could be accessed. This was done by accessing the pad of the compositor class, and referencing the 'operator' property in that pad. Getters and Setters were also created so that the 'operator' could be accessed by software that is based on GES, such as Pitivi. Related to but does not close Issue https://gitlab.gnome.org/GNOME/pitivi/-/issues/2313 Part-of: <!236>
-
- 14 Apr, 2021 1 commit
-
-
Seungha Yang authored
GstCaps is not a GObject! Part-of: <!238>
-
- 08 Apr, 2021 1 commit
-
-
Adam Leppky authored
Part-of: <!235>
-
- 19 Mar, 2021 1 commit
-
-
Matthew Waters authored
volatile is not sufficient to provide atomic guarantees and real atomics should be used instead. GCC 11 has started warning about using volatile with atomic operations. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1719 Discovered in gst-plugins-good#868 Part-of: <!234>
-
- 08 Mar, 2021 1 commit
-
-
Thibault Saunier authored
-