- Mar 14, 2022
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
This removes warning like: ../subprojects/gstreamer/gst/gstchildproxy.h:57: Error: Gst: identifier not found on the first line: * #GstChildProxyInterface::get_child_by_name: ^ Part-of: <gstreamer/gstreamer!1951>
-
Part-of: <gstreamer/gstreamer!1950>
-
Decoders that required frame aligmment and didn't have an associated alpha decoder were skipped. This is because the parser was constructing caps based on the software alpha decoder, which specify super-frame alignment. Iterate over the caps to filter the one that have a matching codec-alpha, with the semantic the no codec-alpha field means codec-alpha=false. Then if everything was removed, callback to the original, so that the first non-alpha decoder will be picked. Fixes #820 Part-of: <gstreamer/gstreamer!1949>
-
Needed for _IOR/_IORW Part-of: <!1947>
-
There is a chance that pool->buffers[index] sets BUFFER_STATE_QUEUED, but it has not been queued yet which makes pool->buffers[index] still NULL. At this time, if pool_streamff release all buffers with BUFFER_STATE_QUEUED state regardless of whether the buffer is NULL or not, it will cause segfault. To fix this, also check buffer when streamoff release buffer. Part-of: <gstreamer/gstreamer!1948>
-
- Mar 13, 2022
-
-
We only need the current field, just like `linear`. Part-of: <gstreamer/gstreamer!1944>
-
- Mar 12, 2022
-
-
The pool size might need to be larger than encoding surface pool size. Also, because we always copy input frame into internal CUDA memory, there's no reason to restrict max size of buffer pool. Part-of: <gstreamer/gstreamer!1942>
-
Used to make comb artifacts for videotestsrc pattern=ball for YUY2 format only (not AYUV). Part-of: <gstreamer/gstreamer!1943>
-
Address compare was not a valid approach since it works only if SPS/PPS id are changed. Otherwise it will always point to the same address of member variables of h265parser. Part-of: <gstreamer/gstreamer!1941>
-
- Mar 11, 2022
-
-
gst_h264_dpb_needs_bump() can be called with null picture in case of live Part-of: <gstreamer/gstreamer!1929>
-
- Mar 10, 2022
-
-
Tim-Philipp Müller authored
Those are needed by rtpjitterbuffer to do the right thing, e.g. a=ts-refclk:ptp=IEEE1588-2008:00-**-**-**-**-**-**-**:0 a=mediaclk:direct=1266592257 Part-of: <gstreamer/gstreamer!1925>
-
By using a workaround to the lack of g_ptr_array_steal_index. Fixes #1078 Part-of: <gstreamer/gstreamer!1919>
-
There could be a case where the new program has the same program number as the previous one ... but is actually located on a PID previously used for elementary stream. In that case the program is guaranteed to not be an update of the previous program but a completely new one. Part-of: <gstreamer/gstreamer!1919>
-
We need to be able to look for programs by their PID also. Using a hash table was a bit sub-par (and overkill) for storing a range of programs. This is needed because there could potentially be two programs with the same program id but different PMT PID (while one is being deactivated the new one would "exist"). Part-of: <gstreamer/gstreamer!1919>
-
This feature was removed in 7a53fbad, but this code was left behind. Part-of: <gstreamer/gstreamer!1922>
-
This patch fixes a seg.fault in gst_structure_new() with warnings as below. GLib-GObject-WARNING **: ../gobject/gtype.c:4330: type id '0' is invalid GLib-GObject-WARNING **: can't peek value table for type '<invalid>' which is not currently referenced Part-of: <gstreamer/gstreamer!1920>
-
- Mar 09, 2022
-
-
libsoup-2.4.so / libsoup-3.0.so are symlinks installed by development packages, they are not available at runtime. Also eliminate G_MODULE_SUFFIX since it's not useful for us, and is actually incorrect on macOS anyway. Fixes gstreamer/gstreamer#1071 Part-of: <gstreamer/gstreamer!1907>
-
Fix a small race where a group can receive stream-start and post a pending buffering message just as another thread posts a different buffering message, causing them to be received by the application out of order. In the worst case, this leads the application receiving a stale 99% buffering message and going back to buffering right after the 100% buffering message. Part-of: <gstreamer/gstreamer!1901>
- Mar 08, 2022
-
-
And use the output segment position for the outgoing timestamp while it is. This is needed to delay the calculation of `output_ts_offset` until we actually have a usable timestamp, as tsmux will output a few initial packets while `last_ts` is still unset. Without this, the calculation would use the initial `0` value, which did not have the intended effect of making VBR mode behave like CBR mode, but always calculated an offset equal to the selected start time. Part-of: <gstreamer/gstreamer!1895>
-
It's a GstClockTimeDiff, thus GST_CLOCK_TIME_NONE isn't appropriate. Part-of: <gstreamer/gstreamer!1895>
-
When doing only a single stream of audio/video this hardly matters, but when doing many at the same time, the fact that you have to get a hold of the glib global type-system lock every time you process a buffer, means that there is a limit to how many streams you can process in parallel. Luckily the fix is very simple, by doing a cast rather than a full type-check. Part-of: <gstreamer/gstreamer!1890>
-
Part-of: <gstreamer/gstreamer!1888>
-
- Mar 07, 2022
-
-
Part-of: <gstreamer/gstreamer!1871>
-
Specially when parsing errors and warnings, the details field can be NULL and the gst_structure_get() call would return FALSE in such cases, triggering false positive errors. Follow-up for #1063 Part-of: <gstreamer/gstreamer!1871>
-
The GError is an out parameter, so should be a ** parameter, like the details parameter. See also #1063 Part-of: <gstreamer/gstreamer!1871>
-
When tunneling over HTTP, if connection on the second channel happens before the control timer is created we may trigger an assert in rtsp_ctrl_timeout_remove(). Avoid that by taking the priv->lock before attaching the client thread to the context. Fixes #1025 Part-of: <gstreamer/gstreamer!1870>
-
- Mar 05, 2022
-
-
"egl-device" should be checked before the "egl", otherwise unexpected egl will be picked Part-of: <gstreamer/gstreamer!1862>
-
- Mar 04, 2022
-
-
It's possible that the method is being manipulated while downstream queries our latency, leading to crashes. Prevent that from happening. Part-of: <gstreamer/gstreamer!1859>
-
While the actual PES header parser could notify us that it needed more data, we would never actually act on it. This commit will accumulate incoming packets in such situation and re-attempt the header parsing. Fixes #1027 Part-of: <gstreamer/gstreamer!1858>
-
The GError is an out parameter, so should be a ** parameter, like the details parameter. Fixes #1063 Part-of: <gstreamer/gstreamer!1850>
-
- Mar 03, 2022
-
-
../ext/soup/gstsouploader.c(818): error C4098: '_soup_session_send_async': 'void' function returning a value It's technically a false warning, but that's how MSVC works, so fix it. Part-of: <gstreamer/gstreamer!1846>
-
Part-of: <gstreamer/gstreamer!1846>
-
Fixes gstreamer/gstreamer#1007 Part-of: <gstreamer/gstreamer!1846>
-
Part-of: <gstreamer/gstreamer!1846>
-
Fixes #1007 Part-of: <gstreamer/gstreamer!1846>
-
- Mar 02, 2022
-
-
Not having this field is equivalent with it being 1/1 so consider it like that. The generic caps functions are not aware of these semantics and would consider the caps different, causing a negotiation failure when caps are changing from caps with to caps without or the other way around. Part-of: <gstreamer/gstreamer!1833>
-
Not having these fields is equivalent with them being mono/0 so consider them like that. The generic caps functions are not aware of these semantics and would consider the caps different, causing a negotiation failure when caps are changing from caps with to caps without or the other way around. Part-of: <gstreamer/gstreamer!1833>
-