| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
- use right fallback variable
- get platform/winsys variables from subproject instead of pkg-config
With contributions from Thibault Saunier.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Since they rely on GstVideoAggregator.
Fix detection of things again, and Meson
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=754094
|
|
|
|
|
|
|
|
| |
This is to mimic LV2 and what is commonly documented over the
web. We also completely track these directories when updating
the cache now. Unlike LV2, the plugins are flat in the plugin
directories, so no need for the recursive lookup. This also fixes
support for Fedora and other architecture using lib64 as a libdir.
|
| |
|
|
|
|
|
|
|
|
|
| |
While keeping it simple, this patch tries and mimic lilv default path.
It does not matter if some path are duplicated due to symlink because in
the end it's lilv that will walk these paths. The worst case is that we
update our cache more often then strictly needed.
https://bugzilla.gnome.org/show_bug.cgi?id=791717
|
|
|
|
|
|
| |
Otherwise we might not update the cache when needed.
https://bugzilla.gnome.org/show_bug.cgi?id=791717
|
|
|
|
|
|
|
| |
This reverts commit 8a056af05e23ad5b81cd1dc2699ae20abcf9b91a.
Accidentally pushed this element, oops! Progress on this element is
being tracked at: https://bugzilla.gnome.org/show_bug.cgi?id=788200
|
|
|
|
|
|
|
| |
LIBDIR must include the prefix. Also use set_quoted instead of
manually quoting because it's clearer what the intention is.
https://bugzilla.gnome.org/show_bug.cgi?id=791751
|
|
|
|
|
|
| |
This plugin is useful when you want to pipe arbitrary data to
a different pipeline within the same process. Buffers, events, and caps
are transmitted as-is without copying or manipulation.
|
|
|
|
|
|
| |
Note that I only support lilv 0.22+ for now, because it's simple and old
enough. If anyone needs to use the 0.16 support it will need to be
added.
|
|
|
|
|
|
| |
range_start/range_end shall be logged as G_GINT64_FORMAT
https://bugzilla.gnome.org/show_bug.cgi?id=791735
|
|
|
|
|
|
|
| |
The lexical form of xs:dateTime is YYYY-MM-DDThh:mm:ss[Z|(+|-)hh:mm]
timezone indicator (+|-)hh:mm] needs to be parsed.
https://bugzilla.gnome.org/show_bug.cgi?id=791602
|
|
|
|
| |
instead of a player instance
|
|
|
|
|
| |
The latter needs additional metadata, and the former was already used
everywhere except for the functions: in properties in playbin itself.
|
|
|
|
|
| |
In preparation of making such properties configurable
via gobject properties.
|
|
|
|
| |
And use standard debugging system for it
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=784160
|
| |
|
|
|
|
|
|
|
|
|
| |
in render()
This seems to allow to schedule audio samples correctly at their right
times already.
https://bugzilla.gnome.org/show_bug.cgi?id=790114
|
|
|
|
|
|
|
|
|
|
|
| |
Not only if the video sink is set to PLAYING so far. Also give more
useful debug output about why we don't start, and don't start if already
started.
Also refactor the function to early-return instead of having a huge
if-else block over the whole function.
https://bugzilla.gnome.org/show_bug.cgi?id=790114
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=790114
|
|
|
|
|
|
|
|
|
|
| |
too much
The buffer level as reported by the Decklink driver is completely
unreliable, and we could otherwise easily run ahead >1s if we're
unlucky.
https://bugzilla.gnome.org/show_bug.cgi?id=790114
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=790114
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Decklink and GstAudioBaseSink APIs don't fit very well together,
which causes various problems due to inaccuracies in the clock
calculations and the actual ringbuffer and GStreamer's copy getting of
sync.
Problems are audio drop-outs and A/V sync getting wrong after
pausing/seeking.
https://bugzilla.gnome.org/show_bug.cgi?id=790114
|
|
|
|
| |
From e8c7a71 to 3fa2c9e
|
|
|
|
|
| |
vtenc.c:564:20: error: incompatible pointer types passing 'GstVTEnc *' (aka 'struct _GstVTEnc *')
to parameter of type 'GstVideoEncoder *' (aka 'struct _GstVideoEncoder *')
|
|
|
|
|
| |
gstglwindow_cocoa.m:186:60: error: incompatible pointer types sending 'GstGLContextCocoa *'
(aka 'struct _GstGLContextCocoa *') to parameter of type 'GstGLContext *' (aka 'struct _GstGLContext *')
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=791391
|
|
|
|
|
|
|
|
|
|
|
| |
"avwait-status" is posted when avwait starts or stops passing through
data (e.g. because target-timecode and end-timecode respectively have
been reached). The attached structure includes a "dropping" boolean (set
to TRUE if we are currently dropping data, FALSE otherwise), and a
"running-time" GST_CLOCK_TIME which contains the running time of the
change.
https://bugzilla.gnome.org/show_bug.cgi?id=790170
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=789064
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=790628
|
|
|
|
|
|
| |
... instead of crash without any information
https://bugzilla.gnome.org/show_bug.cgi?id=791329
|
|
|
|
|
|
|
|
| |
This fixes conflict resolution error introduced in commit:
816d115317c522c87297109de781c63b16146493
http://bugzilla.gnome.org/show_bug.cgi?id=790042
|
|
|
|
|
|
| |
gst_allocator_find() needs gst_object_unref() after usage.
https://bugzilla.gnome.org/show_bug.cgi?id=790042
|
|
|
|
|
|
| |
fix wrong AdaptationSet list iterator
https://bugzilla.gnome.org/show_bug.cgi?id=790812
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The AVERAGE-BANDWIDTH attribute in the EXT-X-STREAM-INF tag represents
the average segment bit rate of the Variant Stream, while the BANDWIDTH
attribute represents the peak segment bit rate of the Variant Stream.
(https://tools.ietf.org/html/draft-pantos-http-live-streaming-23#section-4.3.4.2)
Using the average bit rate instead of the peak bit rate for variant switching
is more efficient and appropriate. Sometimes due to VBR encoding,
the BANDWIDTH may represent a value way above the average bit rate,
which could result to players not switching to that variant stream
although network bandwidth is sufficiently available.
https://bugzilla.gnome.org/show_bug.cgi?id=790821
|
|
|
|
|
|
|
| |
matrix-value-array property is removed since
18917de9562d0d33cf80ca68c071eee3572d4483 commit applied
https://bugzilla.gnome.org/show_bug.cgi?id=790836
|
|
|
|
|
|
|
| |
We copy the meta's from the original buffer to the wrapper or copied
buffer.
https://bugzilla.gnome.org/show_bug.cgi?id=790473
|
|
|
|
|
|
|
|
| |
When we cannot scale, we need to enforce the pixel aspect ratio.
This was partly implemented in the previous patch. Doing this
simplify some of the code.
https://bugzilla.gnome.org/show_bug.cgi?id=784599
|
|
|
|
|
|
|
|
|
| |
continuing
Otherwise we might "start" again, just to get finally stopped and then
getting errors all over the place.
https://bugzilla.gnome.org/show_bug.cgi?id=790114
|
|
|
|
|
|
|
|
| |
gstsrt.c: In function ‘gst_srt_client_connect_full’:
gstsrt.c:151:6: error: ‘sock’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
if (sock != SRT_INVALID_SOCK) {
https://bugzilla.gnome.org/show_bug.cgi?id=791302
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
from getOutputBuffer
1. Similar to 880f3d8, don't consider not getting an output buffer as
an error during flushing. I've seen the following sometimes when
encoding:
W GStreamer+amcvideoenc: java.lang.IllegalStateException
W GStreamer+amcvideoenc: at android.media.MediaCodec.getBuffer(Native Method)
W GStreamer+amcvideoenc: at android.media.MediaCodec.getOutputBuffer(MediaCodec.java:2886)
2. For amcvideodec/enc, call _find_nearest_frame (which grabs a fresh
reference on a GstVideoCodecFrame) after we have an output buffer,
so as to not leak the reference, in case getting an output buffer
fails.
Otherwise, if we get an error grabbing the output buffer, we leak
the reference to the frame. This can cause issues with a
v4l2bufferpool feeding the encoder not being able to clean itself
up properly due to buffers still being marked as in-use.
https://bugzilla.gnome.org/show_bug.cgi?id=791258
|