- 31 Oct, 2021 1 commit
-
-
webrtcbin can act as a sink/source depending on the SDP later. Without setting this here already, surrounding bins might not notice this and the pipeline configuration might become inconsistent, e.g. with regards to latency. See gstreamer#737 Part-of: <!2556>
-
- 29 Oct, 2021 2 commits
-
-
Theoretically the version number is incremented every time there's a new section, but in a world of streaming we can't easily make that assumption. An example of a broken use case is when we're cat-ing two mpeg-ts files together, which is equivalent of capturing a DVB stream while switching channels. A set-top box would know that we switched the channels and reset the demuxer, but in practice this might not happen. Part-of: <!2555>
-
Support new API in 1.1.1 Update the supported input video format. Update tests to use parse_launch Part-of: <!2554>
-
- 21 Oct, 2021 1 commit
-
-
Jan Alexander Steffens authored
Trying to reset before the pads have been deactivated races with the streaming thread. There was also a buggy buffer clear leaving a dangling `stored_frame` pointer around. Use `gst_interlace_reset` so this happens properly. Part-of: <!2553>
-
- 08 Sep, 2021 3 commits
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
hotdoc doesn't know about that symbol Part-of: <!2518>
-
- 06 Sep, 2021 3 commits
-
-
We can reset the URI to NULL and this fix a deadlock in that case or when the URI was invalid. Part-of: <!2512>
-
This avoids sending out partial invalid data downstream which could cause decoders (ex: `dvdlpmdec`) to error out. Part-of: <!2511>
-
Having an unlimited input queue is very bad if the encoder can't run at real-time. Eventually it will consume all RAM. I don't really see any reason to have more than 1 outstanding encoded frame, so remove the queue and limit things to 1 pending frame. Part-of: <!2510>
-
- 02 Sep, 2021 1 commit
-
-
The minimum possible size of valid CEA708 data is 3 bytes, not 7 bytes Part-of: <!2507>
-
- 30 Aug, 2021 1 commit
-
-
Previously, the code was always assuming progressive input, fix this by looking at the caps. Part-of: <!2500>
-
- 25 Aug, 2021 2 commits
-
-
Tim-Philipp Müller authored
This encoder advertises alignment=au as output format, which means each output frame should contain a full decodable access unit. The video encoder base class is not aware of our output alignment and will output spurious buffers with just the SPS/PPS inside when we call gst_video_encoder_set_headers(), which is broken because each buffer is supposed to contain a full decodable access unit in our case. Just don't tell the base class about our headers, they will be sent at the beginning of each IDR frame anyway. Part-of: <!2478>
-
Tim-Philipp Müller authored
Part-of: <!2478>
-
- 24 Aug, 2021 1 commit
-
-
Tim-Philipp Müller authored
This was putting a truncated SPS into the initial header instead of the PPS because it was always reading from the beginning of the bitstream buffer (pBsBuf) and not from the offset where the current NAL is at in the bitstream buffer (psBsBuf + nal_offset). This was broken in commit 17113695. Fixes #1576 Part-of: <!2478>
-
- 23 Aug, 2021 1 commit
-
-
Part-of: <!2479>
-
- 20 Aug, 2021 1 commit
-
-
Negative stride value can be used in MediaFoundation to inform whether memory layout is top-down or bottom-up manner. Note that negative stride is allowed only for RGB, system memory. See also https://docs.microsoft.com/en-us/windows/win32/medfound/image-stride Fixes: #1646 Part-of: <!2477>
-
- 18 Aug, 2021 1 commit
-
-
The emulation bytes need to be removed as bytes, not bit. This fixes decoding issues with files that have emulation bytes with the Cedrus driver. Part-of: <!2472>
-
- 09 Aug, 2021 1 commit
-
-
The GST_ELEMENT_ERROR will call the gst_object_get_path_string and use gst_object_get_parent to get the full object path name, which needs to lock the object. But we are already in a locked context and so this will cause a deadlock, the pipeline can not exit normally. Part-of: <!2460>
-
- 29 Jul, 2021 1 commit
-
-
Nirbheek Chauhan authored
pipewiresrc outputs audio buffers without a valid duration, so we need to calculate it manually in that case. Upstream issue: pipewire/pipewire#1438 Part-of: <!2444>
-
- 16 Jul, 2021 1 commit
-
-
https://gitlab.gnome.org/GNOME/glib/-/issues/803 Basically, if destruction of a GSource and its associated GMainContext are not synchronised, Then the GSource destruction can access freed GMainContext resources and cause a crash. This is not super common but can happen. Part-of: <!2416>
-
- 09 Jul, 2021 1 commit
-
-
Philippe Normand authored
Follow-up from: !2392 Part-of: <!2395>
-
- 08 Jul, 2021 5 commits
-
-
GstDashDemuxStream is not a GstObject, so use its pad as associated object when emitting log messages. Part-of: <!2392>
-
-
We can only convert from non-cdp to cdp within the confines of valid cdp framerates. The existing caps negotiation code was allowing any framerate to convert to a cdp output which is incorrect and would hit an assertion later. Part-of: <!2388>
-
Not having any *actual* ANC is totally fine and common usage with several MXF variants. In order to properly advance the streams, the essence handler returns an empty GAP buffer which gets converted to a GST_EVENT_GAP. Part-of: <!2387>
-
The build fails on macos with the following error: /usr/local/Cellar/opencv/4.5.0_5/include/opencv4/opencv2/core/mat.hpp:2226:15: error: no template named 'initializer_list' in namespace 'std' Mat_(std::initializer_list<_Tp> values); fatal error: too many errors emitted, stopping now [-ferror-limit=] 35 warnings and 20 errors generated. Part-of: <!2386>
-
- 24 Jun, 2021 2 commits
-
-
Some elements will make use of the automatically generated names to create new pads in future muxer instances, for example splitmuxsink. Previously we would've created a pad with a random pid that would become "sink_0", and then on a new muxer instance a pad "sink_0" and tsmux would've then failed because 0 is not a valid PID. Part-of: <!2358>
-
Previously pads might have been requested already (e.g. in NULL state), then reset was called (e.g. because changing state) and then a new pad was requested. Resetting is re-creating the internal muxer object and as such resetting the pid counter, so the next requested pad would get the same pid as the first requested pad which then leads to collisions. Part-of: <!2357>
-
- 22 Jun, 2021 2 commits
-
-
Some decoder implementations might drain out internal buffers and reset its status on segment-done event. So, in case that upstream stream-format is packetized but downstream supports only byte-format, required codec-data might not be forwarded toward downstream if such parameter set NAL units don't exist in inband bitstream. Therefore, parse elements should re-send parameter set NAL units like the case of flush event. Part-of: <!2351>
-
The GST_H265_PROFILE_MAIN_444_10 profile should be compatible with GST_H265_PROFILE_SCREEN_EXTENDED_MAIN_444_10, not the current GST_H265_PROFILE_SCREEN_EXTENDED_MAIN_10. Part-of: <!2350>
-
- 02 Jun, 2021 1 commit
-
-
We were doing our initial "empty" commit on the subsurface instead of the toplevel surface. As an incidence, we should not have received a configure event ever, not just on mutter. This fixes the following warning when using mutter compositor (aka gnome-shell): waylandsink wlwindow.c:304:gst_wl_window_new_toplevel: The compositor did not send configure event. Part-of: <!2300>
-
- 01 Jun, 2021 2 commits
- 20 May, 2021 3 commits
-
-
stream-start, caps, and segment events will be pushed by internal audiotestsrc element. Part-of: <!2271>
-
Expected use case of audiolatency element is that mimic audio capture device which is most likely live source. So audiolatency element should use live mode as well. Part-of: <!2271>
-
Even though input/output resolutions are identical there, default buffer size of progressive and interleaved formats could be different because we are rounding up height of all plane of interlaced frame to be multiple of two. Part-of: <!2270>
-
- 14 May, 2021 3 commits
-
-
Jan Alexander Steffens authored
Part-of: <!2251>
-
Jan Alexander Steffens authored
Bizarrely, it returned a pad from the child rtpbin. I noticed because our application leaked the implicitly created ghost pad. Make an explicit ghost pad so this works properly. Part-of: <!2250>
-
Part-of: <!2248>
-
