Recherche avancée

Sur d’autres sites (4892)

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

• NodeJS Server Start FFMPEG capture of UDP stream without blocking

  1er mars 2016, par shreddish

  I have a nodejs server running on localhost that examines the incoming URL and if it sees a .m3u8 extension serves up the HLS streaming files to the client for playback. I also have the server start an FFMPEG child process to convert a UDP stream to HLS.

  An example URL passed to the server might be
  http://localhost:7070/udphelp/239.255.1.1:59001/out.m3u8

  Right now my server extracts that UDP address, starts FFMPEG to convert that UDP stream to HLS fine. However, I am finding that since UDP streams are "never ending" this is causing a block on the server from serving up the .m3u8 and .ts files for playback.

  Is there a way to get FFMPEG to not block the server while its running ? Or is there a better server to be using for this other than nodejs ?

• NodeJS HLS stall initial m3u8 for playback

  7 mars 2016, par shreddish

  I have a nodejs server running, when user enters the follow address

  http://localhost:7070/udp/239.1.1.1:1234/out.m3u8

  My server starts an ffmpeg child process that connects to that UDP stream and converts it to HLS segmented files.

  In order to give FFMPEG a chance to begin and start creating the first out.m3u8 file I call the FFMPEG process and then immediately set a timeout of about 8 seconds before the server responds to the request for the .m3u8 file.

  Eventually the video will start to play but only get through 2-3 .ts files before playback stops and the browser stops requesting additional .ts files.

  When it’s stalled, if I hit refresh (since FFMPEG is still running) it doesn’t try to start ffmpeg and delay the response. Instead it just immediately serves up the files being requested and playback works fine.

  So I am thinking that clearly something to do with delaying my response for that long is mucking up the playback of the stream. Is there a better way to wait for FFMPEG to start generating the HLS files and respond ?

  Here is the part of the server that is delaying the response.

  // Check if ffmpeg is running yet, also check to see if user has switched to a different udp address
  
          if (filename == "out.m3u8" && (!ffmpegRunning || udpAddress != runningUDPAddress)) 
  
              {
  
                  runFFMPEG(filename, udpAddress);
  
                  setTimeout(function() { streamFile(req, res, uri, filename); return; }, 8000);
  
              }
  
              else
  
              {
  
                  streamFile(req, res, uri, filename);
  
              }