- Mar 19, 2018
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
As on Ubuntu Trusty. https://bugzilla.gnome.org/show_bug.cgi?id=794493
-
Sebastian Dröge authored
76e458a1 changed the conditions from "queued > threshold" to "queued >= threshold", which broke hlssink2 and resulting in too small fragments being created although keyframes would be at *exactly* the configured threshold. https://bugzilla.gnome.org/show_bug.cgi?id=794440
- Mar 17, 2018
-
-
Tim-Philipp Müller authored
Fix compilation with MSVC. We still assume that attribute is supported by all other relevant compilers, which seems to be the case since we haven't had any complaints about similar code in rtpsbcpay.
-
Tim-Philipp Müller authored
Use GLib macro instead, even if it's a bit unwieldy.
-
Tim-Philipp Müller authored
Fixes build with MSVC, and possibly other compilers too.
-
- Mar 13, 2018
-
-
Tim-Philipp Müller authored
- Mar 12, 2018
-
-
Tim-Philipp Müller authored
-
- Mar 10, 2018
-
-
Nirbheek Chauhan authored
These were missed when they were added to Makefile.am
-
- Mar 08, 2018
- Mar 07, 2018
-
-
- Mar 03, 2018
-
-
Tim-Philipp Müller authored
- Mar 01, 2018
-
-
Olivier Crête authored
The muxed buffers will not carry the duration of the incoming buffers. https://bugzilla.gnome.org/show_bug.cgi?id=793457
-
-
Sebastian Dröge authored
This works around a bug in various ONVIF cameras that implement the attributes the wrong way around. They still won't work with a backchannel but at least normal playback will work for the time being. It restores pre-1.14 behaviour where we would fail to preroll on any SDP that lists a recvonly stream. For 1.16 a better solution should be found. The problem here is that the ONVIF spec has the meaning of the two attributes the wrong way around in the examples, compared to RFC4566. https://bugzilla.gnome.org/show_bug.cgi?id=793715
-
-
Mathieu Duponchelle authored
The aggregator segment is now exposed on the src pad https://bugzilla.gnome.org/show_bug.cgi?id=793945
-
Nirbheek Chauhan authored
As stated in commit c2956036 in -bad, the wasapi elements are now better than directsound, and should be preferred if they are available. For a later release, once the elements have more testing, we can consider moving them to -good.
-
- Feb 28, 2018
-
-
Sebastian Dröge authored
matroskamux: Only mark new clusters as keyframe if they start on a keyframe or we're muxing only audio Based on a patch by Nicola Murino <nicola.murino@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=792775
-
Sebastian Dröge authored
Only up to timescale * G_MAXINT16 is possible as cluster duration, which is already higher than our default value. Using higher values would cause overflows and broken files. Based on the investigation by Nicola Murino <nicola.murino@gmail.com> https://bugzilla.gnome.org/show_bug.cgi?id=792775
-
Sebastian Dröge authored
Matroska does not support changing the stream type and stream properties after the headers were started to be written, and for example H264 codec_data changes can't be supported. https://bugzilla.gnome.org/show_bug.cgi?id=782949
-
- Feb 27, 2018
-
-
Mathieu Duponchelle authored
The default of the allow-no-red-blocks property was changed in a previous commit, thus breaking the test assumptions
-
Tim-Philipp Müller authored
rtpulpfeccommon.c:432:27: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 10 has type ‘guint64 {aka long long unsigned int}’ https://bugzilla.gnome.org/show_bug.cgi?id=793732
-
- Feb 26, 2018
-
-
Mathieu Duponchelle authored
-
Mathieu Duponchelle authored
-
Mathieu Duponchelle authored
The ulpfecenc "mux-seq" and "ssrc" properties were initially added because the element did more than implement ULPFEC. As it was decided that FLEXFEC would be implemented in a separate element, both properties are now unneeded and confusing. Change the default for the ulpfecenc multi-packet property, as it is expected that most users of this element will be protecting video streams. Change the default property for the rtpredenc allow-no-red-blocks property, as it should also be its default mode of operation. https://bugzilla.gnome.org/show_bug.cgi?id=793843
-
- Feb 24, 2018
-
-
Mathieu Duponchelle authored
It is expected that when connecting to a stream that has already started, the caps will only arrive at the interval specified on rtpgstpay, we shouldn't be warning as this is a normal mode of operation. https://bugzilla.gnome.org/show_bug.cgi?id=793798
-
- Feb 23, 2018
- Feb 22, 2018
-
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- Feb 21, 2018
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
Fixes make distcheck
-
Tim-Philipp Müller authored
-
Mathieu Duponchelle authored
-
Mathieu Duponchelle authored
The test name was updated but not the build definition
-
Mathieu Duponchelle authored
Also slightly refactor complete_session_src https://bugzilla.gnome.org/show_bug.cgi?id=792696
-