Recherche avancée

Sur d’autres sites (8667)

• FFMPEG re-broadcast/proxy MJPEG stream

  10 septembre 2022, par Ollie Pugh

  I have an MJPEG stream coming from an RPI on my home network and have an NGINX acting as a proxy on an EC2.

  


  For the camera access the flow of stream to the user is the following

  


  RPi -> mjpeg-proxy (running on EC2) -> NGINX (running on same EC2) -> user

  


  the point of mjpeg-proxy is to reduce the load on the RPi and only have one stream to the Pi and allow the EC2 to distribute that one stream.

  


  Now this work fine-ish from my PC (on same network as Pi) the streams work perfectly. But when it comes to my phone on roaming data, the stream is super choppy and the latency grows massively (this project needs minimal latency, like sub 300ms).

  


  I can't understand why this would happen ? Because even when running of my local PC its going through the Proxy hosted in the cloud, so its not as if its an advantage to it being local ?

  


  the stream is fine on another device, e.g. my laptop, but thats on the same network as the RPi. But like I said, it shouldn't makea difference as its going through a proxy !

  


  I was wondering if using FFMPEG to re-stream the mjpeg stream would be beneficial as node is notoriously slow. But I don't really want to be writing my own mjpeg-proxy in C++ to speed this all up.

  


  I have looked online for answers to FFMPEG MJPEG proxy and have been very unsuccesful

  


• avformat/mlvdec : demux LJ92 huffman comressed frames

  13 décembre 2024, par Peter Ross

  avformat/mlvdec : demux LJ92 huffman comressed frames
  A minimal DNG header is added to each LJ92 compressed frame, allowing
  
  thme to be decoded by the TIFF decoder. The TIFF decoder is responsible
  
  for setting up the MJPEG decoder, signalling the correct s->bayer flag,
  
  and setting pix_fmt.
  The LJ92 compressed frames can be muxed out to DNG files, and manipulated
  
  in DNG software. Tested with darktable and rawtherapee.
  Contributor : South East <8billion.people@gmail.com>
  

  • [DH] libavformat/mlvdec.c

• FFmpeg : Is it better to make a application then using ffmepg directly

  14 juillet 2020, par Mirabeau

  For all my IP camera streams, I use, under Linux, ffmpeg by a bash script which allows me at the same time to manage :

  


  1/ Convert the RTSP streams to HTTP (HLS) for the "Live" and therefore which generates "m3u8" file and *.ts segments

  


  2/ Backup the stream for archiving (in increments of 5 minutes), a cron remove older files (xx days)

  


  ffmpeg -i "rtsp://[IP_CAM01]" -rtsp_transport tcp -c copy -map 0 -f segment -segment_time 300 -segment_atclocktime 1 -segment_format mkv "cam01-% 03d.mkv" -c copy -f segment -segment_list cam01.m3u8 -segment_list_flags + live -segment_time 2 -segment_list_size 20 -segment_wrap 20 cam01-% 03d.ts


  


  The question I ask myself, and the reason for this message is as follows :

  


  

  • would there be an interest (memory / cpu / speed) to develop a program (C/C++/other ?) to do the same thing by using the libraries of ffmpeg ?

  


  • or the "gain" and the interest would be so minimal that it is not worth the expenditure of energy and time ?

  


  


  I appeal to your feedback, your opinions, your tips !, and if you had leads (sample) to attack this kind of development, I am interested.

  


  Thank you very much in advance for your feedback.
(this is my fist question on stackoverflow, Champagne ! ;))