Recherche avancée

Sur d’autres sites (8366)

• Connect a remote Ip camera as a Webrtc client

  5 avril 2017, par idosh

  I have 2 cameras :

  • An internal webcam embedded in my laptop.
  • A remote IP camera that is connected to my laptop through Wifi (transmits TCP, raw H264 data - no container). I’m getting the stream using node.js.

  My goal is to create a Webrtc network and connect the remote camera as another client.

  I’m trying to figure out possible solutions :

  • My naive thinking was that I would stream the remote camera payload to the browser. But as I came to understand the browser can’t handle the stream without a container. Fair enough. But I don’t understand why it does handle the video stream that arrives from my internal camera (from the navigator.getUserMedia() function). what’s the difference between the two streams ? why can’t I mimic the stream from the remote camera as the input ?
  • To bypass this problem I thought about creating a virtual camera using Manycam (or Manycam like app). To accomplish that I need to convert my TCP stream into an RTP stream (in order to feed Manycam). Though I did saw some info in ffmpeg command line, I couldn’t find info in their node.js api package "fluent-ffmpeg". Is it possible to do it using fluent-ffmpeg ? Or only using the command line tool ? Would it require another rtp server in the middle such as this one ?.
  • Third option I read about is using node.js as a client in Webrtc. I saw it was implemented in "simple-peer". I tried it out using their co-work with socket.io (socket.io-p2p). unfortunately I couldn’t get it to work / : When i’m trying to create a socket/peer in the server - it throws errors, as it expect options that are only available on the client-side (like window, location, etc.). Am I doing something wrong ? maybe there is more suitable framework for this matter ?
  • Forth option is to use a streaming server in the middle such as Kurnto. From my understanding it receives rtp as an input and transmits it as a webrtc client. I feel it’s the most excessive option, but maybe it’s not so bad (I have to admit that I haven’t investigate this option yet).

  any thoughts ?

  thanks !

• RTSP Feed Screen Cutoff

  25 août 2021, par Jackson Medina

  Recently I have been trying to consume the RTSP stream from a Vivitar Folding Drone. By reverse-engineering the .apk file for the Vivitar Folding Drone app, I was able to find that the RTSP address for the drone is rtsp://192.168.1.1:7070/webcam however, whenever I consume this stream through VLC or FFPLAY, most of the feed gets cut off and replaced with a green screen or gray screen (depends on whether I save to a .mjpeg file or a .dump file). What is the cause of this problem and what steps can I take to fix it ?

  


  

  


  When using FFPLAY, I use the following command :

  


  ffplay -i -rtsp_flags rtsp://192.168.1.1:7070/webcam


  


  I also receive this error when I first start consuming the stream with ffplay :

  


  [swscaler @ 00000240daeadf80] deprecated pixel format used, make sure you did set range correctly


  


  I receive this error message for about every frame of the stream :

  


  [mjpeg @ 00000240d6226b00] mjpeg_decode_dc: bad vlc: 0:0 (00000240d6266050)
[mjpeg @ 00000240d6226b00] error dc
[mjpeg @ 00000240d6226b00] error y=1 x=0


  


  NOTE : I am unsure if this is relevant, but the Vivitar Drone creates its own wifi network that must be signed onto if you want to consume the RTSP stream

  


  Also, the drone feed works perfectly fine when viewed through the Vivitar Folding Drone app. I just can't seem to get it to display properly through FFPLAY, FFMPEG, or VLC.

  


  UPDATE :

  


  Upon further inspection, it seems like the Vivitar Folding Drone may not be sending all of the jpg data for a single frame. Here is an image generated by unaltered byte data sent through the RTSP feed.


  


  I noticed three things from this image :

  


  

  1. The image appears to be missing large chunks of data.

  


  2. The image appears to be redshifted

  


  3. The two visible portions of the image should be sequential (it looks as though the second visual portion lines up with the first). An example of this can be seen below.

  


  


• Revision 36980 : La bonne méta dans la base pour éviter le message "Echec" en 2.1 Une ...

  5 avril 2010, par kent1@… — Log

  La bonne méta dans la base pour éviter le message "Echec" en 2.1
  Une icone pour les boutons de récupération d’infos
  Certains codecs (libx264) nécessitent de pouvoir diviser la taille de la video par 2 ... on fait en sorte que cela passe