1. 09 Mar, 2017 1 commit
    • wm4's avatar
      avcodec: clarify some decoding/encoding API details · 8a60bba0
      wm4 authored
      Make it clear that there is no timing-dependent behavior. In particular,
      there is no state in which both input and output are denied, and where
      you have to wait for a while yourself to make progress (apparently some
      hardware decoders like to do this).
      
      Avoid wording that makes references to time. It shouldn't be mistaken
      for some kind of asynchronous API (like POSIX read() can return EAGAIN
      if there is no new input yet). It's a state machine, so try to use
      appropriate terms.
      Signed-off-by: 's avatarDiego Biurrun <diego@biurrun.de>
      8a60bba0
  2. 07 Mar, 2017 13 commits
  3. 06 Mar, 2017 1 commit
    • Vittorio Giovara's avatar
      pixlet: Fix architecture-dependent code and values · b44bd7ee
      Vittorio Giovara authored
      The constants used in the decoder used floating point precision,
      and this caused different values to be generated on different
      architectures. Additionally on big endian machines, the fate test
      would output bytes in native order, which is different from the one
      hardcoded in the test.
      
      So, eradicate floating point numbers and use fixed point (32.32)
      arithmetics everywhere, replacing constants with precomputed integer
      values, and force the pixel format output to be the same in the fate
      test.
      Signed-off-by: 's avatarVittorio Giovara <vittorio.giovara@gmail.com>
      b44bd7ee
  4. 05 Mar, 2017 2 commits
  5. 04 Mar, 2017 1 commit
  6. 01 Mar, 2017 13 commits
  7. 28 Feb, 2017 5 commits
  8. 27 Feb, 2017 4 commits