1. 29 Jan, 2016 1 commit
  2. 21 Jan, 2016 2 commits
  3. 21 Oct, 2015 1 commit
  4. 09 Sep, 2015 1 commit
  5. 08 Sep, 2015 1 commit
  6. 27 Jul, 2015 3 commits
  7. 20 Jul, 2015 2 commits
    • Vittorio Giovara's avatar
      Deprecate avctx.coded_frame · 40cf1bba
      Vittorio Giovara authored
      The rationale is that coded_frame was only used to communicate key_frame,
      pict_type and quality to the caller, as well as a few other random fields,
      in a non predictable, let alone consistent way.
      
      There was agreement that there was no use case for coded_frame, as it is
      a full-sized AVFrame container used for just 2-3 int-sized properties,
      which shouldn't even belong into the AVCodecContext in the first place.
      
      The appropriate AVPacket flag can be used instead of key_frame, while
      quality is exported with the new AVPacketSideData quality factor.
      There is no replacement for the other fields as they were unreliable,
      mishandled or just not used at all.
      Signed-off-by: 's avatarVittorio Giovara <vittorio.giovara@gmail.com>
      40cf1bba
    • Vittorio Giovara's avatar
      Gather all coded_frame allocations and free functions to a single place · d6604b29
      Vittorio Giovara authored
      Allocating coded_frame is what most encoders do anyway, so it makes
      sense to always allocate and free it in a single place. Moreover a lot
      of encoders freed the frame with av_freep() instead of the correct API
      av_frame_free().
      
      This bring uniformity to encoder behaviour and prevents applications
      from erroneusly accessing this field when not allocated. Additionally
      this helps isolating encoders that export information with coded_frame,
      and heavily simplifies its deprecation.
      Signed-off-by: 's avatarVittorio Giovara <vittorio.giovara@gmail.com>
      d6604b29
  8. 31 May, 2015 1 commit
  9. 24 Apr, 2015 1 commit
  10. 25 Aug, 2014 1 commit
  11. 19 Aug, 2014 1 commit
  12. 23 Jun, 2014 1 commit
  13. 19 Jun, 2014 1 commit
    • Christophe Gisquet's avatar
      huffyuv: change statistics initialization · e7fc5d53
      Christophe Gisquet authored
      Normally, a Laplace distribution is more typical of the residuals
      encoded, but for noisy input, it's both better and simpler to be
      safe and use a 1/d^2 distribution. Second hunk could use some
      renormalization but it has effectively little impact.
      
      Output size of ffvhuff on various 4:2:0 sequences:
      context=0,1/d:    851974   27226   1137281
      context=0,1/d²:   619081   25069   1051500
      context=0,1/d³:   501983   30454   1290561
      context=0,lapl:   500650   31754   1304082
      Signed-off-by: 's avatarMichael Niedermayer <michaelni@gmx.at>
      e7fc5d53
  14. 09 Jun, 2014 1 commit
  15. 29 May, 2014 1 commit
  16. 27 May, 2014 1 commit
  17. 07 May, 2014 1 commit
  18. 28 Feb, 2014 1 commit
  19. 15 Feb, 2014 1 commit
  20. 28 Jan, 2014 1 commit
  21. 27 Jan, 2014 3 commits
  22. 26 Jan, 2014 2 commits
  23. 25 Jan, 2014 1 commit
  24. 20 Jan, 2014 4 commits
  25. 16 Jan, 2014 6 commits