Skip to content
Snippets Groups Projects
  1. Mar 22, 2013
  2. Mar 21, 2013
  3. Mar 13, 2013
  4. Feb 18, 2013
    • Stefan Sauer's avatar
      adder: fix setting caps via the "caps" property · 22ebdaa0
      Stefan Sauer authored
      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.
      22ebdaa0
    • Vincent Penquerc'h's avatar
      encodebin: sync muxer state with parent bin · ad34961d
      Vincent Penquerc'h authored
      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.
      ad34961d
  5. Feb 07, 2013
  6. Feb 06, 2013
  7. Feb 04, 2013
  8. Jan 24, 2013
    • yanghuolin's avatar
      alsasink: don't use 100% CPU · db7ff0e2
      yanghuolin authored
      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
      db7ff0e2
  9. Jan 21, 2013
  10. Jan 14, 2013
  11. Jan 08, 2013
  12. Jan 04, 2013
  13. Dec 23, 2012
  14. Dec 18, 2012
  15. Dec 17, 2012
  16. Dec 14, 2012
  17. Dec 10, 2012
Loading