Recherche avancée

Sur d’autres sites (7521)

• avformat/mux : Fix double-free when using AVPacket.opaque_ref

  1er septembre 2021, par Andreas Rheinhardt

  avformat/mux : Fix double-free when using AVPacket.opaque_ref
  Up until now, ff_write_chained() copied the packet (manually, not with
  
  av_packet_move_ref()) from a packet given to it to a stack packet whose
  
  timing and stream_index is then modified before being sent to another
  
  muxer via av_(interleaved_)write_frame(). Afterwards it is intended to
  
  sync the fields of the packet relevant to freeing again ; yet this only
  
  encompasses buf, side_data and side_data_elems and not the newly added
  
  opaque_ref. The other fields are not synced so that the returned packet
  
  can have a size > 0 and data != NULL despite its buf being NULL (this
  
  always happens in the interleaved codepath ; before commit
  
  fe251f77c80b0512ab8907902e1dbed3f4fe1aad it could also happen in the
  
  noninterleaved one). This leads to double-frees if the interleaved
  
  codepath is used and opaque_ref is set.
  This commit therefore changes this by directly reusing the packet
  
  instead of a spare packet. Given that av_write_frame() does not
  
  change the packet given to it, one only needs to restore the timing
  
  information to return it as it was ; for the interleaved codepath
  
  it is not possible to do likewise*, because av_interleaved_write_frame()
  
  takes ownership of the packets given to it and returns blank packets.
  
  But precisely because of this users of the interleaved codepath
  
  have no legitimate expectation that their packet will be returned
  
  unchanged. In line with av_interleaved_write_frame() ff_write_chained()
  
  therefore returns blank packets when using the interleaved codepath.
  Making the only user of said codepath compatible with this was trivial.
  * : Unless one wanted to create a full new reference.
  Reviewed-by : Lynne <dev@lynne.ee>
  
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavformat/internal.h
  • [DH] libavformat/mux.c
  • [DH] libavformat/segment.c

• Automator shell script (using ffmpeg) won't run on other machine

  24 mai 2014, par kava

  I have an Automator patch that runs a shell script that calls ffmpeg on a 10.9.3 mac.

  I just try to call it via

  ffmpeg

  for test reasons without any arguments.

  but it returns

  ffmpeg: command not found. 

  But I can open ffmpeg regularly from terminal AND I can run the script on my other machine (10.9.2)

  What’s wrong ?

  EDIT : I also tried to add :

  /opt/local/bin

  in the shell script to the path variable, but it still won’t run.
  also

  /opt/local/bin/ffmpeg -arguments....

  won’t run

• Revision 7050074756 : Make the api behavior conform to api spec. When no more data is available, vpx_

  1er août 2014, par Hangyu Kuang

  Changed Paths :
   Modify /test/decode_test_driver.cc

  
   Modify /vp8/vp8_dx_iface.c

  
   Modify /vp9/vp9_dx_iface.c

  
  
  Make the api behavior conform to api spec.

  When no more data is available, vpx_codec_decode should
  be called with NULL as data and 0 as data_sz.

  vpx_codec_get_frame iterates over a list of the frames
  available for display. The iterator storage should be initialized
  to NULL to start the iteration. Iteration is complete when this
  function returns NULL.

  Also change the unit test to conform to the api spec.

  Change-Id : I4b258b309f5df3d37d10c82f01492c0394181c2a