1. 03 Oct, 2013 1 commit
  2. 02 Aug, 2013 1 commit
  3. 29 May, 2013 1 commit
    • Reimar Döffinger's avatar
      wamenc: handle failure to encode. · dccaad3b
      Reimar Döffinger authored
      This is necessary since the switch to floating point
      input means there is no longer sufficient input data
      validation.
      There is a good chance that other encoders are affected
      by similar issues.
      This problem can be triggered by trying to encode
      extremely large values and probably also with Inf and
      possibly also NaNs.
      Signed-off-by: 's avatarReimar Döffinger <Reimar.Doeffinger@gmx.de>
      dccaad3b
  4. 04 May, 2013 1 commit
  5. 09 Mar, 2013 1 commit
  6. 06 Mar, 2013 1 commit
  7. 12 Feb, 2013 1 commit
  8. 22 Jan, 2013 1 commit
  9. 05 Dec, 2012 1 commit
  10. 26 Nov, 2012 1 commit
  11. 01 Nov, 2012 1 commit
  12. 06 Oct, 2012 1 commit
  13. 01 Oct, 2012 1 commit
  14. 07 Aug, 2012 1 commit
  15. 02 Jul, 2012 1 commit
  16. 01 Jul, 2012 1 commit
  17. 30 Jun, 2012 4 commits
  18. 17 Jun, 2012 1 commit
  19. 06 Apr, 2012 1 commit
  20. 23 Mar, 2012 1 commit
  21. 22 Mar, 2012 1 commit
  22. 21 Mar, 2012 1 commit
  23. 17 Mar, 2012 1 commit
    • Justin Ruggles's avatar
      wmaenc: remove bit-exact hack · c3da9f50
      Justin Ruggles authored
      It may have improved cross-platform stability, but wasn't the only place in
      the encoder with bitexact issues. It is no longer needed because we have FATE
      tests for float encoders using fuzzy comparison.
      c3da9f50
  24. 05 Mar, 2012 3 commits
  25. 03 Mar, 2012 6 commits
  26. 20 Oct, 2011 1 commit
  27. 24 Sep, 2011 1 commit
  28. 12 May, 2011 1 commit
  29. 24 Mar, 2011 1 commit
  30. 19 Mar, 2011 1 commit