1. 18 May, 2014 1 commit
  2. 15 May, 2014 1 commit
    • Anton Khirnov's avatar
      lavf: add AVFMT_FLAG_BITEXACT. · 0c1959b0
      Anton Khirnov authored
      Use it instead of checking CODEC_FLAG_BITEXACT in the first stream's
      codec context.
      
      Using codec options inside lavf is fragile and can easily break when the
      muxing codec context is not the encoding context.
      0c1959b0
  3. 25 Apr, 2014 2 commits
  4. 01 Apr, 2014 1 commit
  5. 31 Mar, 2014 1 commit
  6. 28 Mar, 2014 1 commit
  7. 22 Mar, 2014 1 commit
  8. 09 Mar, 2014 3 commits
  9. 08 Mar, 2014 1 commit
  10. 19 Feb, 2014 1 commit
  11. 23 Nov, 2013 1 commit
  12. 23 Oct, 2013 1 commit
  13. 22 Sep, 2013 4 commits
  14. 19 Sep, 2013 1 commit
  15. 17 Sep, 2013 2 commits
  16. 09 Sep, 2013 2 commits
  17. 03 Sep, 2013 1 commit
  18. 27 Aug, 2013 4 commits
  19. 25 Aug, 2013 1 commit
  20. 23 Aug, 2013 1 commit
  21. 21 Aug, 2013 3 commits
  22. 20 Aug, 2013 2 commits
  23. 19 Aug, 2013 3 commits
  24. 17 Aug, 2013 1 commit
    • Martin Storsjö's avatar
      movenc: Indicate that negative timestamps are supported · 0a14fefd
      Martin Storsjö authored
      
      
      The mov/mp4 muxer has support for handling negative timestamps
      via edit lists (which customarily is used for handling the 1-frame
      delay due to B-frames as well).
      
      Using the muxer's native way of handling it is better than using
      the generic offsetting. The generic offsetting is a bit too
      crude when e.g. the timebase of one track is 1/fps, where the
      edit lists can handle it accurately.
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>
      0a14fefd