Recherche avancée

Sur d’autres sites (6014)

• avformat/hls : reduce default max reload to 3

  15 mai 2023, par Michael Niedermayer

  avformat/hls : reduce default max reload to 3
  The 1000 did result in the appearance of a never ending reload loop
  The RFC mandates that "If the client reloads a Playlist file and finds that it has not
  
  changed, then it MUST wait for a period of one-half the target
  
  duration before retrying." and if it has changed
  
  "the client MUST wait for at least the target duration before attempting to reload the
  
  Playlist file again"
  Trying to reload 3 times seems a better default than 1000 given these
  
  durations
  Issue found by : Сергей Колесников
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavformat/hls.c

• avcodec : export motion vectors in frame side data on demand

  16 juillet 2014, par Clément Bœsch

  avcodec : export motion vectors in frame side data on demand
  The reasoning behind this addition is that various third party
  
  applications are interested in getting some motion information out of a
  
  video "for free" when it is available.
  It was considered to export other information as well (such as the intra
  
  information about the block, or the quantization) but the structure
  
  might have ended up into a half full-generic, half full of codec
  
  specific cruft. If more information is necessary, it should either be
  
  added in the "flags" field of the AVMotionVector structure, or in
  
  another side-data.
  This commit also includes an example exporting them in a CSV stream.
  

  • [DH] .gitignore
  • [DH] configure
  • [DH] doc/APIchanges
  • [DH] doc/Makefile
  • [DH] doc/codecs.texi
  • [DH] doc/examples/Makefile
  • [DH] doc/examples/extract_mvs.c
  • [DH] libavcodec/avcodec.h
  • [DH] libavcodec/mpegvideo.c
  • [DH] libavcodec/options_table.h
  • [DH] libavutil/Makefile
  • [DH] libavutil/frame.c
  • [DH] libavutil/frame.h
  • [DH] libavutil/motion_vector.h
  • [DH] libavutil/version.h

• avcodec/pthread_frame : Fix cleanup during init

  11 février 2021, par Andreas Rheinhardt

  avcodec/pthread_frame : Fix cleanup during init
  In case an error happened when setting up the child threads,
  
  ff_frame_thread_init() would up until now call ff_frame_thread_free()
  
  to clean up all threads set up so far, including the current, not
  
  properly initialized one.
  
  But a half-allocated context needs special handling which
  
  ff_frame_thread_frame_free() doesn't provide.
  
  Notably, if allocating the AVCodecInternal, the codec's private data
  
  or setting the options fails, the codec's close function will be
  
  called (if there is one) ; it will also be called if the codec's init
  
  function fails, regardless of whether the FF_CODEC_CAP_INIT_CLEANUP
  
  is set. This is not supported by all codecs ; in ticket #9099 it led
  
  to a crash.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavcodec/pthread_frame.c