Recherche avancée

Sur d’autres sites (10360)

• Node.js, stream pipe output data to client with socket io-stream

  22 mai 2018, par Empha

  Sorry for a repeating topic, but i’ve searched and experimented for 2 days now and i haven’t been able to solve the problem.

  I am trying to live stream pictures every 1 second to a client via socket.io-stream using the following code :

  var args = [
  
      "-i",
  
      "/dev/video0",
  
      "-s",
  
      "1280x720",
  
      "-qscale",
  
      1,
  
      "-vf",
  
      "fps=1",
  
      config.imagePath,
  
      "-s",
  
      config.imageStream.resolution[0],
  
      "-f",
  
      "image2pipe",
  
      "-qscale",
  
      1,
  
      "-vf",
  
      "fps=1",
  
      "pipe:1"
  
  ];
  
  camera = spawn("avconv", args);    // avconv = ffmpeg

  The settings are good, and the process writes to stdout successfully. I capture all outgoing image data using this simplified code :

  var ss = require("socket.io-stream");
  
  camera.stdout.on("data", function(data) {
  
      var stream = ss.createStream();
  
      ss(socket).emit("img", stream, "newImg");
  
      // how do i write the data-object to the stream?
  
      // fs.createReadStream(imagePath).pipe(stream);
  
  });

  "socket" comes from the client using the socket.io-package, no problem there. So what i am doing is that i listen to the stdout-pipe for the "data" event. That data gets passed to the function above. That means that at this stage "data" is not a stream, its a "<buffer></buffer>code>"-object, and therefore i cannot stream it like i could previously using the commented createReadStream-statement where i read the image from disk. <strong>How do i stream the data (Buffer at this stage) to the client? Can i do this differently, perhaps not using socket.io-stream?</strong> "data" is just one part of the whole image, so perhaps two or three "data"-objects need to be put together to form the complete image.

  I tried using "stream.write(data, "binary") ;" which did transfer the Buffer-objects, problem is that there is not end of stream-event and therefore i do not know when an image is complete. I tried registering to stdout.on "close", "end", "finish", nothing triggers. Am i missing something ? Am i making it overly complex ? The reasoning behind my implementation is that i need a new stream for each complete image, is that right ?

  Thanks alot !

• RTSP Client for H264 Audio/Video Stream

  10 juin, par Jean-Philippe Encausse

  I'm looking for a simple way to get data of an IP Camera RTSP Stream (using H264 Audio/Video) and get on the other side

  



  

  • a frame by frame byte[]

  


  • a stream of the audio

  


  



  After many research

  



  

  • EmguCV Capture seems hanging forever (no answer from forum)

  


  • There is many (too big) RTSP Server few decode H264

  


  • There is "slow" ffmpeg wrapper

  


  • There is some managed DirectShow wrapper

  


  



  So I don't know where to go ? And how to do this ?

  



  It seems iSpyCamera is doing the job but it's a big project not a little library to query ip cameras.

  


• RTSP Client for H264 Audio/Video Stream

  1er avril 2015, par Jean-Philippe Encausse

  I’m looking for a simple way to get data of an IP Camera RTSP Stream (using H264 Audio/Video) and get on the other side

  • a frame by frame byte[]
  • a stream of the audio

  After many research

  • EmguCV Capture seems hanging forever (no answer from forum)
  • There is many (too big) RTSP Server few decode H264
  • There is "slow" ffmpeg wrapper
  • There is some managed DirectShow wrapper

  So I don’t know where to go ? And how to do this ?

  It seems iSpyCamera is doing the job but it’s a big project not a little library to query ip cameras.