Recherche avancée

Sur d’autres sites (8629)

• I can't understand how to use ffmpeg in javascript (if it's even possible)

  28 juin, par Laimonas Rupeika

  Straight to the problem, I want to use ffmpeg in my javascript project for video editing. So I found cdn : <code class="echappe-js">&lt;script src=&quot;https://cdn.jsdelivr.net/npm/@salomvary/ffmpeg.js-umd@3.1.9001/ffmpeg-mp4.min.js&quot;&gt;&lt;/script&gt; which references to "https://github.com/Kagami/ffmpeg.js", which is ffmpeg port to javascript as I understand ?
I don't get any errors on import, but if I try loading ffmpeg :

  


  // Initialize FFmpeg after the GAPI client is loaded
  const ffmpeg = createFFmpeg({ log: true });

  // // Load the FFmpeg library
  await ffmpeg.load();


  


  I get error : Uncaught (in promise) ReferenceError: createFFmpeg is not defined at initializeGapiClient (index:89:18) and it also messes my whole project. So if possible, how can I use ffmpeg in pure javascript, not Node.js. Should I download ffmpeg library files and then include them in project, I'm totally lost at this.

  


• Can no longer get ffmpeg to run in Terminal on macOS

  31 décembre 2023, par Chewie The Chorkie

  Here's a command I tried to run which always worked :

  


  Mac-mini:images Admin$ ffmpeg -r 30  -f image2 -s 1080x1080 -i %d.png -vcodec h264 -crf 25  -pix_fmt yuv420p zVideo.mp4


  


  The output I get is :

  


  dyld[94095]: Library not loaded: /usr/local/opt/theora/lib/libtheoraenc.1.dylib
  Referenced from: <20EBE016-0DD0-3F29-96CD-D22BC2E40B38> /usr/local/Cellar/ffmpeg/6.1.1/bin/ffmpeg
  Reason: tried: '/usr/local/opt/theora/lib/libtheoraenc.1.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/theora/lib/libtheoraenc.1.dylib' (no such file), '/usr/local/opt/theora/lib/libtheoraenc.1.dylib' (no such file)
Abort trap: 6


  


  I've tried reinstalling ffmpeg, installing the command line tools from Xcode, and Xcode itself.

  


• avformat/aviobuf : Avoid allocating buffer when using dynamic buffer

  27 novembre 2019, par Andreas Rheinhardt

  avformat/aviobuf : Avoid allocating buffer when using dynamic buffer
  Up until now, using a dynamic buffer entailed at least three
  
  allocations : One for the AVIOContext, one for the AVIOContext's opaque
  
  (which, among other things, contains the small write buffer), and one
  
  for the big buffer that is independently allocated that is returned when
  
  calling avio_close_dyn_buf().
  It is possible to avoid the third allocation if one doesn't use a
  
  packetized dynamic buffer, if all the data written so far fit into the
  
  write buffer and if one does not require the actual (big) buffer to have
  
  an indefinite lifetime. This is done by making avio_get_dyn_buf() return
  
  a pointer to the data in the write buffer if nothing has been written to
  
  the main buffer yet. The dynamic buffer will then be freed using
  
  ffio_free_dynamic_buffer (which needed to be modified not to call
  
  avio_close_dyn_buf() internally).
  So a typical use-case like :
  size = avio_close_dyn_buf(dyn_pb, &buf) ;
  
  do something with buf
  
  av_free(buf) ;
  can be converted to :
  size = avio_get_dyn_buf(dyn_pb, &buf) ;
  
  do something with buf
  
  ffio_free_dynamic_buffer(&dyn_pb) ;
  In more complex scenarios this can simplify freeing as well, because it
  
  is now clear that freeing always has to be performed via
  
  ffio_free_dynamic_buffer().
  Of course, in case this saves an allocation it also saves a memcpy.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavformat/aviobuf.c