- Aug 19, 2016
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Aug 17, 2016
-
-
One location was forgotten in a913a0b9 https://bugzilla.gnome.org/show_bug.cgi?id=767492
-
- Aug 16, 2016
-
-
After seeking in aiff files the information about the data end offset is discarded, leading to audio artifacts with metadata chunks at the end of a file. This patch retains the end offset information after a seek event. https://bugzilla.gnome.org//show_bug.cgi?id=769376
-
As might happen with e.g. vaapi and the test file from https://bugzilla.gnome.org/show_bug.cgi?id=736227
-
Sebastian Dröge authored
-
Sebastian Dröge authored
On the ODroid C1+ the H265 and H264 have the same name but are listed as two different codecs. We have to handle them as the same one that supports both, as otherwise we will register the same GType name twice which fails and we then only have H265 support and not H264 support.
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Matthew Waters authored
Another case of incorrect calling conventions. Using this function on win32 would corrupt the stack pointer and end in massive hilarity.
-
- Aug 15, 2016
-
-
Jan Schmidt authored
It relies on GstGL features and GstVideoAffineTransformationMeta that are only available in git master.
-
Jan Schmidt authored
Sometimes wglCreateContextAttribsARB() exists, but isn't functional (some Intel drivers), so it's easiest to do the workaround unconditionally.
-
Jan Schmidt authored
Don't output debug to an uninitialised debug category.
-
Haihua Hu authored
[Matthew Waters]: gst-indent sources https://bugzilla.gnome.org/show_bug.cgi?id=768160
-
Tim-Philipp Müller authored
Compiler would complain about include directory that didn't exist because QPA_INCLUDE_PATH gets subst-ed regardless (and if it didn't we'd have just an empty -I argument). https://bugzilla.gnome.org/show_bug.cgi?id=767553
-
Haihua Hu authored
Check header file existance and wrap the header file include in the necessary #ifdef to avoid build error. https://bugzilla.gnome.org/show_bug.cgi?id=767553
-
Matthew Waters authored
The current state of c++ ABI's on Window's and Gst's/Qt's conflicting mingw builds means that we cannot use mingw for building the qt plugin. Instead, a qmake .pro file is provided that is expected to be used with the msvc binaries provided by Qt like so: (with the PATH environment variable containing the path to the qt biniaries and PKG_CONFIG_PATH containing the path to GStreamer modules) cd /path/to/sources/gst-plugins-bad/ext/qt qmake -tp vc Then open the resulting VS project and build the library. Then cp debug/libgstqtsink.dll /path/to/prefix/lib/gstreamer-1.0/libgstqtsink.cll https://bugzilla.gnome.org/show_bug.cgi?id=761260
-
-
Matthew Waters authored
Otherwise an application cannot know if the qmlglsink will be displaying frames incorrectly/at all.
-
Matthew Waters authored
-
Haihua Hu authored
Don't use gstgldisplay to get wayland display. Should use QPA on wayland to get wayland display for QT. https://bugzilla.gnome.org/show_bug.cgi?id=767553
-
-
Jan Schmidt authored
Uncompressed RGB frames can be (usually are) bottom-up layout in DirectShow, and the code to flip them wasn't properly ported from 0.10. Fix it. Fix post-processing of RGB buffers. We need a writable buffer, but the requests pool is holding an extra ref. This could use more fixing to use a buffer pool
-
Jan Schmidt authored
It's the primary video source on Windows, so give it a rank for autoplugging by camerabin and friends
-
Jan Schmidt authored
The RGBx and RGB format mappings were reversed. What Windows calls RGB are laid out as BGR in our parlance, so switch that too
-
Nirbheek Chauhan authored
strcasecmp is not defined on MSVC, so just use the glib wrapper. Also pretend to be Windows XP explicitly since the API we use was deprecated and removed (ifdef-ed) from the SDK after this version of Windows. This will be especially relevant once we stop supporting Windows XP soon: https://bugzilla.gnome.org/show_bug.cgi?id=756866
-
- Aug 13, 2016
-
-
Tim-Philipp Müller authored
Update for API changes in v1.6.0. https://bugzilla.gnome.org/show_bug.cgi?id=768771
-
Tim-Philipp Müller authored
It's what introspection.mak does as well. Should fix spurious build failures on gnome-continuous.
-
- Jul 25, 2016
-
-
Thiago Santos authored
When the test involves doing a seek, only check for data size after the seek. The final segment range after seek might be different/smaller than the threshold for doing the seek and doing the check before seeking would fail.
-
Jan Schmidt authored
Make state changes of internal elements more reliable by locking their state, and ensuring that they aren't blocked pushing data downstream before trying to set their state. Add a boolean to avoid starting tasks when the main thread is busy trying to shut the element down.
-
Jan Schmidt authored
Release the manifest lock when signalling no-more-pads, as that can call back into adaptivedemux again Partial cherry-pick of 03f96d
-
Jan Schmidt authored
Drop the manifest lock when performing actions that might call back into adaptivedemux and trigger deadlocks, such as adding/removing pads or sending in-band events (EOS). Unlock the manifest lock when changing the child bin state to NULL, as it might call back to acquire the manifest lock when shutting down pads. Drop the manifest lock while pushing events.
-
-
- Jul 18, 2016
-
-
Sebastian Dröge authored
Some were missing from noinst_HEADERS. https://bugzilla.gnome.org/show_bug.cgi?id=766163
-
- Jul 04, 2016
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
openh264enc: Remove broken byte-stream to avc conversion and just output byte-stream as generated by the encoder The byte-stream to avc conversion did not consider NAL sizes bigger than 2^16, multiple layers, multiple NALs per layer, and various other things. This caused corrupted streams in higher bitrates and other circumstances. Let's just forward byte-stream as generated by the encoder and let h264parse handle conversion to avc if needed. That way we only have to keep around one version of the conversion and don't have to fix it in multiple places.
-
-
- Jun 27, 2016
-
-
If the pad was still owning a buffer when being destroyed it was leaked. Fix a leak with the test_flush_start_flush_stop test. https://bugzilla.gnome.org/show_bug.cgi?id=766663
-