Recherche avancée

Sur d’autres sites (7812)

• MAINTAINERS : Add a profile entry for fate

  28 août 2024, par Michael Niedermayer

  MAINTAINERS : Add a profile entry for fate
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] MAINTAINERS

• lavfi : add ICC profile support via lcms2

  9 avril 2022, par Niklas Haas

  lavfi : add ICC profile support via lcms2
  This introduces an optional dependency on lcms2 into FFmpeg. lcms2 is a
  
  widely used library for ICC profile handling, which apart from being
  
  used in almost all major image processing programs and video players,
  
  has also been deployed in browsers. As such, it's both widely available
  
  and well-tested.
  Add a few helpers to cover our major use cases. This commit merely
  
  introduces the helpers (and configure check), even though nothing uses
  
  them yet.
  It's worth pointing out that the reason the cmsToneCurves for each
  
  AVCOL_TRC are cached inside the context, is because constructing a
  
  cmsToneCurve requires evaluating the curve at 4096 (by default) grid
  
  points and constructing a LUT. So, we ideally only want to do this once
  
  per curve. This matters for e.g. ff_icc_profile_detect_transfer, which
  
  essentially compares a profile against all of these generated LUTs.
  
  Re-generating the LUTs for every iteration would be unnecessarily
  
  wasteful.
  The same consideration does not apply to e.g. cmsCreate*Profile, which
  
  is a very lightweight operation just involving struct allocation and
  
  setting a few pointers.
  The cutoff value of 0.01 was determined by experimentation. The lowest
  
  "false positive" delta I saw in practice was 0.13, and the largest
  
  "false negative" delta was 0.0008. So a value of 0.01 sits comfortaby
  
  almost exactly in the middle.
  Signed-off-by : Niklas Haas <git@haasn.dev>
  

  • [DH] configure
  • [DH] libavfilter/fflcms2.c
  • [DH] libavfilter/fflcms2.h

• FFmpeg Arthenica always encodes with x265 Main10 profile [closed]

  5 avril, par Jabed Dhali

  I'm using FFmpeg-Kit (Arthenica) for iOS to compress videos using the libx265 encoder. I'm building FFmpeg with a custom configuration script :

  


  export CUSTOM_CONFIG="--disable-indevs \
  --disable-outdevs \
  --disable-hwaccels \
  --enable-videotoolbox \
  --disable-protocols \
  --enable-protocol=file,fd,saf,async \
  --disable-decoders \
  --enable-decoder=${ENABLE_DECODER_LIST} \
  --disable-encoders \
  --enable-encoder=${ENABLE_ENCODER_LIST}"

export CUSTOM_CONFIG_IOS=${CUSTOM_CONFIG}
  ./ios.sh --enable-ios-videotoolbox --enable-lame --enable-libaom  --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libxml2 --enable-opencore-amr --enable-openh264 --enable-opus --enable-twolame --enable-x264 --enable-x265 --enable-gpl


  


  Then I run FFmpeg with the following commands :

  


  -y -hide_banner -i input.MOV -vcodec libx265 -x265-params profile=main output.mov
-y -hide_banner -i input.MOV -vcodec libx265 -x265-params profile=main10 output.mov


  


  However, regardless of the profile I set, the output always ends up being encoded with the Main10 profile.

  


  Here’s the log output :

  


  x265 [info]: HEVC encoder version 3.4
x265 [info]: build info [Mac OS X][clang 16.0.0][32 bit][noasm] 10bit
x265 [info]: using cpu capabilities: none!
x265 [info]: Main 10 profile, Level-5 (Main tier)


  


  It seems that the FFmpeg build only supports 10-bit encoding. I want to be able to encode with different profiles (main, main10, etc.), as well as to build libx265 in a way that supports 8-bit + 10-bit + 12-bit encoding (unified 64-bit build), as like as the same command executes for MacOS.

  


  x265 [info]: HEVC encoder version 4.1+1-1d117be
x265 [info]: build info [Mac OS X][clang 16.0.0][64 bit] 8bit+10bit+12bit
x265 [info]: using cpu capabilities: NEON Neon_DotProd Neon_I8MM
x265 [info]: Main profile, Level-2.1 (Main tier)


  


  How can I correctly configure and build FFmpeg and libx265 with Mobile FFmpeg to support multiple bit depths and allow setting different profiles via -x265-params ?