Recherche avancée

Sur d’autres sites (9879)

• avcodec/hevc_ps : fix range of num_tile_{columns,rows}_minus1

  30 juin 2019, par James Almer

  avcodec/hevc_ps : fix range of num_tile_columns,rows_minus1
  From 7.4.3.3.1 :
  num_tile_columns_minus1 shall be in the range of 0 to PicWidthInCtbsY - 1, inclusive.
  
  num_tile_rows_minus1 shall be in the range of 0 to PicHeightInCtbsY - 1, inclusive.
  Reviewed-by : Michael Niedermayer <michael@niedermayer.cc>
  
  Signed-off-by : James Almer <jamrial@gmail.com>
  

  • [DH] libavcodec/hevc_ps.c

• avfilter/vf_blackdetect : support full-range YUV

  8 décembre 2022, par Niklas Haas

  avfilter/vf_blackdetect : support full-range YUV
  This filter currently makes the distinction between limited and full
  
  range by testing for the deprecated YUVJ pixel formats at link setup
  
  time. This is deprecated and should be improved to perform the detection
  
  based on the per-frame metadata.
  Rewrite it to calculate the black pixel threshold at the time of
  
  filtering a frame, when metadata about the frame's color range is known.
  
  Doing it this way has the small side benefit of being able to handle
  
  streams with variable metadata, and is not a meaningful performance
  
  cost.
  Signed-off-by : Niklas Haas <git@haasn.dev>
  

  • [DH] libavfilter/vf_blackdetect.c

• avformat/matroskadec : Accept more unknown-length elements

  17 mai 2019, par Andreas Rheinhardt

  avformat/matroskadec : Accept more unknown-length elements
  The current Matroska specifications mandate that only two elements may
  
  use an unknown-length length : Segments and clusters. But this was not
  
  always so : For the greater part of Matroska's existence, all master
  
  elements were allowed to make use of the unknown-length feature.
  And there were muxers creating such files : For several years
  
  libavformat's Matroska muxer used unknown-length for all master
  
  elements when the output wasn't seekable. This only stopped in March
  
  2010 with 2529bb30. And even afterwards it was possible (albeit
  
  unlikely) for libavformat to create unknown-length master elements
  
  that are in violation of today's specifications, namely if the master
  
  element was so big that the seek backwards to update the size could
  
  no longer be performed inside the AVIOContext's write buffer. This
  
  has only been fixed in October 2016 (with the patches that introduced
  
  support for writing CRC-32 elements).
  Libavformat's Matroska demuxer meanwhile has never really supported
  
  unknown-length elements besides segments and clusters. Support for the
  
  latter was hardcoded. This commit changes this : Now all master elements
  
  for which a syntax to parse them is available are supported. This
  
  includes the files produced by old versions of libavformat's muxer.
  More precisely, master elements that have unknown length and are about
  
  to be parsed (not skipped) are supported ; only a warning is emitted for
  
  them. For normal files, this means that level 1 elements after the
  
  clusters that are encountered after the clusters have been parsed (i.e.
  
  not because they are referenced by the seekhead at the beginning of the
  
  file) are still unsupported (they would be skipped at this point if
  
  their length were known).
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavformat/matroskadec.c