Recherche avancée

Sur d’autres sites (8586)

• 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.

• "does not contain any stream" if "EXT-X-MEDIA-SEQUENCE" > 0

  6 mars 2019, par Wonson

  I have a list of .ts files and want to save them as multiple video files.

  ---

  First I have a .m3u8 like this obtained from streaming :

  #EXTM3U
  
  #EXT-X-VERSION:3
  
  #EXT-X-TARGETDURATION:5
  
  #EXT-X-MEDIA-SEQUENCE:0
  
  #EXT-X-KEY:METHOD=AES-128,URI="aaa001_00001.key"
  
  #EXTINF:3.01,
  
  aaa001_00002.ts
  
  #EXTINF:3.01,
  
  aaa001_00003.ts
  
  
  
  ...
  
  
  
  #EXTINF:3.01,
  
  aaa001_01944.ts
  
  #EXT-X-ENDLIST

  ---

  Step 1 :

  So, I tried to convert it into several m3u8 like the followings :

  segment1.m3u8

  #EXTM3U
  
  #EXT-X-VERSION:3
  
  #EXT-X-TARGETDURATION:5
  
  #EXT-X-MEDIA-SEQUENCE:0
  
  #EXT-X-KEY:METHOD=AES-128,URI="aaa001_00001.key"
  
  #EXTINF:3.01,
  
  aaa001_00002.ts
  
  #EXTINF:3.01,
  
  aaa001_00003.ts
  
  
  
  ...
  
  
  
  #EXTINF:3.01,
  
  aaa001_00569.ts
  
  #EXT-X-ENDLIST

  segment2.m3u8

  #EXTM3U
  
  #EXT-X-VERSION:3
  
  #EXT-X-TARGETDURATION:5
  
  #EXT-X-MEDIA-SEQUENCE:567
  
  #EXT-X-KEY:METHOD=AES-128,URI="aaa001_00001.key"
  
  #EXTINF:3.01,
  
  aaa001_00002.ts
  
  #EXTINF:3.01,
  
  aaa001_00003.ts
  
  
  
  ...
  
  
  
  #EXTINF:3.01,
  
  aaa001_01288.ts
  
  #EXT-X-ENDLIST

  and so on...

  then do the ffmpeg cmd one by one..

  ffmpeg -i /fs/segment2.m3u8 -safe 0 -map 0:v -map 0:a -cpu-used 4 -threads 0 -preset veryfast -c copy -bsf:a aac_adtstoasc output.mp4

  ---

  But those EXT-X-MEDIA-SEQUENCE > 0 (i.e. since segment2.m3u8...) will result in

  "Output file #0 does not contain any stream"

  ---

  Then I tried to make the ’segment2.m3u8’ looks like this

  #EXTM3U
  
  #EXT-X-VERSION:3
  
  #EXT-X-TARGETDURATION:5
  
  #EXT-X-MEDIA-SEQUENCE:0
  
  #EXT-X-KEY:METHOD=AES-128,URI="aaa001_00001.key"
  
  #EXTINF:3.01,
  
  aaa001_00002.ts <--the first video chunk
  
  #EXTINF:3.01,
  
  aaa001_00570.ts <--the start point of segment 2
  
  #EXTINF:3.01,
  
  aaa001_00571.ts
  
  
  
  ...
  
  
  
  #EXTINF:3.01,
  
  aaa001_01288.ts
  
  #EXT-X-ENDLIST

  ---

  ffmpeg works fine, and gives me an output video, so it seems the stream channel info is in the first chunk.

  However, there are still several problems

  1. the first chunk of video is in segment2.mp4 which I clearly do not want it here.

  2. the segment2 output video plays first the 3.01s, then freezed the image until the time reach aaa001_00570.ts and play again

  ---

  So, any suggestion so that I can reference the stream info from first chunk ? or ignore it in the playlist, etc ?

  ---

  UPDATE SOLUTION

  As it works when #EXT-X-MEDIA-SEQUENCE:0, and #EXT-X-KEY : IV = by default

  So I add IV=hex(#EXT-X-MEDIA-SEQUENCE)in every playlist

  segment1.m3u8

  #EXTM3U
  
  #EXT-X-VERSION:3
  
  #EXT-X-TARGETDURATION:5
  
  #EXT-X-MEDIA-SEQUENCE:0
  
  #EXT-X-KEY:METHOD=AES-128,URI="aaa001_00001.key",IV=0x00000000000000000000000000000000
  
  #EXTINF:3.01,
  
  aaa001_00002.ts
  
  #EXTINF:3.01,
  
  aaa001_00003.ts
  
  
  
  ...
  
  
  
  #EXTINF:3.01,
  
  aaa001_00569.ts
  
  #EXT-X-ENDLIST

  segment2.m3u8

  #EXTM3U
  
  #EXT-X-VERSION:3
  
  #EXT-X-TARGETDURATION:5
  
  #EXT-X-MEDIA-SEQUENCE:567
  
  #EXT-X-KEY:METHOD=AES-128,URI="aaa001_00001.key",IV=0x00000000000000000000000000000237
  
  #EXTINF:3.01,
  
  aaa001_00570.ts
  
  
  
  ...
  
  
  
  #EXTINF:3.01,
  
  aaa001_01288.ts
  
  #EXT-X-ENDLIST

• How to deal with "[asf XX] too long payload" message in ffmpeg ?

  28 mars 2019, par Ayorus

  I am trying to cut a small section of a video using the following sentence :

  ffmpeg.exe -i video.wmv -ss 00:20:02 -to 00:20:09 -crf 22  "C:\test.mp4" -y

  However, ffmpeg hangs showing messages like :

  [asf @ 03327b00] too long payload 0kB time=00:00:00.00 bitrate=N/A speed=   0x
  
         Last message repeated 352 times 
  
  [asf @ 03327b00] too long payload 0kB time=00:00:00.00 bitrate=N/A speed=   0x
  
        Last message repeated 331 times

  I have waited for more than 30 minutes and ffmpeg did not finish the cutting. Does anyone have any idea how to solve this ?

  Any suggestion will be appreciated

  PD. the ffprobe output of the source file is the following :

  ffprobe version N-81831-g97e7f03 Copyright (c) 2007-2016 the FFmpeg developers
  
    built with gcc 5.4.0 (GCC)
  
    configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-dxva2 --enable-libmfx --enable-nvenc --enable-avisynth --enable-bzlib --enable-libebur128 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib
  
    libavutil      55. 32.100 / 55. 32.100
  
    libavcodec     57. 60.101 / 57. 60.101
  
    libavformat    57. 51.102 / 57. 51.102
  
    libavdevice    57.  0.102 / 57.  0.102
  
    libavfilter     6. 63.100 /  6. 63.100
  
    libswscale      4.  1.100 /  4.  1.100
  
    libswresample   2.  2.100 /  2.  2.100
  
    libpostproc    54.  0.100 / 54.  0.100
  
  [asf @ 03b7afe0] too long payload
  
      Last message repeated 159 times
  
  Input #0, asf, from 'F:\video.wmv':
  
    Metadata:
  
      WMFSDKVersion   : 11.0.5721.5145
  
      WMFSDKNeeded    : 0.0.0.0000
  
      IsVBR           : 0
  
      DeviceConformanceTemplate: M
  
    Duration: 01:41:25.95, start: 0.000000, bitrate: 1649 kb/s
  
      Stream #0:0(eng): Video: wmv2 (WMV2 / 0x32564D57), yuv420p, 640x480, 1500 kb/s, 29.97 fps, 29.97 tbr, 1k tbn, 1k tbc
  
      Stream #0:1(eng): Audio: wmav2 (a[1][0][0] / 0x0161), 44100 Hz, 2 channels, fltp, 128 kb/s