- Sep 14, 2012
-
-
Tim-Philipp Müller authored
-
Might cause crashes with debug logging enabled. https://bugzilla.gnome.org/show_bug.cgi?id=683996
-
Tim-Philipp Müller authored
-
- Sep 13, 2012
-
-
Tim-Philipp Müller authored
Name it properly, so it, like, works. Clearly no one actually used that..
-
Wim Taymans authored
-
Wim Taymans authored
-
Wim Taymans authored
-
Wim Taymans authored
from git grep for ffmpegcolorspace and x-raw-
-
Wim Taymans authored
-
Wim Taymans authored
-
Jan Schmidt authored
To be used by sub-classes implementing video formats with reordering such as MPEG.
-
Jan Schmidt authored
Hacky, because the still-frame code all lives in -base, where we can't use it - so this is a hacky duplication of -base code. Not sure which way to fix this: Move baseparse to -base, or move still-frame events to core?
-
Jan Schmidt authored
Make the event handling more like what videodecoder does, to ensure that all events are passed to child classes before being placed on the pending queue or pushed onward.
-
Jan Schmidt authored
Reverse the list just before sending. Prepending is more efficient than appending, so this saves some cycles.
-
Jan Schmidt authored
-
- Sep 12, 2012
-
-
Tim-Philipp Müller authored
Facilitate GstBuffer -> GstSample transition for some tags, could be hard to catch otherwise when creating tags, since it'll only be apparent later when someone tries to read the tags.
-
Stefan Sauer authored
-
Tim-Philipp Müller authored
-
Stefan Sauer authored
Rename gst_collect_pads_add_pad_full() to gst_collect_pads_add_pad() and fix all invocations.
-
Mark Nauwelaerts authored
... where __fbufsize is not available
-
Tim-Philipp Müller authored
This reverts commit 232fd295. This was already fixed.
-
Fix race that could cause data corruption when seeking in ring buffer mode. In perform_seek_to_offset(), called from the demuxer's pull_range request, we drop the lock, tell upstream (usually a http source) to seek to a different offset, then re-acquire the lock before we do things to the ranges. However, between us sending the seek event and re-acquiring the lock, the source thread might already have pushed some data and moved along the range's writing_pos beyond the seek offset. In that case we don't want to set the writing position back to the requested seek position, as it would cause data to be written to the wrong offset in the file or ring buffer. Reproducible doing seek-emulated fast-forward/backward on 006653. Conflicts: plugins/elements/gstqueue2.c
-
-
Mark Nauwelaerts authored
-
Mark Nauwelaerts authored
-
Mark Nauwelaerts authored
-
Mark Nauwelaerts authored
-
- Sep 11, 2012
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
Now that we have a gst-libav git repository (symlinked to gst-ffmpeg).
-
Mark Nauwelaerts authored
-
Mark Nauwelaerts authored
-
Wim Taymans authored
We won't be able to implement this so it's better to move it out of the way.
-
Wim Taymans authored
-
Wim Taymans authored
We usually first create the stream_id for the stream_start event and then add the pad to the element. This means that this functions should work when there are no pads on the element yet.
-
Tim-Philipp Müller authored
Upstream might support pull mode, but only sequential pulls, which isn't gonna do much for us. https://bugzilla.gnome.org/show_bug.cgi?id=634927
-
- Sep 10, 2012
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
-
Mark Nauwelaerts authored
-
Mark Nauwelaerts authored
-