Here is a howto for building this. It's an earlier version of the fork which does not use mmal component connections. I thought I'd work on a simpler version. Before you invest time or effort or hardware in this, understand that it may not work. Do so at your own risk.
1. Install Raspbian Lite Stretch. Update the system
Code: Select all
sudo apt-get update
sudo apt-get dist-upgrade
2. Install Zoneminder and its dependencies including ffmpeg
*ffmpeg is installed as a dependency and it is already compiled with mmal support.
3. Allow user pi and www-data to access the video encoder
Code: Select all
sudo usermod -a -G video pi
sudo usermod -a -G video www-data
4.Install other dependencies of Zoneminder
Code: Select all
sudo apt-get install libmp4v2-2
sudo apt-get install libapache2-mod-fcgid
sudo apt-get install libexpect-perl
sudo apt-get install netpbm
sudo apt-get install php-gd
sudo apt-get install libssl-dev
*You probably ended up with libjpeg62-turbo and jpeg8 as a dependency. Uninstall zoneminder and uninstall libjpeg8.
Code: Select all
sudo apt-get remove zoneminder
sudo apt-get remove libjpeg8
*Build jpegturbo with jpeg8 support
Code: Select all
sudo apt-get build dep libjpeg62-turbo
*edit debian/rules and add --with-jpeg8 to the following line
Code: Select all
dh_auto_configure -- --with-build-date=$(DEB_VERSION) $(DISABLE_SIMD) --with-jpeg8
*edit debian/libjpeg62-turbo.install and change the entry to:
Code: Select all
usr/lib/arm-linux-gnueabihf/libjpeg.so.8*
Build libturbo jpeg
*Install the packages.
Code: Select all
sudo dpkg -i ./libjpeg-dev_1.5.1-2_all.deb
sudo dpkg -i ./libjpeg62-turbo-dev_1.5.1-2_armhf.deb
sudo dpkg -i ./libturbojpeg0-dev_1.5.1-2_armhf.deb
sudo dpkg -i ./libjpeg62-turbo_1.5.1-2_armhf.deb
sudo dpkg -i ./libturbojpeg0_1.5.1-2_armhf.deb
sudo dpkg -i ./libjpeg-turbo-progs_1.5.1-2_armhf.deb
*Just remember not to let a system update overwrite these packages with the official ones with jpeg62 support.
5.Build and install the libraries for RPI userland
Code: Select all
sudo apt-get install git
sudo apt-get install cmake
mkdir raspberrypi
cd raspberrypi
git clone https://github.com/raspberrypi/userland.git
cd userland
./buildme
6. Zoneminder looks for a systemd service when started, so create it here
Code: Select all
sudo nano /lib/systemd/system/zoneminder.service
*Paste the following
Code: Select all
# ZoneMinder systemd unit file
# This file is intended to work with all Linux distributions
[Unit]
Description=ZoneMinder CCTV recording and security system
After=network.target mysql.service apache2.service
Requires=mysql.service apache2.service
[Service]
User=www-data
Type=forking
ExecStart=/usr/bin/zmpkg.pl start
ExecReload=/usr/bin/zmpkg.pl restart
ExecStop=/usr/bin/zmpkg.pl stop
PIDFile=/var/run/zm/zm.pid
[Install]
WantedBy=multi-user.target
7. Create the tmpfiles directory with systemd
*Create a file called zoneminder.conf
Code: Select all
sudo nano /etc/tmpfiles.d/zoneminder.conf
*Paste or enter the following to above file
Code: Select all
d /var/run/zm 0755 www-data www-data
d /var/tmp/zm 0755 www-data www-data
*Then save the file.
*Change permissions on the file
Code: Select all
sudo chmod 755 /etc/tmpfiles.d/zoneminder.conf
* Let systemd process the file
Code: Select all
sudo /bin/systemd-tmpfiles --create /etc/tmpfiles.d/zoneminder.conf
* Enable the zoneminder systemd service
Code: Select all
sudo systemctl enable zoneminder.service
8. Make the changes to apache2
* Enable some modules
Code: Select all
sudo a2enmod cgi
sudo a2enmod rewrite
sudo systemctl reload apache2
*If zoneminder.conf is not enabled by now in apache2, enable it and reload apache.
*Verify that zoneminder.conf is in /etc/apache2/conf-available, then
Code: Select all
sudo a2enconf zoneminder
sudo systemctl reload apache2
9. Adust time/date in php.ini
Code: Select all
sudo nano /etc/php/7.0/apache2/php.ini
sudo chown -R www-data:www-data /usr/share/zoneminder/
10. The database zm should have been created by now. If not create with:
Code: Select all
mysql < /usr/share/zoneminder/db/zm_create.sql
mysql -e "grant select,insert,update,delete,create on zm.* to 'zmuser'@localhost identified by 'zmpass';"
*Modify the tables
Code: Select all
sudo mysql -uroot
use zm;
ALTER TABLE Monitors modify column Type enum('Local','Remote','File','Ffmpeg','Ffmpeghw','Libvlc','cURL') NOT NULL default 'Local';
ALTER TABLE MonitorPresets modify column Type enum('Local','Remote','File','Ffmpeg','Ffmpeghw','Libvlc','cURL') NOT NULL default 'Local';
ALTER TABLE Controls modify column Type enum('Local','Remote','Ffmpeg','Ffmpeghw','Libvlc','cURL') NOT NULL default 'Local';
alter table Monitors modify column Function enum('None','Monitor','Modect','Mvdect','Record','Mocord','Nodect') NOT NULL default 'Monitor';
11. Install the modified zoneminder.deb. Hopefully postinst completes with no issue.
*If the postinst script gets stuck and asks to do a "sudo dpkg --configure -a" which just loops the postinst script, then
Code: Select all
sudo dpkg --remove --force-remove-reinstreq zoneminder
*ZM complains of unreadable zm.conf
Code: Select all
sudo chmod 740 /etc/zm/zm.conf
sudo chown root:www-data /etc/zm/zm.conf
*Can't access the webserver if UFW is in use
*ZM complains of not having write access to events and images directories
Code: Select all
sudo chown -R www-data:www-data /usr/share/zoneminder/
*The events, images and temp directories are symlinks to /var/cache/zoneminder
Code: Select all
sudo chown -R www-data:www-data /var/cache/zoneminder/
*Cannot validate swap, disabling buffered playback,
Edit /etc/zm/zm.conf and add
* After all the above probably best to
Code: Select all
sudo systemctl reload apache2
sudo service zoneminder restart
12. Access the Web UI and
* Add New Monitor
Code: Select all
Select Ffmpeg and Mvdect for software h264 decoding via ffmpeg with motion vector extraction.
Select Ffmpeghw and Mvdect for hardware h264 decoding via ffmpeg using mmal and motion vector extraction via hardware mmal h264 encoder.
Hardware Scaling is used when Source=Ffmpeghw Function=Mvdect
Software Scaling is used when source=Ffmpeg Function=Modect|Mvdect
Software Scaling is used when Source=Ffmpeghw Function=Modect
*For an sv3c camera, the settings are:
Code: Select all
Source path = rtsp://mysv3c.chris.net/12
Remote Method = TCP
Capture width = 640
Capture height = 360
Source path = rtsp://mysv3c.chris.net/11
Remote Method = TCP
Capture width = 1280
Capture height = 720
1920x1080 is possible with MVDECT.
***I could only test with one camera but in theory, it should be able to run multiple cameras. Just keep an eye on memory consumption. The kernel uses 25% of the 1GB RAM already, and with 256 MB set aside for GPU MEM, that leaves ~500 MB for all the cameras, mysql and any other running processes.
My current system is a PI3B with 16GB SDCARD. I don't have a hard disk attached so the jpegwriter, mp4writer and mysql are writing to the SD card.
* Define the Zone settings for this camera.
Code: Select all
Click the Zones associated with the Monitor and Select Alarm Check Method as "AlarmPixels"
Put reasonable value for Min Alarmed Area. This value is computed as percentage of polygon area that needs to be covered
by macroblocks to label the frame as motion detected. Its an all or none score.
***The logic of the motion vector score calculation:
The Min Alarmed Area is taken as a percentage value of the polygon total area. Each vector is weighted as having equivalent of 16x16 pixels and each vector is given 4x weight, meaning a 25% pixel coverage is considered 100% coverage. The full frame will be tested so should give meaningful scores. The alarm centre is not being calculated at this time.
My Settings:
Code: Select all
Camera is set at 15 fps on its web UI. //Lower this value to solve problems with buffer overruns.
Source Type = Ffmpeghw
Function = Mvdect
Enabled = checked
Reference Image Blend %ge = No Blending
Alarm Reference Image Blend %ge = No blending (Alarm lasts forever)
Source path = rtsp://mysv3c.chris.net/12
Remote Method = TCP
Target Colorspace = 24 bit color
Capture width = 640
Capture height = 360
Image Buffer size = 20 // Since I started using an external USB drive for storing events, this number has seemed adequate
Warm Up frames = 0
Pre Event Image Count = 1 //All JPEGs are created in the capture process.
Post Event Image Count =60 //increase to have longer events instead of many short ones
Stream Replay Image Buffer = 200
Alarm Frame Count =1 //1 alarm frame is alert only, 2 alarm frames mean record the event as an alarm.
Storage Tab:
Save JPEGs: Frames only.
Video Writer: H264 Camera Passthrough
Zoneminder Config
WATCH_MAX_DELAY = 10
WATCH_CHECK_INTERVAL = 20
OPT_ADAPTIVE_SKIP = checked
CREATE_ANALYSIS_FRAMES = unchecked
13. Optimizations
* Select high bitrate rtsp stream. I think this reduces encoding artifacts that might be seen by the mmal encoder as motion.
* No need to blend the image because we don't use pixel analysis. This greatly reduces zma's cpu utilization.
Code: Select all
Set Reference Image Bled %ge to No Blending.
Set Alarm Reference Image Blend %ge to No blending.
*Reduce the framerate of your rtsp camera. This will be done on the camera side web UI.
*Edit Monitor Options and under Buffers (Image Buffer Size) increase to a higher number
*Uncheck Create_Analsyis_Images
*Adjust WATCH_MAX_DELAY if it keeps restarting zma.
*Set Warm-Up Frames to 0 since we dont need to generate a reference image.
*Use a fast hard disk to ensure jpeg writing and mysql writes don't delay zma and video storage writes don't delay zmc.
*Disable any debugging or logging options not needed in the Logging tab of Options. .
Other Optimizations (dont't know if relevant):
?In Options config OPT_ADAPTIVE_SKIP needs to be checked
?Set Analysis Update Delay
<From Google> Currently, video analysis is performed at full framerate, this can lead to high cpu load.
In order to reduce the cpu load, this PR add an analysis interval parameter to monitors settings.
Default value is 1, all images are processed.
If a greater value is set, for example 5, only images with count multiple of 5 will be processed.
The reason for this is to make it possible to reduce CPU-load if split-second motion detection is not required.
?Set Motion Frame Skip
<From Google> There is a new setting "Motion Frame Skip" under the "Misc" tab in the Monitor settings where you configure the value.
The default value is 0, so the feature is not active by default.
The feature works like Frame Skip. That is, if the value is "5" every 6th image will be analyzed for motion. The reference image is updated every frame to not change the effect of current blend settings.
14. Building the zoneminder deb
*Install the necessary packages for building
Code: Select all
sudo apt-get install ccache
sudo apt-get install build-essential fakeroot devscripts
*Install the dependencies for building
Code: Select all
sudo apt-get install libnetpbm10-dev
sudo apt-get install libvlccore-dev
sudo apt-get install libgcrypt11-dev
sudo apt-get install libssl-dev
sudo apt-get build-dep zoneminder
*Clone the repo
Code: Select all
git clone https://github.com/cmisip/ZoneMinder.git
cd ZoneMinder
Latest work is now merged in the fork's master branch. It uses mmal decoder natively now so no need for ffmpeg's h264_mmal decoder. The motion vector code is now integrated into the video capture module. I use passthrough mode. Some of the analysis processing has been moved to the capture side to reduce zma's latency. The capture process zmc is now computing alarm_frames and sending the value to zma. Zmc is preemptively encoding jpegs using the mmal jpeg encoder and sending them to zma via shared mem when zmc thinks an alarm will be triggered in zma. To make 1920x1080 rtsp stream useable using 150 size ringbuffer ( to prevent buffer overruns) , an intermediate downscale step is introduced. The steps are: Rtsp packets are decoded by MMAL_COMPONENT_DEFAULT_VIDEO_DECODER at full resolution. vc.ril.isp, downscales to 640x360 and creates the RGB buffer. MMAL_COMPONENT_DEFAULT_VIDEO_ENCODER processes the downscaled video for motion vectors. MMAL_COMPONENT_DEFAULT_IMAGE_ENCODER converts the downscaled frames into jpegs. The video capture module will save the original decoded packets at full resolution into an mp4 file.
Due to the changes above, there are some UI issues that have not been fixed yet. The zones page on the web UI displays the downscaled frame but the zone polygon is displayed at full resolution. Setting the video resolution to 640x360 fixes the UI issue but adjusting the zone polygon may cause a segfault. I think the web interface is communicating with zoneminder via database and so does not know of the adjustments to resolution and polygon coordinates. Text annotation on jpeg does not work on the capture side jpegs. The jpeg display in the Event window now includes pixel arrows to show the direction and clustering of motion vectors which would be useful in developing a scoring system. It is turned on in the code so performance will suffer a little.
* Download the web api
Code: Select all
git submodule update --init --recursive
* Edit /etc/apt/sources.list and uncomment the deb-src line
* Make changes to the source.
* Build the package.
Code: Select all
cd cmake
cmake ../
cd ..
debuild --prepend-path=/usr/lib/ccache -us -uc -b
Issues:
This is about 4000 commits behind zoneminder master so it will look and work differently than the most recent builds.
1. Frames jumping back in time or skipping. This might be due to an overburdened system where the capture and analysis components are being restarted by zoneminder. If you can avoid buffer overruns, this should be minimized. This doesn't matter if you use the video capture module as the event display will playback the mp4 at full resolution.
2. Alignment trap might show up here and there.
3. I have done all this work on the arm natively and so probably won't compile on X86.
4. Software motion vector code has been removed for now.
5. The resolution you put in the monitor setup screen may not matter because the video resolution is autodetected by avcodec and it will be downscaled to 640x360 anyway internally. The recorded jpegs will be at 640x360 but the recorded mp4 video will be in full resolution.
Here is the speed test with one rtsp stream at 640x360 with buffer visualization turned on at 15 fps source.
Code: Select all
PIDSTAT zmc : Reporting average of 12 readings at 5 seconds intervals
ZMC Process ID : 27301 ==> ( 15.40 + 14.60 + 14.00 + 14.20 + 13.40 + 12.80 + 13.20 + 13.20 + 12.20 + 13.00 + 12.80 + 13.60 ) / 12
AVERAGE : 13.53
PIDSTAT zma : Reporting average of 12 readings at 5 seconds intervals
ZMA Process ID : 27305 ==> ( 5.40 + 1.40 + 0.20 + 0.00 + 1.40 + 2.80 + 4.20 + 1.60 + 2.40 + 0.40 + 0.00 + 3.20 ) / 12
AVERAGE : 1.91
And the output of top:
Code: Select all
Tasks: 128 total, 2 running, 82 sleeping, 0 stopped, 0 zombie
%Cpu(s): 3.3 us, 4.2 sy, 0.0 ni, 80.8 id, 11.6 wa, 0.0 hi, 0.1 si, 0.0 st
KiB Mem : 604356 total, 41972 free, 155468 used, 406916 buff/cache
KiB Swap: 102396 total, 52220 free, 50176 used. 345532 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
27301 www-data 20 0 285124 51852 43556 R 13.8 8.6 0:28.61 zmc
27305 www-data 20 0 237468 45552 38584 S 3.0 7.5 0:04.64 zma
27372 pi 20 0 8448 3084 2560 R 1.6 0.5 0:00.20 top
754 mysql 20 0 639116 43456 9096 S 1.3 7.2 2:15.32 mysqld
Please try at your own risk. I am not responsible for wasted time, effort or hardware. I have only done very limited testing. It might crash in the morning or on rainy days or everyday.
If there is an expert here with regards to figuring out memory issues, I would appreciate some assistance with the code. Have Fun.
Thanks,
Chris