- Jun 09, 2016
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Fix unref assertion failure https://bugzilla.gnome.org/show_bug.cgi?id=767424
-
- Jun 08, 2016
-
-
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
-
- Jun 07, 2016
-
-
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
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
-
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
-
* If outgoing format is unfixated, try to set it to input format. * Call gst_caps_fixate () at end of fixation routine https://bugzilla.gnome.org/show_bug.cgi?id=766719
-
Scalers may change width and height independently, allow to change pixel aspect ratio. https://bugzilla.gnome.org/show_bug.cgi?id=766712
-
To change pixel aspect ratio from DAR to PAR, the necessary scaling factor is DAR/PAR, not DAR*PAR. For good measure, add debug output similar to the fixed-width and fixed-height cases. https://bugzilla.gnome.org/show_bug.cgi?id=766711
-
gst_v4l2_probe_caps() returns the coded size, not the visible size. Subtract the known padding from probed caps with the coded size before using them as filter for caps negotiation with downstream elements. https://bugzilla.gnome.org/show_bug.cgi?id=766382
-
On modern kernels, the G/S_FMT ioctls will always fail using V4L2_BUF_TYPE_VIDEO_OVERLAY with VFL_DIR_TX (e.g. real overlay out drivers) since this is not the intented use (rather rx, according to v4l2 API doc). Probably this is why the Video Output Overlay interface was created, so if the driver advertises it we might as well use. For old kernels (pre 2012) the old way might still work so keeping this for compatibility. https://bugzilla.gnome.org/show_bug.cgi?id=761165
-
Support for the updated V4L2_PIX_FMT_XRGB555 was added in commit 2538fee2 however, when setting the format for use in v4l2 ioctls, the old deprecated format is still used. Convert this to the new accepted format type, as the preferred format. https://bugzilla.gnome.org/show_bug.cgi?id=767300
-
Discard buffers that doesn't contain enough data when dealing with raw video inputs. https://bugzilla.gnome.org/show_bug.cgi?id=767086
-
-
- Jun 06, 2016
-
-
Sebastian Dröge authored
But in that case also remove the pending newsegment event, otherwise we would later send a possibly outdated event. https://bugzilla.gnome.org/show_bug.cgi?id=767071
-
Sebastian Dröge authored
Upstream might have told us something about the to be expected segment, so let's use that information instead of coming up with a [0,-1] segment. https://bugzilla.gnome.org/show_bug.cgi?id=767071
-
Sebastian Dröge authored
The point of d8fb7a9c was to not have any spurious segments stored for later if we do BYTES->TIME conversion, but overriding any TIME segments from upstream does not make any sense. See https://bugzilla.gnome.org/show_bug.cgi?id=763165 https://bugzilla.gnome.org/show_bug.cgi?id=767071
-
- Jun 02, 2016
-
-
After clearing the adapter due to a DISCONT, as might happen when some packet(s) have been lost, the depayloader was pushing data into the adapter (which had no header due to the clear), creating a headerless frame out of it, and sending it downstream. The downstream decoder would then usually ignore it; unless there were lots of DISCONTs from the jitterbuffer in which case the decoder would reach its max_errors limit and throw an element error. Now we just discard that data. It is probaby not worth trying to salvage this data because non-progressive jpeg does not degrade gracefully and makes the video unwatchable even with low packet loss such as 3-5%.
-
- May 27, 2016
-
-
Input buffer memory was not unmapped https://bugzilla.gnome.org/show_bug.cgi?id=766870
-
- May 25, 2016
-
-
gst_v4l2_object_probe_caps() was taking an extra ref on the returned caps for no reason. https://bugzilla.gnome.org/show_bug.cgi?id=766610
-
Sebastian Dröge authored
avidemux: Pass through seek event seqnums in all SEGMENT/EOS events and SEGMENT_DONE messages/events See https://bugzilla.gnome.org/show_bug.cgi?id=765935
-
Sebastian Dröge authored
Some were forgotten. See https://bugzilla.gnome.org/show_bug.cgi?id=765935
-
Sebastian Dröge authored
Also actually store the seqnum in pull mode seeks. See https://bugzilla.gnome.org/show_bug.cgi?id=765935
-
The caps returned by gst_pad_get_current_caps() was never unreffed when not early returning. Fix a leak with the elements/deinterlace test. https://bugzilla.gnome.org/show_bug.cgi?id=766558
-
Some endpoints (like Tandberg E20) can send BYE packet containing our internal SSRC. I this case we would detect SSRC collision and get rid of the source at some point. But because we are still sending packets with that SSRC the source will be recreated immediately. This brand new internal source will not have some variables incorrectly set in its state. For example 'seqnum-base` and `clock-rate` values will be -1. The fix is not to act on BYE RTCP if it contains internal or unknown SSRC. https://bugzilla.gnome.org/show_bug.cgi?id=762219
-
- May 20, 2016
-
-
segment_duration and media_time should be parsed based on version of elst box. Specification defines that an elst box with version 1 has uint64 and int64 values for segment_duration and media_time, respectively. https://bugzilla.gnome.org/show_bug.cgi?id=766301
-
-
Make sure that src pad has caps before sending segment event. https://bugzilla.gnome.org/show_bug.cgi?id=766359
-
- May 19, 2016
-
-
matroskademux would take the GST_OBJECT_LOCK in - gst_matroska_demux_push_codec_data_all() - gst_matroska_demux_query() Some parse element such as FLAC checks upstream seekability, and there is some use cases that matroska-demux is linked to a parse element (e.g.,FLAC format) without intermediate elements (e.g., queue). In this case, matroska-demux never returns from _push_codec_data_all() because the parser can return only after it receives the response to the upstream query, but that's not going to happen because it's deadlocked. Elements must not hold the object lock whilst pushing out events or data. https://bugzilla.gnome.org/show_bug.cgi?id=766645
-
Otherwise we might use an already freed list later and crash or worse.
-
- May 16, 2016
-
-
Jan Schmidt authored
Fix a race in splitmuxsrc by properly connecting to the demuxer signals we're interested in *before* setting it running.
-
Jan Schmidt authored
Set the async-handling property on GstBin to let it manage async-handling instead of the local handling from the previous commit. Works because of #174a5e in core
-
Jan Schmidt authored
When switching fragments, hide the async-start/async-done messages from the parent bin, as otherwise we sometimes (very rarely) hang in PAUSED instead of returning / continuing to PLAYING state.
-
Jan Schmidt authored
-