Recherche avancée

Sur d’autres sites (6689)

• libavutil : Add wchartoutf8(), wchartoansi(), utf8toansi(), getenv_utf8(), freeenv_utf...

  20 juin 2022, par Nil Admirari

  libavutil : Add wchartoutf8(), wchartoansi(), utf8toansi(), getenv_utf8(), freeenv_utf8() and getenv_dup()
  wchartoutf8() converts strings returned by WinAPI into UTF-8,
  
  which is FFmpeg's preffered encoding.
  Some external dependencies, such as AviSynth, are still
  
  not Unicode-enabled. utf8toansi() converts UTF-8 strings
  
  into ANSI in two steps : UTF-8 -> wchar_t -> ANSI.
  
  wchartoansi() is responsible for the second step of the conversion.
  
  Conversion in just one step is not supported by WinAPI.
  Since these character converting functions allocate the buffer
  
  of necessary size, they also facilitate the removal of MAX_PATH limit
  
  in places where fixed-size ANSI/WCHAR strings were used
  
  as filename buffers.
  On Windows, getenv_utf8() wraps _wgetenv() converting its input from
  
  and its output to UTF-8. Strings returned by getenv_utf8()
  
  must be freed by freeenv_utf8().
  On all other platforms getenv_utf8() is a wrapper around getenv(),
  
  and freeenv_utf8() is a no-op.
  The value returned by plain getenv() cannot be modified ;
  
  av_strdup() is usually used when modifications are required.
  
  However, on Windows, av_strdup() after getenv_utf8() leads to
  
  unnecessary allocation. getenv_dup() is introduced to avoid
  
  such an allocation. Value returned by getenv_dup() must be freed
  
  by av_free().
  Because of cleanup complexities, in places that only test the existence
  
  of an environment variable or compare its value with a string
  
  consisting entirely of ASCII characters, the use of plain getenv()
  
  is still preferred. (libavutil/log.c check_color_terminal()
  
  is an example of such a place.)
  Plain getenv() is also preffered in UNIX-only code,
  
  such as bktr.c, fbdev_common.c, oss.c in libavdevice
  
  or af_ladspa.c in libavfilter.
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] configure
  • [DH] libavutil/getenv_utf8.h
  • [DH] libavutil/wchar_filename.h

• GOL-1361 : Remove invalid CTTS sample_offset check

  18 avril 2023, par ekir

  GOL-1361 : Remove invalid CTTS sample_offset check
  We checked in this places :
  
  * In 8.6.1.3 of ISO/IEC 14496-12 about the CTTS box
  
  * In Apples MOV spec : https://developer.apple.com/library/archive/documentation/QuickTime/QTFF/QTFFChap2/qtff2.html#//apple_ref/doc/uid/TP40000939-CH204-SW19
  

  • [DH] libavformat/mov.c

• FFmpeg split 10 bit HDR x265 mp4 to exr sequence

  13 juillet 2022, par bvs

  I have x265 mp4 files of gameplay recorded with Nvidia Shadowplay with HDR information which I want to display in two places : my Vulkan app which supports HDR EXRs and Affinity photo which I paid for and acts as my control and also supports HDR exr under its HDR 32-Bit Preview panel. I can also convert to mov with FFmpeg to check that this isn't just an mp4 problem) by converting to mov first

  


  ffmpeg -i input.mp4 output.mov


  


  When I go to grab the image sequence of exrs with

  


  ffmpeg -i input.mp4 output%04d.exr


  


  My resulting image in my control (Affinity) is incredibly washed out and not HDR at all. How, using ffmpeg, can I grab the still frames from my recorded video. Am I missing a conversion, is this an error in ffmpeg itself, or something else ?