1. 22 Dec, 2014 5 commits
    • Sebastian Dröge's avatar
      MAINTAINERS: Update my mail address · 77c80f68
      Sebastian Dröge authored
      77c80f68
    • Sebastian Dröge's avatar
      video{en,de}coder: Call reset() before the start() vfunc · 87d6c265
      Sebastian Dröge authored
      This makes sure that the element is in the same state before start() is called
      the very first time and every future call after the element was used already.
      
      Also it ensure that we always have a clean state before start(), cleaned the
      same way in every case.
      87d6c265
    • Sebastian Dröge's avatar
      audioencoder: Call reset() before the start() vfunc to guarantee a clean state · aae64009
      Sebastian Dröge authored
      The same was done already in the decoder, and we cleaned some state just above
      manually that would also be taken care of by reset().
      
      This makes sure that the element is in the same state before start() is called
      the very first time and every future call after the element was used already.
      aae64009
    • Sebastian Dröge's avatar
      video{en,de}coder: Reset the codec after calling the stop() vfunc · 098b42f3
      Sebastian Dröge authored
      The stop() vfunc might mess with some of our fields we have just
      reset, which could cause memory leaks or invalid state taken over
      to later.
      
      Also the stop() vfunc, or anything called until it from another thread,
      might want to be able to use the fields that were just resetted and
      become confused because of that.
      
      In the decoder we already had a workaround for things like this happening,
      this workaround is not needed anymore.
      098b42f3
    • Sebastian Dröge's avatar
      audiobase{sink,src}: Don't hold the object lock while calling create_ringbuffer() vfunc · ceb9de6e
      Sebastian Dröge authored
      The implementation of that vfunc might want to use the object lock for
      something too. It's generally not a good idea to keep the object lock while
      calling any function implemented elsewhere.
      
      Also the ringbuffer can only be NULL at this point, remove a useless if block.
      
      And in the sink actually hold the object lock while setting the ringbuffer on
      the instance. Code accessing this is expected to use the object lock, so do it
      here ourselves too.
      ceb9de6e
  2. 18 Dec, 2014 4 commits
  3. 17 Dec, 2014 11 commits
  4. 16 Dec, 2014 2 commits
  5. 15 Dec, 2014 5 commits
  6. 14 Dec, 2014 2 commits
  7. 13 Dec, 2014 3 commits
  8. 12 Dec, 2014 7 commits
  9. 11 Dec, 2014 1 commit