Recherche avancée

Sur d’autres sites (10329)

• 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 !

  


• Edit audio files on the server with Meteor

  28 décembre 2015, par Mohammed Hussein

  I am building a Meteor application to split uploaded audio files.

  I upload the audio files and store them using GridFS :

  child = Npm.require('child_process');
  
  
  
  var fs = Npm.require('fs');
  
  
  
  storagePath= fs.realpathSync(process.env.PWD+'/audio');
  
  
  
  StaticServer.add('/audio', clipsPath);

  and then using a method I split the audio file using :

  child.exec(command);

  the command is the ffmpeg command used to cut the source audio file and store it on the storagePath.

  The application worked fine locally but when I tried to deploy it to digital ocean I got errors, stating that the file /audio does not exist.
  I use mupx to deploy and the error appears after "verifying deployment".

  Here is the error :

      -----------------------------------STDERR-----------------------------------
  
      eteor-dev-bundle@0.0.0 No README data
  
      => Starting meteor app on port:80
  
  
  
      /bundle/bundle/programs/server/node_modules/fibers/future.js:245
  
                                                      throw(ex);
  
                                                            ^
  
      Error: ENOENT, no such file or directory '/bundle/bundle/audio'
  
          at Object.fs.lstatSync (fs.js:691:18)
  
          at Object.realpathSync (fs.js:1279:21)
  
          at server/startup.js:10:20
  
          at /bundle/bundle/programs/server/boot.js:249:5
  
      npm WARN package.json meteor-dev-bundle@0.0.0 No description
  
      npm WARN package.json meteor-dev-bundle@0.0.0 No repository field.
  
      npm WARN package.json meteor-dev-bundle@0.0.0 No README data
  
      => Starting meteor app on port:80
  
  
  
      /bundle/bundle/programs/server/node_modules/fibers/future.js:245
  
                                                      throw(ex);
  
                                                            ^
  
      Error: ENOENT, no such file or directory '/bundle/bundle/audio'
  
          at Object.fs.lstatSync (fs.js:691:18)
  
          at Object.realpathSync (fs.js:1279:21)
  
          at server/startup.js:10:20
  
          at /bundle/bundle/programs/server/boot.js:249:5
  
  
  
      => Redeploying previous version of the app
  
  
  
      -----------------------------------STDOUT-----------------------------------
  
  
  
      To see more logs type 'mup logs --tail=50'
  
  
  
      ----------------------------------------------------------------------------

  The main question is how to generate an output file using ffmpeg and store it in a place where I can access it and display it in the browser.

• ffmpeg won't execute properly in google app engine standard nodejs

  3 septembre 2019, par tommyc38

  I have tried for three full days to get GAE (standard - nodejs) to run a simple video transcoder from MOV to MP4 using ffmpeg. I have tried using ffluent-ffmpeg, kicking off a child process (e.g. spawn), and nothing works. As soon as it hits the call to the executable it always errors. I have confirmed ffmpeg is installed and even tried using ffmpeg-static. Moreover, I have it working on my local machine with no problems (using all of the aforementioned ways).

  I have also tried logging the errors and nothing is really all that helpful. I can see its working through any installed package including ffmpeg (system package).

  Below is the pseudo code...step three is where the problem occurs.

  1. Send file name to GAE endpoint
  2. Download the file from google cloud storage to a temp file
  3. Transcode using ffmpeg
  4. Upload temp file to google cloud storage
  5. Remove old google cloud storage file
  6. Remove temp file

  The file I am using to test is 6MB...a 5 second video I took on my iPhone. Thank you in advance.

  UPDATE : I successfully deployed the exact same code to Node Flex environment and everything works great. I wasn’t able to get any errors in the standard environment that directed me where to look but my guess is it has something to do with how it stores the file I pipe into FFMPEG on GAE Node Standard. The docs say its a virtual file system that uses RAM. I’d love to hear if anybody managed to get it working in the standard environment.