Recherche avancée

Sur d’autres sites (11036)

• mediastreamsegmenter over UDP vs FFmpeg pipe

  6 août 2015, par Joseph K

  I’m trying to pipe FFMpeg output into mediastreamsegmenter to create HLS.

  However this procedure :

  Ffmpeg -i {file} <other arguments="arguments"> -f mpegts | mediastreamsegmenter <arguments>
  
  </arguments></other>

  Makes the segmenter create an index for a VOD using the output of FFmpeg rather than a live event. Re-executing this instruction would override the manifest file for every output of ffmpeg.

  Is there any way I could have a live ffmpeg pipe to mediastreamsegmenter ? I don’t want to use UDP as it doesn’t make sense here. Video fragments are all local.

• phplondon conference 2008

  2 mars 2008, par Mikko Koppanen — Everything else, Imagick, PHP stuff, phplondon08

  To summarize it : I had fun My conference preparations started about two weeks before the conference. The PHPLondon fellows (Paul, Matt and Richard) asked me to do a small presentation about Imagick at the pre-conference social event. The presentation I assembled ended up being a little over two hours, give or take. The hardest part was to trim down from two hours to about 40 minutes (I didn’t want to bore the people with too many code examples). The slides are available at http://valokuva.org/talks if you need them for some reason.

  My conference day was pretty hectic from the beginning to the end. I gave a few demos about the products that we represent and the moment I opened my mouth for the first time people started leaving the room. I hope that it had something to do with the “My Framework is better than yours ?” talk starting at the same time

  I met quite a lot of new people at the conference and of course it was nice to see the familiar faces from other conferences and PHPLondon meetings. I was especially happy that I was able to answer the questions Nigel James had

  A huge thanks to the organizers for making this day possible !

• Unhandled stream error in pipe : write EPIPE in Node.js

  28 novembre 2013, par Michael Romanenko

  The idea is to serve screenshots of RTSP video stream with Express.js server. There is a continuously running spawned openRTSP process in flowing mode (it's stdout is consumed by another ffmpeg process) :

  function spawnProcesses (camera) {
  
    var openRTSP = spawn('openRTSP', ['-c', '-v', '-t', camera.rtsp_url]),
  
        encoder = spawn('ffmpeg', ['-i', 'pipe:', '-an', '-vcodec', 'libvpx', '-r', 10, '-f', 'webm', 'pipe:1']);
  
  
  
    openRTSP.stdout.pipe(encoder.stdin);
  
  
  
    openRTSP.on('close', function (code) {
  
      if (code !== 0) {
  
        console.log('Encoder process exited with code ' + code);
  
      }
  
    });
  
  
  
    encoder.on('close', function (code) {
  
      if (code !== 0) {
  
        console.log('Encoder process exited with code ' + code);
  
      }
  
    });
  
  
  
    return { rtsp: openRTSP, encoder: encoder };
  
  }
  
  
  
  ...
  
  
  
  camera.proc = spawnProcesses(camera);

  There is an Express server with single route :

  app.get('/cameras/:id.jpg', function(req, res){
  
    var camera = _.find(cameras, {id: parseInt(req.params.id, 10)});
  
    if (camera) {
  
      res.set({'Content-Type': 'image/jpeg'});
  
      var ffmpeg = spawn('ffmpeg', ['-i', 'pipe:', '-an', '-vframes', '1', '-s', '800x600', '-f', 'image2', 'pipe:1']);
  
      camera.proc.rtsp.stdout.pipe(ffmpeg.stdin);
  
      ffmpeg.stdout.pipe(res);
  
    } else {
  
      res.status(404).send('Not found');
  
    }
  
  });
  
  
  
  app.listen(3333);

  When i request http://localhost:3333/cameras/1.jpg i get desired image, but from time to time app breaks with error :

  stream.js:94
  
    throw er; // Unhandled stream error in pipe.
  
          ^
  
  Error: write EPIPE
  
      at errnoException (net.js:901:11)
  
      at Object.afterWrite (net.js:718:19)

  Strange thing is that sometimes it successfully streams image to res stream and closes child process without any error, but, sometimes, streams image and falls down.

  I tried to create on('error', ...) event handlers on every possible stream, tried to change pipe(...) calls to on('data',...) constructions, but could not succeed.

  My environment : node v0.10.22, OSX Mavericks 10.9.

  UPDATE :

  I wrapped spawn('ffmpeg',... block with try-catch :

  app.get('/cameras/:id.jpg', function(req, res){
  
  ....
  
      try {
  
        var ffmpeg = spawn('ffmpeg', ['-i', 'pipe:', '-an', '-vframes', '1', '-s', '800x600', '-f', 'image2', 'pipe:1']);
  
        camera.proc.rtsp.stdout.pipe(ffmpeg.stdin);
  
        ffmpeg.stdout.pipe(res);
  
      } catch (e) {
  
        console.log("Gotcha!", e);
  
      }
  
  ....
  
  });

  ... and this error disappeared, but log is silent, it doesn't catch any errors. What's wrong ?