1. 10 May, 2014 1 commit
  2. 02 May, 2014 1 commit
  3. 30 Apr, 2014 1 commit
  4. 04 Feb, 2014 1 commit
  5. 05 Dec, 2013 1 commit
  6. 04 Nov, 2012 1 commit
  7. 27 Aug, 2012 1 commit
  8. 03 Aug, 2012 1 commit
  9. 25 Jul, 2012 1 commit
  10. 09 Apr, 2012 1 commit
  11. 28 Mar, 2012 1 commit
  12. 19 Mar, 2012 1 commit
  13. 15 Mar, 2012 1 commit
  14. 09 Feb, 2012 1 commit
  15. 01 Feb, 2012 1 commit
  16. 25 Jan, 2012 1 commit
  17. 20 Jan, 2012 1 commit
  18. 19 Jan, 2012 1 commit
  19. 06 Jan, 2012 1 commit
  20. 12 Dec, 2011 1 commit
  21. 28 Nov, 2011 1 commit
  22. 22 Nov, 2011 1 commit
  23. 15 Nov, 2011 1 commit
    • Vincent Penquerc'h's avatar
      flacdec: fix spurious timestamp discontinuity · 8548b2c7
      Vincent Penquerc'h authored
      We need to tell the base class that we're dropping buffers,
      so it drops the input timestamps corresponding to these.
      Otherwise, the first actual audio buffers we output will be
      stamped with those - GST_CLOCK_TIMESTAMP_NONE. That mismatch
      between input buffer count and output buffer count will stay
      while playing. With enough headers and long enough buffer
      durations, the sink will have played enough before receiving
      the first valid timestamp (usually 0), and will trigger an
      audible discontinuity.
      8548b2c7
  24. 07 Nov, 2011 1 commit
  25. 30 Oct, 2011 5 commits
  26. 28 Sep, 2011 3 commits
  27. 23 Aug, 2011 1 commit
    • Monty Montgomery's avatar
      flacdec: Correct sample number rounding resulting in timestamp jitter · 799c8e3d
      Monty Montgomery authored
      flacdec converts the src timestamp to a sample number, uses that internally, then reconverts the sample number to a timestamp for the output buffer.  Unfortunately, sample numbers can't be represented in an integer number of nanoseconds, and the conversion process was truncating rather than rounding, resulting in sample numbers and output timestamps that were often off by a full sample.
      
      This corrects the time->sample convesion
      799c8e3d
  28. 17 Aug, 2011 1 commit
    • Vincent Penquerc'h's avatar
      flacdec: avoid timestamp/offset tracking going out of sync · 3e0134f5
      Vincent Penquerc'h authored
      The libFLAC API is callback based, and we must only call it to
      output data when we know we have enough input data. For this
      reason, a single processing step is done when receiving a buffer.
      However, if there were metadata buffers still pending, a step
      intended for the first audio frame might end up writing that
      leftover metadata. Since a single step is done per buffer, this
      will cause every buffer to be written one step late.
      
      This would add some latency (a bufferfull's worth), possibly
      lose a buffer when seeking or the like, and also cause timestamp
      and offset to be applied to the wrong buffer, as updates to
      the "current" segment last_stop (from incoming buffer timestamp)
      will be applied to an output buffer originating from the previous
      incoming buffer.
      
      This fixes the issue by ensuring that, upon receiving the first
      audio frame, processing is done till all metadata is processed,
      so the next "single step" done will be for the audio frame. After
      this, we should keep to 1 input buffer -> 1 output buffer and so
      avoid getting out of sync.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=650960
      3e0134f5
  29. 16 Aug, 2011 3 commits
  30. 23 May, 2011 1 commit
  31. 14 May, 2011 1 commit
  32. 19 Apr, 2011 1 commit