This appears to be a byproduct of the low-end of the CCTV industry playing fast and loose with standards, RTSP and ONVIF being the two most frequently abused.įortunately, you can usually work around these problems. So I've opted to code a controller in Python using the 'subprocesses' module to invoke and monitor the stdout of each openRTSP client instance, and also check that the files are continuing to grow in size. Sometimes the openRTSP client does not catch these glitches. You will need to play with the options in order to find the combination which suits you.įrankly, the cameras themselves are sometimes unreliable, or just implemented differently -like closing the socket unexpectedly is not all that unusual. Removing the -t option causes openRTSP to default to UDP instead, which can reduce network traffic a bit. u admin 123456 # Username and password expected by camera t # Request camera end stream over TCP, not UDP P 900 # Start a new output file every -P seconds d 28800 # Run openRTSP this many seconds F cam_eight # Prefix output filenames with this text
c # Continuously record, after completion of -d timeframe These options mean: -D 1 # Quit if no packets for 1 second or more
Onvif recorder mp4#
The Live555 project provides a relatively fault-tolerant RTSP client implementation, openRTSP, for pulling RTSP audio/video streams via CLI: įor example, to save a camera's RTSP audio/video to files in QuickTime format (AVI and MP4 also available), one file every 15 minutes: $ openRTSP -D 1 -c -B 10000000 -b 10000000 -q -Q -F cam_eight -d 28800 -P 900 -t -u admin 123456 rtsp://192.168.1.108:554/11 Dealing with their RTSP streams requires a dose of fault-tolerance. IP cameras are of varying quality, some behaving erratically in my experience.
0 kommentar(er)
