{"id":1723,"date":"2017-04-30T12:10:17","date_gmt":"2017-04-30T20:10:17","guid":{"rendered":"https:\/\/chriscarey.com\/wp\/?p=1723"},"modified":"2019-06-26T09:58:30","modified_gmt":"2019-06-26T17:58:30","slug":"achieving-high-frame-rate-with-a-raspberry-pi-camera-system","status":"publish","type":"post","link":"https:\/\/chriscarey.com\/blog\/2017\/04\/30\/achieving-high-frame-rate-with-a-raspberry-pi-camera-system\/","title":{"rendered":"Achieving high frame rate with a Raspberry Pi camera system"},"content":{"rendered":"

\"\"<\/a><\/p>\n

When you read about using Raspberry Pi cameras as part of your home security system, most of the information you will find will point you in the direction of running motion<\/a> which is the de-facto standard for doing video motion detection on Linux. There are also variants of motion such as MotionEye<\/a> or motionEyeOS<\/a> which provide a nicer UI on top of motion.<\/p>\n

Motion requires some horsepower to handle the video processing to detect motion, and also to run the web server and other features. On the modest hardware on the Raspberry Pi, I was only able to reliably achieve 4-10 frames-per-second at 800×600, depending on the Raspberry Pi model in use.<\/p>\n

Using this technique below, my camera system is now able to get closer to the full resolution for each Raspberry Pi camera which is 1920×1080 at 30 frames per second – and reliably running for years without issue.
\n<\/strong><\/p>\n

<\/p>\n

The problem with using motion on the Raspberry Pi<\/h2>\n

After much experimentation and time trying to make it work, I found the motion solution is not that great in practice. I have spent countless hours writing scripts, web pages, and various hacks to build a robust 4 camera home security system using this setup.<\/p>\n

The cameras suffered from low frame rate (FPS), high load average, frequent lockups, and SD cards dying. This slow frame rate is due to the high CPU needed by motion performing image processing on the low powered Pi. The high load average and SD card death is being caused by the high number of writes (images and video files) on the SD card.<\/p>\n

Managing all the video files was a problem as well. Files from the multiple cameras need to be remotely viewable in one central location. The SD card fills up fast and old files need to be deleted to make room for new files.<\/p>\n

There has to be a better way!<\/p>\n

The Solution<\/h2>\n

The solution I found was to take as much of the processing off of the Raspberry Pis as possible. I wanted to get the devices to send video, and not write anything on the local SD card. The image processing \/ motion detection needs to be removed from the Pi and moved to a more powerful machine.<\/p>\n

The NVR software I went with<\/h4>\n

For your camera server, you could choose any NVR hardware or software which supports the RTSP standard for video streams.<\/p>\n

In my case I had an old Mac Mini in the closet, and went on the hunt for software that would work on MacOS. After some research, I came across a software called SecuritySpy<\/a> from Ben Software. This software provides so many capabilities that I was attempting to create myself and now I am a huge fan of it. For the purpose of this article I will go through how I set up SecuritySpy, but you can use any video recording software that you want.<\/p>\n

SecuritySpy is a paid software and is totally worth the price for the features and support that you get.<\/p>\n

Configure the Raspberry Pi camera to be a RTSP streaming server<\/h2>\n

Set up the Pi camera according to the camera setup guide. You need to run raspi-config<\/strong> and enable the camera module.<\/p>\n

This technique uses the software raspivid<\/strong> and the VLC command line interface cvlc<\/strong>. raspivid should already be installed with your Raspbian install, but you will probably need to install VLC:<\/p>\n

sudo apt-get install vlc<\/div><\/div>\n

Create a script to turn your Raspberry Pi into a RTSP streaming server. In the pi home directory \/home\/pi, create the file stream-rtsp.sh<\/strong>:<\/p>\n

#!\/bin\/bash
\nraspivid -o - -t 0 -w 1920 -h 1080 -fps 30 -b 250000 | cvlc -vvv stream:\/\/\/dev\/stdin --sout '#rtp{access=udp,sdp=rtsp:\/\/:8554\/stream}' :demux=h264<\/div><\/div>\n

Tweak the settings to your liking. The -w width -h height -fps fps -b bitrate are good values to play with.<\/p>\n

I sometimes run on a lower configuration to reduce network bandwidth:<\/p>\n

#!\/bin\/bash
\nraspivid -o - -t 0 -w 1000 -h 576 -fps 20 -b 250000 | cvlc -vvv stream:\/\/\/dev\/stdin --sout '#rtp{access=udp,sdp=rtsp:\/\/:8554\/stream}' :demux=h264<\/div><\/div>\n

With this simple script, your Pi will be running as a RTSP server listening on both TCP and UDP. Remove access=udp to disable the UDP stream if you want. My suggestion is to leave both enabled, and see which one works best for you.<\/p>\n

Make the script executable:<\/p>\n

chmod +x stream-rtsp.sh<\/div><\/div>\n

Test the script by running it manually:<\/p>\n

.\/stream-rtsp.sh<\/div><\/div>\n

Making the script run on startup<\/h3>\n

After you see it is working, set up the script to run automatically on startup. I have two examples of how to do this here. First is using a systemd startup script which is recommended. Second is inside of a screen session. You only need to choose one option.<\/p>\n

Script startup Option 1 – systemd startup script<\/h4>\n

Create the file \/etc\/systemd\/system\/stream-rtsp.service<\/p>\n

[Unit]
\nDescription=auto start stream
\nAfter=multi-user.target<\/div><\/div>\n
<code><\/div><\/div>\n

<\/code><\/p>\n

[Service]
\nType=simple
\nExecStart=\/home\/pi\/stream-rtsp.sh
\nUser=pi
\nWorkingDirectory=\/home\/pi
\nRestart=on-failure<\/p>\n

 <\/div><\/div>\n
[Install]
\nWantedBy=multi-user.target<\/div><\/div>\n

Set the service to auto start<\/p>\n

sudo systemctl enable stream-rtsp.service<\/div><\/div>\n

Then you can start, stop, or check on the service with:<\/p>\n

sudo systemctl start stream-rtsp.service
\nsudo systemctl stop stream-rtsp.service
\nsudo systemctl status stream-rtsp.service<\/div><\/div>\n

Script startup Option 2 – Using screen<\/h4>\n

As a reminder, you do not need to do this part if you did the systemd startup script above.<\/p>\n

Install screen<\/p>\n

sudo apt-get install screen<\/div><\/div>\n

To make screen start every boot, add this to the middle of your \/etc\/rc.local file (above exit 0):<\/p>\n

# start streaming video
\nsu - pi -c "\/usr\/bin\/screen -dmS stream \/home\/pi\/stream-rtsp.sh"<\/div><\/div>\n

Note: When using this method the stream-rtsp script will NOT auto restart if for some reason it crashes. That it one benefit in using systemd. Easiest is to just reboot the box.<\/p>\n

Option 1 for NVR – Using SecuritySpy<\/h2>\n

Download, Install and set up SecuritySpy<\/h2>\n

SecuritySpy download page<\/a><\/p>\n

Some of the features SecuritySpy provides:<\/p>\n

– Live Video with FPS overlay
\n– Constant recording, or motion detection recording
\n– A robust interface for viewing recorded videos
\n– Web based interface for viewing on computer, phone, TV
\n– iOS client for live viewing on iPhone, iPad, AppleTV
\n– Automatic deletion of old video files (by age, or when the hard drive fills)
\n..and much more<\/p>\n

Add a new camera in the SecuritySpy setup.<\/p>\n

Enter the Raspberry Pi camera IP address. Select “Profile” “Manual configuration”, “Format” “RTSP TCP (video and audio)”, and down in “Request” enter “\/stream”.<\/p>\n

\"\"<\/a><\/p>\n

Apply Preferences, then the video should show up.<\/p>\n

\"\"<\/a><\/p>\n

Option 2 for NVR – Monitor the camera with any NVR software of your choosing<\/h2>\n

The important part here is that we configured the Raspberry Pi to run a RTSP<\/strong> server which accepts connections over TCP or UDP<\/strong> on port 8554<\/strong> and the request url is \/stream<\/strong><\/p>\n

You can connect to this stream with a variety of applications.<\/p>\n

One example is to stream this to another Raspberry Pi, you could do it with omxplayer:<\/p>\n

Install omxplayer on some other Raspberry Pi:<\/p>\n

sudo apt-get install omxplayer<\/div><\/div>\n

Make a script called stream-video.sh<\/strong><\/p>\n

#!\/bin\/bash
\nkillall omxplayer.bin
\nsleep 1
\nomxplayer --aspect-mode stretch -o hdmi rtsp:\/\/10.69.0.23:8554\/stream<\/div><\/div>\n

Edit the IP address to be the camera’s IP.<\/p>\n

Make the script executable:<\/p>\n

chmod +x stream-video.sh<\/div><\/div>\n

Run the script<\/p>\n

.\/stream-video.sh<\/div><\/div>\n

and you should see the full screen video sent out the hdmi port<\/p>\n

Works with Raspberry Pi Zero W<\/h2>\n

This technique of creating a RTSP server also works for getting high resolution and high frame rate out of the new Raspberry Pi Zero W camera packs (infrared<\/a> or standard<\/a>)! At $45 the bundle pack that comes with the case and infrared camera is a great way to add extra wireless cameras to your home security system.<\/p>\n

\"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

When you read about using Raspberry Pi cameras as part of your home security system, most of the information you will find will point you in the direction of running motion which is the de-facto standard for doing video motion detection on Linux. There are also variants of motion such as MotionEye or motionEyeOS which […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[59],"tags":[],"class_list":["post-1723","post","type-post","status-publish","format-standard","hentry","category-raspberry-pi"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/prpYG-rN","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/chriscarey.com\/blog\/wp-json\/wp\/v2\/posts\/1723","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/chriscarey.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/chriscarey.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/chriscarey.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/chriscarey.com\/blog\/wp-json\/wp\/v2\/comments?post=1723"}],"version-history":[{"count":78,"href":"https:\/\/chriscarey.com\/blog\/wp-json\/wp\/v2\/posts\/1723\/revisions"}],"predecessor-version":[{"id":2129,"href":"https:\/\/chriscarey.com\/blog\/wp-json\/wp\/v2\/posts\/1723\/revisions\/2129"}],"wp:attachment":[{"href":"https:\/\/chriscarey.com\/blog\/wp-json\/wp\/v2\/media?parent=1723"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/chriscarey.com\/blog\/wp-json\/wp\/v2\/categories?post=1723"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/chriscarey.com\/blog\/wp-json\/wp\/v2\/tags?post=1723"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}