Recherche avancée

Sur d’autres sites (12665)

• rtsp stream transcode with ffserver/ffmpeg

  30 juin 2018, par Torbjørn

  I’m having a unifi dome webcam. Connected thrue a USG Pro4. I’m sending a rtsp live stream at 1024x576px. Until now I have been using ffserver to transcode the stream into a new mpjpeg stream that I can show in a html file.
  But after I updated ffserver to the newest version. This does not work.

  Using debian.

  ffserver.conf file :

      HTTPPort 8090
  
      # bind to all IPs aliased or not
  
      HTTPBindAddress 0.0.0.0
  
      # max number of simultaneous clients
  
      MaxClients 1000
  
      # max bandwidth per-client (kb/s)
  
      MaxBandwidth 100000
  
      # Suppress that if you want to launch ffserver as a daemon.
  
      # NoDaemon
  
      NoDefaults
      File /tmp/feed1.ffm
  
      FileMaxSize 500M
      Feed feed1.ffm
  
      Format mpjpeg
  
      VideoCodec mjpeg
  
      VideoFrameRate 1
  
      #VideoBufferSize 80000
  
      VideoQMin 1
  
      VideoQMax 5
  
      VideoSize 1024x576
  
      PreRoll 0
  
      Noaudio
  

  ffmpeg startup :

  `ffmpeg -rtsp_transport tcp -re -i "rtsp ://user:pass@193.213.XXX.XXX:554/s2" -b:v 1016k http://localhost:8090/feed1.ffm`

  I’ve tried with different startups after some google search. But I can get 1-10 fps before it shuts down.
  Sometimes I get :

  `rtsp ://user:pass@193.213.XXX.XXX:554/s2 : Invalid data found when processing input`

      Input #0, rtsp, from ’rtsp ://user:pass@193.213.XXX.XXX:554/s2’ :
  
        Metadata :
  
          title : s2
  
        Duration : N/A, start : 0.000000, bitrate : N/A
  
          Stream #0:0 : Audio : aac (LC), 11025 Hz, mono, fltp
  
          Stream #0:1 : Video : h264 (Main), yuvj420p(pc, bt709, progressive), 1024x576 [SAR 189:190 DAR 168:95], 1 fps, 1 tbr, 90k tbn, 2 tbc
  
      Output #0, ffm, to ’http://localhost:8090/feed1.ffm’ :
  
        Metadata :
  
          title : s2
  
          creation_time : now
  
          encoder : Lavf57.56.101
  
          Stream #0:0 : Video : mjpeg, yuvj420p(pc), 1024x576 [SAR 189:190 DAR 168:95], q=1-5, 1016 kb/s, 1 fps, 1000k tbn, 1 tbc
  
          Metadata :
  
            encoder : Lavc57.64.101 mjpeg
  
          Side data :
  
            cpb : bitrate max/min/avg : 0/0/1016000 buffer size : 0 vbv_delay : -1
  
      Stream mapping :
  
        Stream #0:1 -> #0:0 (h264 (native) -> mjpeg (native))
  
      Press [q] to stop, [?] for help
  
      frame=    4 fps=0.7 q=2.1 Lsize=     564kB time=00:00:03.00 bitrate=1540.1kbits/s dup=1 drop=0 speed=0.54x
  
      video:558kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead : 1.089245%
  

  Is there an easy way to get this working, or is there a much better way of doing it ?
  What i want out of this is an live web cam stream in an html site that works on all platforms without any plugins on clients end.

• Streaming low latency video

  26 août 2018, par user4893295

  Goal is to get low latency HD video over the LAN from a USB camera on a ARM device (a10 Lime running Armbian Jessie) to OBS Studio.

  Thinking first step is to at least get it viewable on VLC on another device. So, to that end, I have tried gstreamer (no joy), ffmpeg (same) and VLC. Best luck with VLC so far, but the picture is mostly blank with occasional spots of picture.

  This is the command I’m using :

  cvlc v4l2:///dev/video0:chroma=h264:width=1920:height=1080 --sout '#standard{access=http,mux=ts,dst=0.0.0.0:8080/stream,name=stream,mime=video/ts}' -vvv

  It moans a bit at first with

  [00b4a178] core interface error: no suitable interface module
  
  [00ab18f8] core libvlc error: interface "globalhotkeys,none" initialization failed
  
  [00b4a178] core interface debug: looking for interface module matching "dbus,none": 18 candidates
  
  [00b4a178] dbus interface error: Failed to connect to the D-Bus session daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
  
  [00b4a178] core interface debug: no interface modules matched
  
  [00b4a178] core interface error: no suitable interface module
  
  [00ab18f8] core libvlc error: interface "dbus,none" initialization failed

  But then seems to get a bit happier

  [b4316038] core demux meta debug: no meta reader modules matched
  
  [b4300508] core input debug: `v4l2:///dev/video0:chroma=h264:width=1920:height=1080' successfully opened
  
  [b4300508] core input debug: Buffering 0%
  
  [b4300508] core input debug: switching to sync mode
  
  [b430cce8] packetizer_h264 decoder debug: found NAL_SPS (sps_id=0)
  
  [b430cce8] packetizer_h264 decoder debug: found NAL_PPS (pps_id=0 sps_id=0)
  
  [b4300508] core input debug: Buffering 10%
  
  [b43041a0] core stream output debug: adding a new sout input (sout_input:0xb49004f0)
  
  [b43060f8] core mux debug: adding a new input
  
  [b43060f8] mux_ts mux debug: adding input codec=h264 pid=68
  
  [b43060f8] mux_ts mux debug: new PCR PID is 68
  
  [b4300508] core input debug: Buffering 32%
  
  [b4300508] core input debug: Buffering 44%
  
  [b4300508] core input debug: Buffering 55%
  
  [b4300508] core input debug: Buffering 65%
  
  [b4300508] core input debug: Buffering 77%
  
  [b4300508] core input debug: Buffering 88%
  
  [b4300508] core input debug: Buffering 98%
  
  [b4300508] core input debug: Stream buffering done (332 ms in 331 ms)
  
  [b4300508] core input debug: Decoder wait done in 0 ms

  And I can connect to it from VLC, but the picture looks like

  

  Processor peaks at around 17% and memory even less than that, so it’s not that.

  Any suggestions ?

• ffmpeg posting to nginx hangs after 90 minutes

  22 octobre 2018, par Harnek Gulati

  I’m using a very simple program to push an ffmpeg stream from my raspberry pi camera to a nginx server. However, it fails after 90 minutes, with almost every single Raspberry Pi I use (I have this code on 12 Raspberry Pis).
  Here is my ffmpeg command :

  raspivid -o - -t 0 -w 640 -h 480 -fps 25 | ffmpeg -re -i - -vcodec copy -hls_time 4 -f hls -hls_list_size 5 -hls_wrap 5 -threads 0  -timeout 5000 -max_reload 20000 -method PUT http://{}:{}/live/{}

  And here is my configuration for nginx.conf :

  #user nobody;
  
  load_module /usr/lib/nginx/modules/ndk_http_module.so;
  
  load_module /usr/lib/nginx/modules/ngx_http_lua_module.so;
  
  
  
  worker_processes auto;
  
  env CONTROL_SERVER_IP;
  
  
  
  
  
  #error_log /var/log/nginx/error.log;
  
  error_log /dev/stdout info;
  
  events {
  
      worker_connections 1024;
  
  }
  
  
  
  http {
  
      include     mime.types;
  
      default_type    application/octet-stream;
  
      access_log /dev/stdout;
  
      sendfile on;
  
      keepalive_requests 100000;
  
      keepalive_timeout 30;
  
  
  
    client_max_body_size 10M;
  
    server {
  
      listen 80;
  
      server_name localhost;
  
  
  
      location /live {
  
        root /var/static;
  
              client_body_temp_path   /var/static/client_temp;
  
  
  
              dav_methods PUT;
  
              create_full_put_path on;
  
              dav_access user:rw  group:r     all:r;
  
  
  
              types {
  
                  application/vnd.apple.mpegurl m3u8;
  
              }
  
  
  
              # Disable Cache
  
              add_header Cache-Control no-cache;
  
              include cors.conf;
  
    }
  
    }
  
  }
  
  
  
  daemon off;

  If anyone can help me, I would deeply appreciate it. I’ve been pulling my hair out trying to figure out this bug. On the raspberry pi, it hangs on this :

  [hls @ 0x25a8c90] Opening 'http://192.168.8.1:80/live/c35d8935-0a31-4d22-b71a-ad3f4f1d47631.ts' for writing
  
  frame=105609 fps= 25 q=-1.0 q=1.6 size=N/A time=01:11:40.00 bitrate=N/A dup=0 drop=105518 speed=1.02xframe=105623 fps= 25 q=-1.0 q=1.6 size=N/A time=01:11:40.00 bitrate=N/A dup=0 drop=105532 speed=1.02xframe=105636 fps= 25 q=-1.0 q=1.6 size=N/A time=01:11:40.00 bitrate=N/A dup=0 drop=105545 speed=1.02xframe=105648 fps= 25 q=-1.0 q=1.6 size=N/A time=01:11:40.00 bitrate=N/A dup=0 drop=105557 speed=1.02xframe=105662 fps= 25 q=-1.0 q=1.6 size=N/A time=01:11:40.00 bitrate=N/A dup=0 drop=105571 speed=1.02xframe=105674 fps= 25 q=-1.0 q=1.6 size=N/A time=01:11:40.00 bitrate=N/A dup=0 drop=105583 speed=1.02xframe=105688 fps= 25 q=-1.0 q=1.6 size=N/A time=01:11:40.00 bitrate=N/A dup=0 drop=105597 speed=1.02xframe=105700 fps= 25 q=-1.0 q=1.6 size=N/A time=01:11:40.00 bitrate=N/A dup=0 drop=105609 speed=1.02xframe=105714 fps= 25 q=-1.0 q=1.6 size=N/A time=01:11:40.00 bitrate=N/A dup=0 drop=105623 speed=1.02x[hls muxer @ 0x25a9200] Duplicated segment filename detected: c35d8935-0a31-4d22-b71a-ad3f4f1d47631.ts
  
  [hls @ 0x25a8c90] Opening 'http://192.168.8.1:80/live/c35d8935-0a31-4d22-b71a-ad3f4f1d47632.ts' for writing

  And on the nginx logs, I get :

  192.168.10.242 - - [21/Oct/2018:22:34:01 +0000] "PUT /live/c35d8935-0a31-4d22-b71a-ad3f4f1d4763.m3u8 HTTP/1.1" 204 0 "-" "Lavf/57.83.100"
  
  192.168.10.242 - - [21/Oct/2018:22:35:04 +0000] "PUT /live/c35d8935-0a31-4d22-b71a-ad3f4f1d47633.ts HTTP/1.1" 408 0 "-" "Lavf/57.83.100"

  I need to set up a way to either a) keep consistent connections longer than 90 minutes or b) detect when the 408 error happens and stop it from hanging.

  FFMPEG version : 3.4.1