1. 12 12月, 2020 1 次提交
  2. 22 11月, 2020 1 次提交
  3. 05 11月, 2020 1 次提交
  4. 31 10月, 2020 1 次提交
  5. 29 9月, 2020 1 次提交
  6. 25 5月, 2020 1 次提交
  7. 11 12月, 2019 1 次提交
  8. 10 10月, 2019 1 次提交
  9. 21 3月, 2019 1 次提交
  10. 05 10月, 2017 1 次提交
    • L
      avformat: fix id3 chapters · 1fd80106
      Lukas Stabe 提交于
      These changes store id3 chapter data in ID3v2ExtraMeta and introduce
      ff_id3v2_parse_chapters to parse them into the format context if needed.
      
      Encoders using ff_id3v2_read, which previously parsed chapters into the
      format context automatically, were adjusted to call
      ff_id3v2_parse_chapters.
      Signed-off-by: Nwm4 <nfxjfg@googlemail.com>
      1fd80106
  11. 29 3月, 2017 1 次提交
  12. 14 12月, 2016 1 次提交
  13. 19 5月, 2016 1 次提交
  14. 17 5月, 2016 1 次提交
  15. 15 5月, 2016 1 次提交
  16. 13 5月, 2016 1 次提交
  17. 05 5月, 2016 1 次提交
  18. 01 5月, 2016 1 次提交
  19. 24 2月, 2016 1 次提交
    • A
      lavf: replace AVStream.codec with AVStream.codecpar · 9200514a
      Anton Khirnov 提交于
      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
  20. 27 10月, 2015 1 次提交
  21. 26 9月, 2015 1 次提交
  22. 15 2月, 2015 1 次提交
  23. 26 9月, 2014 1 次提交
  24. 18 8月, 2014 1 次提交
  25. 08 8月, 2014 1 次提交
  26. 06 8月, 2014 1 次提交
  27. 20 4月, 2014 1 次提交
  28. 13 4月, 2014 2 次提交
  29. 11 3月, 2014 1 次提交
  30. 29 12月, 2013 1 次提交
  31. 15 12月, 2013 2 次提交
  32. 21 6月, 2013 1 次提交
  33. 18 3月, 2013 1 次提交
  34. 16 3月, 2013 1 次提交
  35. 05 3月, 2013 1 次提交
  36. 07 1月, 2013 1 次提交
  37. 11 12月, 2012 1 次提交
  38. 04 12月, 2012 1 次提交