Recherche avancée

Sur d’autres sites (8427)

• Pipe images to video with flutter_ffmpeg in flutter

  10 août 2020, par Avi Sangray

  I'm trying to manipulate images from image stream received from camera in flutter and then save them to a video using flutter_ffmpeg.
i'm able to open a pipe but code is unresponsive after that
here's the code

  


  controller.startImageStream((CameraImage camimage) {

  //do manipulations and get pointer of the data returned from the function to a List
  List imgData = add_filters_and_text(camimage);
  imglib.Image img =  imglib.Image.fromBytes(_savedImage.height, _savedImage.width, imgData);

  _flutterFFmpegConfig.registerNewFFmpegPipe().then((pipe1) {
     print("New ffmpeg pipe at $pipe1");
     var exec0 = "-y -i " + pipe1 + " -filter:v loop=loop=25*3:size=1 -c:v mpeg4 -r 25 file2.mp4";
     _flutterFFmpeg.execute(exec0).then((rc0){
 // how to pass frame??
   });
});


  


• Nodejs + FFMPEG + AWS EC2 - Broken Pipe

  5 juillet 2020, par Jordan H.

  I have an AWS EC2 instance (t2.micro) running a Nodejs script. This script awaits an FFMPEG stream via HTTP and re-broadcasts it via a websocket server (see websocket-relay.js here). On the same EC2 instance, I use FFMPEG to stream from a file to the aforementioned HTTP input. After exactly one (1) minute, FFMPEG generates the following error :

  


  ------ BEGINNING OF ERROR ------

  


  av_interleaved_write_frame() : Broken pipe

  


  Last message repeated 1 times Error writing trailer of http://127.0.0.1:8081/secretkey :

  


  Broken pipe frame= 1209 fps= 20 q=1.0 Lsize= 49968kB time=00:00:59.89 bitrate=6834.5kbits/s speed=0.998x video:54878kB audio:0kB subtitle:0kB other streams:601kB global headers:0kB muxing overhead : unknown

  


  [http @ 0x62a81c0] URL read error : End of file Conversion failed !

  


  ------ END OF ERROR ------

  


  I do not receive any errors when running this on a local machine. The problem seems to be isolated to running the combination of FFMPEG and the Nodejs script on AWS EC2. Any thoughts on what is causing the connection between FFMPEG and Nodejs to break ?

  


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

  13 juillet 2020, 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 ?