=== release 1.0.6 === 2013-03-22 Tim-Philipp Müller <tim@centricular.net> * configure.ac: releasing 1.0.6 2013-02-14 01:35:45 +0100 Arnaud Vrac <avrac@freebox.fr> * gst/subparse/gstsubparse.c: * gst/subparse/gstsubparse.h: subparse: fix off by one offset calculation Do not use the buffer start offset when it is invalid, otherwise a discontinuity is detected on the next buffer, and the subtitle parser reset and some subtitle lines are not shown. Also remove unused next_offset field. https://bugzilla.gnome.org/show_bug.cgi?id=693981 2013-03-22 09:35:21 +0000 Tim-Philipp Müller <tim.muller@collabora.co.uk> * gst/typefind/gsttypefindfunctions.c: typefinding: fix y4m caps We need to specify the y4mversion field now. https://bugzilla.gnome.org/show_bug.cgi?id=696282 2013-03-21 15:37:31 +0100 Sebastian Dröge <sebastian.droege@collabora.co.uk> * gst/playback/gstsubtitleoverlay.c: subtitleoverlay: Return ANY caps for the GET_CAPS query subtitleoverlay handles any caps, not just the ones for which a subtitle parser/renderer exist. It will just ignore any unsupported streams instead of causing an error. https://bugzilla.gnome.org/show_bug.cgi?id=688476 2013-03-20 19:34:06 +0100 Jan Schole <jan581984@web.de> * gst/videoscale/gstvideoscale.c: videoscale: Correct DAR and border calculations changed: gst_video_scale_set_info in gst/videoscale/gstvideoscale.c DAR on sink side now calculated with PAR on sink side ratio of output width/height now calculated with inverse PAR additional condition that borders are 0:0 for passthrough mode https://bugzilla.gnome.org/show_bug.cgi?id=696019 2013-03-21 11:42:43 +0100 Sebastian Dröge <sebastian.droege@collabora.co.uk> * gst/playback/gstplaysinkconvertbin.c: playsinkconvertbin: Use gst_caps_is_subset() for handling the ACCEPT_CAPS query 2013-03-21 13:33:44 +0100 Sebastian Dröge <sebastian.droege@collabora.co.uk> * gst/playback/gstplaysinkconvertbin.c: playsinkconvertbin: Make sure to return all allowed caps in the GET_CAPS query Add all the caps that we can convert to to the filter caps, otherwise downstream might just return EMPTY caps because it doesn't handle the filter caps but we could still convert to these caps, causing us to return EMPTY caps although conversion would be possible. https://bugzilla.gnome.org/show_bug.cgi?id=688803 2013-03-21 13:29:06 +0100 Sebastian Dröge <sebastian.droege@collabora.co.uk> * sys/ximage/ximagesink.c: ximagesink: Don't access structures of EMPTY caps If the intersection between our caps and the filter caps is empty, just immediately return EMPTY caps instead of trying to access the (non-existant) structures. 2013-03-11 21:55:28 -0600 Greg Rutz <greg@gsr-tek.com> * ext/libvisual/gstaudiovisualizer.c: libvisual: fix improper video frame clear operation The current code is memsetting the GstVideoFrame.data address to 0s (which causes a segfault). This member is actually an array of data buffers (one for each plane). This fix iterates over each data plane to clear them all. https://bugzilla.gnome.org/show_bug.cgi?id=695655 2013-02-13 21:08:48 +0100 Stefan Sauer <ensonic@users.sf.net> * gst/adder/gstadder.c: * tests/check/elements/adder.c: adder: fix setting caps via the "caps" property We were setting the query-func on the sink-pad, which got overwritten when adding the new pad to collect pads. Instead register our query-func with the collect pads object. This fixes filter caps. Add a test for it. 2013-02-12 17:22:23 +0000 Vincent Penquerc'h <vincent.penquerch@collabora.co.uk> * gst/encoding/gstencodebin.c: encodebin: sync muxer state with parent bin Other elements were synced, but not the muxer. Makes sure the muxer is in the right state even when encodebin gets added to the pipeline dynamically after the pipeline has been started. 2013-02-07 21:51:06 +0000 Tim-Philipp Müller <tim.muller@collabora.co.uk> * configure.ac: build: fix build with automake 1.13 AM_CONFIG_HEADER -> AC_CONFIG_HEADERS 2013-02-08 00:05:24 +1100 Jan Schmidt <thaytan@noraisin.net> * ext/pango/gstbasetextoverlay.c: pango: 3rd time's the charm. Fix attribute list handling. Really really fix attribute list handling by taking a copy of the original attributes that pango_attr_list_filter can mutate, but keep the original around intact to restore later. 2013-02-07 23:45:26 +1100 Jan Schmidt <thaytan@noraisin.net> * ext/pango/gstbasetextoverlay.c: pango: Don't modify the original attributes list. Take a copy of the original attributes list instead of just a ref, since pango_attr_list_filter can remove elements from it. 2013-02-07 23:06:16 +1100 Jan Schmidt <thaytan@noraisin.net> * ext/pango/gstbasetextoverlay.c: pango: Remove extra pango_attr_list_copy() from basetextoverlay Fixes a per-buffer memory leak of the attribute list. 2013-02-06 10:00:27 +0100 Wim Taymans <wim.taymans@collabora.co.uk> * gst-libs/gst/app/gstappsrc.c: appsrc: always take mutex before object lock The locking order is to first take the appsrc mutex and then the object lock. Fixes https://bugzilla.gnome.org/show_bug.cgi?id=693224 2013-01-24 20:15:09 -0500 Olivier Crête <olivier.crete@collabora.com> * docs/libs/gst-plugins-base-libs-sections.txt: docs: Put GST_*_INIT into the -sections.txt file too 2013-01-24 20:12:41 -0500 Olivier Crête <olivier.crete@collabora.com> * docs/libs/gst-plugins-base-libs-docs.sgml: * docs/libs/gst-plugins-base-libs-sections.txt: doc: Sort new things into ..-libs-sections.txt 2012-11-15 03:31:47 -0500 yanghuolin <Huolin.Yang@delphi.com> * ext/alsa/gstalsasink.c: * ext/alsa/gstalsasink.h: alsasink: don't use 100% CPU The root cause is that alsa-lib is not thread safe for the same handle. There are two threads in the gstreamer accessing alsa-lib not serilized. The race condition happens when one thread holds the old framebuffer app_ptr position in the kernel, another thread advances the framebuffer app_ptr. when the former thread is scheduled to run again, it overwrites the app_ptr to old value by copying from kernel.Thus,the app_ptr in the upper alsa-lib(pcm_rate) become one period size more advanced than the lower alsa-lib(pcm_hw & kernel). gstreamer uses noblock and poll method to communicate with the alsa-lib. The app_ptr unsync situation as described above makes the poll return immediately because it concludes there is enough space for the ring-buffer via the low-level alsa-lib. The write function returns immediately because it concludes there is not enough space for the ring-buffer from the upper-level alsa-lib. Then the loop of poll and write runs again and again until another period size is available for ring-buffer.This leads to the cpu 100 problem. delay_lock is used to avoid the race condition. Fixes: https://bugzilla.gnome.org/show_bug.cgi?id=690937 2013-01-17 09:50:16 +0000 Tim-Philipp Müller <tim.muller@collabora.co.uk> * tests/check/libs/libsabi.c: tests: disable ABI checks for architectures with outdated structure size files 2013-01-14 10:34:04 +0000 Tim-Philipp Müller <tim.muller@collabora.co.uk> * gst-libs/gst/tag/tag.h: docs: fix 0.10-ism in GstTagImageType docs The image type is not in the info structure in the sample, not in the caps. https://bugzilla.gnome.org/show_bug.cgi?id=691687