1. 14 Feb, 2018 1 commit
  2. 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
  3. 18 Feb, 2016 1 commit
  4. 26 Dec, 2015 1 commit
  5. 27 Jul, 2015 1 commit
  6. 19 Apr, 2015 1 commit
  7. 09 Mar, 2015 1 commit
  8. 24 Feb, 2015 8 commits
  9. 23 Feb, 2015 1 commit
  10. 21 Feb, 2015 3 commits
  11. 12 Feb, 2015 1 commit
  12. 17 Jan, 2015 1 commit
  13. 20 Oct, 2014 1 commit
  14. 15 Oct, 2014 3 commits
  15. 24 Sep, 2014 1 commit
    • Vittorio Giovara's avatar
      rtpdec_hevc: Drop a duplicated, nonstandard entry · c463dfc7
      Vittorio Giovara authored
      The RFC spec draft only specifies the "H265" name - there is no
      specification saying how to interpret "HEVC" (if such a packet
      format is specified it could be an entirely different format).
      
      Since this is a very new standard (still a draft), there is little
      need for compatibility with existing, broken implementations. Therefore
      remove the extra alias, to avoid the risk of encouraging incorrect
      usage.
      
      Intentionally keeping the ff_hevc_dynamic_handler name for the
      handler, to use "hevc" consistently as name for the codec instead
      of "h265" within the library internals as long as there only is one
      single variant in actual use.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      c463dfc7
  16. 21 Sep, 2014 1 commit
  17. 03 Sep, 2014 1 commit
  18. 30 Aug, 2014 1 commit
  19. 26 Aug, 2014 1 commit