- Apr 18, 2014
-
-
Sebastian Dröge authored
-
Wim Taymans authored
Make a new method to disable the jitterbuffer buffering. Rework the update_estimated_eos() method. Calculate how much time there is left to play. If we have less than the delay of the jitterbuffer, we disabled buffering because we might never be able to fill the complete jitterbuffer again. If we receive an EOS event, disable buffering. We will drain the buffer and eventually push the EOS event out. When we reach the estimated NPT timeout and we didn't receive an EOS event, make one and queue it so that it can be pushed. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=728017 Conflicts: gst/rtpmanager/gstrtpjitterbuffer.c
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Wim Taymans authored
Rework the logic to make buffering messages a little, make sure we don't make the same message multiple times. Consider the buffer full when EOS was received. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=728017 Conflicts: gst/rtpmanager/gstrtpjitterbuffer.c
-
- Apr 12, 2014
-
-
The marker bit isn't mandatory and we had in place code to guess AU boundaries by detecting a new picture start. This guessing code didn't work with interlaced content that has proper marker bits to indicate the AU boundaries. It was leaking the first field buffer and producing a corrupted output. fixes: https://bugzilla.gnome.org/show_bug.cgi?id=728041
-
- Apr 08, 2014
-
-
Reynaldo H. Verdejo Pinochet authored
From libsoup docs: Prior to 2.44 SoupStatus was called SoupKnownStatusCode, but the individual values have always had the names they have now. Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=727329
-
- Apr 01, 2014
-
-
Nicolas Dufresne authored
We set the dimensions just in case but don't validate them afterwards. For some codecs the dimensions are *not* in the bitstream, IIRC VC1 in ASF mode for example. https://bugzilla.gnome.org/show_bug.cgi?id=720568 Conflicts: sys/v4l2/gstv4l2object.c
-
Nicolas Dufresne authored
For format like mpegts, width and height is rarely in the negotiated caps. This patch fixes failure when setting format, and prevent introducing width, height, framerate and format to the caps when fixating. https://bugzilla.gnome.org/show_bug.cgi?id=725860 Conflicts: sys/v4l2/gstv4l2object.c
-
- Mar 29, 2014
-
-
It seems that GStreamer's mpegts elements (tsdemux, tsparse) require caps `video/mpegts,systemstream=true`. As far as I can see the significance of systemstream is to indicate that this is a container format rather than an elementary stream. As this is the case (and I can't understand how it could not be the case with mpegts) I add systemstream=true to v4l2src's caps. This allows v4l2src to be linked with tsdemux for playback from my Hauppauge HD-PVR with the pipeline: v4l2src ! queue ! tsdemux ! video/x-h264 ! decodebin ! xvimagesink In combination with the next commit this fixes using Hauppauge HD-PVR with GStreamer 1.0+.
-
- Mar 27, 2014
- Mar 06, 2014
-
-
Olivier Crête authored
Remove caps restrictions that correspond to the default and are not required in SDP. With the new usage of having pads require a subset of the caps, they will make the negotiation fail.
-
Olivier Crête authored
The "encoding-params" is optional in the SDP, because we now require a subset of the caps, it would fail caps negotiatioin if it wasn't present. So removed it from the template caps.
-
- Mar 05, 2014
-
-
- Mar 03, 2014
-
-
Thiago Santos authored
After a seek, the position and segments info of qtdemux are reset to null or invalid values. For reverse playback, qtdemux will seek to a keyframe and play until the next keyframe, then seek to another previous keyframe. This seeking function requires the position and segments info of qtdemux to be properly initialized. Due to a missing check for segment.rate in the movie demuxing loop it would consider the current segment to have ended without having it initialized, leading qtdemux to attempt to do a previous keyframe seek without proper position and segment info data. This would cause a segfault. This patch fixes it by correctly checking for segment boundaries taking the segment.rate into consideration. https://bugzilla.gnome.org/show_bug.cgi?id=725104
-
Thiago Santos authored
all jpeg frames are sync points, so mark them as such so reverse playback can properly work with the video decoder base class https://bugzilla.gnome.org/show_bug.cgi?id=725104
-
- Feb 28, 2014
- Feb 23, 2014
-
-
- Feb 22, 2014
-
-
- Feb 21, 2014
-
-
We need at least 6 bytes to pass over to _get_frame_len() but we were just checking for a minimum of 2 bytes for the syncword. https://bugzilla.gnome.org/show_bug.cgi?id=724638
-
- Feb 19, 2014
-
-
Commit 46fd12ae introduced connection recovery. But when server does not specify content-size, souphttpsrc tries to reconnect even after regular end of stream. Http server replies with SOUP_STATUS_REQUESTED_RANGE_NOT_SATISFIABLE but souphttpsrc still emits error instead of EOS. https://bugzilla.gnome.org/show_bug.cgi?id=724717 Signed-off-by:
Branislav Katreniak <bkatreniak@nuvotechnologies.com>
-
- Feb 18, 2014
-
-
Stefan Sauer authored
It turns out that the change in gtk-doc-1.20 which wraps the |[]| content in CDATA break xi:inlcude examples. As in a whole jhbuild checkout these where the only 4, we're fixing them instead.
-
Stefan Sauer authored
The "goto unlock" is wrong as in this code path we haven't take the lock yet. Fixes #724619
-
- Feb 17, 2014
-
-
William Jon McCann authored
newer gtkdoc is more sensitive to mismatched docbook tags. This fixes the build in master.
-
- Feb 12, 2014
-
-
Sebastian Dröge authored
souphttpsrc: Retry connection if we're finished before the content size only if we actually have a content size https://bugzilla.gnome.org/show_bug.cgi?id=722185
-
- Feb 11, 2014
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Feb 08, 2014
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Feb 06, 2014
-
-
Wim Taymans authored
-
- Feb 04, 2014
-
-
Not all systems with v4l have ENODATA defined, so check that we have it before attempting to use it. https://bugzilla.gnome.org/show_bug.cgi?id=722953
-
-
Sebastian Dröge authored
Instead do it like all other demuxers and let parsers and decoders handle that. The keyframe information inside the container might be completely wrong like in the sample file of the bug report, and if it is correct and we push no keyframes, then the parsers and decoders will handle that properly anyway. https://bugzilla.gnome.org/show_bug.cgi?id=682276
-
Sebastian Dröge authored
- Jan 19, 2014
-
-
Mark Nauwelaerts authored
-
-
- Jan 14, 2014