1. 10 May, 2015 1 commit
  2. 24 Feb, 2015 1 commit
  3. 06 Feb, 2015 1 commit
  4. 27 Jan, 2015 1 commit
    • Anton Khirnov's avatar
      nutenc: do not use has_b_frames · 80a11de7
      Anton Khirnov authored
      It is unreliable, especially when the stream codec context is not the
      encoding context. Use the codec descriptor properties instead.
      80a11de7
  5. 14 Dec, 2014 1 commit
  6. 21 Oct, 2014 1 commit
  7. 18 Jun, 2014 1 commit
  8. 10 Jun, 2014 3 commits
  9. 30 May, 2014 1 commit
  10. 29 May, 2014 4 commits
  11. 28 May, 2014 4 commits
  12. 18 May, 2014 1 commit
  13. 24 Jan, 2014 1 commit
  14. 04 Jan, 2014 1 commit
  15. 25 Dec, 2013 2 commits
  16. 22 Dec, 2013 1 commit
  17. 23 Nov, 2013 1 commit
  18. 22 Oct, 2013 2 commits
  19. 14 Sep, 2013 2 commits
  20. 27 Jul, 2013 1 commit
  21. 06 May, 2013 1 commit
  22. 18 Feb, 2013 1 commit
  23. 28 Nov, 2012 1 commit
  24. 29 Oct, 2012 1 commit
  25. 28 Oct, 2012 1 commit
  26. 16 Oct, 2012 1 commit
  27. 13 Oct, 2012 1 commit
  28. 03 Oct, 2012 1 commit
  29. 01 Oct, 2012 1 commit
    • Michael Niedermayer's avatar
      nutenc: choose for non audio streams a timebase with finer resolution. · 4abc411b
      Michael Niedermayer authored
      While a 25 fps stream can in general store frame durations in 1/25
      units, this is not true for the timestamps. For example a 25fps
      and a 25000/1001 fps stream when they are stored together might have
      a matching 0 timestamp point but when for example a chapter from
      this is cut the new start is no longer aligned. The issue gets
      MUCH worse when the streams are lower fps, like 1 or 2 fps.
      
      This commit thus makes the muxer choose a multiple of the
      framerate as timebase that is at least about 20 micro seconds precise
      Signed-off-by: 's avatarMichael Niedermayer <michaelni@gmx.at>
      4abc411b