1. 09 Jun, 2014 1 commit
  2. 05 Jun, 2014 1 commit
  3. 03 Jun, 2014 4 commits
  4. 02 Jun, 2014 1 commit
  5. 01 Jun, 2014 1 commit
  6. 29 May, 2014 2 commits
  7. 28 May, 2014 2 commits
  8. 25 May, 2014 1 commit
  9. 19 May, 2014 2 commits
  10. 11 May, 2014 1 commit
  11. 03 May, 2014 1 commit
  12. 24 Apr, 2014 1 commit
  13. 22 Apr, 2014 2 commits
  14. 17 Apr, 2014 1 commit
  15. 07 Apr, 2014 1 commit
  16. 06 Apr, 2014 3 commits
  17. 04 Apr, 2014 1 commit
    • Alessandro Ghedini's avatar
      replaygain: correctly parse peak values · 8542f9c4
      Alessandro Ghedini authored
      According to the ReplayGain spec, the peak amplitude may overflow and may result
      in peak amplitude values greater than 1.0 with psychoacoustically coded audio,
      such as MP3. Fully compliant decoders must allow peak overflows.
      
      Additionally, having peak values in the 0<->UINT32_MAX scale makes it more
      difficult for applications to actually use the peak values (e.g. when
      implementing clipping prevention) since values have to be rescaled down.
      
      This patch corrects the peak parsing by removing the rescaling of the decoded
      values between 0 and UINT32_MAX and the 1.0 upper limit.
      Signed-off-by: 's avatarAnton Khirnov <anton@khirnov.net>
      8542f9c4
  18. 03 Apr, 2014 5 commits
  19. 01 Apr, 2014 1 commit
  20. 24 Mar, 2014 2 commits
  21. 22 Mar, 2014 1 commit
  22. 20 Mar, 2014 1 commit
  23. 19 Mar, 2014 1 commit
  24. 18 Mar, 2014 2 commits
  25. 16 Mar, 2014 1 commit