1. 02 Jul, 2020 1 commit
  2. 29 Feb, 2020 1 commit
  3. 06 Mar, 2019 1 commit
  4. 17 Jan, 2018 1 commit
  5. 24 Dec, 2017 3 commits
    • Henrik Gramner's avatar
      0fe75403
    • Vittorio Giovara's avatar
      lavf: Upgrade to some newer API:s · dae7f18d
      Vittorio Giovara authored
       * Use the codec parameters API instead of the AVStream codec field.
       * Use av_packet_unref() instead of av_free_packet().
       * Use the AVFrame pts field instead of pkt_pts.
      dae7f18d
    • Vittorio Giovara's avatar
      Unify 8-bit and 10-bit CLI and libraries · 71ed44c7
      Vittorio Giovara authored
      Add 'i_bitdepth' to x264_param_t with the corresponding '--output-depth' CLI
      option to set the bit depth at runtime.
      
      Drop the 'x264_bit_depth' global variable. Rather than hardcoding it to an
      incorrect value, it's preferable to induce a linking failure. If applications
      relies on this symbol this will make it more obvious where the problem is.
      
      Add Makefile rules that compiles modules with different bit depths. Assembly
      on x86 is prefixed with the 'private_prefix' define, while all other archs
      modify their function prefix internally.
      
      Templatize the main C library, x86/x86_64 assembly, ARM assembly, AARCH64
      assembly, PowerPC assembly, and MIPS assembly.
      
      The depth and cache CLI filters heavily depend on bit depth size, so they
      need to be duplicated for each value. This means having to rename these
      filters, and adjust the callers to use the right version.
      
      Unfortunately the threaded input CLI module inherits a common.h dependency
      (input/frame -> common/threadpool -> common/frame -> common/common) which
      is extremely complicated to address in a sensible way. Instead duplicate
      the module and select the appropriate one at run time.
      
      Each bitdepth needs different checkasm compilation rules, so split the main
      checkasm target into two executables.
      71ed44c7
  6. 21 Jan, 2017 1 commit
  7. 20 Sep, 2016 1 commit
  8. 16 Jan, 2016 2 commits
  9. 23 Feb, 2015 1 commit
  10. 26 Aug, 2014 1 commit
  11. 08 Jan, 2014 1 commit
  12. 25 Oct, 2013 1 commit
  13. 23 Apr, 2013 1 commit
  14. 09 Jan, 2013 1 commit
  15. 19 Nov, 2012 1 commit
  16. 26 Sep, 2012 1 commit
  17. 04 Feb, 2012 1 commit
  18. 01 Dec, 2011 1 commit
    • Steven Walters's avatar
      YUV range detection and support for x264CLI · 6767f967
      Steven Walters authored
      Two new options: --input-range and --range.
      --input-range forces the range of the input in case of misdetection; auto by default.
      -- range sets the range of the output; x264cli will convert if necessary, TV by default.
      --fullrange is now removed as a CLI option (but the libx264 API is unchanged).
      6767f967
  19. 05 Aug, 2011 1 commit
  20. 18 Jul, 2011 1 commit
  21. 10 Jul, 2011 1 commit
  22. 10 May, 2011 1 commit
  23. 26 Apr, 2011 1 commit
  24. 25 Jan, 2011 2 commits
  25. 10 Jan, 2011 1 commit
  26. 18 Sep, 2010 1 commit
    • Fiona Glaser's avatar
      Update source file headers · 213a99d0
      Fiona Glaser authored
      Update dates, improve file descriptions, make things more consistent.
      Also add information about commercial licensing.
      213a99d0
  27. 16 Aug, 2010 3 commits
  28. 15 Jul, 2010 1 commit
  29. 03 Jul, 2010 1 commit
  30. 07 Apr, 2010 1 commit
  31. 15 Feb, 2010 1 commit
  32. 14 Jan, 2010 1 commit
    • Kieran Kunhya's avatar
      LAVF/FFMS input support, native VFR timestamp handling · 30d76a5e
      Kieran Kunhya authored
      libx264 now takes three new API parameters.
      b_vfr_input tells x264 whether or not the input is VFR, and is 1 by default.
      i_timebase_num and i_timebase_den pass the timebase to x264.
      
      x264_picture_t now returns the DTS of each frame: the calling app need not calculate it anymore.
      
      Add libavformat and FFMS2 input support: requires libav* and ffms2 libraries respectively.
      FFMS2 is _STRONGLY_ preferred over libavformat: we encourage all distributions to compile with FFMS2 support if at all possible.
      FFMS2 can be found at http://code.google.com/p/ffmpegsource/.
      --index, a new x264cli option, allows the user to store (or load) an FFMS2 index file for future use, to avoid re-indexing in the future.
      
      Overhaul the muxers to pass through timestamps instead of assuming CFR.
      Also overhaul muxers to correctly use b_annexb and b_repeat_headers to simplify the code.
      Remove VFW input support, since it's now pretty much redundant with native AVS support and LAVF support.
      Finally, overhaul a large part of the x264cli internals.
      
      --force-cfr, a new x264cli option, allows the user to force the old method of timestamp handling.  May be useful in case of a source with broken timestamps.
      Avisynth, YUV, and Y4M input are all still CFR.  LAVF or FFMS2 must be used for VFR support.
      
      Do note that this patch does *not* add VFR ratecontrol yet.
      Support for telecined input is also somewhat dubious at the moment.
      
      Large parts of this patch by Mike Gurlitz <mike.gurlitz@gmail.com>, Steven Walters <kemuri9@gmail.com>, and Yusuke Nakamura <muken.the.vfrmaniac@gmail.com>.
      30d76a5e