- Aug 19, 2016
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Aug 18, 2016
-
-
Sebastian Dröge authored
Some servers add properties like charset, e.g. application/sdp; charset=utf8 Ideally we should also parse the charset and do conversion of all messages, but that's for a later time.
-
- Aug 16, 2016
-
-
This fixes endpoints not receiving any data intermittently. https://bugzilla.gnome.org/show_bug.cgi?id=769773
-
This is a normal scenario and should not be a warning. This can happen frequently when re-transmits of lost packets are enabled. https://bugzilla.gnome.org/show_bug.cgi?id=762208
-
- Aug 08, 2016
-
-
Jan Schmidt authored
Use the correct collected timestamp.
-
- Aug 07, 2016
-
-
Jan Schmidt authored
This reverts commit fa008f27. async-handling in GstBin causes the pipeline to spin at 100% CPU as the top-level pipeline tries to change that state to PLAYING constantly. This is a workaround for a core problem, essentially, but an improvement in this case for now.
-
Jan Schmidt authored
After dropping the splitmux lock, re-check the state, don't just fall through and sleep unconditionally, as we may have already missed the wakeup. https://bugzilla.gnome.org/show_bug.cgi?id=769514
-
Jan Schmidt authored
Don't immediately halt on EOS flow return from downstream due to out of segment. Let the demuxer handle it and send EOS.
-
Jan Schmidt authored
The ts variable is a GstClockTime, don't print it as a GstClockTimeDiff.
-
Jan Schmidt authored
Use signed clock times for running time everywhere so that we handle negative running times without going haywire, similar to what queue and multiqueue do these days.
-
Jan Schmidt authored
When pushing the dummy event into the multiqueue, drop the splitmux lock or else we might deadlock.
-
- Jul 28, 2016
-
-
Sebastian Dröge authored
-
Always intersect with the filter caps in the getcaps function to make sure we return a subset of what was requested. Other payloaders also have this problem and need fixing in future commits.
-
- Jul 25, 2016
-
-
Otherwise we'll wait forever. https://bugzilla.gnome.org/show_bug.cgi?id=747275
-
Sebastian Dröge authored
This can only happen if a) upstream somehow gets around the CAPS event failing or b) there never being any CAPS event. The following code assumes that all pads have a codec-id. https://bugzilla.gnome.org/show_bug.cgi?id=768509
-
Sebastian Dröge authored
-
Sebastian Dröge authored
If necessary, a demuxer will have to invent something here but this is only a problem with non-conformant files anyway.
-
Sebastian Dröge authored
Without, raw AAC can't be handled and we have some information available in the decoder that most likely allows us to decode the stream in one way or another. This is the same code already used by matroskademux for the same reasons, and ffmpeg/vlc play such files just fine too by guesswork.
-
Sebastian Dröge authored
The resulting file is not going to be playable without guesswork and raw caps should always have codec_data.
-
Sebastian Dröge authored
There's a small window for a race condition otherwise.
-
- Jul 11, 2016
-
-
Sebastian Dröge authored
Fixes the build on FreeBSD, which does not have the latter. https://bugzilla.gnome.org/show_bug.cgi?id=768623
-
- Jul 08, 2016
-
-
Nicolas Dufresne authored
This reverts commit d6c8cb63. Apparently this was not fully tested and cause regressions.
-
- Jul 07, 2016
-
-
The same physical device can export multiple devices. In this case, the capabilities field now contains a union of all caps available from all exported V4L2 devices alongside a V4L2_CAP_DEVICE_CAPS flag that should be used to decide what capabilities to consider. In our case, we need the ones from the exported device we are using. https://bugzilla.gnome.org/show_bug.cgi?id=768195
-
- Jul 04, 2016
-
-
Commit 7873bede caused new caps event per moof without consideration of duplication. https://bugzilla.gnome.org/show_bug.cgi?id=768268
-
10 bytes was allocated for stream_format but size of "byte-stream" is more. Use g_strdup() instead. https://bugzilla.gnome.org/show_bug.cgi?id=753760
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
-
Sebastian Dröge authored
rtspsrc: When seeking, consider the current element state or pending state instead of the RTSP state If we consider the RTSP state, what can happen is that it is PLAYING but the element already asynchronously tried to PAUSE and it just did not happen yet. We would then override this setting to PAUSED (while the element actually is in PAUSED) and set the RTSP state to PLAYING again. This would then cause us to produce packets while the sinks are all PAUSED, piling up thousands of packets in the rtpjitterbuffer and other elements and finally failing.
-
- Jun 27, 2016
-
-
Sebastian Dröge authored
And the caps in the sink pad template already used variant (only).
-
Fixes sps/pps/vps insertion via the config-interval property. https://bugzilla.gnome.org//show_bug.cgi?id=767680
-
- Jun 10, 2016
-
-
Tim-Philipp Müller authored
Fixes parsing of "Thu May 11 15:57:46 2006 ". https://bugzilla.gnome.org/show_bug.cgi?id=767496
-
- Jun 09, 2016
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-