- Jul 20, 2018
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Jul 18, 2018
-
-
When negotiation is triggered by receiving caps on our sink pad probes, we could encounter a race condition where need-negotiation is emitted and the application requires the creation of an offer before the current caps were actually updated. This led to retrieving incomplete caps when creating the offer, using find_codec_preferences -> pad_get_current_caps. Instead, as we save the caps in the probe callback anyway, it is better and thread safe to use these if they were set. https://bugzilla.gnome.org/show_bug.cgi?id=796801
-
-
Otherwise we end up trying to flush before sample rate of SoundTouch is set https://bugzilla.gnome.org/show_bug.cgi?id=796613
-
This was wreaking havoc when used with a downstream audiomixer. https://bugzilla.gnome.org/show_bug.cgi?id=796603
-
When max is GST_CLOCK_TIME_NONE in the query, it should not be set in the query handler, this otherwise could lead to impossible situations, where the minimum latency ended up greater than the maximum. https://bugzilla.gnome.org/show_bug.cgi?id=796603
-
The flush function immediately returned when pitch->next_buffer_offset was 0. This is clearly wrong, as next_buffer_offset can be 0 when a single input buffer has been received, and no output buffer has been produced before receiving EOS. Simply remove that condition. https://bugzilla.gnome.org/show_bug.cgi?id=796603
-
gst_video_colorimetry_to_string() returns allocated memory which must be freed. https://bugzilla.gnome.org/show_bug.cgi?id=796596
-
Tim-Philipp Müller authored
-
-
Update the license blurb in camconditionalaccess.[hc] from GPL to LGPL. The plugin is LGPL and the GPL header in those two files was just a copy/paste mistake.
-
- Jul 16, 2018
-
-
Jan Schmidt authored
Fix a leaked string when building RTX info.
-
Jan Schmidt authored
Refactor transportsendbin, and change the way pads are blocked on dtlssrtpenc so that they don't interfere with state changes. As well as being easier to read, this fixes spurious failures shutting down webrtcbin if DTLS negotiation hasn't completed yet.
-
Jan Schmidt authored
Move the errant piece of dtlssrtpenc state change management from dtlstransport in the Webrtc libs, into the transportsendbin that does the rest of the element management so it's all in one place.
-
Jan Schmidt authored
Rename the dtlstransport debug category to webrtcdtlstransport.
-
Jan Schmidt authored
Release references in pad blocks and release the memory in the dispose function too, in case the state change doesn't get run (because calling the parent state change fails).
-
- Jul 04, 2018
-
-
Jan Schmidt authored
Move freeing of the pad blocks back to before we call the GstBin state change function, as there's something racy going on on the build server otherwise, where the pads don't unblock during downward state changes. This is a bit of a stab in the dark, since I can't recreate the build server failure locally.
-
- Jul 03, 2018
-
-
Thibault Saunier authored
Those are GObjects not GstBins
-
- Jul 02, 2018
-
-
Jan Schmidt authored
Fixes random crashes when an allocated webrtcbin isn't given fresh 0-filled memory in its allocation. It works mostly because GMutex and GCond are automatically initialised in that case.
-
- Jun 27, 2018
-
-
Jan Schmidt authored
When changing state downward, we can't set pads to inactive if they are blocked, it will deadlock trying to acquire the streaming lock. Just calling the parent state change function will do the correct things to unblock probes and set the pad inactive, so let it do that and remove the probes after the parent state change function has run https://bugzilla.gnome.org/show_bug.cgi?id=796682
-
Mathieu Duponchelle authored
This lets users call gst_pad_get_current_caps on newly-added pads to easily determine what to plug them into. We cannot copy sticky events unconditionally in core, see #719437 https://bugzilla.gnome.org/show_bug.cgi?id=796387
-
-
-
- Jun 21, 2018
-
-
Check if duration is changed before emitting duration-changed signal https://bugzilla.gnome.org/show_bug.cgi?id=796491
-
-
- Jun 19, 2018
-
-
-
* If the seek was handled upstream, use that SEGMENT seqnum * Use the proper invalid default value
- Jun 01, 2018
-
-
Sreerenj Balachandran authored
It is completely legal to have packets with zero sizes. Zero-sized packet indicates header with only Start Code. One eg: is user data packet. The patch allows having GstMpegVideoPacket with zero sizes. https://bugzilla.gnome.org/show_bug.cgi?id=796477
-
- May 25, 2018
-
-
The calculation for the frame count in the non-aligned case resulted in a one too low buffer frame count. This resulted in: 1) exclusive mode not working as the frame count has to match exactly there. 2) Buffer underruns in shared mode as the current write() code doesn't handle catching up to low buffer levels (fixed in the next commit) To fix just use the wasapi API to get the buffer size which will always be correct. https://bugzilla.gnome.org/show_bug.cgi?id=796354
-
- May 23, 2018
-
-
S_FALSE is a valid return value which does not indicate an error. For example IAudioClient_Stop() returns S_FALSE when it is already stopped. Use the FAILED macro instead which just checks if an error occured or not. This fixes spurious warnings when using the wasapisink element. https://bugzilla.gnome.org/show_bug.cgi?id=796280
-
CoTaskMemFree has a different calling convention than GDestroyNotify and things crash at least with MinGW. https://bugzilla.gnome.org/show_bug.cgi?id=796280
-
- May 17, 2018
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- May 14, 2018
-
-
Regardless of LIVE or VOD, "a manifest has next period but currently EOSed" state is meaning that it's time to advance period. Previous behavior of adpativedemux, however, was able to period advancing only for VOD case, since the adaptivedemux tried to update and wait new manifest without respecting existence of the next period. https://bugzilla.gnome.org/show_bug.cgi?id=781183
-
_get_next_fragment_timestamp() returns relative timestamp to period start. But gst_mpd_client_stream_seek() uses absolute MPD timeline. https://bugzilla.gnome.org/show_bug.cgi?id=781183
-