1. 02 Sep, 2015 1 commit
  2. 12 Jul, 2015 1 commit
  3. 19 Apr, 2015 1 commit
  4. 18 Jan, 2015 2 commits
  5. 15 Oct, 2014 2 commits
  6. 25 Aug, 2014 1 commit
  7. 31 Oct, 2013 1 commit
  8. 03 May, 2013 1 commit
  9. 27 Mar, 2013 1 commit
  10. 26 Mar, 2013 1 commit
  11. 05 Dec, 2012 1 commit
  12. 02 Nov, 2012 1 commit
    • Heesuk Jung's avatar
      Fix bit_rate in MPEG1/2 Video · 25b7aa98
      Heesuk Jung authored
      In ISO/IEC 13818-2, bit rate is differently determined according to video type
      
      1) MPEG1 Video
       Bit_rate and vbv_delay are set to 3FFFF and FFFF respectively
       to indicate variable bitrate. Other values are for constant bitrate.
       VBV is only defined for constant bit rate operation.
       Ths STD supersedes the VBV model for vbr.
      
      2) MPEG2 Video
       Even if the bitrate is constant, the value of bit_rate may not be the actual bitrate
       since bit_rate need only be an upper bound to that actual bitrate.
       VBV is only defined for variable bit rate operation.
       Constant bit rate is viewed as a special case of vbr.
      Signed-off-by: 's avatarMichael Niedermayer <michaelni@gmx.at>
      25b7aa98
  13. 30 Oct, 2012 2 commits
  14. 18 Oct, 2012 1 commit
  15. 07 Aug, 2012 1 commit
  16. 16 Mar, 2012 1 commit
  17. 04 Mar, 2012 1 commit
    • Anton Khirnov's avatar
      lavc: deprecate AVCodecContext.sub_id. · 02beb982
      Anton Khirnov authored
      In most places where it's used, it's as a pointless write-only field.
      
      Only rv10 decoder actually reads from it, but it stores some internal
      version info in it. There is no reason for it to be in a public field.
      02beb982
  18. 10 Feb, 2012 1 commit
  19. 02 Nov, 2011 1 commit
  20. 20 Oct, 2011 2 commits
  21. 18 Oct, 2011 1 commit
  22. 31 Aug, 2011 1 commit
  23. 02 Jun, 2011 1 commit
  24. 29 Apr, 2011 1 commit
  25. 19 Mar, 2011 1 commit
  26. 28 Jan, 2011 1 commit
  27. 26 Jan, 2011 1 commit
  28. 03 Feb, 2010 1 commit
    • Michael Niedermayer's avatar
      Revert · 299fd396
      Michael Niedermayer authored
      	r12684 | michael | 2008-04-04 02:43:34 +0200 (Fri, 04 Apr 2008) | 2 lines
      	Disable the split function. This should end the mpeg1/2 global header issues.
      The split function is essential for -ss to work
      Fixes issue1226
      If this breaks something please tell me, also if someoen remembers what problem
      this originally caused tell me too, i searched but couldnt find it.
      
      Originally committed as revision 21621 to svn://svn.ffmpeg.org/ffmpeg/trunk
      299fd396
  29. 14 Dec, 2009 1 commit
  30. 05 Dec, 2009 2 commits
  31. 02 Mar, 2009 1 commit
    • Michael Niedermayer's avatar
      Call ff_fetch_timestamp() for mpeg1/2 when a picture start code is found instead · a4c7a5ea
      Michael Niedermayer authored
      of calling it at the end of a frame with a large negative offset.
      This significantly reduces the maximal distance in container packets between
      the point where the first byte of the "access unit" was stored and where
      we call ff_fetch_timestamp() thus reducing the constraints on our parser.
      Also change the parser from next_frame_offset to cur, this is needed
      because now the reference is from container packet start instead of
      frame start. (i previously misinterpreted this as bug)
      
      Originally committed as revision 17731 to svn://svn.ffmpeg.org/ffmpeg/trunk
      a4c7a5ea
  32. 24 Feb, 2009 1 commit
  33. 19 Jan, 2009 1 commit
  34. 03 Jun, 2008 1 commit
    • Michael Niedermayer's avatar
      In mpeg1/2 timestamps are associated with the access unit which · d59591fb
      Michael Niedermayer authored
      contains the first picture startcode that commences in the PES
      packet, instead of the first access unit that commences in the
      PES packet. Fix the parser to
      handle that properly. This was a very long standing bug ...
      The change to the seek regressions is because the mpeg ts muxer
      stores too many invalid and randomized timestamps which overflow
      the 4 entry buffer we use in the parser.
      
      Originally committed as revision 13643 to svn://svn.ffmpeg.org/ffmpeg/trunk
      d59591fb
  35. 04 Apr, 2008 1 commit