1. 10 Nov, 2017 1 commit
  2. 29 Oct, 2017 1 commit
  3. 23 Oct, 2017 1 commit
  4. 08 Aug, 2017 1 commit
  5. 26 Jul, 2017 2 commits
  6. 06 Apr, 2017 1 commit
  7. 03 Mar, 2017 1 commit
  8. 25 Feb, 2017 2 commits
  9. 13 Feb, 2017 1 commit
    • wm4's avatar
      AVFrame: add an opaque_ref field · e3af49b1
      wm4 authored
      This is an extended version of the AVFrame.opaque field, which can be
      used to attach arbitrary user information to an AVFrame.
      
      The usefulness of the opaque field is rather limited, because it can
      store only up to 32 bits of information (or 64 bit on 64 bit systems).
      It's not possible to set this field to a memory allocation, because
      there is no way to deallocate it correctly.
      
      The opaque_ref field circumvents this by letting the user set an
      AVBuffer, which makes the user data refcounted.
      Signed-off-by: 's avatarAnton Khirnov <anton@khirnov.net>
      
      Merges Libav commit 04f3bd34.
      e3af49b1
  10. 11 Feb, 2017 2 commits
    • wm4's avatar
      AVFrame: add an opaque_ref field · 04f3bd34
      wm4 authored
      This is an extended version of the AVFrame.opaque field, which can be
      used to attach arbitrary user information to an AVFrame.
      
      The usefulness of the opaque field is rather limited, because it can
      store only up to 32 bits of information (or 64 bit on 64 bit systems).
      It's not possible to set this field to a memory allocation, because
      there is no way to deallocate it correctly.
      
      The opaque_ref field circumvents this by letting the user set an
      AVBuffer, which makes the user data refcounted.
      Signed-off-by: 's avatarAnton Khirnov <anton@khirnov.net>
      04f3bd34
    • Anton Khirnov's avatar
      frame: allow align=0 (meaning automatic) for av_frame_get_buffer() · 4de220d2
      Anton Khirnov authored
      This will avoid every caller from hardcoding some specific alignment,
      which may break in the future with new instruction sets.
      4de220d2
  11. 30 Jan, 2017 1 commit
  12. 12 Jan, 2017 1 commit
  13. 16 Nov, 2016 2 commits
  14. 19 Sep, 2016 1 commit
  15. 25 Jul, 2016 1 commit
  16. 21 Jun, 2016 1 commit
    • Anton Khirnov's avatar
      lavc: export the timestamps when decoding in AVFrame.pts · 32c83590
      Anton Khirnov authored
      Currently it's exported as AVFrame.pkt_pts, which is also the only use
      for that field. The reason it is done like this is that lavc used to
      export various codec-specific "timing" information in AVFrame.pts, which
      is not done anymore.
      
      Since it is confusing to the callers to have a separate field which is
      used only for decoder timestamps and nothing else, deprecate pkt_pts and
      use just AVFrame.pts everywhere.
      32c83590
  17. 05 Jun, 2016 1 commit
  18. 18 Feb, 2016 1 commit
  19. 14 Feb, 2016 1 commit
  20. 13 Feb, 2016 1 commit
  21. 01 Feb, 2016 1 commit
  22. 27 Jan, 2016 1 commit
  23. 22 Jan, 2016 1 commit
  24. 11 Jan, 2016 1 commit
  25. 08 Dec, 2015 1 commit
  26. 30 Sep, 2015 1 commit
  27. 05 Sep, 2015 1 commit
  28. 22 Aug, 2015 1 commit
  29. 13 Jul, 2015 1 commit
  30. 25 Mar, 2015 2 commits
  31. 18 Dec, 2014 1 commit
    • Luca Barbato's avatar
      lavu: Refactor side data wiping · 5d839778
      Luca Barbato authored
      And make sure the nb_side_data field is reset as well.
      
      Based on an initial patch from wm4 <nfxjfg@googlemail.com>.
      
      CC: libav-stable@libav.org
      5d839778
  32. 15 Dec, 2014 1 commit
  33. 29 Aug, 2014 1 commit
  34. 18 Aug, 2014 1 commit
    • Clément Bœsch's avatar
      avcodec: export motion vectors in frame side data on demand · b0352b19
      Clément Bœsch authored
      The reasoning behind this addition is that various third party
      applications are interested in getting some motion information out of a
      video "for free" when it is available.
      
      It was considered to export other information as well (such as the intra
      information about the block, or the quantization) but the structure
      might have ended up into a half full-generic, half full of codec
      specific cruft. If more information is necessary, it should either be
      added in the "flags" field of the AVMotionVector structure, or in
      another side-data.
      
      This commit also includes an example exporting them in a CSV stream.
      b0352b19
  35. 14 Aug, 2014 1 commit