- Sep 19, 2014
- Sep 17, 2014
- Sep 16, 2014
-
-
Similar to 94f3d6fc / bz 709423 On some systems (E.G. uClibc and older Glibc versions), O_CLOEXEC is only defined when _GNU_SOURCE is specified, so do so. https://bugzilla.gnome.org/show_bug.cgi?id=736670
-
- Sep 15, 2014
-
-
Wim Taymans authored
In 1.0, we pass the complete caps to transform_caps to allow for better optimizations. Make this function actually work on non-simple caps instead of just ignoring the configured filter caps.
-
- Sep 13, 2014
-
-
Sebastian Dröge authored
We have to skip 12 bytes of data for the chunk, and the data size passed to the sub-chunk parsing functions should have 4 bytes less than the data size. Also when parsing the sub-chunks, check if we actually have enough data to read instead of just crashing. https://bugzilla.gnome.org/show_bug.cgi?id=736266
-
- Sep 11, 2014
-
-
Sebastian Dröge authored
But only if they happen after the Matroska segment. https://bugzilla.gnome.org/show_bug.cgi?id=735833
-
Sebastian Dröge authored
-
- Sep 10, 2014
- Sep 09, 2014
-
-
Nicolas Dufresne authored
This will prevent the converter to be picked automatically in case someone implement dynamic converter selection support. I'd like this to be ranked only for known device, as it's hard to be sure a device is a converter suited for general purpose. Re-negotiation is also needed before we can rank it. https://bugzilla.gnome.org/show_bug.cgi?id=733607
-
There is still around 18 drivers not yet ported to videobuf2. These driver don't support freeing buffetrs through REQBUFS(0) hence for these the memory type probing fails. In order to gain back our previous behaviour in presence of these, we implement a workaround that assuming MMAP is supported. Note that an allocator is only created for device with STREAMING support in the device capabilities. In such case one of MMAP, USERPTR and DMABUF is required. Though DMABUF came afterward, so is not an option and in practice none of these drivers will only do USERPTR. https://bugzilla.gnome.org/show_bug.cgi?id=735660 Also-by: Hans de Goede <hdegoede@redhat.com>
-
- Sep 07, 2014
-
-
Tim-Philipp Müller authored
This is a regression from 1.2 caused by the port to the pad flow combiner. https://bugzilla.gnome.org/show_bug.cgi?id=736192
-
- Sep 04, 2014
-
-
Sebastian Dröge authored
Just giving the original URI can give the false impression that e.g. that one failed host name resolution, while actually the redirection target did.
-
This makes sure that also properties like the pixel-aspect-ratio are the same between both streams and that the output caps contain all fields necessary for complete video caps. https://bugzilla.gnome.org/show_bug.cgi?id=735804
-
- Sep 02, 2014
-
-
Sebastian Dröge authored
They are reported properly by libvpx if the correct struct members are used. This also fixes handling of resolution changes without input caps changes. https://bugzilla.gnome.org/show_bug.cgi?id=719359
-
If the resolution changes in the bitstream without the input caps changing we would previously output corrupted video or crash. https://bugzilla.gnome.org/show_bug.cgi?id=719359
-
Remember to unref the output caps when a new caps event is received as it should generate a new one based on the new caps. https://bugzilla.gnome.org/show_bug.cgi?id=734266
-
- Aug 29, 2014
-
-
Most V4L2 ioctls like try_fmt will adjust input fields to match what the hardware can do rather then returning -EINVAL. As is docmented here: http://linuxtv.org/downloads/v4l-dvb-apis/vidioc-g-fmt.html EINVAL is only returned if the buffer type field is invalid or not supported. So upon requesting V4L2_FIELD_NONE devices which can only do interlaced mode will change the field value to e.g. V4L2_FIELD_BOTTOM as only returning half the lines is the closest they can do to progressive modes. In essence this means that we've failed to get a (usable) progessive mode and should fall back to interlaced mode. This commit adds a check for having gotten a usable field value after the first try_fmt, to force fallback to interlaced mode even if the try_fmt succeeded, thereby fixing get_nearest_size failing on these devices. https://bugzilla.gnome.org/show_bug.cgi?id=735660
-
They may have been modified by the ioctl even if it failed. This also makes the S_FMT fallback path try progressive first, making it consistent with the preferred TRY_FMT path. https://bugzilla.gnome.org/show_bug.cgi?id=735660
-
- Aug 27, 2014
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Aug 25, 2014
-
-
Sebastian Dröge authored
Before it was always using whatever downstream preferred, while the code and documentation claimed something different. https://bugzilla.gnome.org/show_bug.cgi?id=727180
-
- Aug 13, 2014
-
-
Commit 2b9493b5 broke this in two ways: a) we should only pass duration queries in TIME format upstream (or at least not those in DEFAULT or BYTE format), and b) we mustn't overwrite the default value of 'res' from TRUE to FALSE and not set it again later. This led to bogus durations being reported for FLV playback from file, because TIME queries would fail (as 'res' had been set to FALSE) and parsers then do a BYTE query as fallback and try to guesstimate something in return, which of course goes horribly wrong since the BYTE size returned is for the muxed file.
-
- Aug 11, 2014
-
-
Set output caps layout independently from input caps layout which can be either non-interleaved or interleaved. https://bugzilla.gnome.org/show_bug.cgi?id=733866
- Aug 10, 2014
-
-
Mark Nauwelaerts authored
... and correspondingly unexpected buffer sizes.
-
- Aug 08, 2014
-
-