1. 04 Apr, 2013 1 commit
  2. 15 Mar, 2013 1 commit
  3. 11 Mar, 2013 4 commits
  4. 08 Mar, 2013 1 commit
  5. 07 Mar, 2013 1 commit
  6. 27 Feb, 2013 1 commit
    • Martin Storsjö's avatar
      lavf: Handle the environment variable no_proxy more properly · de9cd1b1
      Martin Storsjö authored
      The handling of the environment variable no_proxy, present since
      one of the initial commits (de6d9b64), is inconsistent with
      how many other applications and libraries interpret this
      variable. Its bare presence does not indicate that the use of
      proxies should be skipped, but it is some sort of pattern for
      hosts that does not need using a proxy (e.g. for a local network).
      
      As investigated by Rudolf Polzer, different libraries handle this
      in different ways, some supporting IP address masks, some supporting
      arbitrary globbing using *, some just checking that the pattern matches
      the end of the hostname without regard for whether it actually is
      the right domain or a domain that ends in the same string.
      
      This simple logic should be pretty similar to the logic used by
      lynx and curl.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      de9cd1b1
  7. 08 Dec, 2012 1 commit
  8. 04 Dec, 2012 1 commit
  9. 28 Nov, 2012 1 commit
  10. 26 Nov, 2012 1 commit
  11. 09 Oct, 2012 3 commits
  12. 08 Oct, 2012 1 commit
  13. 01 Oct, 2012 3 commits
  14. 24 Sep, 2012 1 commit
  15. 21 Sep, 2012 1 commit
  16. 20 Sep, 2012 1 commit
  17. 15 Sep, 2012 3 commits
  18. 14 Sep, 2012 2 commits
  19. 18 Aug, 2012 1 commit
  20. 12 Aug, 2012 2 commits
  21. 11 Aug, 2012 1 commit
  22. 10 Aug, 2012 1 commit
  23. 07 Aug, 2012 1 commit
  24. 05 Aug, 2012 1 commit
  25. 29 Jul, 2012 4 commits
    • 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
    • Anton Khirnov's avatar
      f66eeff1
    • Anton Khirnov's avatar
      lavf: use dts difference instead of AVPacket.duration in find_stream_info() · fe1c1198
      Anton Khirnov authored
      AVPacket.duration is mostly made up and thus completely useless, this is
      especially true for video streams.
      Therefore use dts difference for framerate estimation and
      the max_analyze_duration check.
      
      The asyncts test now needs -analyzeduration, because the default is 5
      seconds and the audio stream in the sample appears at ~10 seconds.
      fe1c1198
    • Luca Barbato's avatar
      avf: introduce nobuffer option · 681ed000
      Luca Barbato authored
      Useful in cases where a significant analyzeduration is
      still needed, while minimizing buffering before output.
      
      An example is processing low-latency streams where all
      media types won't necessarily come in if the
      analyzeduration is small.
      
      Additional changes by Josh Allmann <joshua.allmann@gmail.com>
      Signed-off-by: 's avatarAnton Khirnov <anton@khirnov.net>
      681ed000
  26. 28 Jul, 2012 1 commit