1. 05 Mar, 2016 1 commit
    • Anton Khirnov's avatar
      asfenc: fix some possible integer overflows · ff3db937
      Anton Khirnov authored
      Store the file duration in the same timebase it arrives (i.e.
      milliseconds) and only convert it to the file duration units (100ns)
      when it's actually written, thus simplifying some calculations. Also,
      store the duration as unsigned, since it cannot be negative.
      
      CC: libav-stable@libav.org
      Bug-ID: CVE-2016-2326
      ff3db937
  2. 04 Mar, 2016 1 commit
  3. 01 Mar, 2016 6 commits
  4. 26 Feb, 2016 14 commits
  5. 25 Feb, 2016 4 commits
  6. 24 Feb, 2016 10 commits
  7. 23 Feb, 2016 4 commits
    • 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
    • Anton Khirnov's avatar
      avconv: switch opening decoders and encoders · 5b9cdf8c
      Anton Khirnov authored
      Open decoders first, next encoders. This makes sure that that
      subtitle_header is always set properly, without relying on
      avformat_find_stream_info() setting it.
      5b9cdf8c
    • Anton Khirnov's avatar
      lavf: replace AVStream.codec with AVStream.codecpar · 9200514a
      Anton Khirnov authored
      Currently, AVStream contains an embedded AVCodecContext instance, which
      is used by demuxers to export stream parameters to the caller and by
      muxers to receive stream parameters from the caller. It is also used
      internally as the codec context that is passed to parsers.
      
      In addition, it is also widely used by the callers as the decoding (when
      demuxer) or encoding (when muxing) context, though this has been
      officially discouraged since Libav 11.
      
      There are multiple important problems with this approach:
          - the fields in AVCodecContext are in general one of
              * stream parameters
              * codec options
              * codec state
            However, it's not clear which ones are which. It is consequently
            unclear which fields are a demuxer allowed to set or a muxer allowed to
            read. This leads to erratic behaviour depending on whether decoding or
            encoding is being performed or not (and whether it uses the AVStream
            embedded codec context).
          - various synchronization issues arising from the fact that the same
            context is used by several different APIs (muxers/demuxers,
            parsers, bitstream filters and encoders/decoders) simultaneously, with
            there being no clear rules for who can modify what and the different
            processes being typically delayed with respect to each other.
          - avformat_find_stream_info() making it necessary to support opening
            and closing a single codec context multiple times, thus
            complicating the semantics of freeing various allocated objects in the
            codec context.
      
      Those problems are resolved by replacing the AVStream embedded codec
      context with a newly added AVCodecParameters instance, which stores only
      the stream parameters exported by the demuxers or read by the muxers.
      9200514a
    • Anton Khirnov's avatar