git.videolan.org Git - ffmpeg.git/rss log

Les articles publiés sur le site

• avcodec/amfenc_av1 : Add B-frame QP control

  4 avril, par Dmitrii Ovchinnikov

  avcodec/amfenc_av1: Add B-frame QP control
  

  • [DH] libavcodec/amfenc.h
  • [DH] libavcodec/amfenc_av1.c

• vulkan_ffv1 : slightly optimize the range decoder

  4 avril, par Lynne

  vulkan_ffv1: slightly optimize the range decoder
  
  GPUs have cmovs as standard.
  

  • [DH] libavcodec/vulkan/rangecoder.comp

• avutil/tests/aes_ctr : also randomize the encryption key

  3 avril, par James Almer

  avutil/tests/aes_ctr: also randomize the encryption key
  
  And not just the IV.
  
  Signed-off-by: James Almer <jamrial@gmail.com>
  

  • [DH] libavutil/tests/aes_ctr.c

• avutil/tests/aes_ctr : reindent after the previous commit

  3 avril, par James Almer

  avutil/tests/aes_ctr: reindent after the previous commit
  
  Signed-off-by: James Almer <jamrial@gmail.com>
  

  • [DH] libavutil/tests/aes_ctr.c

• avutil/tests/aes_ctr : also check the encrypted buffer

  3 avril, par James Almer

  avutil/tests/aes_ctr: also check the encrypted buffer
  
  The test in its current form is just ensuring the plain text output is the same
  as the plain text input, not bothering to check if anything was done with the
  latter. av_aes_ctr_crypt() could be a simple memcpy under the hood and this
  test would still succeed.
  
  To check the integrity of the encrypted buffer, both the IV and the key need to
  be fixed. As such, and in order to not remove the existing randomization of the
  input IV, do two runs, one with random initialization data, and one with static
  data.
  
  Signed-off-by: James Almer <jamrial@gmail.com>
  

  • [DH] libavutil/tests/aes_ctr.c