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

Les articles publiés sur le site

• avutil/frame : move side data helpers to a new file

  23 janvier, par James Almer

  avutil/frame: move side data helpers to a new file
  
  Should reduce clutter in frame.c, plus allow us to make opaque changes to
  side data handling.
  
  Signed-off-by: James Almer <jamrial@gmail.com>
  

  • [DH] libavutil/Makefile
  • [DH] libavutil/frame.c
  • [DH] libavutil/side_data.c
  • [DH] libavutil/side_data.h

• avcodec/nvenc : Enable recovery point SEI for intra refresh mode

  23 janvier, par Zhao Zhili

  avcodec/nvenc: Enable recovery point SEI for intra refresh mode
  
  Otherwise all frames can be dropped after seek without the
  output_corrupt/showall flags.
  
  Signed-off-by: Zhao Zhili <zhilizhao@tencent.com>
  Reviewed-by: Timo Rothenpieler <timo@rothenpieler.org>
  

  • [DH] libavcodec/nvenc.c

• avcodec/hevc : Parse recovery point SEI

  23 janvier, par Zhao Zhili

  avcodec/hevc: Parse recovery point SEI
  
  Signed-off-by: Zhao Zhili <zhilizhao@tencent.com>
  

  • [DH] libavcodec/hevc/hevcdec.c
  • [DH] libavcodec/hevc/sei.c
  • [DH] libavcodec/hevc/sei.h

• rtmpproto : Avoid rare crashes in the fail : codepath in rtmp_open

  23 janvier, par Martin Storsjö

  rtmpproto: Avoid rare crashes in the fail: codepath in rtmp_open
  
  When running the cleanup in rtmp_close on failures in rtmp_open,
  we can in rare cases end up using rt->playpath, assuming that it
  is still set.
  
  The crash could happen if we hit the fail codepath in rtmp_open
  while publishing (rt->is_input == 0) with rt->state set to
  a value > STATE_FCPUBLISH.
  
  This would normally not happen while publishing; either we have
  an error (and rt->state <= STATE_FCPUBLISH) or we reach
  rt->state = STATE_PUBLISHING, and then we also return successfully
  from rtmp_open.
  
  The unexpected combination of states could happen if the server
  responds with e.g. "NetStream.Play.Stop" while expecting
  "NetStream.Publish.Start"; this sets rt->state to STATE_STOPPED,
  which also fulfills the condition "> STATE_FCPUBLISH".
  
  We don't need to free the rt->playpath/tcurl/flashver strings here;
  they're handled via AVOption, and thus are freed automatically when
  the protocol instance is freed (that's why they aren't freed
  manually within the rtmp_close function either).
  
  We also don't need to free the AVDictionary with options; it's
  owned by the caller.
  
  A smaller fix would be to just call rtmp_close before freeing
  the strings and dictionary, but as we don't need to free them
  at all, let's remove that redundant code.
  
  Signed-off-by: Martin Storsjö <martin@martin.st>
  

  • [DH] libavformat/rtmpproto.c

• avfilter/setpts : add option strip_fps to decide framerate handling

  23 janvier, par Gyan Doshi

  avfilter/setpts: add option strip_fps to decide framerate handling
  
  In f121d95, the outlink framerate was unconditionally unset.
  This breaks/bloats outputs from CFR muxers unless the user explicitly
  sets a sane framerate. And the most common invocation for setpts seen in
  workflows, our docs and across the web is `PTS-STARTPTS` or others of the
  general form `PTS+constant` which preserves the input framerate.
  
  Default value is false, which restores old behaviour.
  
  Fixes #11428
  

  • [DH] doc/filters.texi
  • [DH] libavfilter/setpts.c
  • [DH] tests/fate/hevc.mak
  • [DH] tests/fate/mov.mak
  • [DH] tests/filtergraphs/setpts