1. 27 Mar, 2017 1 commit
    • wm4's avatar
      avformat, ffmpeg: deprecate old rotation API · ddef3d90
      wm4 authored
      The old "API" that signaled rotation as a metadata value has been
      replaced by DISPLAYMATRIX side data quite a while ago.
      
      There is no reason to make muxers/demuxers/API users support both. In
      addition, the metadata API is dangerous, as user tags could "leak" into
      it, creating unintended features or bugs.
      
      ffmpeg CLI has to be updated to use the new API. In particular, we must
      not allow to leak the "rotate" tag into the muxer. Some muxers will
      catch this properly (like mov), but others (like mkv) can add it as
      generic tag. Note applications, which use libavformat and assume the
      old rotate API, will interpret such "rotate" user tags as rotate
      metadata (which it is not), and incorrectly rotate the video.
      
      The ffmpeg/ffplay tools drop the use of the old API for muxing and
      demuxing, as all muxers/demuxers support the new API. This will mean
      that the tools will not mistakenly interpret per-track "rotate" user
      tags as rotate metadata. It will _not_ be treated as regression.
      
      Unfortunately, hacks have been added, that allow the user to override
      rotation by setting metadata explicitly, e.g. via
      
        -metadata:s:v:0 rotate=0
      
      See references to trac #4560. fate-filter-meta-4560-rotate0 tests this.
      It's easier to adjust the hack for supporting it than arguing for its
      removal, so ffmpeg CLI now explicitly catches this case, and essentially
      replaces the "rotate" value with a display matrix side data. (It would
      be easier for both user and implementation to create an explicit option
      for rotation.)
      
      When the code under FF_API_OLD_ROTATE_API is disabled, one FATE
      reference file has to be updated (because "rotate" is not exported
      anymore).
      Tested-by: 's avatarMichael Niedermayer <michael@niedermayer.cc>
      Reviewed-by: 's avatarMichael Niedermayer <michael@niedermayer.cc>
      ddef3d90
  2. 01 Jan, 2017 1 commit
  3. 16 Nov, 2016 1 commit
  4. 08 Nov, 2016 1 commit
  5. 09 Oct, 2016 1 commit
  6. 24 Sep, 2016 1 commit
    • Clément Bœsch's avatar
      ffmpeg: switch to the new BSF API · 5ef19590
      Clément Bœsch authored
      This commit is initially largely based on commit 4426540f from Anton
      Khirnov <anton@khirnov.net> and two following fixes (80fb19bc and
      fe7b21c8) which were previously skipped respectively in 98e3153f, c9ee36e6,
      and 7fe7cdca.
      
      mpeg4-bsf-unpack-bframes FATE reference is updated because the bsf
      filter now actually fixes the extradata (mpeg4_unpack_bframes_init()
      changing one byte is now honored on the output extradata).
      
      The FATE references for remove_extra change because the packet flags
      were wrong and the keyframes weren't marked, causing the bsf relying on
      these proprieties to not actually work as intended.
      
      The following was fixed by James Almer:
      
      The filter option arguments are now also parsed correctly.
      
      A hack to propagate extradata changed by bitstream filters after the
      first av_bsf_receive_packet() call is added to maintain the current
      behavior. This was previously done by av_bitstream_filter_filter() and
      is needed for the aac_adtstoasc bsf.
      
      The exit_on_error was not being checked anymore, and led to an exit
      error in the last frame of h264_mp4toannexb test. Restoring this
      behaviour prevents erroring out. The test is still changed as a result
      due to the badly filtered frame now not being written after the failure.
      Signed-off-by: 's avatarClément Bœsch <u@pkh.me>
      Signed-off-by: 's avatarJames Almer <jamrial@gmail.com>
      5ef19590
  7. 21 Sep, 2016 1 commit
    • Clément Bœsch's avatar
      ffmpeg: switch to codecpar · 955b818c
      Clément Bœsch authored
      This commit is largely based on commit 15e84ed3 from Anton Khirnov
      <anton@khirnov.net> which was previously skipped in bbf5ef9d.
      
      There are still a bunch of things raising codecpar related warnings that
      need fixing, such as:
      - the use of codec->debug in the interactive debug mode
      - read_ffserver_streams(): it's probably broken now but there is no test
      - lowres stuff
      - codec copy apparently required by bitstream filters
      
      The matroska references are updated because they now properly forward
      the field_order (previously unknown, now progressive).
      
      Thanks to James Almer for fixing a bunch of FATE issues in this commit.
      Signed-off-by: 's avatarClément Bœsch <clement@stupeflix.com>
      Signed-off-by: 's avatarJames Almer <jamrial@gmail.com>
      955b818c
  8. 29 Aug, 2016 1 commit
  9. 08 Aug, 2016 1 commit
  10. 20 Mar, 2016 1 commit
  11. 15 Mar, 2016 1 commit
  12. 23 Feb, 2016 1 commit
    • Anton Khirnov's avatar
      avconv: convert to codecpar · 15e84ed3
      Anton Khirnov authored
      The switch is not yet complete because the parsers and the bistream
      filters do not have a new AVCodecParam-based API yet.
      15e84ed3
  13. 06 Feb, 2016 1 commit
  14. 07 Dec, 2015 2 commits
  15. 03 Nov, 2015 1 commit
  16. 25 Oct, 2015 1 commit
  17. 15 Oct, 2015 2 commits
  18. 03 Oct, 2015 1 commit
  19. 19 Sep, 2015 1 commit
  20. 11 Aug, 2015 1 commit
  21. 08 Aug, 2015 4 commits
  22. 27 Jul, 2015 1 commit
  23. 19 Jul, 2015 1 commit
  24. 02 Jul, 2015 1 commit
  25. 18 May, 2015 1 commit
  26. 09 May, 2015 1 commit
  27. 05 May, 2015 2 commits
  28. 04 May, 2015 1 commit
  29. 03 May, 2015 1 commit
  30. 19 Apr, 2015 2 commits
  31. 03 Apr, 2015 1 commit
  32. 20 Mar, 2015 1 commit
  33. 11 Feb, 2015 1 commit