- Jun 28, 2014
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Jun 27, 2014
-
-
Thiago Santos authored
The gst_query_set_caps_result doesn't take ownership of caps
-
Thiago Santos authored
Fix leak of caps event and of caps objects when setting caps on sink and src pads
-
Thiago Santos authored
Instead of just feeing the queue structs
-
Thiago Santos authored
gst_event_replace increments the refcount
-
Thiago Santos authored
Avoids an assertion. The cached string will be assigned an empty string as its value when size is 0.
-
Gwenole Beauchesne authored
The gst_h264_parse_pps() function dynamically allocates the slice group ids map array, so that needs to be cleared before parsing a new PPS NAL unit again, or when it is no longer needed. Likewise, a clean copy to the internal NAL parser state needs to be performed so that to avoid a double-free corruption. https://bugzilla.gnome.org/show_bug.cgi?id=707282 Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
-
- Jun 26, 2014
-
-
Gwenole Beauchesne authored
-
Aurélien Zanelli authored
The recovery point SEI message helps a decoder in determining if the decoding process would produce acceptable pictures for display after the decoder initiates random access or after the encoder indicates a broken link in the coded video sequence. This is not used in the h264parse element, but it could help debugging. https://bugzilla.gnome.org/show_bug.cgi?id=723380
-
Gwenole Beauchesne authored
Add nal_reader_skip_long() helper function to allow an arbitrary number of bits to be skipped. The former nal_reader_skip() function is too limited to the actual cache size. Use this new function to simplify gst_h264_parser_parse_sei_message() default case, that skips unsupported payloads. v2: made args consistent from header to source file. Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
-
Matthew Waters authored
We take a ref on the pad's buffer at the beginning so we need to unref when we are done in all cases.
-
Gwenole Beauchesne authored
Use the first _gst_reserved[] slot to hold the built-in range decoder private data. The first slot was formerly the buffer size, which was then promoted to semi-public namespace when it got integrated as git commit 2940ac6. Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
-
Matthew Waters authored
-
Matthew Waters authored
Use the GstObject lock instead
-
Matthew Waters authored
Also plugs a memory leak
-
Matthew Waters authored
gst_query_set_caps_result() takes a ref on the caps
-
Matthew Waters authored
-
Matthew Waters authored
-
Matthew Waters authored
-
- Jun 25, 2014
-
-
Edward Hervey authored
It was previously a mix and match of both variants, introducing just too much confusion. The prefix are from now on: * GstMpegts for structures and type names (and not GstMpegTs) * gst_mpegts_ for functions (and not gst_mpeg_ts_) * GST_MPEGTS_ for enums/flags (and not GST_MPEG_TS_) * GST_TYPE_MPEGTS_ for types (and not GST_TYPE_MPEG_TS_) The rationale for chosing that is: * the namespace is shorter/direct (it's mpegts, not mpeg_ts nor mpeg-ts) * the namespace is one word under Gst * it's shorter (yah)
-
Edward Hervey authored
Data is marked as "transfer full", if we have an error we need to free it.
-
Matthew Waters authored
Otherwise two GL elements on either side will fail to use the same GL context.
-
Matthew Waters authored
-
Matthew Waters authored
-
-
-
Julien Isorce authored
Prefer to stay in the same memory space if possible. Also it let a chance to do passthrough. See https://bugzilla.gnome.org/show_bug.cgi?id=732178
-
Julien Isorce authored
-
Reynaldo H. Verdejo Pinochet authored
-
Reynaldo H. Verdejo Pinochet authored
-
Matthew Waters authored
Allows automatic negotiation of the size in the following case: gst-launch-1.0 glvideomixer name=m sink_0::xpos=0 sink_1::xpos=320 ! glimagesink \ videotestsrc ! m. \ videotestsrc pattern=1 ! m. https://bugzilla.gnome.org/show_bug.cgi?id=731878
-
Matthew Waters authored
-
- Jun 24, 2014
-
-
Edward Hervey authored
Still not done :(
-
Edward Hervey authored
-
Matthew Waters authored
This is too allow gst-launch debugging with multiple GL contexts as well as avoiding segfaulting innocent gtk+ apps that have not called XInitThreads. https://bugzilla.gnome.org/show_bug.cgi?id=731525
-
Matthew Waters authored
We cannot do it as the winsys may crash if we initialize too late. Example, GLX contexts with Intel drivers: Intel requires the X Display to be the same in order to share GL resources across GL contexts. These GL contexts are generally accessed from different threads. Without winsys support it is nearly impossible to guarentee that concurrent access will not occur. This concurrent access could result in crashes or abortion by the winsys (xcb). https://bugzilla.gnome.org/show_bug.cgi?id=731525