1. 28 Feb, 2015 2 commits
  2. 26 Feb, 2015 1 commit
  3. 22 Feb, 2015 2 commits
  4. 19 Feb, 2015 2 commits
  5. 15 Feb, 2015 1 commit
  6. 04 Feb, 2015 1 commit
  7. 02 Feb, 2015 2 commits
  8. 27 Jan, 2015 1 commit
  9. 08 Jan, 2015 1 commit
  10. 06 Jan, 2015 1 commit
    • Martin Storsjö's avatar
      libavcodec: Add an OpenH264 encoder wrapper · 8a3d9ca6
      Martin Storsjö authored
      Compared to existing, common opensource H264 encoders, this can be
      useful since it has got a different license (BSD instead of GPL).
      Performance- and qualitywise it is comparable to x264 in ultrafast
      Hooking it up as an encoder in libavcodec also simplifies comparing
      it against other common encoders.
      This requires OpenH264 1.3 or newer. Since the OpenH264 API and ABI
      changes frequently, only releases are supported.
      To take advantage of the OpenH264 patent offer, the OpenH264 library
      must not be redistributed, but downloaded at runtime at the end-user's
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>
  11. 05 Jan, 2015 1 commit
  12. 04 Jan, 2015 1 commit
  13. 19 Dec, 2014 1 commit
    • Martin Storsjö's avatar
      libavformat: Only use MoveFileExA when targeting the desktop API subset · 8ebf02f8
      Martin Storsjö authored
      The MoveFileExA is available in the headers regardless which API
      subset is targeted, but it is missing in the Windows Phone link
      libraries. When targeting Windows Store apps, the function is
      available both in the headers and in the link libraries, and thus
      there is no indication for the build system that this function
      should be avoided - such an indication is only given by the
      Windows App Certification Kit, which forbids using the MoveFileExA
      Therefore check the WINAPI_FAMILY defines instead, to figure out
      which API subset is targeted.
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>
  14. 09 Dec, 2014 1 commit
  15. 03 Dec, 2014 1 commit
  16. 27 Nov, 2014 1 commit
  17. 18 Nov, 2014 1 commit
  18. 17 Nov, 2014 1 commit
    • Martin Storsjö's avatar
      lavf: Add an MPEG-DASH ISOFF segmenting muxer · fe5e6e34
      Martin Storsjö authored
      This is mostly to serve as a reference example on how to segment
      the output from the mp4 muxer, capable of writing the segment
      list in four different ways:
      - SegmentTemplate with SegmentTimeline
      - SegmentTemplate with implicit segments
      - SegmentList with individual files
      - SegmentList with one single file per track, and byte ranges
      The muxer is able to serve live content (with optional windowing)
      or create a static segmented MPD.
      In advanced cases, users will probably want to do the segmenting
      in their own application code.
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>
  19. 28 Oct, 2014 1 commit
  20. 26 Oct, 2014 1 commit
  21. 25 Oct, 2014 1 commit
    • Martin Storsjö's avatar
      lavu: Provide fallbacks for gmtime_r and localtime_r · 3f8f1c6f
      Martin Storsjö authored
      This allows writing most code as if they always are is available.
      These are ok to use from other libraries even though it's not a
      public header, since they only provide an inline declaration, and
      doesn't add an actual dependency on lavu internals. (This can be
      considered more a build system compatibility fallback than a
      libavutil feature.)
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>
  22. 10 Oct, 2014 1 commit
  23. 04 Oct, 2014 1 commit
  24. 27 Sep, 2014 1 commit
  25. 26 Sep, 2014 1 commit
  26. 17 Sep, 2014 1 commit
  27. 16 Sep, 2014 2 commits
  28. 07 Sep, 2014 1 commit
  29. 04 Sep, 2014 1 commit
  30. 03 Sep, 2014 1 commit
  31. 23 Aug, 2014 1 commit
    • Reinhard Tartler's avatar
      configure: add --enable-rpath · 749b1f13
      Reinhard Tartler authored
      This option facilitates testing shared libarary builds: for instance
      fate builders do no longer need to set LD_LIBRARY_PATH as the binaries will
      get the right search paths hardcoded into their executable file.
      This option is only meant to be used for testing purposes: The installed
      libraries must not move around in the file system, and doing so will
      cause a lot of subtle problems. For more information why using RPATH is
      dangerous, please refer to
  32. 22 Aug, 2014 1 commit
  33. 21 Aug, 2014 1 commit
  34. 13 Aug, 2014 1 commit
  35. 10 Aug, 2014 1 commit
    • Martin Storsjö's avatar
      configure: Don't pass MSVC compiler options -M[TD] to armasm · 08b94f16
      Martin Storsjö authored
      The -MD option (for enabling a dynamically linked crt) gets interpreted
      as a cpp option for generating dependency information (into a file named
      '-.d', when preprocessing to a pipe). We shouldn't be passing
      any and all C compiler flags to armasm (which is a plain assembler,
      only with cpp bolted on via gas-preprocessor), but these are the
      main conflicting ones.
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>