Recherche avancée

Sur d’autres sites (10665)

• avcodec/jpeg2000htdec : check if block decoding will exceed internal precision

  12 août 2023, par Pierre-Anthony Lemieux

  avcodec/jpeg2000htdec : check if block decoding will exceed internal precision
  Intended to replace https://patchwork.ffmpeg.org/project/ffmpeg/patch/20230802000135.26482-3-michael@niedermayer.cc/
  
  with a more accurate block decoding magnitude bound.
  Fixes : 62433/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_JPEG2000_fuzzer-5828618092937216
  
  Fixes : 58299/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_JPEG2000_fuzzer-5828618092937216
  
  Previous-version-reviewed-by : Tomas Härdin <git@haerdin.se>
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavcodec/jpeg2000htdec.c

• avcodec/h264 : keep SPS and PPS bitstream data

  2 octobre 2015, par wm4

  avcodec/h264 : keep SPS and PPS bitstream data
  We assume an upper bound of 4096 bytes for each raw SPS/PPS. It’s hard
  
  to determine an exact maximum size, but this value was was considered
  
  high enough and safe.
  Needed for the following VideotoolBox commit.
  

  • [DH] libavcodec/h264.h
  • [DH] libavcodec/h264_ps.c

• Gallery of VP8 Encoding Naivete

  15 octobre 2010, par Multimedia Mike — VP8

  I’ve been toiling away as a multimedia technology generalist for so long that it’s easy for me to forget that not everyone is as versed in the minutiae of the domain as I am. But I recently experienced what it’s like to be such an outsider when I posted about my toy VP8 encoder, expressing that it’s one of the hardest things I have ever tried to do. I heard of from number of people who do have extensive experience in video encoding, particularly with the H.264 and VP8 codecs. Their reactions were predictable : What’s so hard ? Look, you might be a little too immersed in the area to really understand a relative beginner’s perspective.

  And to all the people who suggested that I should get the encoder into FFmpeg ASAP : Are you crazy ?! Did you see what the first pass of the encoder produced ? Do you have lower standards than even I do ?

  
  
  

  Not Giving Up
  I worked a little more on the toy encoder. Remember that the above image is what I’m hoping to encode somewhat faithfully for this experiment. In my first pass, I attempted vertical prediction for all planes. For my next pass, I forced the chroma planes to mid-level (which results in a greyscale image) and played with the 16×16 luma prediction modes. When implementing an extremely naive algorithm to decide which 16×16 prediction mode would be the best for a particular block, this is what the program produced :

  
  
  

  For fun, here is what the image encodes to when forcing various prediction modes :
  

  I think the DC-only prediction mode actually looks a little better than the image that the naive algorithm produced :

  
  
  

  Vertical 16×16 prediction, similar to the image from the last post (just in black and white) :
  

  
  
  

  Horizontal 16×16 prediction :
  

  
  
  

  This is the 16×16 prediction mode unique to VP8, the TrueMotion mode (based on On2/Duck’s very first video codec) :
  

  
  
  

  Wow, these encodings really bring down the cheerful tone of the original image.

  Next Steps
  I have little reason to believe that I am encoding and subsequently reconstructing the image correctly (i.e., error is likely propagating through the entire encoding). If I have time, the next step is to validate my reconstruction against the encoder. Then I need to get the entropy considerations correct so that I actually get some compression out of this format.