Recherche avancée

Sur d’autres sites (9825)

• obtain RTSP Describe info and screenshot [closed]

  26 juillet 2024, par Charlie Bronson

  good morning, given an rtsp streaming that responds 200 to a request and has both PLAY and DESCRIBE options, how can I capture a screenshot in jpg without running into errors like 400 Bed Request, using a command line tool like ffmpeg ?
there are other answers on the site but without knowing the nature of streaming how can this operation be best carried out ?

  


  I found very little documentation online

  


  I tried with ffprobe and ffmpeg, in tcp and udp, but each camera has its own options and before using ffmpeg I should understand what the streaming settings are.

  


• ffmpeg start/stop rtmp streams on the fly

  14 août 2020, par almosnow

  I have a media stream that I transmit as rtmp to several endpoints, for this I use ffmpeg and the tee pseudo-format.

  


  Sometimes one of the sites may come online (or go offline) and I would like to start/stop streaming to it accordingly.

  


  Restarting ffmpeg is not an optimal choice as all the streams that are currently being transmitted would get cut.

  


  Is there a way to add/remove targets to tee on the fly ? Or a way to achieve a similar thing with ffmpeg and tools from a linux environment ? Perhaps there's something that already does this with rtmp streams.

  


• FFmpeg -> JSMpeg Websocket Closes Repeatedly

  13 mars 2018, par Kyle Martin

  I’m trying to create a fairly simple streaming server/site. Here’s the current flow :

  • OBS streams to an RTMP URL
  • Nginx accepts the RTMP stream and uses exec-push to have FFmpeg pick up the stream and transcode it
  • FFmpeg transcodes the stream and outputs it to a JSMpeg application, which displays the stream on a webpage.

  When I have my exec_push statement as follows, everything seems to work perfectly, except the browser says Possible garbage data. Skipping. on every frame it receives :

  exec_push /usr/bin/ffmpeg -re -i rtmp://127.0.0.1:1935/$app/$name -f mpeg1video  http://localhost:8080/supersecret;

  This behavior is understandable, because JSMpeg must receive MPEG-TS data, not MPEG1 data. It sees the MPEG1 frames and thinks they’re garbage.

  So through some online research, I found this :

  exec_push /usr/bin/ffmpeg -re -i rtmp://127.0.0.1:1935/$app/$name -c:v copy -c:a copy -f mpegts http://localhost:8080/supersecret;

  Supposedly, this is supposed to transcode my RTMP stream into an MPEG-TS format, which should be compatible with JSMpeg.

  However, with the second version of the command, my FFmpeg -> JSMpeg stream keeps connecting and disconnecting, connecting and disconnecting, and so on. This behavior is observed in terminal :

  Stream Connected: ::1:40208
  
  close
  
  Stream Connected: ::1:40212
  
  close
  
  Stream Connected: ::1:40216
  
  close
  
  Stream Connected: ::1:40220
  
  close
  
  Stream Connected: ::1:40224
  
  close
  
  ...

  What would cause this ? I am pretty certain the issue is in my exec_push command. OBS is perfectly content, which tells me that the stream is making it to the server, and if I do a push, I can do a test push to Ustream just fine, which tells me that Nginx is at least processing the stream with some reasonable degree of success.

  ---

  Disclaimer : I have no idea what I’m talking about. Everything I know about FFmpeg and JSMpeg/Node is from snippets of code that I found online.