- Jun 07, 2015
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Jun 05, 2015
-
-
Sebastian Dröge authored
Otherwise ssrc changes via rtpsession's (deprecated!) internal-ssrc property are not possible anymore. rtpsession was now patched to only suggest an ssrc if it makes sense to do so. In 2.0 we should get rid of all the properties that are also negotiated via caps, the code and behaviour is too confusing otherwise. https://bugzilla.gnome.org/show_bug.cgi?id=749581
-
Sebastian Dröge authored
Also actually add them to the documentation.
-
According to this section of the rfc. https://tools.ietf.org/html/rfc5506#section-3.4.2 The validation should be updated to accept more types of RTCP packages, with this mask change feedback packages will be also accepted. Change-Id: If5ead59e03c7c60bbe45a9b09f3ff680e7fa4868
-
- Jun 04, 2015
-
-
-
-
-
Mathieu Duponchelle authored
Which contains fields such as duration, uri and tags. https://bugzilla.gnome.org/show_bug.cgi?id=749673
-
Sebastian Dröge authored
-
- Jun 02, 2015
-
-
Makes source code smaller, and ensures we go through common initialization path (like the one that sets up XML unit test output ...)
-
-
Edward Hervey authored
-
- Jun 01, 2015
-
-
Tim-Philipp Müller authored
Micro-optimisation: if the buffer consist of just one memory, we know we have already mapped that memory to read the headers, so no need to map it another time to get to the payload data, we can just set up the payload data details right there and then and avoid another map call in gst_rtp_buffer_get_payload(). Adds up when receiving RTP-payloaded raw video which can easily be thousands of packets per frame.
-
Tim-Philipp Müller authored
Implement a chain_list function, which avoids lots of locking compared to the default fallback implementation in GstPad. We may also want to do some more sophisticated timestamp tracking here at some point, but for now leave it up to the jitterbuffer and/or subclasses (in case buffers in the buffer list have no timestamp set on them, there may only be a timestamp for the whole list on the first buffer). This provides the exact same behaviour as the default fallback implementation.
-
Thibault Saunier authored
Summary: So that the user can easily use the same encoding profile to render with/without audio/video stream. API: gst_encoding_profile_is_disabled gst_encoding_pofile_set_enabled https://bugzilla.gnome.org/show_bug.cgi?id=749056
-
- May 30, 2015
-
-
Luis de Bethencourt authored
The second assignment of sret is never used. We can remove the first assignment and use the value directly instead.
-
Sebastian Dröge authored
id3v2frames.c:951:20: error: unused variable 'utf16enc' [-Werror,-Wunused-const-variable] static const gchar utf16enc[] = "UTF-16"; ^ id3v2frames.c:952:20: error: unused variable 'utf16leenc' [-Werror,-Wunused-const-variable] static const gchar utf16leenc[] = "UTF-16LE"; ^ id3v2frames.c:953:20: error: unused variable 'utf16beenc' [-Werror,-Wunused-const-variable] static const gchar utf16beenc[] = "UTF-16BE"; ^
-
- May 29, 2015
-
-
Jan Schmidt authored
-
Jan Schmidt authored
-
Jan Schmidt authored
-
Jan Schmidt authored
-
Jan Schmidt authored
Instead of returning the first video meta found on a buffer, return the one with the lowest id (which is usually the same thing, except on multi-view buffers)
-
Tim-Philipp Müller authored
Handle unknown info types when deserializing instead of dereferencing NULL pointers. Coverity CID 1302394
-
George Kiagiadakis authored
Otherwise, a malformed SDP message could crash the application, or even maliciously gather data from the memory located after this buffer... https://bugzilla.gnome.org/show_bug.cgi?id=750096
-
George Kiagiadakis authored
tests: add test for videorate caps renegotiation after a framerate has been calculated and added to caps The original 0/1 framerate must still be allowed to be configured on the upstream side of videorate, otherwise future caps renegotiation is going to fail. https://bugzilla.gnome.org/show_bug.cgi?id=750032
-
George Kiagiadakis authored
When a stream has a variable framerate, videorate calculates it and forces it on the output caps. However, the code in _transform_caps() currently also does that if the transform is going in the opposite direction (GST_PAD_SRC), so during a renegotiation it tries to force upstream to use the calculated framerate and it fails. https://bugzilla.gnome.org/show_bug.cgi?id=750032
-
- May 28, 2015
-
-
Thiago Santos authored
This part of pipeline is: tee name=t ! visualizationbin ! streamsynchronizer name=s t. ! s. streamsynchronizer might block and it could starve the visualization branch of the pipeline when it is enabled. The visualization bin has queues internally but the other branch that links the audiotee directly to the synchronizer is vulnerable to block. Adding a queue between "t. ! s." fixes deadlocks. https://bugzilla.gnome.org/show_bug.cgi?id=749676
-
- May 26, 2015
-
-
This will be more useful once we have absolute direct control bindings. https://bugzilla.gnome.org/show_bug.cgi?id=749824
-
Don't leak the building_chain when destroying. Fix leaks with the validate.http.playback.reverse_playback.vorbis_theora_1_ogg scenario. https://bugzilla.gnome.org/show_bug.cgi?id=748964
-
- May 25, 2015
-
-
Tim-Philipp Müller authored
Use g_utf16_to_utf8() instead of the more generic g_convert(), so that we can extract text in UTF-16 format even on embedded systems with crippled iconv support. This code path is exercised by the id3demux test_unsync_v23 check in gst-plugins-good. https://bugzilla.gnome.org/show_bug.cgi?id=741144
-
Tim-Philipp Müller authored
-
- May 24, 2015
-
-
Tim-Philipp Müller authored
Instead of resetting rate to 1.0
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
- May 23, 2015
-
-
Tim-Philipp Müller authored
Has been removed in 835422b2 as part of porting things over to the new videoscale API.
-
- May 21, 2015
-
-
Tim-Philipp Müller authored
And change --interactive option to --no-interactive.
-
Sebastian Dröge authored
-
- May 20, 2015
-
-
Sebastian Dröge authored
And also add missing headers/sources https://bugzilla.gnome.org/show_bug.cgi?id=749632
-