1. 06 Nov, 2017 1 commit
  2. 27 Jun, 2017 2 commits
  3. 26 Jun, 2017 1 commit
  4. 31 Jan, 2017 2 commits
  5. 09 Dec, 2016 2 commits
  6. 20 Nov, 2016 1 commit
  7. 17 Nov, 2016 1 commit
  8. 25 Oct, 2016 1 commit
  9. 17 Aug, 2016 1 commit
  10. 16 Aug, 2016 3 commits
  11. 07 Aug, 2016 2 commits
  12. 06 Aug, 2016 1 commit
  13. 29 Jun, 2016 1 commit
  14. 17 Jun, 2016 1 commit
  15. 04 May, 2016 1 commit
  16. 27 Jan, 2016 1 commit
  17. 21 Jan, 2016 1 commit
  18. 11 Jan, 2016 1 commit
  19. 01 Jan, 2016 1 commit
  20. 19 Dec, 2015 1 commit
  21. 18 Dec, 2015 1 commit
  22. 07 Dec, 2015 1 commit
  23. 04 Dec, 2015 1 commit
  24. 16 Nov, 2015 1 commit
    • Vittorio Giovara's avatar
      ffv1: Explicitly name the coder type · 4bb1070c
      Vittorio Giovara authored
      FFv1 uses two types of coders, golomb and range with two different
      tables. This is exposed this in a rather convoluted way, for example
      mentioning to set coder type 1 while initializing the variable 'ac' to 2,
      because encoder does not use range coder with default table.
      
      Appropriate internal coder type values have been added and used in any
      check rather than using raw numbers.
      
      Initialization of avctx.coder_type in ffv1dec is removed because this
      field is encoder only. An unneeded validation check in the encoder
      is dropped too.
      Signed-off-by: 's avatarVittorio Giovara <vittorio.giovara@gmail.com>
      4bb1070c
  25. 24 Sep, 2015 1 commit
  26. 15 Sep, 2015 1 commit
  27. 08 Sep, 2015 1 commit
  28. 22 Aug, 2015 1 commit
  29. 27 Jul, 2015 4 commits
  30. 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