Recherche avancée

Sur d’autres sites (3686)

• How to use the latest version of @ffmpeg/ffmpeg in a React.js project ?

  21 janvier, par Muzammil Raza

  I'm working on a React.js project where I need to process videos in the browser using @ffmpeg/ffmpeg. I noticed that the package has been updated recently, and the API and functions have changed.

  


  In the older version, I used to import the package and functions like this :

  


  import { createFFmpeg, fetchFile } from '@ffmpeg/ffmpeg';


  


  However, in the latest version, I see that the import has changed to :

  


  import { FFmpeg } from '@ffmpeg/ffmpeg';


  


  and all new functions are changed I have checked in by log :

  


  I have check by console ffmpeg, it show :

  


  createDir: path => {…}
deleteDir: path => {…}
deleteFile: path => {…}
exec: ƒ ( /** ffmpeg command line args */ args)
listDir: path => {…}
load: ƒ ()
loaded: true
readFile: ƒ (path)
rename: (oldPath, newPath) => {…}
terminate: () => {…}
writeFile: (path, data) => {…}


  


  I'm not sure about the changes in the API and functions, and I couldn't find any updated documentation or guides on how to use the latest version of @ffmpeg/ffmpeg in a React.js project.

  


  I have task of video processing for streaming and need to add logo in video.

  


  Could someone please provide guidance on how to use the latest version of @ffmpeg/ffmpeg in a React.js project ? Specifically, I'm looking for information on the changes in the API, the new function names, and how to perform video processing tasks with the latest version.

  


  If anyone has experience with the latest version of @ffmpeg/ffmpeg or knows the updated usage, any help or examples would be greatly appreciated. Thank you !

  


• Cleaning up after av_frame_get_buffer

  30 juillet 2022, par Jason C

  There are two aspects of my question. I'm using libav, ffmpeg, 3.1.

  



  ---

  



  First, how do you appropriately dispose of a frame whose buffer has been allocated with av_frame_get_buffer ? E.g. :

  



  AVFrame *frame = av_frame_alloc();
frame->width = ...;
frame->height = ...;
frame->format = ...;
av_frame_get_buffer(frame, ...);


  



  Do any buffers have to be freed manually, beyond the call to av_frame_free(frame) ? The documentation doesn't mention anything special, but in my experience the ffmpeg documentation often leaves out important details, or at least hides them in places far away from the obvious spots. I took a look at the code for av_frame_free and av_frame_unref but it branched out quite a bit and I couldn't quite determine if it covered everything.

  



  ---

  



  Second, if something beyond av_frame_free needs to be done, then is there any catch-all way to clean up a frame if you don't know how its data has been allocated ? For example, assuming someBuffer is already allocated with the appropriate size :

  



  AVFrame *frame2 = av_frame_alloc();
frame2->width = ...;
frame2->height = ...;
frame2->format = ...;
av_image_fill_arrays(frame2->data, frame2->linesize, someBuffer, 
                     frame2->format, frame2->width, frame2->height, 1);


  



  Is there a way to free both frame and frame2 in the above examples using the exact same code ? That is frame and its data should be freed, and frame2 should be freed, but not someBuffer, since libav did not allocate it.

  


• Cleaning up after av_frame_get_buffer

  4 novembre 2016, par Jason C

  There are two aspects of my question. I’m using libav, ffmpeg, 3.1.

  ---

  First, how do you appropriately dispose of a frame whose buffer has been allocated with av_frame_get_buffer ? E.g. :

  AVFrame *frame = av_frame_alloc();
  
  frame->width = ...;
  
  frame->height = ...;
  
  frame->format = ...;
  
  av_frame_get_buffer(frame, ...);

  Do any buffers have to be freed manually, beyond the call to av_frame_free(frame) ? The documentation doesn’t mention anything special, but in my experience the ffmpeg documentation often leaves out important details, or at least hides them in places far away from the obvious spots. I took a look at the code for av_frame_free and av_frame_unref but it branched out quite a bit and I couldn’t quite determine if it covered everything.

  ---

  Second, if something beyond av_frame_free needs to be done, then is there any catch-all way to clean up a frame if you don’t know how its data has been allocated ? For example, assuming someBuffer is already allocated with the appropriate size :

  AVFrame *frame2 = av_frame_alloc();
  
  frame2->width = ...;
  
  frame2->height = ...;
  
  frame2->format = ...;
  
  av_image_fill_arrays(frame2->data, frame2->linesize, someBuffer, 
  
                       frame2->format, frame2->width, frame2->height, 1);

  Is there a way to free both frame and frame2 in the above examples using the exact same code ? That is frame and its data should be freed, and frame2 should be freed, but not someBuffer, since libav did not allocate it.