1. 31 Jan, 2017 1 commit
  2. 20 Jul, 2016 1 commit
  3. 22 May, 2016 2 commits
  4. 13 Mar, 2016 3 commits
  5. 08 Mar, 2016 1 commit
  6. 06 Mar, 2016 1 commit
  7. 05 Mar, 2016 2 commits
  8. 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.
      9200514a
  9. 21 Feb, 2016 2 commits
  10. 20 Feb, 2016 1 commit
  11. 19 Feb, 2016 1 commit
  12. 18 Feb, 2016 2 commits
  13. 12 Sep, 2015 1 commit
  14. 18 Aug, 2015 1 commit
  15. 28 May, 2015 1 commit
  16. 23 May, 2015 1 commit
  17. 19 Mar, 2015 4 commits
  18. 03 Mar, 2015 1 commit
  19. 14 Feb, 2015 1 commit
  20. 19 Nov, 2014 2 commits
  21. 24 Sep, 2014 1 commit
  22. 16 Sep, 2014 1 commit
  23. 18 Jun, 2014 2 commits
    • Anton Khirnov's avatar
      lavf: switch to AVStream.time_base as the hint for the muxer timebase · 194be1f4
      Anton Khirnov authored
      Previously, AVStream.codec.time_base was used for that purpose, which
      was quite confusing for the callers. This change also opens the path for
      removing AVStream.codec.
      
      The change in the lavf-mkv test is due to the native timebase (1/1000)
      being used instead of the default one (1/90000), so the packets are now
      sent to the crc muxer in the same order in which they are demuxed
      (previously some of them got reordered because of inexact timestamp
      conversion).
      194be1f4
    • Anton Khirnov's avatar
      riffenc: take an AVStream instead of an AVCodecContext · d754ed41
      Anton Khirnov authored
      It will be useful in the following commits.
      
      Also, rename the AVCodecContext pointer name from 'stream' to 'codec'.
      d754ed41
  24. 23 May, 2014 1 commit
  25. 18 May, 2014 2 commits
  26. 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
          ff_put_wav_header
      
      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: 's avatarMichael Niedermayer <michaelni@gmx.at>
      5e7d21c7
  27. 14 Apr, 2014 1 commit
  28. 11 Apr, 2014 1 commit