1. 20 Mar, 2019 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. 05 Aug, 2013 1 commit
  4. 01 Feb, 2013 1 commit
  5. 24 Jan, 2013 1 commit
  6. 23 Jan, 2013 1 commit
  7. 11 Jan, 2013 2 commits
  8. 20 Dec, 2012 1 commit
  9. 14 Nov, 2012 1 commit
  10. 07 Aug, 2012 1 commit
  11. 23 Jul, 2012 1 commit
  12. 22 Jul, 2012 1 commit
  13. 23 Feb, 2012 1 commit
    • Martin Storsjö's avatar
      rtpenc: Allow packetizing H263 according to the old RFC 2190 · c4584f3c
      Martin Storsjö authored
      According to newer RFCs, this packetization scheme should only
      be used for interfacing with legacy systems.
      
      Implementing this packetization mode properly requires parsing
      the full H263 bitstream to find macroblock boundaries (and knowing
      their macroblock and gob numbers and motion vector predictors).
      
      This implementation tries to look for GOB headers (which
      can be inserted by using -ps <small number>), but if the GOBs
      aren't small enough to fit into the MTU, the packetizer blindly
      splits packets at any offset and claims it to be a GOB boundary
      (by using Mode A from the RFC). While not correct, this seems
      to work with some receivers.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      c4584f3c
  14. 17 Oct, 2011 1 commit
  15. 12 Oct, 2011 1 commit
  16. 29 Sep, 2011 1 commit
  17. 26 Sep, 2011 2 commits
  18. 23 Sep, 2011 1 commit
  19. 19 Mar, 2011 1 commit
  20. 15 Sep, 2010 1 commit
  21. 30 Mar, 2010 1 commit
  22. 11 Jan, 2010 1 commit
  23. 13 Apr, 2009 1 commit
  24. 07 Apr, 2009 1 commit
  25. 17 Feb, 2009 1 commit
  26. 16 Feb, 2009 1 commit
  27. 27 Jan, 2009 1 commit
  28. 19 Jan, 2009 1 commit
  29. 24 Jun, 2008 1 commit
  30. 09 May, 2008 1 commit
  31. 31 Mar, 2008 4 commits
  32. 06 Jan, 2008 1 commit
  33. 04 Jan, 2008 2 commits
  34. 02 Dec, 2007 1 commit