Video from a surveillance camera on the site for free and without SMS
There is a need to show video from the camera on the site online. There were several options (I will add options from comments, if there are any):
This option will be considered below. Since " flash died " or " flash is about to die, " the option of placing a flash player on the site was not considered. The thorny way of finding solutions on the Internet did not lead to a ready-made solution. I had to invent a bicycle.
More inventions under the cut.
On each stream from the camera, you need to run ffmpeg to convert rtsp to files that hls will understand.
')
We take a stream, without transcoding we create files and a list for playback in the folder / tmp / www / .
We shorten the standard for the debian package file default to, for example, this:
Sample video page:
The script should be placed locally, it has no external dependencies. Read more about hls settings .
hls connects to the page and plays files from the index1.m3u8 list. List and files are updated ffmpeg.
» Hls implementation
» Work demo hls
» Ffmpeg
» Nginx
» Updated and expanded text of the article on my blog
- Give access to the camera. Just do not give access to the camera for security reasons. The camera will fall under a very small load.
- Commercial service. We give them access to the camera and money, they link us to post on the site. They also solve the problem of camera compatibility and user browsers, channel performance and availability.
- In their capacities. Something is put between the user and the camera that is responsible for browser compatibility, performance and accessibility. We solve problems ourselves.
This option will be considered below. Since " flash died " or " flash is about to die, " the option of placing a flash player on the site was not considered. The thorny way of finding solutions on the Internet did not lead to a ready-made solution. I had to invent a bicycle.
More inventions under the cut.
Description of the bike received in more detail:
- Surveillance camera gives stream via rtsp protocol.
- ffmpeg takes a video stream from the camera and creates a video for display via the html5 standard video tag.
- nginx gives the created files to users
- video on the page is shown using hls , or rather this implementation
More about settings
On each stream from the camera, you need to run ffmpeg to convert rtsp to files that hls will understand.
')
ffmpeg and stream with sound
/usr/bin/ffmpeg \ -i rtsp://< ONVIF Device Manager> \ -ar 44100 \ -acodec aac -ac 1 -strict -2 -crf 18 \ -c:v copy -preset ultrafast \ -flags -global_header \ -fflags flush_packets -tune zerolatency \ -hls_time 1 -hls_list_size 3 -hls_wrap 4 -hls_flags delete_segments -start_number 0 \ /tmp/www/index1.m3u8 ffmpeg at start writes 25 fps with FullHD
Noname camera.
Guessed Channel Layout for Input Stream #0.1 : mono Input #0, rtsp, from 'rtsp://192.168.XX:554/user=admin_password=tlJwpbo6_channel=1_stream=0.sdp?': Metadata: title : RTSP Session Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: h264 (Baseline), yuv420p, 1920x1080, 25 fps, 9 tbr, 90k tbn, 50 tbc Stream #0:1: Audio: pcm_alaw, 8000 Hz, 1 channels, s16, 64 kb/s Output #0, hls, to '/tmp/www/index1.m3u8': Metadata: title : RTSP Session encoder : Lavf56.25.101 Stream #0:0: Video: h264, yuv420p, 1920x1080, q=2-31, 25 fps, 9 tbr, 90k tbn, 25 tbc Stream #0:1: Audio: aac, 44100 Hz, mono, fltp, 128 kb/s Metadata: encoder : Lavc56.26.100 aac Stream mapping: Stream #0:0 -> #0:0 (copy) Stream #0:1 -> #0:1 (pcm_alaw (native) -> aac (native)) The video is simply copied, the audio had to be recoded otherwise silence.Noname camera.
How does it work:
We take a stream, without transcoding we create files and a list for playback in the folder / tmp / www / .
nginx
We shorten the standard for the debian package file default to, for example, this:
/ etc / nginx / sites-enabled / default
server { listen 80 default_server; listen [::]:80 default_server; access_log off; error_log /dev/null; root /tmp/www; index index.html; server_name _; location / { # First attempt to serve request as file, then # as directory, then fall back to displaying a 404. try_files $uri $uri/ =404; } } Sample video page:
/tmp/www/index.html
<!DOCTYPE html> <html> <head> <title></title> </head> <body> <script src="https://cdn.jsdelivr.net/hls.js/latest/hls.min.js"></script> <video id="video"></video> <script> if(Hls.isSupported()) { var video = document.getElementById('video'); var hls = new Hls(); hls.loadSource('/index1.m3u8'); hls.attachMedia(video); hls.on(Hls.Events.MANIFEST_PARSED,function() { video.play(); }); } </script> The script should be placed locally, it has no external dependencies. Read more about hls settings .
How does it work:
hls connects to the page and plays files from the index1.m3u8 list. List and files are updated ffmpeg.
What happened:
- Works;
- The biggest load is created by ffmpeg, on an Atom processor three years ago;
- Camera resolution Full HD without sound - 1%;
- Full HD camera resolution with sound - 5%;
- The number of nginx processes - look at the load and the available channel. The load on the processor could not be seen - not very much to just return small files.
- A server with ffmpeg and nginx can be placed anywhere, not necessarily on hosting or in the location of cameras;
- The lag of the stream depends on the number of files in the list and the size (in seconds) of the file. For example, a delay of 10 seconds does not really affect the viewing of the construction of a high-rise building;
- Video files are best placed on tmpfs, they are small and often overwritten;
- All service should be placed in a container. All packages are standard for
FROM debian:jessie; - According to the results of operation, ffmpeg sometimes falls, you need to monitor it and restart if it fell.The top output from the container:
top - 11:05:20 up 6 days, 12:15, 0 users, load average: 1.29, 1.09, 1.03 Tasks: 17 total, 1 running, 16 sleeping, 0 stopped, 0 zombie %Cpu(s): 38.8 us, 1.0 sy, 0.0 ni, 59.6 id, 0.0 wa, 0.0 hi, 0.5 si, 0.0 st KiB Mem: 16359132 total, 16027988 used, 331144 free, 782968 buffers KiB Swap: 6369276 total, 3776 used, 6365500 free. 12784916 cached Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 281 root 20 0 341040 29192 19632 S 4.7 0.2 10:08.39 ffmpeg 16 root 20 0 315888 27944 18984 S 1.0 0.2 2:50.95 ffmpeg 9 root 20 0 46916 15128 6408 S 0.3 0.1 0:58.04 supervisord - You can watch on desktops and mobile devices with modern browsers;
- In the foreseeable future will not require intervention.
References:
» Hls implementation
» Work demo hls
» Ffmpeg
» Nginx
» Updated and expanded text of the article on my blog
Source: https://habr.com/ru/post/401107/
All Articles