1. 26 Oct, 2017 1 commit
  2. 05 Oct, 2017 1 commit
  3. 30 Sep, 2016 1 commit
    • Anton Khirnov's avatar
      lavf: fix usage of AVIOContext.seekable · 83548fe8
      Anton Khirnov authored
      It is supposed to be a flag. The only currently defined value is
      AVIO_SEEKABLE_NORMAL, but other ones may be added in the future.
      However all the current lavf code treats this field as a bool (mainly
      for historical reasons).
      Change all those cases to properly check for AVIO_SEEKABLE_NORMAL.
  4. 23 Feb, 2016 1 commit
    • 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.
  5. 11 Sep, 2015 1 commit
  6. 17 May, 2015 1 commit
  7. 10 May, 2015 2 commits
  8. 29 Mar, 2015 1 commit
  9. 09 Dec, 2014 1 commit
  10. 02 Nov, 2014 1 commit
  11. 11 Jul, 2014 1 commit
  12. 24 Jun, 2014 6 commits
  13. 18 May, 2014 1 commit
  14. 03 May, 2014 1 commit
  15. 30 Apr, 2014 1 commit
    • Daniel Verkamp's avatar
      ff_put_wav_header: add flag to force WAVEFORMATEX · 5e7d21c7
      Daniel Verkamp authored
      Partially undoes commit 2c4e08d8:
          riff: always generate a proper WAVEFORMATEX structure in
      A new flag, FF_PUT_WAV_HEADER_FORCE_WAVEFORMATEX, is added to force the
      use of WAVEFORMATEX rather than PCMWAVEFORMAT even for PCM codecs.
      This flag is used in the Matroska muxer (the cause of the original
      change) and in the ASF muxer, because the specifications for
      these formats indicate explicitly that WAVEFORMATEX should be used.
      Muxers for other formats will return to the original behavior of writing
      PCMWAVEFORMAT when writing a header for raw PCM.
      In particular, this causes raw PCM in WAV to generate the canonical
      44-byte header expected by some tools.
      Signed-off-by: default avatarMichael Niedermayer <michaelni@gmx.at>
  16. 03 Nov, 2013 1 commit
  17. 13 Feb, 2013 1 commit
  18. 12 Feb, 2013 1 commit
  19. 07 Jan, 2013 1 commit
  20. 31 Dec, 2012 1 commit
  21. 27 Nov, 2012 1 commit
  22. 30 Oct, 2012 1 commit
  23. 16 Oct, 2012 1 commit