1. 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
  2. 14 Dec, 2015 1 commit
  3. 12 Dec, 2015 1 commit
  4. 29 Sep, 2015 1 commit
  5. 19 Apr, 2015 1 commit
  6. 14 Feb, 2015 1 commit
  7. 10 Feb, 2015 1 commit
  8. 03 Feb, 2015 1 commit
    • Luca Barbato's avatar
      r3d: Fix pos type · 898276c1
      Luca Barbato authored
      avio_tell can return a negative number.
      
      Bug-Id: CID 1265715
      CC: libav-stable@libav.org
      898276c1
  9. 19 Sep, 2013 1 commit
  10. 15 May, 2013 1 commit
  11. 11 Mar, 2013 1 commit
  12. 07 Aug, 2012 1 commit
  13. 30 Jul, 2012 1 commit
  14. 29 Jul, 2012 1 commit
    • Anton Khirnov's avatar
      lavf: deprecate r_frame_rate. · aba232cf
      Anton Khirnov authored
      According to its description, it is supposed to be the LCM of all the
      frame durations. The usability of such a thing is vanishingly small,
      especially since we cannot determine it with any amount of reliability.
      Therefore get rid of it after the next bump.
      
      Replace it with the average framerate where it makes sense.
      
      FATE results for the wtv and xmv demux tests change. In the wtv case
      this is caused by the file being corrupted (or possibly badly cut) and
      containing invalid timestamps. This results in lavf estimating the
      framerate wrong and making up wrong frame durations.
      In the xmv case the file contains pts jumps, so again the estimated
      framerate is far from anything sane and lavf again makes up different
      frame durations.
      
      In some other tests lavf starts making up frame durations from different
      frame.
      aba232cf
  15. 09 Mar, 2012 1 commit
  16. 02 Mar, 2012 1 commit
  17. 10 Feb, 2012 1 commit
  18. 27 Jan, 2012 1 commit
  19. 30 Nov, 2011 1 commit
  20. 19 Oct, 2011 2 commits
  21. 17 Jul, 2011 1 commit
  22. 03 Jul, 2011 1 commit
  23. 08 Jun, 2011 1 commit
  24. 03 Jun, 2011 1 commit
  25. 31 May, 2011 1 commit
  26. 03 Apr, 2011 1 commit
  27. 19 Mar, 2011 1 commit
  28. 17 Mar, 2011 1 commit
  29. 07 Mar, 2011 1 commit
  30. 04 Mar, 2011 1 commit
  31. 01 Mar, 2011 2 commits
  32. 21 Feb, 2011 1 commit
  33. 29 Jan, 2011 1 commit
  34. 26 Jan, 2011 1 commit
  35. 25 Apr, 2010 1 commit
  36. 30 Mar, 2010 1 commit
  37. 02 Mar, 2010 1 commit
  38. 25 Aug, 2009 1 commit