- Jul 19, 2014
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
Instead leave the x component unset when filling the borders. https://bugzilla.gnome.org/show_bug.cgi?id=733380
-
- Jul 16, 2014
- Jul 11, 2014
-
-
Nicolas Dufresne authored
We cannot allocate new buffer in acquire, otherwise the base class is not aware and get confused. Instead, copy in _process(). This leads to crash on finalize. Fixes regression, see https://bugzilla.gnome.org/show_bug.cgi?id=732912
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Parenting V4l2Memory to DmabufMemory was in conflict with recent optimization in DmabufMemory to avoid dup(), and didn't work with memory sharing. Instead, use a qdata and it's destroy notify. https://bugzilla.gnome.org/show_bug.cgi?id=730441
-
Sebastian Dröge authored
-
- Jul 10, 2014
-
-
Nicolas Dufresne authored
This is a workaround for element that don't request buffers when they should. https://bugzilla.gnome.org/show_bug.cgi?id=732288
-
-
Sebastian Dröge authored
And do it always, not inside a g_return_val_if_fail(). See https://bugzilla.gnome.org/show_bug.cgi?id=732939
-
- Jul 09, 2014
-
-
Before we would hit an assertion "'gst_buffer_pool_is_active (bpool)' failed" if the internal pool was not used to push buffer downstrea, hence not given to the baseclass. https://bugzilla.gnome.org/show_bug.cgi?id=732912
-
- Jul 04, 2014
-
-
Tim-Philipp Müller authored
We only want to unlock if we push an event downstream and jump to done_unlock label afterwards. We would also unlock in case of a segment seek and then unlock again later, and nothing good can come of that. (This code looks a bit dodgy anyway though, shouldn't it also bail out with FLOW_EOS here in case of a segment seek scenario, just without the event?)
-
Tim-Philipp Müller authored
-
Previously this was printed as characters which caused later processing of the error message to sometimes warn about non-UTF-8 characters. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=732714
-
- Jul 03, 2014
-
-
Nicolas Dufresne authored
If special stride is needed and downstream don't support VideoMeta, pool might be NULL in order to let the baseclass create a generic pool. This would lead to assertion with on Exynos with: gst-launch-1.0 -v filesrc location=mov ! qtdemux ! h264parse ! \ v4l2video8dec ! fakesink https://bugzilla.gnome.org/show_bug.cgi?id=732707
-
Nicolas Dufresne authored
This will ensure we fail earlier if something unrecoverable happens.
-
Nicolas Dufresne authored
In kernel before 3.17, polling during queue underrun would unblock right away and trigger POLLERR. As we are not handling POLLERR, we would endup blocking in DQBUF call, which won't be unblocked correctly when going to NULL state. A deadlock at start caused by locking error in libv4l2 was also seen before this patch. Instead, we wait until the queue is no longer empty before polling. https://bugzilla.gnome.org/show_bug.cgi?id=731015
-
- Jul 02, 2014
-
-
Wim Taymans authored
-
- Jul 01, 2014
-
-
Tim-Philipp Müller authored
The code enumerating STEPWISE framesizes would start from (min_w, min_h) and then add (step_w, step_h) to get the next framesize. However, it should really allow any width from min_w to max_w with step_w and same for heights. Secondly, we would add and probe each individual stepped frame size to the caps as separate structure, which would lead to hundreds if not thousands of structs ending up in the probed caps. Use integer ranges with steps instead. This was particularly noticable with the Raspberry Pi Cam. https://bugzilla.gnome.org/show_bug.cgi?id=724521 https://bugzilla.gnome.org/show_bug.cgi?id=732458 https://bugzilla.gnome.org/show_bug.cgi?id=726521
-
This workaround from 2011 was causing 25 S_FMT ioctls to be sent to my UVC webcam from under gst_v4l2_object_get_caps as it probes all the formats. In total, this adds up to about 5 seconds of execution time, or a 10 second delay while starting up cheese. These ioctls come from a workaround from 2011 where TRY_FMT might make changes to hardware settings, so S_FMT was used to restore the original config: https://bugzilla.gnome.org/show_bug.cgi?id=649067 The driver bug is now assumed fixed. Remove the workaround to fix the long startup delay. https://bugzilla.gnome.org/show_bug.cgi?id=732326
-
-
Vincent Penquerc'h authored
This fixes missing frames from being time skipped. https://bugzilla.gnome.org/show_bug.cgi?id=732372
-
- Jun 29, 2014
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Tim-Philipp Müller authored
Compiler complains about uninitialised variables in the impossible 'default' code path in device provider source/sink switch-case.
-
Tim-Philipp Müller authored
Compiler complains about uninitialised variables in the impossible 'default' code path in device provider source/sink switch-case.
-
- Jun 28, 2014
-
-
Tim-Philipp Müller authored
Actually look for error messages on the bus and fail if there is one before the EOS message. Disable pull mode test which is pointless as long as matroskaparse only supports push mode (pull mode support has not been ported over to 1.0).
-
Tim-Philipp Müller authored
gst_matroska_parse_take() would return FLOW_ERROR instead of FLOW_EOS in case there's less data in the adapter than requested, because buffer is NULL in that case which triggers the error code path. This made the unit test fail (occasionally at least, because of a bug in the unit test there's a race and it would happen only sporadically).
-