Recherche avancée

Sur d’autres sites (5243)

• lavf/matroskaenc : Fix memory leak after write trailer

  4 avril 2019, par Jun Zhao

  lavf/matroskaenc : Fix memory leak after write trailer
  Fix memory leak after write trailer for #7827, only store a audio
  
  packet whose buffer has size greater than zero in cur_audio_pkt.
  Audio packets with size zero, but with side-data currently lead to
  
  memleaks, in the Matroska muxer, because they are not properly freed :
  They are currently put into an AVPacket in the MatroskaMuxContext to
  
  ensure that the necessary audio is always available for a new cluster,
  
  but are only written and freed when their size is > 0.
  As the only use we have for such packets consists in updating the
  
  CodecPrivate it makes no sense to store these packets at all and this
  
  is how this commit solves the memleak.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@googlemail.com>
  
  Signed-off-by : Jun Zhao <barryjzhao@tencent.com>
  

  • [DH] libavformat/matroskaenc.c

• issue in converting a stream of images that is jittery and lossy into a video (using ffmpeg or otherwise)

  17 mars 2019, par ksridhar

  i have a program that is the source for png images that are sent out on its stdout. this program is prone to lose images as well have jitter (not deliver them on time precisely i.e. 25 frames/sec).

  i tried the following with ffmpeg

  image_streamer.sh | ffmpeg -vcodec png -i - -vf fps=25 -vcodec libx264 -y foo.mp4.

  it was noticed that (a) when the input rate was wavering around 25 frames/sec with no drops the mp4 file was created fine but when (b) there were drops by the image_streamer.sh the fps filter did not duplicate images. i understand that there is no pts information in this case.

  i read several questions/answers around this issue but there we related to files and not a pipe.

  There was also a thread of conversation a long time back (https://ffmpeg.org/pipermail/ffmpeg-user/2012-December/011855.html) but it lead to a dead end.

  i am quite naive to ffmpeg. i hope that this question is not something really stupid.

• avcodec/mpeg4videodec : Fix nonsense warning

  11 mars 2019, par Andreas Rheinhardt

  avcodec/mpeg4videodec : Fix nonsense warning
  Since db772308941a2a338c7809f90d347219a6a93074 parsing of
  
  mpeg4-extradata lead to a "Failed to parse extradata" warning, because
  
  ff_mpeg4_decode_picture_header returns AVERROR_INVALIDDATA in case that
  
  no VOP was found. This patch adds a parameter to signify whether a
  
  header (where the absence of a VOP does not raise an error) or not is
  
  parsed. The first mode is of course used for parsing headers.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@googlemail.com>
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavcodec/h263dec.c
  • [DH] libavcodec/mpeg4video.h
  • [DH] libavcodec/mpeg4video_parser.c
  • [DH] libavcodec/mpeg4videodec.c