Recherche avancée

Sur d’autres sites (10486)

• ffmpeg issues "501 Not Implemented" while recording an RTSP stream

  28 février 2019, par atsushi

  I have a 4K camera (Sony SNC-VB770) streaming RTSP.

  I’m trying to record the stream into files (each has handy length, say, 1hour)
  using a simple script to repeatedly launch ffmpeg (ver 4.1) :

  while : ; do
  
    # (set $url and $outfile, and then)
  
    ffmpeg -rtsp_transport tcp -t 3600 -y -i $url -c copy -map 0:0 -b:v 16000k $outfile
  
  done

  If I run the script on a local PC directly connected to the camera, it works (longer than a week, at least).
  However, if I do the same on a server machine located in a data center, it fails randomly with no error message.
  Sometimes it runs for a few days, sometimes it dies in one minutes.

  Typical output looks like the following :

  # devname: snc-vb770
  
  # url: rtsp://10.40.35.90/media/video1
  
  # vb: 16000k
  
  # datefmt %d%H
  
  # addtimestamp 0
  
  no timestamp
  
  ffmpeg version 4.1 Copyright (c) 2000-2018 the FFmpeg developers
  
    built with gcc 4.4.7 (GCC) 20120313 (Red Hat 4.4.7-18)
  
    configuration: --prefix=/usr/local/ffmpeg-4.1 --enable-openssl --enable-gpl --enable-version3 --enable-nonfree --enable-shared --enable-libx264 --enable-libvorbis --enable-filter=drawtext --enable-libfreetype --enable-libfribidi --enable-fontconfig
  
    libavutil      56. 22.100 / 56. 22.100
  
    libavcodec     58. 35.100 / 58. 35.100
  
    libavformat    58. 20.100 / 58. 20.100
  
    libavdevice    58.  5.100 / 58.  5.100
  
    libavfilter     7. 40.101 /  7. 40.101
  
    libswscale      5.  3.100 /  5.  3.100
  
    libswresample   3.  3.100 /  3.  3.100
  
    libpostproc    55.  3.100 / 55.  3.100
  
  Input #0, rtsp, from 'rtsp://10.40.35.90/media/video1':
  
    Metadata:
  
      title           : Sony RTSP Server
  
    Duration: N/A, start: 0.066667, bitrate: N/A
  
      Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive), 3840x2160 [SAR 1:1 DAR 16:9], 14.99 fps, 14.99 tbr, 90k tbn, 29.97 tbc
  
  Output #0, mp4, to './2811.mp4':
  
    Metadata:
  
      title           : Sony RTSP Server
  
      encoder         : Lavf58.20.100
  
      Stream #0:0: Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 3840x2160 [SAR 1:1 DAR 16:9], q=2-31, 16000 kb/s, 14.99 fps, 14.99 tbr, 90k tbn, 90k tbc
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (copy)
  
  Press [q] to stop, [?] for help
  
  [mp4 @ 0x24e4ec0] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
  
  [mp4 @ 0x24e4ec0] pts has no value
  
  [mp4 @ 0x24e4ec0] Non-monotonous DTS in output stream 0:0; previous: 0, current: 0; changing to 1. This may result in incorrect timestamps in the output file.
  
  frame=   33 fps=0.0 q=-1.0 size=    1792kB time=00:00:02.00 bitrate=7332.9kbits/s speed=3.57x
  
  ...
  
  frame=  104 fps=8.4 q=-1.0 Lsize=    6532kB time=00:00:06.74 bitrate=7939.6kbits/s speed=0.548x
  
  video:6531kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.023506%

  I’ve looked into RTSP packet and found an "RTSP/1.0 501 Not Implemented" is sent from ffmpeg to the camera.
  After that the camera eventually sent back "RTSP/1.0 505 RTSP Version not supported" and then ffmpeg quits shortly.

  The "501" packet seems to be generated by libavformat/rtsp.c:ff_rtsp_read_reply(),
  when ffmpeg receive a malformed RTSP packet with method=(null), status_code=0.
  I don’t know why such packets arrive at random timing and who is wrong (maybe the camera, maybe any of network switches or routers in the middle of the network path from the camera to the server machine).
  But anyway, I don’t want the recording to be stopped
  due to those malformed packets.

  Is there any workaround to make ffmpeg ignore invalid RTSP packets and just continue the recording ?

  Additional information :

  • I’ve tested the recording with both ffmpeg ver4.1 and 2.8.4 and no difference observed.

  • No difference observed at lower resolution nor at lower bitrate.

  • I have 3 cameras from various manufacturers in the same network environment.
    All of the three are working without problem for more than a month.
    Only the Sony SNC-VB770 shows the strange behavior.

• Connection timed out RTSP stream exited with error"

  30 septembre 2019, par fw08

  I am building an web application on AWS Cloud that requires to stream a recorded/live video over the global network. I purchased an IP camera(GV-AVD4710) and NVR(GV-SNVR0811) for our application. In future I need to stream no. of cameras on my application.

  While Camera in use With NVR, I have connected the NVR in our local network and the camera at channel_1 of NVR. Now the lets assume NVR is getting an IP of 192.168.1.203. So for rtsp streaming URL for channel_1 will be "rtsp://id:password@192.168.1.203:554/ch1" as per manufacturer’s specification. For camera streaming I am using "ffmpeg" multimedia framework (https://github.com/xpcrts/Steaming-IP-Camera-Nodejs ). So it is working fine. I tested it and working well in local network. Code that is running on the server

  Stream = require('node-rtsp-stream')
  
  stream = new Stream({
  
      name: 'name',
  
      streamUrl: 'rtsp://ID:PASSWORD@abcxyz.com:554/ch1',
  
      wsPort:3000,
  
      ffmpegOptions: {
  
          '-stats': '',
  
          '-r': 30
  
      }
  
  })

  and Code running at client side which is independent of any plug-ins

  <div>
  
         <canvas width="auto" height="auto"></canvas>
  
         <code class="echappe-js">&lt;script type=&quot;text/javascript&quot; src='http://stackoverflow.com/feeds/tag/jsmpeg.min.js'&gt;&lt;/script&gt;
         
  &lt;script type=&quot;text/javascript&quot;&gt;<br />
  
              var canvas = document.getElementById('chanel1');<br />
  
              var websocket = new WebSocket(&quot;ws://34.202.222.188:3000&quot;);<br />
  
              var player= new jsmpeg(websocket, {canvas:canvas, autoplay:true, loop:true})<br />
  
         &lt;/script&gt;
  

  When I made this IP address available for public, and then the problem begins. It is not working and giving an error :

   "[tcp @ 0x563911f0a340] Connection to tcp://192.168.1.205:554?timeout=0 failed: Connection timed out
  
  rtsp://admin:admin@192.168.1.205: Connection timed out RTSP stream exited with error"

  In Camera Without NVR, I connected camera directly to our local network and so got an rtsp url like rtsp ://id:password@192.168.1.205/media/video1. Same happens again. Works well in local, but not working when I am making this available on public network.

  How can stream video over global network ? Is it possible to implement these logic using ffmpeg multimedia framework ? Does VLC can help in these cases ?

  I would like to reiterate that, In future there are no. of cameras needs to be stream.