1. 10 Mar, 2020 1 commit
  2. 16 Jan, 2020 1 commit
  3. 18 Sep, 2019 1 commit
  4. 12 May, 2019 1 commit
  5. 01 Mar, 2019 1 commit
  6. 01 Jan, 2019 1 commit
  7. 12 Oct, 2018 1 commit
  8. 21 Sep, 2018 1 commit
  9. 02 Apr, 2018 1 commit
  10. 27 Mar, 2018 1 commit
  11. 22 Mar, 2018 1 commit
  12. 14 Feb, 2018 1 commit
  13. 01 Feb, 2018 1 commit
  14. 22 Oct, 2017 1 commit
  15. 28 Sep, 2017 1 commit
  16. 26 Sep, 2017 1 commit
  17. 11 Jun, 2017 1 commit
  18. 12 May, 2017 2 commits
  19. 06 May, 2017 1 commit
  20. 06 Apr, 2017 1 commit
  21. 21 Mar, 2017 1 commit
    • wm4's avatar
      avcodec, avformat: deprecate anything related to side data merging · d682ae70
      wm4 authored
      This patch deprecates anything that has to do with merging/splitting
      side data. Automatic side data merging (and splitting), as well as all
      API symbols involved in it, are removed completely.
      
      Two FF_API_ defines are dedicated to deprecating API symbols related to
      this: FF_API_MERGE_SD_API removes av_packet_split/merge_side_data in
      libavcodec, and FF_API_LAVF_KEEPSIDE_FLAG deprecates
      AVFMT_FLAG_KEEP_SIDE_DATA in libavformat.
      
      Since it was claimed that changing the default from merging side data to
      not doing it is an ABI change, there are two additional FF_API_ defines,
      which stop using the side data merging/splitting by default (and remove
      any code in avformat/avcodec doing this): FF_API_MERGE_SD in libavcodec,
      and FF_API_LAVF_MERGE_SD in libavformat.
      
      It is very much intended that FF_API_MERGE_SD and FF_API_LAVF_MERGE_SD
      are quickly defined to 0 in the next ABI bump, while the API symbols are
      retained for a longer time for the sake of compatibility.
      AVFMT_FLAG_KEEP_SIDE_DATA will (very much intentionally) do nothing for
      most of the time it will still be defined. Keep in mind that no code
      exists that actually tries to unset this flag for any reason, nor does
      such code need to exist. Code setting this flag explicitly will work as
      before. Thus it's ok for AVFMT_FLAG_KEEP_SIDE_DATA to do nothing once
      side data merging has been removed from libavformat.
      
      In order to avoid that anyone in the future does this incorrectly, here
      is a small guide how to update the internal code on bumps:
      
      - next ABI bump (probably soon):
        - define FF_API_LAVF_MERGE_SD to 0, and remove all code covered by it
        - define FF_API_MERGE_SD to 0, and remove all code covered by it
      - next API bump (typically two years in the future or so):
        - define FF_API_LAVF_KEEPSIDE_FLAG to 0, and remove all code covered
          by it
        - define FF_API_MERGE_SD_API to 0, and remove all code covered by it
      
      This forces anyone who actually wants packet side data to temporarily
      use deprecated API to get it all. If you ask me, this is batshit fucked
      up crazy, but it's how we roll. Making AVFMT_FLAG_KEEP_SIDE_DATA to be
      set by default was rejected as an ABI change, so I'm going all the way
      to get rid of this once and for all.
      Reviewed-by: 's avatarJames Almer <jamrial@gmail.com>
      Reviewed-by: 's avatarRostislav Pehlivanov <atomnuker@gmail.com>
      Reviewed-by: 's avatarMichael Niedermayer <michael@niedermayer.cc>
      d682ae70
  22. 16 Mar, 2017 1 commit
  23. 01 Mar, 2017 1 commit
  24. 17 Feb, 2017 1 commit
  25. 07 Dec, 2016 1 commit
  26. 23 Nov, 2016 1 commit
  27. 19 Nov, 2016 1 commit
  28. 17 Nov, 2016 1 commit
  29. 22 Sep, 2016 1 commit
  30. 12 Sep, 2016 1 commit
  31. 05 Sep, 2016 1 commit
  32. 13 Jun, 2016 1 commit
  33. 01 Jun, 2016 1 commit
  34. 16 May, 2016 1 commit
  35. 13 May, 2016 1 commit
  36. 20 Apr, 2016 1 commit
  37. 26 Feb, 2016 1 commit
  38. 24 Feb, 2016 1 commit
  39. 23 Feb, 2016 1 commit
    • Stefano Sabatini's avatar
      lavc/lavf: transmit stream_id information for mpegts KLV data packets · 14f7a3d5
      Stefano Sabatini authored
      This allows to copy information related to the stream ID from the demuxer
      to the muxer, thus allowing for example to retain information related to
      synchronous and asynchronous KLV data packets. This information is used
      in the muxer when remuxing to distinguish the two kind of packets (if the
      information is lacking, data packets are considered synchronous).
      
      The fate reference changes are due to the use of
      av_packet_merge_side_data(), which increases the size of the output
      packet size, since side data is merged into the packet data.
      14f7a3d5