1. 19 May, 2014 1 commit
  2. 15 May, 2014 1 commit
    • Anton Khirnov's avatar
      lavf: add AVFMT_FLAG_BITEXACT. · 0c1959b0
      Anton Khirnov authored
      Use it instead of checking CODEC_FLAG_BITEXACT in the first stream's
      codec context.
      Using codec options inside lavf is fragile and can easily break when the
      muxing codec context is not the encoding context.
  3. 19 Apr, 2014 1 commit
  4. 06 Apr, 2014 1 commit
  5. 27 Mar, 2014 1 commit
  6. 24 Mar, 2014 1 commit
  7. 09 Feb, 2014 1 commit
  8. 04 Feb, 2014 1 commit
    • Luca Barbato's avatar
      lavf: improve handling of sparse streams when muxing · d9ae1031
      Luca Barbato authored
      Currently ff_interleave_packet_per_dts() waits until it gets a frame for
      each stream before outputting packets in interleaved order.
      Sparse streams (i.e. streams with much fewer packets than the other
      streams, like subtitles or audio with DTX) tend to add up latency and in
      specific cases end up allocating a large amount of memory.
      Emit the top packet from the packet_buffer if it has a time delta
      larger than a specified threshold.
      Original report of the issue and initial proposed solution by
      Bug-id: 31
      Signed-off-by: default avatarAnton Khirnov <anton@khirnov.net>
  9. 17 Jan, 2014 1 commit
  10. 09 Jan, 2014 1 commit
  11. 26 Dec, 2013 1 commit
  12. 22 Nov, 2013 1 commit
  13. 02 Nov, 2013 1 commit
  14. 01 Nov, 2013 1 commit
  15. 31 Oct, 2013 5 commits
  16. 29 Oct, 2013 1 commit
  17. 23 Oct, 2013 1 commit
  18. 13 Oct, 2013 2 commits
    • Martin Storsjö's avatar
      http: Support auth method detection for POST · 71549a85
      Martin Storsjö authored
      Inspired by a patch by Jakob van Bethlehem. But instead of doing
      an empty POST first to trigger the WWW-Authenticate header (which
      would succeed if no auth actually was required), add an Expect:
      100-continue header, which is meant to be used exactly for
      cases like this.
      The header is added if doing a post, and the user has specified
      authentication but we don't know the auth method yet.
      Not all common HTTP servers support the Expect: 100-continue header,
      though, so we only try to use it when it really is needed. The user
      can request it to be added for other POST requests as well via
      an option - which would allow the caller to know immediately that
      the POST has failed (e.g. if no auth was provided but the server
      required it, or if the target URL simply doesn't exist).
      This is only done for write mode posts (e.g. posts without pre-set
      post_data) - for posts with pre-set data, we can just redo the post
      if it failed due to 401.
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>
    • Martin Storsjö's avatar
      http: Add an option for forcing basic authentication · eb8b05a3
      Martin Storsjö authored
      The default is to autodetect the auth method. This does require one
      extra request (and also closing and reopening the http connection).
      For some cases such as HTTP POST, the autodetection is not handled
      properly (yet).
      No option is added for digest, since this method requires getting
      nonce parameters from the server first and can't be used straight
      away like Basic.
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>
  19. 12 Oct, 2013 1 commit
  20. 26 Sep, 2013 2 commits
    • Martin Storsjö's avatar
      tls: Add support for listen mode · 705b748e
      Martin Storsjö authored
      Also add options for specifying a certificate and key, which can
      be used both when operating as client and as server.
      Partially based on a patch by Peter Ross.
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>
    • Martin Storsjö's avatar
      tls: Add options for verifying the peer certificate · 8b09d917
      Martin Storsjö authored
      A file containing the trusted CA certificates needs to be
      supplied via the ca_file AVOption, unless the TLS library
      has got a system default file/database set up.
      This doesn't check the hostname of the peer certificate with
      openssl, which requires a non-trivial piece of code for
      manually matching the desired hostname to the string provided
      by the certificate, not provided as a library function.
      That is, with openssl, this only validates that the received
      certificate is signed with the right CA, but not that it is
      the actual server we think we're talking to.
      Verification is still disabled by default since we can't count
      on a proper CA database existing at all times.
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>
  21. 19 Sep, 2013 1 commit
  22. 17 Sep, 2013 1 commit
  23. 16 Sep, 2013 1 commit
  24. 19 Aug, 2013 1 commit
  25. 02 Aug, 2013 1 commit
  26. 28 May, 2013 1 commit
  27. 03 May, 2013 1 commit
  28. 11 Mar, 2013 6 commits
  29. 08 Mar, 2013 1 commit