Recherche avancée

Sur d’autres sites (16239)

• ffv1/vulkan : redo context count tracking and quant_table_idx management

  5 avril, par Lynne

  ffv1/vulkan : redo context count tracking and quant_table_idx management
  This commit also makes it possible for the encoder to choose a different
  
  quantization table on a per-slice basis, as well as adding this capability
  
  to the decoder.
  Also, this commit fully fixes decoding of context=1 encoded files.
  

  • [DH] libavcodec/ffv1_vulkan.h
  • [DH] libavcodec/ffv1enc_vulkan.c
  • [DH] libavcodec/vulkan/ffv1_common.comp
  • [DH] libavcodec/vulkan/ffv1_dec.comp
  • [DH] libavcodec/vulkan/ffv1_dec_setup.comp
  • [DH] libavcodec/vulkan/ffv1_enc_setup.comp
  • [DH] libavcodec/vulkan/ffv1_reset.comp
  • [DH] libavcodec/vulkan_ffv1.c

• ffmpeg change framerate : Question about bitrate [closed]

  9 février, par schweigerson

  Thanks to the forum, I successfully can reduce the frame rate of a video.

  


  ffmpeg -i input_50fps.mp4 -filter:v fps=25 output_25fps.mp4

  


  Input and output have a similar bitrate as well as filzesize :

  


  




  


  


  


  


  


  



  


  


  


  


  


  


  


  


  


  


  File	bitrate	filesize
  input_50fps.mp4	2900kBit/s	1.9GB
  output_25fps.mp4	2528kBit/s	1.7GB

  


  Assumption : Divide the number of frames into half should both reduce the bitrate and the filesize accordingly (half the size).

  


  Question : Does it make sense to enforce the reduction of the bitrate to approx. half the original one, when I reduce the framerate by to 50% (e.g. with -b:v 1500k) ? IMHO, the video quality should be comparable to the original video then.

  


  Note : I may make according test runs, but I perhaps do not have the ability to recognize the quality difference as I'm not an advanced video expert.

  


  Would be happy to read your advice.

  


• swscale/cms : add color management subsystem

  29 novembre 2024, par Niklas Haas

  swscale/cms : add color management subsystem
  The underlying color mapping logic was ported as straightforwardly as possible
  
  from libplacebo, although the API and glue code has been very heavily
  
  refactored / rewritten. In particular, the generalization of gamut mapping
  
  methods is replaced by a single ICC intent selection, and constants have been
  
  hard-coded.
  To minimize the amount of overall operations, this gamut mapping LUT now embeds
  
  a direct end-to-end transformation to the output color space ; something that
  
  libplacebo does in shaders, but which is prohibitively expensive in software.
  In order to preserve compatibility with dynamic tone mapping without severely
  
  regressing performance, we add the ability to generate a pair of "split" LUTS,
  
  one for encoding the input and output to the perceptual color space, and a
  
  third to embed the tone mapping operation. Additionally, this intermediate
  
  space could be used for additional subjective effect (e.g. changing
  
  saturation or brightness).
  The big downside of the new approach is that generating a static color mapping
  
  LUT is now fairly slow, as the chromaticity lobe peaks have to be recomputed
  
  for every single RGB value, since correlated RGB colors are not necessarily
  
  aligned in ICh space. Generating a split 3DLUT significantly alleviates this
  
  problem because the expensive step is done as part of the IPT input LUT, which
  
  can share the same hue peak calculation at least for all input intensities.
  

  • [DH] libswscale/Makefile
  • [DH] libswscale/cms.c
  • [DH] libswscale/cms.h