- 21 Jun, 2016 10 commits
-
-
-
Nicolas Dufresne authored
From ac2f647 to f363b32
-
Aaron Boxer authored
Now we don't have to rely on a special value for the tile number. https://bugzilla.gnome.org/show_bug.cgi?id=767817
-
Tim-Philipp Müller authored
gstrtpj2kpay.c:364:21: error: implicit truncation from 'int' to bitfield changes value from -1 to 65535 https://bugzilla.gnome.org/show_bug.cgi?id=767817
-
Tim-Philipp Müller authored
-
Guillaume Desmottes authored
Need to call gst_check_drop_buffers() to release the buffers exchanged during the test. https://bugzilla.gnome.org/show_bug.cgi?id=766561
-
Guillaume Desmottes authored
Flush the bus when cleaning up so pending messages are destroyed. https://bugzilla.gnome.org/show_bug.cgi?id=766561
-
-
Guillaume Desmottes authored
- Flush the bus so messages aren't leaked - Fix pad leak https://bugzilla.gnome.org/show_bug.cgi?id=766561
-
Sebastian Dröge authored
This is supposed to be either in the codec_data (avc stream format) or inside the stream, and we extract it from there. It should not be set from a property as it's stream specific. https://bugzilla.gnome.org/show_bug.cgi?id=767789
-
- 20 Jun, 2016 1 commit
-
-
Aleix Conchillo Flaqué authored
The Session Data Protocol doesn't allow specifying a cipher for the SRTCP, so it will use the SRTP one. In the "srtpenc" element the cipher "aes-128-icm" is the default for SRTP and SRTCP, but if we want to have an SRTCP with the "aes-256-icm" cipher then we also need to set the SRTP cipher to "aes-256-icm", otherwise "aes-128-icm" will be used instead. https://bugzilla.gnome.org/show_bug.cgi?id=767799
-
- 17 Jun, 2016 6 commits
-
-
Tim-Philipp Müller authored
.. by registering the types from the plugin init function. This seems to help, but we'll see if it's enough (might need similar things elsewhere). https://bugzilla.gnome.org/show_bug.cgi?id=693911 https://bugzilla.gnome.org/show_bug.cgi?id=674885
-
Sebastian Dröge authored
And the caps in the sink pad template already used variant (only).
-
Jonas Holmberg authored
There is no valid use case when this property is needed since the values must be in either codec_data or buffer data. https://bugzilla.gnome.org/show_bug.cgi?id=753760
-
Jonas Holmberg authored
Cosmetic change to read NALU type in gst_rtp_h265_pay_decode_nal() the same way as in other places. https://bugzilla.gnome.org/show_bug.cgi?id=753760
-
Aurélien Zanelli authored
Documentation lacks '@' before each enum values and there was an extra line after symbol section which confuses GTK-Doc parser. https://bugzilla.gnome.org/show_bug.cgi?id=767788
-
-
- 15 Jun, 2016 1 commit
-
-
Jürgen Slowack authored
Fixes sps/pps/vps insertion via the config-interval property. https://bugzilla.gnome.org//show_bug.cgi?id=767680
-
- 11 Jun, 2016 1 commit
-
-
Sebastian Dröge authored
-
- 10 Jun, 2016 3 commits
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
Fixes parsing of "Thu May 11 15:57:46 2006 ". https://bugzilla.gnome.org/show_bug.cgi?id=767496
-
Aaron Boxer authored
This field is now required in the sink caps. https://bugzilla.gnome.org/show_bug.cgi?id=766236
-
- 09 Jun, 2016 1 commit
-
-
Fix unref assertion failure https://bugzilla.gnome.org/show_bug.cgi?id=767424
-
- 08 Jun, 2016 3 commits
-
-
Olivier Crête authored
With non-time segments, it now assumes that the arrival time of packets is not relevant and that only the RTP timestamp matter and it produces an output segment start at running time 0. https://bugzilla.gnome.org/show_bug.cgi?id=766438
-
Nicolas Dufresne authored
The heuristic to choose between packetise or not was changed to use the segment format. The problem is that this change is reading the segment during the caps event handling. The segment event will only be sent after. That prevented the decoder to go in packetize mode, and avoid useless parsing. https://bugzilla.gnome.org/show_bug.cgi?id=736252
-
Nicolas Dufresne authored
The heuristic to choose between packetise or not was change to use the segment format. The problem is that this change is reading the segment during the caps event handling. The segment event will only be sent after. That prevented the decoder to go in packetize mode, and avoid useless parsing. https://bugzilla.gnome.org/show_bug.cgi?id=736252
-
- 07 Jun, 2016 13 commits
-
-
Nicolas Dufresne authored
Instead of completely getting rid of the input buffer, copy the metadata, the flags and the timestamp into an empty buffer. This way the decoder base class can copy that information again to the output buffer. https://bugzilla.gnome.org/show_bug.cgi?id=758424
-
Nicolas Dufresne authored
-
Nicolas Dufresne authored
-
Nicolas Dufresne authored
This way one can easily ignore errors. Previously, error were always posted ont he bus. https://bugzilla.gnome.org/show_bug.cgi?id=766172
-
Nicolas Dufresne authored
This is to allow returning an error that can easily be sent as message to the application if the element needs it. Using this also allow ignoring errors. https://bugzilla.gnome.org/show_bug.cgi?id=766172
-
Nicolas Dufresne authored
v4l2src will renegotiate only if the format have changed. As of now, it's not possible to change the allocationw without resetting the camera. To avoid unwanted side effect, simply keep the old allocation if no renegotiation is taking place. This fixes assertion and possible failures in USERPTR or DMABUF import mode (when using downstream pools). https://bugzilla.gnome.org/show_bug.cgi?id=754042
-
Edward Hervey authored
Makes it easier to trace what's going on
-
Edward Hervey authored
That variable is only needed for a debug statement, move it there
-
Edward Hervey authored
No variables were added/removed. This was just a good excuse to: * Comment what most variables are used for (and when) * Order them in such a way as to show first the common variables used in all cases, followed by those only used in push-mode
-
Edward Hervey authored
Let's just remove it, been commented for 7+ years :)
-
Only if the decoder stop command fails, keep queueing empty buffers to signal end of stream as before. https://bugzilla.gnome.org/show_bug.cgi?id=733864
-
Sebastian Dröge authored
We shouldn't go through segment activation as we will only have a limited understanding of how the whole stream timeline looks like from the moof. We only know about the current fragment, while upstream knows about the whole stream. This fixes seeking in DASH streams, both for seeks after the current moof and for seeks into the current moof. The former would fail because the moof ends and we can't activate any segment, the latter would cause a segment that stops at the moof end, and no further fragments would be played because we end up being EOS. https://bugzilla.gnome.org/show_bug.cgi?id=767071
-
- 06 Jun, 2016 1 commit
-
-
Nicolas Dufresne authored
When we fixate for upstream, try to not introduce new fields when not needed. This was imported from videoconvert element.
-