Recherche avancée

Sur d’autres sites (7711)

• Revision 30797 : On passe en version 0.6 avec tout le code revu et plus ou moins corrigé

  10 août 2009, par kent1@… — Log

  On passe en version 0.6 avec tout le code revu et plus ou moins corrigé

• avfilter/formats : Schedule avfilter_make_format64_list() for removal

  8 août 2020, par Andreas Rheinhardt

  avfilter/formats : Schedule avfilter_make_format64_list() for removal
  Despite its name, this function is not part of the public API, as
  
  formats.h, the header containing its declaration, is a private header.
  
  The formats API was once public API, but that changed long ago
  
  (b74a1da49db5ebed51aceae6cacc2329288a92c1, the commit scheduling it to
  
  become private, is from 2012). That avfilter_make_format64_list() was
  
  forgotten is probably a result of the confusion resulting from the
  
  libav-ffmpeg split.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavfilter/aeval.c
  • [DH] libavfilter/af_aresample.c
  • [DH] libavfilter/asrc_afirsrc.c
  • [DH] libavfilter/asrc_anoisesrc.c
  • [DH] libavfilter/asrc_anullsrc.c
  • [DH] libavfilter/asrc_hilbert.c
  • [DH] libavfilter/asrc_sinc.c
  • [DH] libavfilter/asrc_sine.c
  • [DH] libavfilter/avf_showcqt.c
  • [DH] libavfilter/formats.c
  • [DH] libavfilter/formats.h
  • [DH] libavfilter/src_movie.c

• cbs_mpeg2 : Fix parsing of picture and slice headers

  20 juin 2019, par Andreas Rheinhardt

  cbs_mpeg2 : Fix parsing of picture and slice headers
  1. The extra information in slice headers was parsed incorrectly :
  
  In the first reading pass to derive the length of the extra information,
  
  one should look at bits n, n + 9, n + 18, ... and check whether they
  
  equal one (further extra information) or zero (end of extra information),
  
  but instead bits n, n + 8, n + 16, ... were inspected. The second pass
  
  of reading (where the length is already known and the bytes between the
  
  length-determining bits are copied into a buffer) did not record what
  
  was in bits n, n + 9, n + 18, ..., presuming they equal one. And during
  
  writing, the bytes in the buffer are interleaved with set bits and
  
  written. This means that if the detected length of the extra information
  
  was greater than the real length, the output was corrupted. Fortunately
  
  no sample is known that made use of this mechanism : The extra information
  
  in slices is still marked as reserved in the specifications. cbs_mpeg2
  
  is now ready in case this changes.
  2. Furthermore, the buffer is now padded and slightly different, but
  
  very similar code for reading resp. writing has been replaced by code
  
  used for both. This was made possible by a new macro, the equivalent
  
  to cbs_h2645's fixed().
  3. These changes also made it possible to remove the extra_bit_slice
  
  element from the MPEG2RawSliceHeader structure. Said element was always
  
  zero except when the detected length of the extra information was less
  
  than the real length.
  4. The extra information in picture headers (which uses essentially the
  
  same syntax as the extra information in slice headers) has simply been
  
  forgotten. This meant that if this extra information was present, it was
  
  discarded during reading ; and unfortunately writing created invalid
  
  bitstreams in this case (an extra_bit_picture - the last set bit of the
  
  whole unit - indicated that there would be a further byte of data,
  
  although the output didn't contain said data).
  This has been fixed ; both types of extra information are now parsed via
  
  the same code and essentially passed through.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavcodec/cbs_mpeg2.c
  • [DH] libavcodec/cbs_mpeg2.h
  • [DH] libavcodec/cbs_mpeg2_syntax_template.c