{\rtf1\ansi\ansicpg1252\uc1\deff0\stshfdbch0\stshfloch0\stshfhich0\stshfbi0\deflang2057\deflangfe2052{\fonttbl{\f0\froman\fcharset0\fprq2{\*\panose 02020603050405020304}Times New Roman;}{\f1\fswiss\fcharset0\fprq2{\*\panose 020b0604020202020204}Arial;}
{\f37\fnil\fcharset134\fprq2{\*\panose 02010600030101010101}@SimSun;}{\f38\froman\fcharset238\fprq2 Times New Roman CE;}{\f39\froman\fcharset204\fprq2 Times New Roman Cyr;}{\f41\froman\fcharset161\fprq2 Times New Roman Greek;}
{\f42\froman\fcharset162\fprq2 Times New Roman Tur;}{\f43\froman\fcharset177\fprq2 Times New Roman (Hebrew);}{\f44\froman\fcharset178\fprq2 Times New Roman (Arabic);}{\f45\froman\fcharset186\fprq2 Times New Roman Baltic;}
{\f46\froman\fcharset163\fprq2 Times New Roman (Vietnamese);}{\f48\fswiss\fcharset238\fprq2 Arial CE;}{\f49\fswiss\fcharset204\fprq2 Arial Cyr;}{\f51\fswiss\fcharset161\fprq2 Arial Greek;}{\f52\fswiss\fcharset162\fprq2 Arial Tur;}
{\f59\fmodern\fcharset204\fprq1 Courier New Cyr;}{\f61\fmodern\fcharset161\fprq1 Courier New Greek;}{\f62\fmodern\fcharset162\fprq1 Courier New Tur;}{\f63\fmodern\fcharset177\fprq1 Courier New (Hebrew);}
{\f64\fmodern\fcharset178\fprq1 Courier New (Arabic);}{\f65\fmodern\fcharset186\fprq1 Courier New Baltic;}{\f66\fmodern\fcharset163\fprq1 Courier New (Vietnamese);}{\f170\fnil\fcharset0\fprq2 SimSun Western{\*\falt ???????\'a1\'ec????};}
\rsid15665044\rsid15818602\rsid15891821\rsid15940289\rsid15997286\rsid15999523\rsid16081520\rsid16128633\rsid16190191\rsid16201578\rsid16266742\rsid16398105\rsid16411483\rsid16480465\rsid16663174\rsid16720206}{\*\generator Microsoft Word 10.0.2627;}{\info
{\title ZoneMinder v1.21.1}{\subject ZoneMinder User Guide}{\author Philip Coombes}{\operator Philip Coombes}{\creatim\yr2005\mo1\dy16\hr17\min17}{\revtim\yr2005\mo6\dy13\hr11\min9}{\printim\yr2004\mo5\dy20\hr13\min48}{\version52}{\edmins1075}
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid150409 Welcome to ZoneMinder, the all-in-one Linux GPL'd security camera solution.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 A while back my garage was burgled and all my power tools were }{\insrsid14238447 stolen}{\insrsid150409 ! I realise
d shortly after that if I'd just had a camera overlooking the door then at least I'd have know exactly when and who did the dirty deed. And so ZoneMinder was born. It's still }{\insrsid8588488 relatively new}{\insrsid150409 but hopefully it }{
\insrsid8588488 has developed}{\insrsid150409 to be something that can be genuinely useful and prevent similar incidents or }{\insrsid8588488 even }{\insrsid150409 perhaps bring some perpetrators to justice.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 ZoneMinder is designed around a series of independent components that only function when necessary limiting any wasted resource and maximising the efficiency of you
r machine. A fairly ancient Pentium II PC should be able to track one camera per device at up to 25 frames per second with this dropping by half approximately for each additio}{\insrsid8588488 nal camera on the same device. A}{\insrsid150409
dditional cameras on other devices do not interact so can maintain this frame rate. Even monitoring several cameras still will not overload the CPU as frame processing is designed to synchronise with capture and not stall it.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 As well as being fast ZoneMinder is designed to be friendly and even more than
that, actually useful. As well as the fast video interface core it also comes with a user friendly and comprehensive PHP based web interface allowing you to control and monitor your cameras from home or even at work or on the road. It supports variable we
b
capabilities based on available bandwidth. The web interface also allows you to view events that your cameras have captured and archive them or review them time and again, or delete the ones you no longer wish to keep. The web pages directly interact wit
h the core daemons ensuring full co-operation at all times. ZoneMinder can even be installed as a system service ensuring it is right there if your computer has to reboot for any reason.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 The core of ZoneMinder is the capture and analysis of images and there
is a highly configurable set of parameters that allow you to ensure that you can eliminate false positives whilst ensuring that anything you don't want to miss will be captured and saved. ZoneMinder allows you to define a set of 'zones' for each camera o
f varying sensitivity and functionality. This allows you to eliminate regions that you don't wish to track or define areas that will alarm if various thresholds are exceeded in conjunction with other zones.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 ZoneMinder is fresh off the keyboard and so comes
with no warranty whatsoever, please try it, send your feedback and if you get anything useful out of it let me know.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 ZoneMinder is free but if you do get ZoneMinder up and running and find it useful then please feel free to visit }{\field\fldedit{\*\fldinst {\insrsid150409
{\cs16\ul\cf2\insrsid150409 http://www.zoneminder.com/donate.html}}}{\insrsid150409 where }{\b\insrsid150409\charrsid8588488 any donations will be appreciated}{\insrsid150409 and will help to fund future improvements }{\insrsid9068019 to }{
\insrsid150409 ZoneMinder. This would be especially }{\insrsid8588488 relevant}{\insrsid150409 if you use ZoneMinder as part of your business}{\insrsid8588488 ,}{\insrsid150409 or to protect your property.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid150409 ZoneMinder needs a couple of things to work.
Firstly, it uses MySQL so you'll need that. In order to compile you need to make sure you have a development installation and not just a runtime; this is because it needs to use the MySQL header files. If you are running an RPM based distribution then it
\par Next it does things with JPEGs so you'll need at least libjpeg.a which I think come as standard nowadays with most distributions. }{\insrsid6106433
Users have reported varying degrees of success with other jpeg libraries such as jpeg-mmx but these are not officially supported. }{\insrsid150409 It also uses the netpbm utilities in a very limited way to generate thumbnails under
certain circumstances though this can be modified.
ZoneMinder can generate MPEG videos if necessary, for this you'll need either ffmpeg (recommended) or the Berkeley MPEG encoder (mpeg_encode). If you don't have either, don't worry, as the options will be hidden and you'll not really miss }{
\insrsid7103735 too }{\insrsid150409 much. }{\insrsid7103735 Some of the authentication uses openssl MD5 functions, if you get a grumble about these during configuration all it will mean is that authentication won\rquote t be used for streaming. }{
you need that in your apache or other web server as well, make sure MySQL support is available either statically or as a module. There are also various perl modules that you may need that vary depending on which options you choose on installation, for mor
Finally, there is quite a bit of image streaming in the package. So if you don't have Netscape or another browser that supports image streaming natively I recommend you get the excellent Cambozola java applet from }{\cs16\ul\cf2\insrsid150409 http:
//www.charliemouse.com/code/cambozola/}{\insrsid150409 which will let you view the image stream in Internet Explorer and others. Otherwise you're limited to just refreshing still images.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 Hardware-wise, ZoneMinder has been used with various video and USB cameras with the V
4L interface. I don't have a lot of cameras myself so I've not had change to test it with a huge range personally however there is a list of devices that are definitely known to work on the web site. Please let me know if your camera works and is not list
ed. You do need to have Video4Linux installed. I've not got too many machines so I've only really used it on various RedHat}{\insrsid7103735 /Fedora}{\insrsid150409
distributions, which seem to have everything there by default I think. SlackWare does need a bit more tinkering than other dis
tributions; there is a document on the web site describing what users have had to do to get it working. Please give me feedback on other distributions not listed on the site.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid150409 The first thing you need to do is run the included configure script to d
efine some initial configuration, just type
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\i\insrsid150409 ./configure --with-mysql=<your MySQL root> --with-webdir=<your web directory> --with-cgidir=<your cgi directory>
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 where }{\i\insrsid150409 --with-mysql}{\insrsid150409 identifies the root directory where you have installed MySQL (usually /usr), }{\i\insrsid150409 --with-webdir
}{\insrsid150409 is the directory to which you want to install the PHP files, and }{\i\insrsid150409 --with-cgidir}{\insrsid150409 is the directory to which you want to install CGI files. These directories could be }{\i\insrsid150409 /var/www/html/zm}{
\insrsid150409 and }{\i\insrsid150409 /var/www/cgi-bin}{\insrsid150409 for example. If you want to use real MPEG based streaming you will need to have built and installed the ffmpeg tools. You can then also use }{\i\insrsid150409 \endash
with-ffmpeg=<path to ffmpeg }{\i\insrsid16663174 root}{\i\insrsid150409 >}{\insrsid150409 to help configure find it}{\insrsid4538194 if it\rquote s not installed in a default location}{\insrsid150409 .}{\insrsid16663174
Note, you have to make sure you have installed the ffmpeg headers and libraries rather than just the binaries, or a development package with them in.}{\insrsid150409 }{\insrsid16663174 Additionally i}{\insrsid150409
f you have built ffmpeg with the mp3lame feature turned on you}{\insrsid16663174 may}{\insrsid150409 additionally need to tell configure where to find }{\insrsid16663174 that the mp3lame library}{\insrsid150409 , to
prevent unresolved dependencies. To do this add the }{\i\insrsid150409 \endash with-lame=<path to lame directory>}{\insrsid150409 option as well. There are also two further arguments you can add if your web user and group are not both 'apache'. These are
}{\i\insrsid150409 --with-webuser}{\insrsid150409 and }{\i\insrsid150409 --with-webgroup}{\insrsid150409 . Type
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\i\insrsid150409 ./configure \endash help
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 for details on these options.
That's the build configuration sorted out. The next thing you have to do is do a little more runtime specific configuration. ZoneMinder configuration is scattered around various files in the distribution so to m
ake things easier for you there is a ZoneMinder configuration utility included. Type
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 to get it started. It is an interactive utility and will prompt you by asking you various questions. For most questions typing '?' will give you additio
nal help if you need it. Once you've answered all the questions it will write out a configuration file called 'zmconfig.txt' and then process various files to substitute the information in them. If you run it again it will remember your answers from. If y
ou just want to rerun the substitutions you can run zmconfig.pl in non-interactive mode by typing
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 which will just read your file and do the substitutions with no questions asked. There are two classes of options, \lquote core\rquote options which
much be specified with zmconfig which detail things such as database passwords which are compiled into ZoneMinder and other options with are stored in the database and which can be modified dynamically via the \lquote options\rquote
section of the web interface. Only the first set need to be completed with zmconfig at this stage. If you want to change just a few options and can\rquote
t access the options dialog via the web you can append them as parameters to zmconfig and it will just ask you about those. So for example,
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 however it is fairly dumb and will not tell you if you make a typo and misspell an option.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 Among the first questions zmconfig.pl asks you are to do with the database and the next thing you should do is create it and t
he associated database user. The included schema (zmschema.sql) can be used to actually create the tables required. The database is usually called just 'zm'}{\insrsid6106433 but can be anything you like}{\insrsid150409 .
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 If you are a first time user the first run of zmconfig.pl will warn you about the missing database, you can ignore those errors this time. Once you\rquote
ve run it for the first time the schema file should have your desired database name in it so use it to create the database (see below). Once the database and permissions are set up rerun zmconfig.pl with the \endash
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 If you are upgrading from a previous version you can use zmalter-x.y.z.sql to upgrade your database and make the necessary changes where x.y.z identifies
the version of ZoneMinder you had installed previously. So if you are going from version 0.9.7 to version 0.9.11 you would run the scripts for all intervening versions to get to the current one, i.e. zmalter-0.9.7.sql, zmalter-0.9.8.sql, zmalter-0.9.9.sq
l and zmalter0.9.10.sql.}{\insrsid4538194 }{\insrsid6106433 Alternatively}{\insrsid4538194
from version 1.19.5 you can use the zmupdate.pl script to do all the updating for you, this will include all the database changes plus any other tweaks necessary to upgrade to the latest version. To use it you should type}{\insrsid150409
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid4538194 {\insrsid4538194 where \lquote previous version\rquote relates to the ver}{\insrsid7103735 s}{\insrsid4538194
ion of ZM you are upgrading from, 1.19.4 for example. All updates from that versions onwards will be applied, however zmupdate.pl will only work with upgrades from 1.19.0 onwards. The \lquote user\rquote and \lquote pass\rquote
options allow you to specify a database user and password with sufficient privilege to \lquote alter\rquote the structure of the database.}{\insrsid11947186 This is not necessarily the database user you use for Zo
neMinder itself as specified in the section below.}{\insrsid4538194\charrsid4538194
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 For a new installation the simplest way to create your database and users is as follows,
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\i\insrsid150409 grant select,insert,update,delete on <your database name>.* to '<username>'@localhost identified by '<password>';
You may need to supply a username and password to the mysql commands in the first place to give yourself sufficient privileges to perform the required commands. If you want to host your database o
n a different machine than that which ZoneMinder is running on then use the hostname of the remote machine instead of localhost.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 Then just type }{\i\insrsid150409 'make'}{\insrsid150409 and off you go.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid150409 Once the build has completed you should have several shiny new binaries. I w
- This is the ZoneMinder Capture daemon. This binary's job is to sit on a video device and suck frames off it as fast as possible, this should run at more or less constant speed.
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0 {\b\insrsid150409 zma}{\insrsid150409 - This is the ZoneMi
nder Analysis daemon. This is the component that goes through the captured frames and checks them for motion which might generate an alarm or event. It generally keeps up with the Capture daemon but if very busy may skip some frames to prevent it falling
behind.
\par }{\b\insrsid150409 zmf}{\insrsid150409
- This is the ZoneMinder Frame daemon. This is an optional daemon that can run in concert with the Analysis daemon and whose function it is to actually write captured frames to disk. This frees up the Analysis daemon to do more analysis (!) and
so keep up with the Capture daemon better. If it isn\rquote t running or dies then the Analysis daemon just writes them itself.
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0 {\b\insrsid150409 zms}{\insrsid150409 - This is the ZoneMinder Streaming server. The web interface connects with this to get real-time or historical streamed images. It
runs only when a live monitor stream or event stream is actually being viewed and dies when the event finishes or the associate web page is closed. If you find you have several zms processes running when nothing is being viewed then it is likely you need
a patch for apache (see the Troubleshooting section).
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0 {\b\insrsid150409 zmu}{\insrsid150409 - This is the ZoneMinder Utility. It's basically a handy command line interface to several useful functions. It\rquote
s not really meant to be used by anyone except the web page (there's only limited 'help' in it so far) but can be if necessary, especially for debugging video problems.
- This is a small binary that exists only to ensure that the video device files can be read by the main capture daemons. It is often the case that these device files ar
e set to be accessible by root only on boot. This binary runs setuid and ensures that they have appropriate permissions. This is not a daemon and runs only on system start and then exits.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 As well as this there are the web PHP files in the web directory and
some perl scripts in the scripts directory. These scripts all have some configuration at the top of the files which should be viewed and amended if necessary and are as follows.
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0 {\b\insrsid150409 zmpkg.pl}{\insrsid150409 - This is the ZoneMinder Package Control script. This is used by the
web interface and service scripts to control the execution of the system as a whole.
- This is the ZoneMinder Daemon Control script. This is used by the web interface and the zmpkg.pl script to control and maintain the execution of the capture and analysis daemons, amongst others. You should not need to run this script yourself.
\par }{\b\insrsid150409 zmfilter.pl}{\insrsid150409 - This script controls the execution of saved filters and will be started and stopped by the web interface based on whether there are filters that have been def
ined to be autonomous. This script is also responsible for the automatic uploading of events to a 3rd party server.
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0 {\b\insrsid150409 zmaudit.pl}{\insrsid150409 - This script is used to check the consistency of the event file system and database. It can delete orphaned events, i.e. ones th
at appear in one location and not the other as well as checking that all the various event related tables are in line. It can be run interactively or in batch mode either from the command line or a cron job or similar. In the zmconfig.pl there is an optio
n to specify fast event deletes where the web interface only deletes the event entry from the database itself. If this is set then it is this script that tidies up the rest.
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid6360098 {\b\insrsid6360098 zmwatch.pl}{\insrsid6360098 - This is a simple script purely designed to keep an eye on the capture
daemons and restart them if they lockup. It has been known for sync problems in the video drivers to cause this so this script makes sure that nothing important gets missed.
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid6360098 {\b\insrsid6360098 zmupdate.pl}{\insrsid6360098 \endash Currently this script is responsible for checking whether a new vers
ion of ZoneMinder is available and other miscellaneous actions related to upgrades and migrations. It is also intended to be a \lquote one stop shop\rquote
for any upgrades and will execute everything necessary to update your installation to a new version.
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0 {\b\insrsid150409 zmx10.pl}{\insrsid150409 - T
his is an optional script that can be used to initiate and monitor X10 Home Automation style events and interface with an alarm system either by the generation of X10 signals on ZoneMinder events or by initiating ZoneMinder monitoring and capture on recei
pt of X10 signals from elsewhere, for instance the triggering of an X10 PIR. For example I have several cameras that don\rquote
t do motion detection until I arm my alarm system whereupon they switch to active mode when an X10 signal is generated by the alarm system and received by ZoneMinder.
\par }\pard \s15\qj \li357\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin357\itap0\pararsid16398105 {\b\insrsid16398105 zmtrigger.pl}{\insrsid16398105 - This is }{\insrsid6360098 an}{\insrsid16398105
optional script that is a more generic solution to external triggering of alarms. It can handle external connections via either internet socket, unix socket or file/device interfaces. Currently you have to configure these using the \lquote sources
\rquote array in the script itself though ultimately I would expect they would be databased. The format of triggers used by zmtrigger.pl is as follows}{\insrsid16398105\charrsid16398105 }{\insrsid16398105 \'93<id>|<action>|<score>|<cause>|<text>}{
\insrsid7282709 |<showtext>}{\insrsid16398105 \'94 where
\insrsid7282709 'action' is 'on', 'off', }{\insrsid16398105 'cancel' }{\insrsid7282709 or \lquote show\rquote }{\insrsid16398105
where 'on' forces an alarm condition on, 'off' forces an alarm condition off and 'cancel' negates the previous 'on' or 'off'. }{\insrsid7282709 The \lquote show\rquote action merely updates some auxiliary text
which can optionally be displayed in the images captured by the monitor. }{\insrsid16398105
Ordinarily you would use 'on' and 'cancel', 'off' would tend to be used to suppress motion based events. Additionally 'on' and 'off' can take an additional time offset, e.g. on+20 wh
ich automatically 'cancel's the previous action after that number of seconds.
\insrsid16398105 'score' is the score given to the alarm, usually to indicate it's importance. For 'on' triggers it should be non-zero, otherwise it should be zero.
\par {\listtext\pard\plain\s15 \f3\fs20\lang2057\langfe1033\langfenp1033\insrsid16398105 \loch\af3\dbch\af0\hich\f3 \'b7\tab}'cause' is a 32 char max strin
g indicating the reason for, or source of the alarm e.g. 'Relay 1 open'. Ignored for 'off' or 'cancel' messages
'text' is a 256 char max additional info field, currently not used for anything though anything passed in here will get saved. Ignored for 'off' or 'cancel' messages.
\insrsid7282709 \lquote showtext\rquote is up to 32 characters of text that can be displayed in the timestamp that is added to images. The \lquote show\rquote
action is designed to update this text without affecting alarms but the text is updated, if present, for any of the actions. This is designed to allow external input to appear on the images captured, for instance temperature or personnel identity etc.
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid16398105 {\insrsid16398105 Note that multiple messages can be sent at once and should be LF or CRLF delimited.}{\insrsid1904016 Without customisation zmtrigger.pl i
s of little use, but if you configure it correctly it can help integrate other systems to generate external triggers that will cause ZoneMinder events.}{\insrsid16398105
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid6360098 {\b\insrsid6360098 zmcontrol-*.pl}{\insrsid6360098 \endash These are a set of example scripts which can be used to control Pan/Tilt/Zoom class cam
eras. Each script converts a set of standard parameters used for camera control into the actual protocol commands sent to the camera. If you are using a camera control protocol that is not in the shipped list then you will have to create a similar script
though it can be created entirely separately from ZoneMinder and does not need to named as these scripts are.}{\insrsid658843
Although the scripts are used to action commands originated from the web interface they can also be used directly or from other programs or scripts, for instance to implement periodic scanning to different presets.}{\insrsid6360098
This script is used to manage the experimental motion tracking feature. It is responsible for detecting that an alarm is taking place and moving the camera to point to the ala
rmed location, and then subsequently returning it to a defined standby location.}{\insrsid658843
As well as moving the camera it also controls when motion detection is suspended and restored so that the action of the camera tracking does not trigger endless further alarms which are not justified.}{\insrsid6360098
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0 {\b\insrsid150409 zm}{\insrsid150409 - This is the (optional) ZoneMinder init script, see below for details.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 Finally, check zm_config.php in the web directory and amend any configuration necessary in there. Most will have already been done by the configuration uti
lities but some scripts have a \lquote VERBOSE\rquote flag you can set to get more debug out.
At this stage typing 'make install' will install everything to the desired locations, you may wish to su to root first though. The installation routine will copy the binaries
and scripts to your chosen install location, usually /usr/local/bin and then move zms to your cgi-bin area. It will then copy the web files to your chosen directory and ensure they have the right permissions. Finally it tries to link zm.php to index.php b
ut will not overwrite an existing file if it already exists.
\par The 'zm' script does not get installed automatically as it is not necessary for the operation of the ZoneMinder setup per se and is not necessarily supported for distributions other than }{\insrsid658843 those from the }{\insrsid150409 RedHa}{
\insrsid658843 t or Fedora families.}{\insrsid150409 However if you want to ensure that the ZoneMinder daemons are started on reboot etc copy it to your init.d directory, usually something like /etc/rc.d/init.d and then add it by doing
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 or similar command for your distribution. ZoneMinder will then start up when your machine reboots and can be controlled (by the root user) by doing }{
\i\insrsid150409 'service zm start'}{\insrsid150409 or }{\i\insrsid150409 'service zm stop'}{\insrsid150409 etc. You may need to use the \lquote }{\cs26\i\insrsid150409 \emdash levels}{\insrsid150409 \rquote
parameter to chkconfig to ensure that ZoneMinder is started when you need it to.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 Now start your web browser}{\insrsid14175248 , }{\insrsid150409 point it at your zm.php and off you go.
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid9068019 {\insrsid9068019 All documents including this README are installed to the systems default document folder.
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid9068019 {\insrsid9068019 The packaged version of Zone Minder installs all binarys to /usr/lib/zm including the web pages. So don\rquote t worry
when you do not see any files installed to the root directory for your web server. The web pages for Apache are aliased by zm.conf in the apache/conf.d directory which vary depending on your distribution:
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid9068019 {\insrsid9068019 T
he Configuration file for setting up the database is located at /etc/zm.conf and will need to be edited to add the user and password that you want Zone Minder to use. After you have installed the Zone Minder package this will be the first thing you want t
o do. So use your favourite editor and add in the user name and password you want Zone Minder to use. You can also change the database name if you would like.
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid9068019 {\insrsid9068019 Start the mysqld service so you can build the database
\par }\pard \s15\qj \li720\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin720\itap0\pararsid9068019 {\i\insrsid9068019\charrsid8416706 service mysqld start
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid9068019 {\insrsid9068019 Then run zminit to create the database
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid9068019 {\insrsid9068019 The user and password that zminit asks for are for the database only. For the user enter }{\i\insrsid9068019\charrsid8416706 root}{
\insrsid9068019 and leave the password blank (unless of course you changed the password). You should see some information showing that it has created the database and no errors.
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid9068019 {\insrsid9068019 Set the run levels for the services that Zone Minder requires. I like to set the run levels to 3 and 5 with the following command:
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid9068019 {\insrsid9068019 Now start the web server and Zone Minder:
\par }\pard \s15\qj \li720\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin720\itap0\pararsid9068019 {\i\insrsid9068019\charrsid8416706 service httpd start
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid9068019 {\insrsid9068019 You should now be able to access the Zone Minder console through the web browser }{\field\fldedit{\*\fldinst {\insrsid9068019
\par }\pard \s15\qj \li360\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin360\itap0\pararsid9068019 {\insrsid9068019 Log files will be located in /var/log/zm
What you see now (and subsequently) depends on whether you chose to run ZoneMinder in authenticated mode or not. This is an option that lets you specify whether anyone that goes to the ZoneMinder web pages must authentica
te themselves in order to be given permissions to perform certain tasks. If you chose this mode then you will need to log in here. By default a fully privileged user \lquote admin\rquote has been created with a password also of \lquote admin\rquote
. You should change this password as soon as possible.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 Once you\rquote
ve logged in, or if you are running in un-authenticated mode, you will now see the ZoneMinder Console window. This will resize itself to avoid being too intrusive on your desktop. Along the top there are several informational
entries like the time of the last update and the current server load. There will also be an indication of the system state which will probably say \lquote stopped\rquote
to start with. This is a link that you can click on to control the ZoneMinder system as a whole. Be
low that are various other links including one detailing the current user (in authenticated mode only) and one allowing you to configure your bandwidth. This last one enables you to optimise your settings depending on where you are, the actual values rela
t
ing to this are defined in the options. If you are using a browser on the same machine or network then choose high, over a cable or DSL link maybe choose medium and over a dialup choose low. You can experiment to see which is best. This setting is retaine
d on a per machine basis with a persistent cookie. Also on this line are a number of other links that will be covered below.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 Please bear in mind that from here on the descriptions of the web pages are based on what you will see if you are running as a fully
authenticated user. If you are running in un-authenticated mode or as a less privileged user then some elements may not be shown or will be disabled.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid150409 To use ZoneMinder properly you need to define at least one Monitor. Essentially, a moni
tor is associated with a camera and can continually check it for motion detection and such like. So, next click 'Add New Monitor' to bring up the dialog. You will see a bunch of things you have to fill in.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 To help you get started on the video configuration the best thing is to us}{\insrsid6106433 e}{\insrsid150409 a tool like 'xawtv' (}{\field\fldedit{\*\fldinst {
) to get a picture you're happy with, and to check your camera works.}{\insrsid6106433 Please note that just because you can see a video stream in these tools
does not necessarily guarantee that your camera will work with ZoneMinder. This is because most tools just \lquote map\rquote
the video image through onto screen memory transparently without intercepting it, whereas ZoneMinder needs to capture the image and, usually,
inspect it. This is called frame grabbing and to check it you should use the facility in xawtv, or other tool, to capture either one or more still images or possibly a movie. If this works and the images or movie are not garbage then the chances are that
ZoneMinder will work fine also.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid6106433 Once you have validated your camera}{\insrsid150409
run 'zmu -d <device_no> -q -v' to get a dump of the settings (note, you will have to additionally supply a username and password to zmu if you are running in authenticated mode). You can th
en enter these values into the video related options of the monitor configuration panel. The 'device_no' referred to here is a number corresponding to the digit at the end of your device file, so /dev/video0 has a 'device_no' of 0 etc. If 'zmu' gives you
an error related to permissions run 'zmfix -a' to make sure you can access all the video devices.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 The options are divided into a set of tabs to make it easier to edit. You do not have to \lquote save\rquote
to change to different tab so you can make all the changes you require and then click \lquote Save\rquote at the end. The individual option are explained in a little more detail below,
The name for your monitor. This should be made up of alphanumeric characters (a-z,A-Z,0-9) and hyphen (-) and underscore(_) only. Whitespace is not allowed.
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid150409 'None' }{\b\insrsid10880688 \endash }{\insrsid150409 The monitor is currently disabled and no streams can be viewed or events generated.
\par {\listtext\pard\plain\s32 \f3\fs20\lang2057\langfe1033\langfenp1033\insrsid150409 \loch\af3\dbch\af0\hich\f3 \'b7\tab}'Monitor' }{\b\insrsid10880688 \endash }{\insrsid150409 The monitor will only
stream feeds but no image analysis is done and so no alarms or events will be generated,
Record\rquote \endash In this case continuous events of a fixed length are generated regardless of motion which is analogous to a convention time-lapse video recorder. No motion detection takes place in this mode.
Mocord\rquote \endash This is a hybrid of Modect and Record and results in both fixed length events being recorded and also any motion being highlighted within those events.
\insrsid1904016 'Nodect' \endash or No DEteCTtion. This is a special mode designed to be used with external triggers. In Nodect no motion detection takes place but events are recorded if external triggers require it.
\par }\pard\plain \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid150409 Generally speaking it is best to choose \lquote Monitor\rquote as an initial setting here..
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 Section Length}{\insrsid150409 \endash This specifies the length (in seconds) of any fixed length events produced when the monitor function is \lquote
Record\rquote or \lquote Mocord\rquote . Otherwise it is ignored. This should not be so long that events are difficult to navigate nor so short that too many events are generated. A length of between 300 and 900 seconds I recommended.
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 Frame Skip }{\insrsid150409 \endash This setting also applies only to the \lquote Record\rquote or \lquote Mocord\rquote functions and specifies
how many frames should be skipped in the recorded events. The default setting of zero results in ev}{\insrsid7282709 ery captured frame being saved. Using a value of }{\insrsid150409 one would mean that one frame is skipped between ea}{\insrsid7282709
ch saved}{\insrsid150409 , two means that two frames are skipped between each saved }{\insrsid7282709 frame}{\insrsid150409 etc. An alternate way of thinking is that one in every \lquote Frame Skip + 1\rquote
frames is saved. The point of this is to ensure that saved events do not take up too much space unnecessarily whilst still allowing the camera to capture at a fairly hi
gh frame rate. The alternate approach is to limit the capture frame rate which will obviously affect the rate at which frames are saved.
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 Run Mode }{\insrsid150409 \endash Two choices are available here. \lquote Continuous\rquote is the usual setting and means that the monitor is expected to
be performing the function selected above at all times and should one or more of the daemons fail or not be running it will be automatically restarted. By contrast \lquote Triggered\rquote
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 Triggers }{\insrsid150409 \endash This small section lets you select which triggers will apply if the run mode has been set to \lquote triggered\rquote
above. The most common trigger is X10 and this will appear here if you indicated that your system supported it during installation. Only X10 is supported as a shipped trigger with ZoneMinder at present but it is }{\insrsid7282709 possible}{
\insrsid150409 that other triggers will become available as necessary. You can also just use \lquote cron\rquote jobs or other mechanisms to actually control the camera and keep them completely outside of the ZoneMinder settings.}{\insrsid7282709
The zmtrigger.pl script is also available to implement custom external triggering.}{\insrsid150409
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 Source Type}{\insrsid150409 \endash This determines whether the camera is a local one attached to a physical video or USB p
ort on your machine or a remote network camera or similar. Choosing one or the other affects which set of options are shown in the next tab.
For a local camera enter the device number that your camera is
attached to. If it is /dev/video0 enter '0' etc. Some video devices, e.g. BTTV cards support multiple cameras on one device so in this case enter the channel number in the Channel box or leave it at zero if you're using a USB camera or one with just one c
For a local camera enter the video format of the video stream. This is defined in various system files (e.g. /usr/include/linux/videodev.h) but the two most common are 0 for PAL and 1 for NTSC.
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 Capture Palette}{\insrsid150409 }{\b\insrsid10880688 \endash }{\insrsid150409 Finally for the vide
o part of the configuration enter the colour depth. ZoneMinder supports a handful of the most common palettes, so choose one here. If in doubt try grey first, and then 24 bit colour. If neither of these work very well then YUV420P or one of the others pro
b
ably will. There is a slight performance penalty when using palettes other than grey or 24 bit colour as an internal conversion is involved. These other formats are intended to be supported natively in a future version but for now if you have the choice c
The dimensions of the video stream your camera will supply. If your camera supports several just enter the one you'll want to use for this application, you can always change it later. However I woul
d recommend starting with no larger than 320x240 or 352x288 and then perhaps increasing and seeing how performance is affected. This size should be adequate in most cases. Some cameras are quite choosy about the sizes you can use here so unusual sizes suc
If your camera is mounted upside down or at right angles you can use this field to specify a rotation that is applied to the image as it is captured. This incurs an additional processing overhead so if
possible it is better to mount your camera the right way round if you can}{\insrsid7282709 . }{\insrsid150409
If you choose one of the rotation options remember to switch the height and width fields so that they apply, e.g. if your camera captures at 352x288 and you choose \lquote Rotate Right\rquote here then set the height to be 352 and width to be 288.}{
\insrsid7282709 You can also choose to \lquote flip\rquote the image if your camera provides mirrored input.}{\insrsid150409
For remote cameras use these fields to enter the full URL of the camera. Basically if your camera is at }{\cs16\ul\cf2\insrsid150409 http://camserver.home.net:8192/cameras/camera1.jpg}{\insrsid150409
then these fields will be camserver.home.net, 8192 and /cameras/camera1.jopg respectively. Leave the port at 80 if there is no special port required. If you require auth
entication to access your camera then add this onto the host name in the form <username>:<password>@<hostname>.com.
Specify the amount of colours in the captured image. Unlike with local cameras changing this has no controlling effect on the remote camera itself so ensure that your camera is actually capturing to this palette beforehand.
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 Capture Width/Height}{\insrsid150409 \endash As per local devices.
This relates to the timestamp that is applied to each frame. It is a \lquote s}{\insrsid7282709 trftime}{\insrsid150409 \rquote style string. It is actually passed through }{\insrsid7282709 strftime}{\insrsid150409
and then through printf to add the monitor name so a format of '%%s - %y/%m/%d %H:%M:%S' (note the double % at the beginning) would be recommended though you can modify it if necessary. If you don\rquote
t want a timestamp or have a camera that puts one on itself then leave this field blank.}{\insrsid7282709 If you add a second %%s placeholder in the string this will be filled by any of the \lquote show text\rquote detailed in the zmtriggers.pl section.
The X and Y values determine where to put the timestamp. A value of 0 for the X value will put it on the left side of the image and a Y value of 0 will place it at the top of the image. To place the timestamp at the bot
tom of the image use a value eight less than the image height.
This option determines how many frames are held in the ring buffer at any one time. The ring buffer is the storage space where the last \lquote n\rquote images are kept, re
ady to be resurrected on an alarm or just kept waiting to be analysed. It can be any value you like with a couple of provisos, (see next options). However it is stored in shared memory and making it too large especially for large images with a high colour
depth can use a lot of memory. A value of no more than }{\insrsid16398105 50 }{\insrsid150409
is usually ok. If you find that your system will not let you use the value you want it is probably because your system has an arbitrary limit on the size of shared memory that may be used even thou
gh you may have plenty of free memory available. This limit is usually fairly easy to change, see the Troubleshooting section for details.
This specifies how many frames the analysis daemon should process but not examine when it starts. Th
is allows it to generate an accurate reference image from a series of images before looking too carefully for any changes. I use a value of 25 here, too high and it will take a long time to start, too low and you will get false alarms when the analysis da
These options determine how many frames from before and after an event should be preserved with it. This allows you to view what happened immediately prior and subsequent to the event. A value of 10 for both of
these will get you started but if you get a lot of short events and would prefer them to run together to form fewer longer ones then increase the Post Event buffer size. The pre-event buffer is a true buffer and should not really exceed half the ring buff
r size. However the post-event buffer is just a count that is applied to captured frames and so can be managed more flexibly. You should also bear in mind the frame rate of the camera when choosing these values. For instance a network camera capturing at
1
FPS will give you 10 seconds before and after each event if you chose 10 here. This may well be too much and pad out events more than necessary. However a fast video card may capture at 25FPS and you will want to ensure that this setting enables you to vi
This option allows you to specify how many consecutive alarm frames must occur before an alarm event is generated. The usual, and default, value is 1 which implies that any alarm frame will
cause or participate in an event. You can enter any value up to 16 here to eliminate bogus events caused perhaps by screen flickers or other transients. Values over 3 or 4 are unlikely to be useful however. Please note that }{\insrsid342179
if you have statistics recording enabled then currently statistics are not recorded for the first \lquote Alarm Frame Count\rquote
-1 frames of an event. So if you set this value to 5 then the first 4 frames will be missing statistics whereas the more usual value of 1 will ensure that all alarm frames have statistics recorded.}{\insrsid4538194
\rquote , however you are free to rename them individually as you wish. This option lets you modify the event prefix, the \lquote Event-\lquote part, to be a value of your choice
so that events are named differently as they are generated. This allows you to name events according to which monitor generated them.
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 Maximum FPS}{\insrsid150409 \endash On some occasions you may have one or more cameras capable of high capture rates but find that you general
ly do not require this performance at all times and would prefer to lighten the load on your server. This option permits you to limit the maximum capture rate to a specified value. This may allow you to have more cameras supported on your system by reduci
n
g the CPU load or to allocate video bandwidth unevenly between cameras sharing the same video device. This value is only a rough guide and the lower the value you set the less close the actual FPS may approach it especially on shared devices where it can
be difficult to synchronise two or more different capture rates precisely. There is a global configuration option that allows you to turn this limiting off in the event of an alarm.
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 FPS Report Interval}{\insrsid150409 }{\b\insrsid10880688 \endash }{\insrsid150409 How often the current performance in terms of Frames
Per Second is output to the system log. Not used in any functional way so set it to maybe 1000 for now. If you watch /var/log/messages (normally) you will see this value being emitted at the frequency you specify both for video capture and processing.
Each analysed image in ZoneMinder is a composite of previous images and is formed by applying the current image as a certain percentage of the previous reference image. Thus, if we entered the value of 10 here, each image\rquote s part in
the reference image will diminish by a factor of 0.9 each time round. So a typical reference image will be 10% the previous image, 9% the one before that and then 8.1%, 7.2%, 6.5% and so on of the rest of the way. An image will effectively vanish around 2
5
images later than when it was added. This blend value is what is specified here and if higher will make slower progressing events less detectable as the reference image would change more quickly. Similarly events will be deemed to be over much sooner as
t
he reference image adapts to the new images more quickly. In signal processing terms the higher this value the steeper the event attack and decay of the signal. It depends on your particular requirements what the appropriate value would be for you but sta
rt with 10 here and adjust it (usually down) later if necessary.
\par }\pard\plain \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0\pararsid14317457 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\b\insrsid14317457 Note: This tab and its options will only appear if you have }{
\b\insrsid10880688 selected the ZM_OPT_CONTROL option}{\b\insrsid14317457 }{\b\insrsid10880688 to indicated }{\b\insrsid14317457 that your system contains cameras which are able to be}{\b\insrsid10880688 controlled via }{\b\insrsid14317457
Pan/Tilt/Zoom or other mechanisms.}{\b\insrsid10880688 See the Camera Control section elsewhere in this document for further details on camera control protocols and methods.}{\b\insrsid14317457
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0\pararsid14317457 {\b\insrsid10880688 Controllable \endash }{\insrsid1386006 C}{\insrsid10880688 heck this box to indicate your camera can be controlled.
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0\pararsid14317457 {\b\insrsid10880688 Control Type \endash }{\insrsid10880688 Select the con
trol type that is appropriate for your camera. ZoneMinder ships with a small number of predefined control protocols which will works with some cameras without modification but which may have to amended to function with others, Choose the edit link to crea
te new control types or to edit the existing ones.}{\insrsid14317457
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0\pararsid1386006 {\b\insrsid1386006 Control Device \endash }{\insrsid1386006
This is the device that is used to control your camera. This will normally be a serial or similar port. If your camera is a network camera, you will generally not need to specify a control device.}{\insrsid1386006\charrsid1386006
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0\pararsid1386006 {\b\insrsid1386006 Control Address \endash }{\insrsid4074839 This }{\insrsid1386006
is the address of your camera. Some control protocols require that each camera is identified by a particular, usually numeric id. If your camera uses addressing then enter the id of your camera here. If your camera is a netwo
rk camera then you will usually need to enter the hostname or IP address of it here. This is ordinarily the same as that given for the camera itself.}{\insrsid1386006\charrsid1386006
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0\pararsid15402204 {\b\insrsid15402204 Auto Stop Timeout \endash }{\insrsid15402204 Some cameras only support a continuous mode of movement. For instance you tell the cam
era to pan right and then when it is aligned correctly you tell it to stop. In some cases it is difficult to time this precisely over a web interface so this option allows you to specify an automatic timeout where the command will be automatically stopped
.
So a value of 0.25 here can tell the script to stop moving a quarter of a second after starting. This allows a more precise method of fine control. If this value is left blank or at zero it will be ignored, if set then it will be used as the timeout howe
v
er it will only be applied for the lower 25% of possible speed ranges. In other words if your camera has a pan speed range of 1 to 100 then selecting to move at 26 or over will be assumed to imply that you want a larger movement that you can control yours
elf and no timeout will be applied. Selecting motion at lower speeds will be interpreted as requiring finer control and the automatic timeout will be invoked.
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0\pararsid1386006 {\b\insrsid1386006 Track Motion \endash }{\insrsid1386006 This and the following four options are used with the experimental motion function.
This will only work if your camera supports mapped movement modes where a point on an image can be mapped to a control command. This is generally most common on network cameras but can be }{\insrsid4074839
replicated to some degree on other cameras that support relative movement modes. See the Camera Control section for more details. Check this box to enable motion tracking.}{\insrsid1386006
\par }{\b\insrsid1386006 Return Location \endash }{\insrsid4074839 If you camera supports a \lquote home\rquote position or presets you can choose which preset the camera should return to after tracking motion.}{\insrsid1386006
\par }{\b\insrsid1386006 Return Delay \endash }{\insrsid4074839 This is the delay, in seconds, once motion has stopped being detected, before the camera returns to any defined return location.}{\insrsid1386006
Note: This tab and its options will only appear if you have indicated that your system supports the X10 home automation protocol during initial system configuration.
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 X10 Activation String}{\insrsid150409 - The contents of this field determine when a monitor starts and/or stops being active when running in \lquote
Triggered; mode and with X10 triggers. The format of this string is as follows,
: If you simply enter a number then the monitor will be activated when an X10 ON signal for that unit code is detected and will be deactivated when an OFF signal is detected.
\par }{\ul\insrsid150409 !n}{\insrsid150409 : This inverts the previous mode, e.g. !5 means that the monitor is activated when an OFF signal for unit code 5 is detected and deactivated by an ON.
\par }\pard \s15\qj \li720\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin720\itap0 {\ul\insrsid150409 n+}{\insrsid150409 : Entering a unit code
followed by + means that the monitor is activated on receipt of a ON signal for that unit code but will ignore the OFF signal and as such will not be deactivated by this instruction. If you prepend a '!' as per the previous definition it similarly inverts
the mode, i.e. the ON signal deactivates the monitor.
\par }\pard \s15\qj \li720\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin720\itap0 {\ul\insrsid150409 n+<seconds>}{\insrsid150409 : As per the previous mode except that the monitor will deactivate itself after the given number of seconds.
\par }\pard \s15\qj \li720\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin720\itap0 {\ul\insrsid150409 n-}{\insrsid150409 : Entering a unit code followed by - means that the monitor is deactivated on
receipt of a OFF signal for that unit code but will ignore the ON signal and as such will not be activated by this instruction. If you prepend a '!' as per the previous definition it similarly inverts the mode, i.e. the OFF signal activates the monitor.
\par }\pard \s15\qj \li720\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin720\itap0 {\ul\insrsid150409 n-<seconds>}{\insrsid150409 : As per the previous mode except that the monitor will activate itself after the given number of seconds.
You can also combine several of these expressions to by separating them with a comma to create multiple circumstances of activation. However for now leave this blank.
- This has the same format as the previous field but instead of activating the monitor with will cause a forced alarm to be generated and an event recorded if the monitor is Active. The same definition as
above applies except that for activated read alarmed and for deactivated read unalarmed(!). Again leave this blank for now.
\par }\pard \s30\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 X10 Output Alarm String}{\insrsid150409 - This X10 string also has the same format as the two above options. However it works in a slightly differen
t way. Instead of ZoneMinder reacting to X10 events this option controls how ZoneMinder emits X10 signals when the current monitor goes into or comes out of the alarm state. Thus just entering a number will cause the ON signal for that unit code to be sen
when going into alarm state and the OFF signal when coming out of alarm state. Similarly 7+30 will send the unit code 7 ON signal when going into alarm state and the OFF signal 30 seconds later regardless of state. The combination of the X10 instruction
llows ZoneMinder to react intelligently to, and also assume control of, other devices when necessary. However the indiscriminate use of the Input Alarm and Output Alarm signals can cause some horrendous race conditions such as a light going on in response
to an alarm which then causes an alarm itself and so on. Thus some circumspection is required here. Leave this blank for now anyway.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid150409 Finally, click 'Save' to add your monitor.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 On the main console listing you will now see your monitor and some of its vital
statistics. Most columns are also links and you get to other functions of ZoneMinder by choosing the appropriate one. Describing them left to right, they are as follows.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 The first column is the Id, clicking on this gives you the opportunity to edit any of the settings you have just defined your monitor to have.
\par The next column is the Name column, clicking on this will give you the watch window where you can view a live feed from your camera along with recent events. This is described more fully below.
wing that are the Function and Source columns, which may be represented in various colours. Initially both will be showing red. This means that that monitor is not configured for any function and as a consequence has no zmc (capture) daemon running on it.
If it were orange it would mean that a zmc daemon was running but no zma (analysis) daemon and green means both are running. In our case it is red because we defined the Monitor to have a Function of None so no daemons are required. To get the daemons up
and running you can either click on the source listed in the Source column and edit the monitor properties or click on the Function listed and change it to \rquote Monitor\rquote
, which will ensure that one or more appropriate daemons are started automatically.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 Having a device status of red or orange does not necessarily constitute an error if you have deliberately disabled a monitor or have just put it into Passive mode.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 If you have several cameras (and thus monitors) on a device the device status colour reflects all of
them for the capture daemon. So if just one monitor is active then the daemon is active for both even if all the other monitors are switched off.
\par Once you have changed the function of your monitor, the main console window will be updated to reflect this change. If your device status does not go green then check your system and web server logs to see if it's something obvious.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 You can now add further monitors if you have cameras set up to support them. Once you have one or more monitors you may notice the '
<n> Monitors' title becomes a link}{\insrsid10878991
. Clicking on this link will open up a window which allows you to assign your monitors to groups. These let you select certain monitors to view. For instance you may only wish to view outdoor monitors while indoors. You ca
n also choose to view all of them. If you choose a group then your selection will be remembered via a cookie and will be used until you change it. You can call your groups anything you like, though \lquote Mobile\rquote
has a special meaning (see Mobile Devices below). There may also be a \lquote Cycle\rquote link}{\insrsid150409 which allows you to cycle through a shot from each of your monitors (}{\insrsid10878991 in the selected group }{\insrsid150409
unless they are switched off) and get a streamed or still image from each in turn. }{\insrsid10878991 Similarly if you see a link titled}{\insrsid150409 \lquote Montage\rquote }{\insrsid10878991 it will }{\insrsid150409 allow you view all your }{
\insrsid16266742 active }{\insrsid150409 enabled cameras }{\insrsid10878991 (in the selected group) }{\insrsid150409
simultaneously. Be aware however that this can consume large amounts of bandwidth and CPU so should not be used continuously unless you have resource to burn.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid150409 The n
ext important thing to do with a new monitor is set up Zones for it to use. By default you'll already have one }{\insrsid15402204 generated}{\insrsid150409
for you when you created your monitor but you might want to modify it or add others. Click on the Zones column for your monitor and you
should see a small popup window appear which contains an image from your camera overlain with a stippled pattern representing your zone. In the default case this will cover the whole image and will be red. Beneath that will be a table containing a listin
g
of your zones. Clicking on either the relevant bit of the image or on the Id or Name in the table will bring up another window where you can edit the particulars for your Zones. As you can see there are quite a few, so now is a good time to go through th
This is just a label to identify the zone by. You can change this to be more representative if you like, though it isn't used much except for logging and debugging.
: This is the zone type you'll use most often, and which will be set for your default zone. This means that this zone will trigger an alarm on any events that occur within it that meet the selection criteria.
: This zone type can be used for any zones that you want to trigger an alarm only if at least one other Active zone has already triggered one. This might be for example to cover an area of the image like a plant or tree which moves a lot a
nd which would trigger lots of alarms. Perhaps this is behind an area you'd like to monitor though, in this case you'd create an active zone covering the non-moving parts and an inclusive zone covering the tree perhaps with less sensitive detection settin
gs also. If something triggered an alarm in the Active zone and also in the Inclusive zone they would both be registered and the resulting alarm would be that much bigger than if you had blanked it out altogether.
\par }\pard \s15\qj \li720\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin720\itap0 {\ul\insrsid150409 Exclusive}{\insrsid150409 : The next zone Type is Exclusive
. This means that alarms will only be triggered in this zone if no alarms have already been triggered in Active zones. This is the most specialised of the zone types and you may never use it but in its place it is very useful. For instance in the camera c
vering my garden I keep watch for a hedgehog that visits most nights and scoffs the food out of my cats bowls. By creating a sensitive Exclusive zone in that area I can ensure that a hedgehog alarm will only trigger if there is activity in that small area
. If something much bigger occurs, like someone walking by it will trigger a regular alarm and not one from the Exclusive zone. Thus I can ensure I get alarms for big events and also special small events but not the noise in between.
\par }\pard \s15\qj \li720\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin720\itap0 {\ul\insrsid150409 Preclusive}{\insrsid150409 : This zone
type is relatively recent. It is called a Preclusive zone because if it is triggered it actually precludes an alarm being generated for that image frame. So motion or other changes that occur in a Preclusive zone will have the effect of ensuring that no a
l
arm occurs at all. The application for this zone type is primarily as a shortcut for detecting general large-scale lighting or other changes. Generally this may be achieved by limiting the maximum number of alarm pixels or other measure in an Active zone.
However in some cases that zone may cover an area where the area of variable illumination occurs in different places as the sun and/or shadows move and it thus may be difficult to come up with general values. Additionally, if the sun comes out rapidly the
although the initial change may be ignored in this way as the reference image catches up an alarm may ultimately be triggered as the image becomes less different. Using one or more Preclusive zones offers a different approach. Preclusive zones are design
d to be fairly small, even just a few pixels across, with quite low alarm thresholds. They should be situated in areas of the image that are less likely to have motion occur such as high on a wall or in a corner. Should a general illumination change occur
they would be triggered at least as early as any Active zones and prevent any other zones from generating an alarm. Obviously careful placement is required to ensure that they do not cancel any genuine alarms or that they are not so close together that an
y motion just hops from one Preclusive zone to another. As always, the best way is to experiment a little and see what works for you.
\par }\pard \s15\qj \li720\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin720\itap0 {\ul\insrsid150409 Inactive }{\insrsid150409 : This final zone type is the opposite of Active. In this zone type no alarms will ever be reported. You can creat
e an Inactive zone to cover any areas in which nothing notable will ever happen or where you get constant false alarms that don't relate to what you are trying to monitor. An Inactive zone can overlay other zone types and will be processed first.
\par }\pard \s15\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\insrsid150409 I mention
ed above that Inactive zones may be overlaid on other zones to blank out areas however as a general principle you should try and make zones abut each other as much as possible and do not overlap. This helps avoid repeated duplicate processing of the same
a
rea. For instance an Inclusive zone overlaying an Active zone when all other settings are the same will always trigger when the Active zone does which somewhat defeats the object of the exercise. One exception to this is Preclusive zones. These may be sit
uated within Active areas are they are processed first and if small may actually save processing time by preventing full analysis of the image.
\par }\pard \s15\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 Units}{\insrsid150409 - This setting which details whether certain of the following settings are in Pixels or Percent}{\insrsid1314985 , where \lquote Per
cent\rquote refers to a percentage area of the zone itself}{\insrsid150409 . In general \lquote Pixels\rquote
is more precise whereas percentages are easier to use to start with or if you change image sizes frequently. If you change this setting all appropriate values below are redisplayed i
n the correct context. A good tip would be to initially enter the settings in Percent and then change to Pixels and refine any gaps. Repeated flipping between the settings will cause rounding errors, as ZoneMinder in general is not at home to Mr Floating
P
oint for reasons of performance. Note, the sense of the percentage values changed in version 1.19.0. Prior to that percentages referred to the area of the image as a whole, whereas it now only refers to the area of the zone. This makes trying to work out
- Following the units the next four settings define the bounds of the Zone in the monitor frame and are self-explanatory with the exception of the fact that the minima are at the top left of the frame and the m
axima are at the bottom right rather than in a Cartesian style.
- The option after that allows you to specify what colour you'd like any alarms this zone generates to be highlighted on images, pick anything you like that will show up against y
our normal image background. This option is irrelevant for Preclusive and Inactive zones and will be disabled For Inactive zones all subsequent options are likewise disabled.
\par }\pard \s15\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 Alarm Check Method }{\insrsid150409 \endash This is a new addition to Zone definitions. It allows you to
specify the nature of the alarm checking that will take place, and more specifically what tests are applied to determine whether a frame represents an alarm or not. The three options are \lquote AlarmPixels\rquote , \lquote FilteredPixels\rquote and
\lquote Blobs\rquote and depending on which op
tion is chosen some of the following other settings may become unavailable. The first of these indicates that only a count of individual alarmed pixels should be used to determine the state of a image, the second indicate that the pixels should be filtere
d to remove isolated pixels (see below) before being counted, and the third uses a more sophisticated analysis which is designed to aggregate alarmed pixels into continuous groups, or \lquote blobs\rquote
. Blob analysis is the method ZoneMinder has always used previousl
y (before it became optional) and so this is the default. However this method takes slightly longer and so if you find that one of the other methods works just as well for you and you wish to maximise performance you can opt for that instead. Some of the
more useful alarm related features such as highlighted analysis images are only available with the \lquote Blob\rquote setting.
These setting are used to define limits for the difference in value between a pixel and its predecessor in the r
eference image. For greyscale images this is simple but for colour images the colours are averaged first, originally this used an RMS (root mean squared) algorithm but calculating square roots mugs performance and does not seem to improve detection. Using
an average does means that subtle colour changes without any brightness change may go undetected but this is not the normal circumstance. There is also the option to use a more sophisticated integer algorithm to calculate a Y (or brightness) value from th
- The following two settings define the minimum and maximum number of pixels that exceed this threshold that would cause an alarm. If the units are Percent this (and following options) refers to the percentage
of the frame and not the zone, this is so these values can be related between zones. The minimum value must be matched or exceeded for an alarm to be generated whereas the maximum must not be exceeded or the alarm will be cancelled. This is to allow for s
u
dden changes such as lights coming on etc, which you may wish to disregard. In general a value of zero for any of these settings causes that value to be ignored, so you can safely set a maximum to zero and it will not be used. The use of just a number of
pixels is however a very brute force method of detection as many small events dispersed widely are not distinguished from a compact one.
\par }\pard \s15\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 Filter Width/Height}{\insrsid150409 \endash To improve detection of valid event ZoneMinder applies several other functions to the data to impr
ove its ability to distinguish interesting signals from uninteresting noise. The first of these is a filter that removes any pixels that do not participate in a contiguous block of pixels above a certain size. These options are always expressed in pixels
and should be fairly small, and an odd number, three or five is a good value to choose initially. Application of this filter removes any tiny or discontinuous pixels that don't form part of a discrete block.
\par }\pard \s15\qj \li540\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin540\itap0 {\b\insrsid150409 Min/Maximum Filtered Area}{\insrsid150409 \endash These are two additi
onal bounds that specify the limits of pixels that would cause an alarm after this filtering process. As the filtering process can only remove alarmed pixels it makes no sense for the Minimum and Maximum Filtered Area to be larger than the equivalent Alar
med Area and in general they should be smaller or the same.
- The next step in the analysis phase is the collation of any remaining alarmed areas into contiguous blobs. This process parses the image and forms any pixels that adjoin oth
er alarmed pixels into one or more larger blobs. These blobs may be any shape and can be as large as the zone itself or as small as the filtered size. The Minimum and Maximum Blob Size settings allow you to define limits within which an alarm will be gene
rated. Of these only the Minimum is likely to be very useful.
- Finally the Minimum and Maximum Blobs settings specify the limits of the actual number of blobs detected. If an image change satisfies all these requirements it starts or continues an alarm event.
As this point you should have one or more Monitors running with one or more Zones each. Returning to the main Console window you will see your monitors listed once more. The columns not explored so far are the Monitor
name, and various event totals for certain periods of time. Clicking on any of the event totals will bring up a variation on the same window but click on the Monitor name for now. On doing so up will pop another window which should be scaled to contain a
heading, an image from your monitor, a status and a list of recent events if any have been generated. Depending on whether you are able to view a streamed image or not the image frame will either be this stream or a series of stills. You have the option t
o change from one to the other (if available) at the centre of the top heading. Also along the top are a handful of other links. These let you change the scale of the image stream, modify image settings (for local devices) or close the window.}{
\insrsid11954036 If you have cameras that can be controlled, a \lquote Control\rquote link should also be preset which is described below.}{\insrsid150409
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 The image should be self-explanatory but if it looks like garbage it is possible that the video configuration is wrong so look in your system error log and chec
k for or report anything unusual. The centre of the window will have a tiny frame that just contains a status; this will be 'Idle', 'Alarm' or 'Alert' depending on the function of the Monitor and what's going on in the field of view. Idle means nothing is
happening, Alarm means there is an alarm in progress and Alert means that an alarm has happened and the monitor is \lquote cooling down\rquote
, if another alarm is generated in this time it will just become part of the same event. These indicators are colour coded in green, red and amber.
By default if you have minimised this window or opened other windows in front it will pop up to the front if it goes to Alarm state. This behaviour can be turned off in \lquote options\rquote if required. You can also specify a sound file in the co
nfiguration, which will be played when an alarm occurs to alert you to the fact if you are not in front of your computer. This should be a short sound of only a couple of seconds ideally. Note that as the status is refreshed every few seconds it is possib
l
e for this not to alert you to every event that takes place, so you shouldn't rely on it for this purpose if you expect very brief events. Alternatively you can decrease the refresh interval for this window in the configuration though having too frequent
Below the status is a list of recent events that have occurred, by default this is a listing of just the last 10 but clicking on 'All' will give you a full list and 'Archive' will take you to the event archive for thi
s monitor, more on this later. Clicking on any of the column headings will sort the events appropriately.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 From here you can also delete events if you wish. The events themselves are listed with the event id, and event name (which you can change), the time
that the event occurred, the length of the event including any preamble and postamble frames, the number of frames comprising the event with the number that actually contain an alarm in brackets and finally a score. This column lists the average score pe
r alarm frame as well as the maximum score that any alarm frame had.
The score is an arbitrary value that essentially represents the percentage of pixels in the zone that are in blobs divided by the square root of the number of blobs and then divided by the
size of the zone. This gives a nominal maximum of 100 for a zone and the totals for each zone are added together, Active zones scores are added unchanged, Inclusive zones are halved first and Exclusive zones are doubled. In reality values are likely to b
e much less than 100 but it does give a simple indication of how major the event was.
If you have defined your system as having controllable monitors and you are looking at a monitor that is configured for control, then clicking on the \lquote Control\rquote
link along the top of the window will change the short event listing area to a control area. The capabilities you have defined earlier determine exactly what is displayed in this window. Generally you will have a Pan/Tilt control area along with one or }
{\insrsid2915664 subsidiary areas such as zoom or focus control to the }{\insrsid13441986 s}{\insrsid2915664
ide. If you have preset support then these will be near the bottom of the window. The normal method of controlling the monitor is by clicking on the appropriate graphics which then send a comman
d via the control script to the camera itself. This may sometimes take a noticeable delay before the camera responds.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid11954036 {\insrsid2915664 It is usually the case that the control arrows are sensitive to where you click on them. If you have a camera that allows different speeds
to be used for panning or zooming etc then clicking near the point of the arrow will invoke the faster speed whilst clicking near the base of the arrow will be slower. If you have defined continuous motion then ongoing activities can be stopped by clicki
n
g on the area between the arrows, which will either be a graphic in the case of pan/tilt controls or a word in the case of zoom and focus controls etc. Certain control capabilities such as mapped motion allow direct control by clicking on the image itself
when used in browsers which support streamed images directly. Used in this way you can just click on the area of the image that interests you and the camera will centre on that spot. You can also use direct image control for relative motion when the area
of the }{\insrsid6052569 image}{\insrsid2915664 you click on }{\insrsid6052569
defines the direction and the distance away from the centre of the image determines the speed. As it is not always very easy to estimate direction near the centre of the image, the active area does not start until a short distance
away from the centre, resulting in a \lquote dead\rquote zone in the middle of the image.}{\insrsid11954036
The other columns on the main console window contain various event totals for your monitors over the last hour, day, week and month as well as a grand total and a
total for events that you may have archived for safekeeping. Clicking on one of these totals or on the 'All' or 'Archive' links from the monitor window described above will present you with a new display. This is the full event window and contains a list
of events selected according to a filter which will also pop up in its own window. Thus if you clicked on a 'day' total the filter will indicate that this is the period for which events are being filtered. The event listing window contains a similar listi
n
g to the recent events in the monitor window. The primary differences are that the frames and alarm frames and the score and maximum score are now broken out into their own columns, all of which can be sorted by clicking on the heading. Also this window w
ill not refresh automatically, rather only on request. Other than that, you can choose to view events here or delete them as before.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 The other window that appeared is a filter window. You can use this window to create your own filters or to modify existing
ones. You can even save your favourite filters to re-use at a future date. Filtering itself is fairly simple; you first choose how many expressions you'd like your filter to contain. Changing this value will cause the window to redraw with a corresponding
row for each expression. You then select what you want to filter on and how the expressions relate by choosing whether they are 'and' or 'or' relationships. For filters comprised of many expressions you will also get the option to bracket parts of the fil
ter to ensure you can express it as desired.}{\insrsid11877453 Then if you like choose how you want your results sorted and whether you want to limit the amount of events displayed.}{\insrsid150409
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 There are several different elements to an event that you can filter on, some of which requir
e further explanation. These are as follows, 'Date/Time' which must evaluate to a date and a time together, 'Date' and 'Time' which are variants which may only contain the relevant subsets of this, 'Weekday' which as expected is a day of the week. All of
t
he preceding elements take a very flexible free format of dates and time based on the PHP strtotime function (http://www.zend.com/manual/function.strtotime.php). This allows values such as 'last Wednesday' etc to be entered. I recommend acquainting yourse
l
f with this function to see what the allowed formats are. However automated filters are run in perl and so are parsed by the Date::Manip package. Not all date formats are available in both so if you are saved your filter to do automatic deletions or other
tasks you should make sure that the date and time format you use is compatible with both methods. The safest type of format to use is \lquote -3 day\rquote or similar with easily parseable numbers and units are in Engl}{\insrsid11877453 ish.}{
\par The other elements you can filter on are all fairly self explanatory except perhaps for 'Archived' which you can use to include or exclude Archived events. In general you'll probably do most filtering on un-archived events. }{\insrsid11877453
There are also two elements, Disk Blocks and Disk Percent which don\rquote t directly
relate to the events themselves but to the disk partition on which the events are stored. These allow you to specify an amount of disk usage either in blocks or in percentage as returned by the \lquote df\rquote
command. They relate to the amount of disk space used and not the amount left free. }{\insrsid150409 Once your filter is specified, clicking 'submit' will filter the events according to your specification. }{\insrsid11877453
As the disk based elements are not event related directly if you create a filter and include the term \lquote DiskPercent > 95\rquote th
en if your current disk usage is over that amount when you submit the filter then all events will be listed whereas if it is less then none at all will. As such the disk related terms will tend to be used mostly for automatic filters (see below). }{
If you do this then the subsequent dialog will also allow you specify whether you want this filter automatically applied in order to delete events or upload events via ft
p to another server and mail notifications of events to one or more email accounts. In most cases you can specify your preferences for upload formats and email content during configuration time (make sure you type '?' to get help on options). Emails and m
e
ssages (essentially small emails intended for mobile phones or pagers) have a variety of tokens that can be substituted for various details of the event that caused them. This includes links to the event view or the filter as well as the option of attachi
ng images or videos to the email itself. See the included templates zmconfig_eml.txt and zmconfig_msg.txt for a fuller explanation of the availability and meaning of these tokens.}{\insrsid11877453
Finally you can also specify a script which is run on each matched event. Thi
s script should be readable and executable by your web server user. It will get run once per event and the relative path to the directory containing the event in question. Normally this will be of the form <MonitorName>/<EventId> so from this path you can
derive both the monitor name and event id and perform any action you wish. }{\insrsid1666119 Note that arbitrary commands are not allowed to be specified in the filter, for }{\insrsid2967940 security}{\insrsid1666119
Filtering is a powerful mechanism you can use to eliminate events that fit a certain pattern however in many cases modifying the zone settings will better address this. Where it really comes into its own is generally in applying time
filters, so for instance events that happen during weekdays or at certain times of the day are highlighted, uploaded or deleted.}{\insrsid11877453
Additionally using disk related terms in your filters means you can automatically create filters that delete the oldest events
when your disk gets full. Be warned however that if you use this strategy then you should limit the returned results to the amount of events you want deleted in each pass until the disk usage is at an acceptable level. If you do not do this then the firs
t pass when the disk usage is high will match, and then delete, all events unless you have used other criteria inside of limits.}{\insrsid13707462
ZoneMinder ships with a sample filter already installed, though disabled. The PurgeWhenFull filter can be used to delete the old
est events when your disk starts filling up. To use it you should select and load it in the filter interface, modify it to your requirements, and then save it making you sure you check the \lquote Delete Matching Events\rquote
option. This will then run in the background and ensure that your disk does not fill up with events.}{\insrsid150409
From the monitor or filtered events listing you can now click on an event to view it in more detail. If you have streaming capability you will see a series of images that make up the
event. You will also see a link to allow you to view the still images themselves. If you don't have streaming then you will be taken directly to this page. The images themselves are thumbnail size and depending on the configuration and bandwidth you have
chosen will either be the full images scaled in your browser of actual scaled images. If it is the latter, if you have low bandwidth for example, it may take a few seconds to generate the images. If thumbnail images are required to be generated, they will
be kept and not re-generated in future. Once the images appear you can mouse over them to get the image sequence number and the image score.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 You will notice for the first time that alarm images now contain an overlay outlining the blobs that represent the
alarmed area. This outline is in the colour defined for that zone and lets you see what it was that caused the alarm. Clicking on one of the thumbnails will take you to a full size window where you can see the image in all its detail and scroll through th
e
various images that make up the event. If you have the ZM_RECORD_EVENT_STATS option on, you will be able to click the 'Stats' link here and get some analysis of the cause of the event. Should you determine that you don't wish to keep the event, clicking
o
n Delete will erase it from the database and file system. Returning to the event window, other options here are renaming the event to something more meaningful, refreshing the window to replay the event stream, deleting the event, switching between stream
ed and still versions of the event (if supported) and generating an MPEG video of the event (if supported).
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 These last two options require further explanation. Archiving an event means that it is kept to one side and not displayed in the normal event listin
gs unless you specifically ask to view the archived events. This is useful for keeping events that you think may be important or just wish to protect. Once an event is archived it can be deleted or unarchived but you cannot accidentally delete it when vie
The final option of generating an MPEG video is still somewhat experimental and its usefulness may vary. It can use either the Berkeley MPEG encoder or the faster and new ffmpeg encoder. Either of these will generate a short v
ideo, which will be downloaded to your browsing machine to view. Due to the relatively slow frame rate that ZoneMinder will capture at and the high minimum frame rate that the Berkeley encoder uses videos created by this method will be very quick. However
when using the ffmpeg encoder, ZoneMinder will attempt to match the duration of the video with the duration of the event. This has the useful effect of making the video watchable and not too quick while having the unfortunate side effect of increasing fil
e size and generation time. Ffmpeg in particular has a particularly rich set of options and you can specify during configuration which additional options you may wish to include to suit your preferences.}{\insrsid7110331
In particular you may need to specify additional, or different, options }{\insrsid6096418
if you are creating videos of events with particularly slow frame rates as some codecs only support certain ranges of frame rates. Details of these options can be found in the documentation for the encoders and is outside the scope of this document.}{
Building an MPEG video, especially for a large event, can take some time and should not be undertaken lightly as the effect on your host box of many CPU intensive encoders will not be good. However once a video has been created for an event it
will be kept so subsequent viewing will not incur the generation overhead. Videos can also be included in notification emails}{\insrsid6096418 ,}{\insrsid150409
however care should be taken when using this option as for many frequent events the penalty in CPU and disk space can quickly mount up.
The final area covered by the tutorial is the options and user section. If you are running in authenticated mode and don\rquote t have system privileges then you will not see this section at all and if you are running in un-authenticated
The various options you can specify are displayed in a tabbed dialog with each group of options displayed under a different heading. Each option is displayed with its name, a short description and the current value. You can also click on the \lquote ?
\rquote link following each description to get a fuller explanation about each option. This is the same as you would get from zmconfig.pl. A number of option groups have a master option near the top which enables or disables the
whole group so you should be aware of the state of this before modifying options and expecting them to make any difference.
\par If you have changed the value of an option you should then \lquote save\rquote it. A number of the option groups will then prompt you to let you
know that the option(s) you have changed will require a system restart. This is not done automatically in case you will be changing many values in the same session, however once you have made all of your changes you should restart ZoneMinder as soon as p
ossible. The reason for this is that web and some scripts will pick up the new changes immediately but some of the daemons will still be using the old values and this can lead to data inconsistency or loss.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 One of the options you may notice in the \lquote System\rquote
tab allows you to specify the default language for your installation of ZoneMinder. Versions 1.17.0 and later support multiple languages but rely on users to assist in creating language files for specific languages. To specify a language you will have to
g
ive the applicable code, thus for UK English this is en_gb, and for US English it would be en_us, if no language is given then UK English is assumed. Most languages will be specified in this nn_mm format and to check which languages are available look for
files named zm_lang_*.php in the ZoneMinder build directory where the parts represented by the \lquote *\rquote
would be what you would enter as a language. This is slightly unwieldy and will probably be improved in future to make it easier to determine language availa
bility. On checking which languages are available it may be that your preferred language is not currently included and if this is the case please consider doing a translation and sending it back to it may be included in future releases. All the language e
lements are given in the zm_lang_en_gb.php file along with a few notes to help you understand the format.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 As mentioned above, you may also see a \lquote users\rquote
tab in the Options area. In this section you will see a list of the current users defined on the system.
You can also add or delete users from here. It is recommended you do not delete the admin user unless you have created another fully privileged user to take over the same role. Each user is defined with a name and password (which is hidden) as well as an
enabled setting which you can use to temporarily enable or disable users, for example a guest user for limited time access. As well as that there is a language setting that allows you to define user specific languages. Setting a language here that is diff
e
rent than the system language will mean that when that user logs in they will have the web interface presented in their own language rather than the system default, if it is available. Specifying a language here is done in the same way as for the system d
efault language described above.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 There are also four values that define the user permissions, these are \lquote stream\rquote , \lquote events\rquote , \lquote monitors\rquote and \lquote system
\rquote Each can have values of \lquote none\rquote , \lquote view\rquote or \lquote edit\rquote apart from \lquote stream\rquote which has no \lquote edit\rquote setting. These values cover access to the following areas; \lquote stream\rquote
defines whether a user is allowed to view the \lquote live\rquote video feeds coming from the cameras. You may wish to allow a user to view historical events only in which case this setting should be \lquote none\rquote . The \lquote events\rquote
setting determines whether a user can view and modify or delete any retained historical events. The \lquote monitors\rquote setting specifies whether a user can see the current monitor settings and change them. Finally the \lquote system\rquote
setting determines whether a user can view or modify the system settings as a whole, such as options and users or controlling the running of the system as a whole. As well as these settings there is also a monitor ids setting that can be used for non-
\rquote system\rquote users to restrict them to only being able to access streams, events or monitors for the given monitors ids as a comma separated list with no spaces. If a user with \lquote monitors\rquote
edit privileges is limited to specific monitors here they will not be able to add or delete monitors but only change the details of those they have access to. If a user has \lquote system\rquote privileges then the \lquote monitors ids\rquote
setting is ignored and has no effect.\rquote
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 That\rquote s pretty much is it for the tour}{\insrsid806011 , though there is a lot more to ZoneMinder as you will discover.}{\insrsid13707462 }{\insrsid150409
You should experiment with the various setting to get the results you think are right for your}{\insrsid9202225 }{\insrsid806011 requirements.}{\insrsid150409
\tx454\nooverflow\faroman\ls1\outlinelevel0\rin0\lin454\itap0\pararsid10423296 \b\f1\fs28\ulth\lang2057\langfe1033\kerning32\cgrid\langnp2057\langfenp1033 {\insrsid14175248 Camera Control{\*\bkmkend _Toc104622506}
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid4094536 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid4094536 Version 1.21.0 of ZoneMinder introduce}{\insrsid806011 d}{\insrsid4094536
a new feature, allowing you to control cameras from the web interface and to some extent automatically.
Pan/Tilt/Zoom (PTZ) cameras have a wide range of capabilities and use a large number of different protocols making any kind of generic control solution potentially very difficult. To address this ZoneMinder uses two key approaches to get around this probl
\cs35\cf1\insrsid4094536\charrsid4094536 For each camera model you use, an entry in the camera capabilit}{\cs35\cf1\insrsid4094536 ies table}{\cs35\cf1\insrsid4094536\charrsid4094536
must be created. These indicate what functions the camera supports and ensure that the interface presents only those capabilities that the camera su
pports. There are a very large number of capabilities that may be supported and it is very important that the entries in this table reflect the actual abilities of the camera.}{\cs35\cf1\insrsid4094536
A small number of example capabilities are included in ZoneMinder, these can be used \lquote as is\rquote or modified.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid4094536 {\cs35\b\cf1\insrsid4094536\charrsid806011 2) Control Scripts}{\insrsid4094536 \endash
ZoneMinder itself does not generally provide the ability to send commands to cameras or receive responses. What it does is }{\insrsid13007706 mediate motion requests from the web interface into a standard set of commands which a
re passed to a script defined in the control capability. Example scripts are provided in ZoneMinder which support a number of serial or network protocols but it is likely that for many cameras new scripts will have to be created. These can be modelled on
the example ones, or if control commands already exist from other applications, then the script can just act as a \lquote glue\rquote layer between ZoneMinder and those commands.}{\insrsid4094536
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid4094536 {\cf1\insrsid6423682 It should be emphasised that the control and capability elements of ZoneMinder are not inte
nded to be able to support every camera out of the box. Some degree of development is likely to be required for many cameras. This should often be a relatively straightforward task however if you have a camera that you want to be supported then please fee
l
free to get in touch and I should be able to provide an estimate for how much effort this is likely to be. It is also the case that I have only been able to access this limited number of cameras to test against; some other cameras may use different motio
n paradigms that don\rquote t fit into the control capability/script architecture }{\cf1\insrsid6690694 that}{\cf1\insrsid6423682
ZoneMinder uses. If you come across any cameras like this then please forward as much information to me as possible so that I may be able to extend the ZoneMinder model to encompass them.}{\insrsid6423682
If you have a camera that supports PTZ controls and wish to use it with ZoneMinder then the first thing you need to do is ensure that it has an accurate entry in the capabilities table. To do this you need to go to the Contr
ol tab of the Monitor configuration dialog and select \lquote Edit\rquote where it is listed by the Control Type selection box. This will bring up a new window which lists, with a brief summary, the existing capabilities. }{\cf1\insrsid5644657
To edit an existing capability to modify select
the Id or Name of the capability in question, or click on the Add button to add a new control capability. Either of these approaches will create a new window, in familiar style, with tabs along the top and forms fields below. In the case of the capabilit
ies table there are a large number of settings and tabs, the mean and use of these are briefly explained below.}{\cf1\insrsid11548070
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid5644657 Type}{\cf1\insrsid5644657 }{\insrsid5644657 \endash Whether the capability uses a local (usually serial) or network control protocol.
This is the full path to a script or application that will map the standard set of ZoneMinder control commands to equivalent control protocol command. This may be one of the shipped example zmcontrol-*.pl scripts or something else entirely.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid5644657 Can Wake}{\cf1\insrsid5644657 }{\insrsid5644657 \endash
This is the first of the actual capability definitions. Checking this box indicates that a protocol command exists to wake up the camera from a sleeping state.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid5644657 Can Sleep}{\cf1\insrsid5644657 }{\insrsid5644657 \endash The camera can be put to sleep.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid1861622 Can Move}{\cf1\insrsid1861622 }{\insrsid1861622 \endash The camera is able move, i.e. pan or tilt.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid1861622 Can Move Diagonally }{\insrsid1861622 \endash The camera can move diagonally. Some devices ca
\par }{\b\cf1\insrsid1861622 Can Move Mapped }{\insrsid1861622 \endash The camera is able internally map a point on an image to a precise degree of motion to centre that point in the image.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid1861622 Can Move Absolute }{\insrsid1861622 \endash The camera can move to an absolute location.
\par }{\b\cf1\insrsid1861622 Can Move Relative }{\insrsid1861622 \endash The camera can more to a relative location, e.g. 7 point left or up}{\insrsid11481483 .}{\insrsid1861622
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid10379841 Can Pan }{\insrsid10379841 \endash The camera can pan, or move horizontally.
\par }{\b\cf1\insrsid7304956 Min/Man Pan Step }{\insrsid7304956 \endash If the camera supports relative motion, this is the minimum and maximum amount of movement that can be specified.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid7304956 Has Pan Speed }{\insrsid7304956 \endash The camera supports specification of pan speeds.
\par }{\b\cf1\insrsid7304956 Min/Max Pan Speed }{\insrsid7304956 \endash The minimum and maximum pan speed supported.
\par }{\b\cf1\insrsid7304956 Has Turbo Pan}{\insrsid7304956 \endash The camera support}{\insrsid11481483 s an additional turbo pan speed.}{\insrsid7304956
\par }{\b\cf1\insrsid11481483 Turbo Pan Speed }{\insrsid11481483 \endash The actual turbo pan speed.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid11481483 Can Zoom }{\insrsid11481483 \endash The camera can zoom.
\par }{\b\cf1\insrsid11481483 Can Zoom Absolute }{\insrsid11481483 \endash The camera can zoom to an absolute position.
\par }{\b\cf1\insrsid11481483 Can Zoom Relative }{\insrsid11481483 \endash The camera can zoom to a relative position.
\par }{\b\cf1\insrsid11481483 Min/Max Zoom Range }{\insrsid11481483 \endash If the camera supports absolute zoom this is the minimum and maximum zoom amounts that may be specified.
\par }{\b\cf1\insrsid11481483 Min/Man Zoom Step }{\insrsid11481483 \endash If the camera supports relative zoom, this is the minimum and maximum amount of zoom change that can be specified.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid11481483 Has Zoom Speed }{\insrsid11481483 \endash The camera supports specification of zoom speed.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\insrsid16720206 Definition of Focus capabilities, fields as for \lquote Zoom\rquote tab}{\insrsid11481483 , but with the following additional capability.}{
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid11481483 Can Auto Focus }{\insrsid11481483 \endash The camera can focus automatically.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\insrsid16720206 Definition of White Balance capabilities, fields as for \lquote Focus\rquote tab.}{\insrsid16720206\charrsid11481483
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\insrsid16720206 Definition of Iris Control capabilities, fields as for \lquote Focus\rquote tab.}{\insrsid16720206\charrsid11481483
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid16720206 Has Presets }{\insrsid16720206 \endash The camera supports preset positions.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid16720206 Num Presets }{\insrsid16720206 \endash How many presets the camera supports. If the camera supports a huge nu
mber of presets then it makes sense to specify a more reasonable number here, 20 or less is recommended.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid16720206 Has Home Preset }{\insrsid16720206 \endash The camera has a defined \lquote home\rquote position, usually in the mid point of }{
\insrsid1322620 its}{\insrsid16720206 range.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\cf1\insrsid16720206 Can Set Presets }{\insrsid16720206 \endash The camera supports setting preset locations via }{\insrsid1322620 its}{\insrsid16720206
control protocol}{\insrsid1261536 .}{\insrsid16720206
second key element to controlling cameras with ZoneMinder is }{\cf1\insrsid1261536 ensuring that an appropriate control script or application is present. A small number of sample scripts are included with ZoneMinder and c
an be used directly or as the basis for development. Control scripts are run atomically, that is to say that one requested action from the web interface results in one execution of the script and no state information is maintained. If your protocol requir
es state information to be preserved then you should ensure that your scripts do this as ZoneMinder has no concept of the state of the camera in control terms.}{\cf1\insrsid9861573
\par }{\insrsid1261536 If you are writing a new control script then you need to ensure that it supports the parameters t
hat ZoneMinder will pass to it. If you already have scripts or applications that control your cameras, the ZoneMinder control script will just act as glue to convert the parameters passed into a form that your existing application understands.}{
\insrsid9861573 If you are w
riting a script to support a new protocol then you will need to convert the parameters passed into the script to equivalent protocol commands. If you have carefully defined your control capabilities above then you should only expect commands that correspo
nd to those capabilities.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid9861573 {\insrsid9861573 The standard set of parameters passed to control scripts is defined below,
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid9861573 {\b\cf1\insrsid8135487 --device=}{\b\cf1\insrsid9861573 <device> }{\insrsid9861573 \endash This is the control device from the monitor definition.}{
\insrsid10384767 Absent if no device is specified.}{\insrsid9861573
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid9861573 {\b\cf1\insrsid8135487 --address=}{\b\cf1\insrsid9861573 <address> }{\insrsid9861573 \endash This is the control addr
ess from the monitor definition. This will usually be a hostname or ip address for network cameras or a simple numeric camera id for other cameras.
\par }\pard \s15\qj \li567\ri0\sa60\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid806011 {\b\cf1\insrsid806011 --autostop=<timeout> }{\insrsid806011 \endash This indicates whether an automatic timeout should be applied to \lquote stop\rquote
the given command. It will only be included for \lquote continuous\rquote commands, as listed below, and will be a timeout in decimal seconds, probably fractional.
This specifies the command that the script should execute. Valid commands are given below.}{\insrsid8135487
\par }{\b\insrsid8135487 --xcoord=<x>, --ycoord=<y> \endash }{\insrsid8135487\charrsid8135487 This specifies }{\insrsid8135487 the x and/or y coordinates for commands which require them.}{\insrsid10384767 These will normally be absolute or mapped commands.}{
the width and height of the current image, for mapped motion commands where the coordinates values passed must have a context.}{\insrsid10384767\charrsid1115636
indicates the specific pan and tilt speeds for diagonal movements which may allow a different motion rate for horizontal and vertical components}{\insrsid10384767\charrsid8135487 .}{\insrsid10384767\charrsid1115636
\par }\pard \s15\qj \li567\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid10384767 {\b\insrsid10384767 --step=<step> \endash }{\insrsid10384767\charrsid8135487 This specifies the }{\insrsid10384767
amount of motion that the command should use, if appropriate}{\insrsid10384767\charrsid8135487 .}{\insrsid10384767 Normally used for relative commands only.}{\insrsid10384767\charrsid1115636
indicates the specific pan and tilt steps for diagonal movements which may allow a different amount of motion for horizontal and vertical components}{\insrsid10384767\charrsid8135487 .}{\insrsid10384767\charrsid1115636
\insrsid10384767\charrsid10384767 option listed above may take one of the following commands as a parameter}{\insrsid10384767 .}{\insrsid10384767\charrsid10384767
\par }\pard \s15\qj \li567\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid8135487 {\b\insrsid8135487 wake \endash }{\insrsid8135487\charrsid1115636 Wake the camera.
\par }\pard \s15\qj \li567\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid1322620 {\b\insrsid1115636 sleep \endash }{\insrsid1115636\charrsid1115636 Send the camera to sleep.}{\insrsid1115636
\par }\pard \s15\qj \li567\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid10384767 {\b\insrsid1115636 reset}{\insrsid1115636 \endash Reset the camera.}{\insrsid10384767\charrsid1115636
As move_map above. Pseudo-mapped motion can be used when mapped motion is not supported but relative motion is in which case mapped motion can be roughly approximated by careful calibration.
\par }\pard \s15\qj \li567\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid8135487 {\b\insrsid8135487 move_abs}{\b\insrsid10384767 _<direction>}{\b\insrsid8135487 }{\insrsid8135487 \endash Move to a specified absolute
location. The direction element gives a hint to the direction to go but can be}{\insrsid10384767 omitted. If present it will be one of \lquote up\rquote , \lquote down\rquote , \lquote left\rquote , \lquote right\rquote , \lquote upleft\rquote ,
\lquote upright\rquote , \lquote downleft\rquote or \lquote downright\rquote .}{\insrsid8135487\charrsid1115636
\par }\pard \s15\qj \li567\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid8135487 {\b\insrsid8135487 move_rel_<direction> }{\insrsid8135487 \endash Move a specified amount in the given direction.}{\insrsid8135487\charrsid1115636
\par }\pard \s15\qj \li567\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid9861573 {\b\insrsid8135487 move_con_<direction> }{\insrsid8135487 \endash Move }{\insrsid10384767 continuously in the given direction until told to stop}{
\insrsid8135487 .
\par }\pard \s15\qj \li567\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid10384767 {\b\insrsid10384767 move_stop }{\insrsid10384767 \endash Stop any motion which may be in progress.
\par }\pard \s15\qj \li567\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid10384767 {\b\insrsid10384767 zoom_abs_<direction> }{\insrsid10384767 \endash Zoom to a specified absolute zoom position. The direction element gives a hint to t
he direction to go but can be omitted. If present it will be one of \lquote tele\rquote or \lquote wide\rquote .}{\insrsid10384767\charrsid1115636
\par }\pard \s15\qj \li567\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid10384767 {\b\insrsid10384767 zoom_rel_<direction> }{\insrsid10384767 \endash Zoom a specified amount in the given direction.}{\insrsid10384767\charrsid1115636
Focus to a specified absolute focus position. The direction element gives a hint to the direction to go but can be omitted. If present it will be one of \lquote near\rquote or \lquote far\rquote .}{\insrsid10384767\charrsid1115636
\par }\pard \s15\qj \li567\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid10384767 {\b\insrsid10384767 focus_rel_<direction> }{\insrsid10384767 \endash Focus a specified amount in the given direction.}{\insrsid10384767\charrsid1115636
\par }\pard \s15\qj \li567\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid10384767 {\b\insrsid10384767 white_<subcommand> }{\insrsid10384767\charrsid10384767 -}{\insrsid10384767 As per the focus commands, except that direction may be
\par }{\b\insrsid10384767 iris_<subcommand> }{\insrsid10384767\charrsid10384767 -}{\insrsid10384767 As per the focus commands, except that direction may be \lquote open\rquote or \lquote close\rquote .
\par }\pard \s15\qj \li567\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin567\itap0\pararsid9861573 {\b\insrsid10384767 preset_set }{\insrsid10384767 \endash Set the given preset to the current location.
\par }{\b\insrsid10384767 preset_goto }{\insrsid10384767 \endash Move to the given preset.
\par }{\b\insrsid10384767 preset_home }{\insrsid10384767 \endash Move to the \lquote home\rquote preset.
ZoneMinder has always had a minimal WML (Wireless Markup Language) capability to allow it to function on mobile phones and similar devices. However as of 1.20.0 this is now deprecated and has been replaced with a new XHTML}{\insrsid6096418 }{
\insrsid10423296 \endash Mobile Profile mode as well as the default HTML4. XHTML-MP is a small, and limited, version of XHTML intended for mobile devices and is based on XHTML Basic. It does not contain
scripting or other dynamic elements and essentially is a subset of HTML as most people know it.
The ZoneMinder XHTML-MP interface allows you to log into your installation via your phone or mobile devices and perform a limited number of tasks. These include viewing recent events, and monitoring live streams. }{\insrsid16128633
However unlike the full interfaces these elements are presented as still images requiring manual refreshing. For now the XHTML-MP interface is presented as a prototype interface}{\insrsid6690694 ;}{\insrsid16128633 rather than one offering
full capabilities}{\insrsid6690694 . As}{\insrsid16128633 such}{\insrsid6690694 ,}{\insrsid16128633 please feel free to make comments or offer suggestions via the forums on }{\field\fldedit{\*\fldinst {\insrsid16128633
6e0065006d0069006e006400650072002e0063006f006d002f0000000000000000000000000000000000000000000000000000}}}{\fldrslt {\cs16\ul\cf2\insrsid16128633\charrsid2245351 http://www.zoneminder.com}}}{\insrsid16128633 . }{\insrsid6690694 One }{\insrsid16128633
final word on mobile }{\insrsid3231264 mark-up}{\insrsid16128633 standards in general and their application to ZoneMinder. Ideally I\rquote
d like to offer a WML2.0 interface. WML2.0 is a blending of WML1.3, which is traditional WAP, and XHTML. As such it offers the scripting that WML has traditionally included plus the better control of markup that is the realm of XHTML. Unfo
rtunately so far I\rquote m unaware of any devices that support WML2.0, certainly I\rquote ve never had a phone that does. If you find out that a particular phone does support this then please let me know (or better still send me the phone!).}{
\insrsid10423296
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid10423296 {\insrsid16128633 If you wish to use the XHTM
L-MP interface to ZoneMinder there is no extra configuration required to enable it per se. However ZoneMinder needs to be able to figure out what kind of content to deliver to particular browsers}{\insrsid2383329 ,}{\insrsid16128633
so you have two choices. You can either edit zm.php and include a definition that corresponds to your phone describing a small number of basic capabilities, you will see a couple of }{\insrsid11297672
examples already there, or you can use the comprehensive open source WURFL package available from }{\field\fldedit{\*\fldinst {\insrsid11297672 HYPERLINK "}{\insrsid11297672\charrsid11297672 http://wurfl.sourceforge.net/}{\insrsid11297672 " }{
. You will need to download both the WURFL php files and the wurfl.xml file itself. WURFL is a resource containing information on the capabilities of a huge number of mobile phones, devices and browsers. Thus once i
t has matched your phone it can determine various capabilities it may possess. This means that ZoneMinder itself only has to deal with these capabilities and not the individual phone types.}{\insrsid16128633
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid10423296 {\insrsid11297672 To use WURFL you should install the php files in the same directory as ZoneMinder and then create a \lquote wurfl\rquote
sub-directory and ensure it is readable and writeable (or preferably owned by) your web server user. You should put the wurfl.xml file in there. One other thing you may need to change, as the xml file is quite large, is the \lquote memory_limit\rquote
ve done this you should find that your phone or device is recognised and if it can support XHTML-MP it will receive that interface. If your phone is very n
ew, or you are using an old version of the XML file you might find that it is not present however. The WURFL library uses a caching strategy to avoid reloading the whole XML file each time so check if a sensible looking cache file has been created in the
\lquote wurfl\rquote sub-directory also check the wurfl.log in the same place.}{\insrsid11297672
The WURFL is a third party application and as such I am unable to offer support directly for it. If you feel your device is missing or incorrectly represented please contact the authors via t
heir own channels. If on the other hand you have any comments on ZoneMinder on your device specifically please let me know and I would be pleased to hear about it.}{\insrsid5056748\charrsid11297672
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid10423296 {\insrsid4462433 As support for cookies in mobile devices is patchy at best, the groups feature is not fully
implemented in the XHTML-MP views. Instead if there is a group called \lquote Mobile\rquote already defined then that group will always be effective, if not then all monitors }{\insrsid9330742 available to the logged in user }{\insrsid4462433
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid150409 Life eh? Nothing ever works
first time does it? In case you are having problems here are some things to try. If these don't work then check the ZoneMinder FAQ at }{\field\fldedit{\*\fldinst {\insrsid150409 HYPERLINK "http://www.zoneminder.com/faq.html" }{\insrsid12528177
http://www.zoneminder.com/faq.html}}}{\insrsid150409 and then the forums at }{\field\fldedit{\*\fldinst {\insrsid342179 HYPERLINK "http://www.zoneminder.com/forums"}{\insrsid12528177 {\*\datafield
00000000000000000000000000}}}{\fldrslt {\cs16\ul\cf2\insrsid342179 http://www.zoneminder.com/forums.html}}}{\insrsid150409 first and see if anyone has had the same problem in the past}{\insrsid2383329 . }{\insrsid150409
If not then feel free to get in touch and I'll see if I can suggest something else. }{\insrsid2383329 . Please ensure that you read the posting guidelines and go through the steps listed below before posting or mailing though. }{\insrsid150409
The best places to look for errors are in the system error log (normally /var/log/messa}{\insrsid2383329 ges on RedHat), the}{\insrsid150409 ZoneMinder logs, and the web server log (/var/log/httpd/erro
r_log unless otherwise defined). There should be something in one of those that gives you some kind of tip off.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 Some things to check}{\insrsid2383329 first}{\insrsid150409 .
Device configuration. If you can't get your cameras to work in ZoneMinder, firstly make sure that you have the corre
ct settings. Use xawtv or something like that to check for settings that work and then run zmu -d <device_no> -q -v to get the settings. If you can't get them to work with that then the likelihood is they won't work with ZoneMinder. Also check the system
logs (usually /var/log/messages) for any video configuration errors. If you get some and you're sure they're not a problem then switch off ZM_STRICT_VIDEO_CONFIG in zmconfig.pl or the \lquote options\rquote tab.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid150409 \hich\af2\dbch\af0\loch\f2 o\tab}Start simple. Begin with a single monitor and single zone.
You can run the zmc capture daemon from the command line as 'zmc --device 0' (or whatever your video device is). If it returns immediately there's a problem so check the logs, if it stays up then your video configuration is probably ok. To get more infor
m
ation out of it use debug as specified below. Also check that the shared memory segment has been created by doing 'ipcs -m'. Finally, beware of doing tests as root and then trying to run as another user as some files may not be accessible. If you're check
ing things as root make sure that you clean up afterwards!
Web server. Ensure that your web server can serve PHP files. It's also possible that your php.ini file may have some settings which break ZoneMinder, I'm not a PHP guru but setting safe mode may pre
vent your PHP files from running certain programs. You may have to set configuration to allow this. Also since the daemons are started by your web server, if it dies or is shut down then the daemons may disappear. In this version the daemons are run under
the control of a script which should trap expected signals but it is possible this doesn't cover all circumstances.}{\insrsid2383329 If everything else works but you can\rquote
t get images in your browser a likely cause is a mismatch between where your web server expects to exec
ute CGI scripts and where you have installed the zms streaming server. Check your server configuration for the correct CGI location and ensure you have supplied the same directory to the ZoneMinder configure script via the \endash with-cgidir option. }{
\insrsid150409
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid150409 \hich\af2\dbch\af0\loch\f2 o\tab}}\pard \s15\qj \fi-360\li720\ri0\sa180\widctlpar\tx720\nooverflow\faroman\ls2\rin0\lin720\itap0 {\insrsid150409 One of the
more common errors you can see in the log files is of the form 'Can't shmget: Invalid argument'. Generally speaking this is caused by an attempt to allocate an amount of shared memory greater than your system can handle. The size it requests is base on th
following formula, ring buffer size x image width x image height x 3 (for 24 bits images) + a bit of overhead. So if for instance you were using 24bit 640x480 then this would come to about 92Mb if you are using the default buffer size of 100. If this is
too large then you can either reduce the image or buffer sizes or increase the maximum amount of shared memory available. If you are using RedHat then you can get details on how to change these settings at }{\field{\*\fldinst {\insrsid2383329
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid150409 \hich\af2\dbch\af0\loch\f2 o\tab}}\pard \s15\qj \fi-360\li720\ri0\sa180\widctlpar\tx720\nooverflow\faroman\ls2\rin0\lin720\itap0 {\insrsid150409 You should be }{
\insrsid2383329 able to use a similar procedure}{\insrsid150409 with other distributions to modify the shared memory pool without kernel recompilations though in some cases this may be necessary. }{\insrsid2383329
You can also sometimes get shared memory errors if you have changed the monitor image size for instance. In this case it is sometimes that an old process is hanging onto the shared
memory and will not let it be resized. Ensure that you do a full ZoneMinder restart and/or manually delete the shared memory segment to check.}{\insrsid150409 Use the ipcs and ipcrm system commands to check and remove }{\insrsid2383329 segments}{
s and your web console or other screens come up with bits missing then it's possible that there is a problem with the PHP configuration. Since version 0.9.8 ZoneMinder has used short PHP open tags to output information, so instead of something like this '
<?php echo $value ?>', it will be something like this '<?= $value ?>' which is easier and quicker to write as well as being neater. More information about this directive can be seen at the following location, }{\cs16\ul\cf2\insrsid150409 http://www.php.
. However although by default most PHP installations support this form, some will need to have it switched on explicitly. To do this you will first need to find your php.ini file (do a 'locate php.ini' or 'find / -name php.ini'.
Be aware however that sometimes you might find more than one, so ensure you identify the one that is actually being used. You will then need to find the line that starts 'short_open_tag = ' and change the Off value to On. This will correct the problem. H
o
wever in some cases you may have explicitly switched it off, so that XML compliant documents can be more easily served, or you may even not have permission to edit the file. In this case you can go into the web directory of ZoneMinder and run 'sh retag.sh
' which will replace all the short open tags in the files themselves with the longer variant. You will obviously have to remember to do this for each subsequent version of ZoneMinder that you install as well.
\par }\pard \s15\qj \li720\ri0\sa180\widctlpar\nooverflow\faroman\ilvl12\rin0\lin720\itap0 {\insrsid150409 where the zma-0 part identifies the daemon and the device it is running on. Entries
with INF in are informational and not an error, if you see ERR then it is one, though not all are fatal.}{\insrsid2383329 WAR would indicate a warning.}{\insrsid150409
You can prevent this information from being emitted by setting the ZM_DBG_LEVEL_zmc environment variable to -1 or less o
nce things are working. If you want to run any of the daemons from the command line to test, setting ZM_DBG_PRINT to 1 will output the debug on the console. You can also use the USR1 and USR2 signals to increase or decrease the amount of debug being emitt
Paths. I admit it, the various paths in ZoneMinder can be bit of a nightmare}{\insrsid2383329 mainly because some relate to real directories and others to web paths}{\insrsid150409
. Make sure that they are all correct and that permissions are such that the various parts of ZoneMinder can actually run.
Missing perl modules. There are various perl modules used by the various scripts. If you get errors about missing ones, the easiest way to install them is to type the following (you will probably need to be root),}{\i\insrsid150409
\par }\pard \s15\qj \li720\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin720\itap0 {\insrsid150409 this will then (eventually, after some configuration if it\rquote
s your first time) present you with a prompt. From there you can type install module, e.g. Archive::Zip and the rest should be more or less automatic as it will chase any dependencies for you. There may
be some initial configuration questions it might ask you on startup if you've never run it before and to speed things up I would not install a new Bundle at this point (it can end up building you a whole new perl if you\rquote
re not careful) if it asks you but everything else should be quite straightforward.}{\insrsid2383329 You can often also install perl modules via your ordinary package manager, e.g. yum or apt.}{\insrsid150409
Unsupported palettes. ZoneMinder currently is designed to use the simple palettes of greyscale and 24 bit as well a
s now the YUV420P and some other palettes. This should cover most cameras but it's possible that there are ones out there that might want to use more esoteric formats that ZoneMinder doesn\rquote
t support. This will often show up as the capture daemon being unable to set picture attributes. If this occurs try using different palettes starting with greyscale and if you can't get anything to work let me know and I'll try and add it.
USB bus problems. If you have multiple USB cameras on one bus then it can appear as
if ZoneMinder is causing your cameras to fail. This is because the bandwidth available to cameras is limited by the fairly low USB speed. In order to use more than one USB camera with ZoneMinder (or any application) you will need to inform the driver tha
t
there are other cameras requiring bandwidth. This is usually done with a simple module option. Examples are usb_alt=<n> for the OV511 driver and cams=<n> for CPIA etc. Check your driver documentation for more details. Be aware however that sharing camera
s in this way on one bus will also limit the capture rate due to the reduced bandwidth.
Incorrect libjpeg.a detection. It seems to be the case that in some cases the library file libjpeg.a is reported as missing even when apparently present. This appears to
actually be down to the g++ compiler not being installed on the host system. Since ZoneMinder contains both C++ and C files you need to be able to compile both of these file types and so usually need to ensure you have gcc and g++ installed (though they
Httpd and zms memory leaks. It has been reported by some users with RedHat 9 that the zms process fails to terminate correctly when the controlled window is killed and also that it, and it\rquote s associated httpd process, continue to
grow in memory size until they kill the system. This appears to be a bug in early versions of apache 2. On other systems it may appear that zms is leaking and growing. However what grows is the total and shared memory size while the non-shared memory siz
stays constant. It's a little odd but I think what it happening is that as zms picks images out of the shared memory ring buffer to display, as each slot is read the size of that bit of memory is added to the shared memory total for the process. As strea
m
ed images are not read consecutively it's a semi-random process so initially most of the buffer slots are new and the shared memory size grows then as time goes on the remaining unaccessed slots reduce until once all have been read the shared memory use c
a
ps out at the same size as the actual segment. This is what I would have expected it to be in the first place, but it seems to do it incrementally. Then once this total is hit it grows no further. As it's shared memory anyway and already in use this appar
ent leak is not consuming any more memory than when it started.
Cambozola. There appears to be an issue with recent versions of Cambozola that causes image corruption in the stream. If you are getting this then I suggest you stick with version 0.22 which is available from the Downloads section of }{\field{\*\fldinst {
You can also switch between using zms or nph-zms the latter of which supplies non-parsed headers which should work somewhat better.}{\insrsid150409
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0 {\insrsid150409 Also, if you are usi
ng IE under Windows and get lots of annoying clicks when various windows refresh then you'll need to edit your registry and remove the value for HKEY_CURRENT_USER\\AppEvents\\Schemes\\Apps\\Explorer\\Navigating\\
.current or download the registry script to do it for you from http://www.zoneminder.com/downloads/noIEClick.reg
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid15891821 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid15891821 Menage of various new features and bug fixes.
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid15891821 FIX \endash The HTTP refresh method of updating the Cycle view was broken. This is now fixed.
\endash There was an arbitrary limit on the size of a blob due to the dimensioning of the field in the database. This has been increased to allow all possible blob sizes to be accounted for.
\endash On some platforms there is no definition of the \lquote round\rquote function. Previous versions of ZM hav
e detected this and included one if no other is present. However changes in 1.21.0 meant that this did not always happen and the function went undefined. This has been corrected.
FEATURE \endash Support has been added to allow monitors to be defined as mirrored. Thus images can now be flipped horizontally or vertically before processing as well as rotated as in previous versions.
\endash }{\insrsid12717233 Fixed issue where t}{\insrsid15891821 he PTZ control function to set camera presets never passed the preset numb}{\insrsid12717233 er so preset 1 was always used.}{\insrsid15891821
FEATURE \endash A custom title can now be added via the normal Options dialog}{\insrsid4725983 (}{\insrsid4725983\charrsid4725983 ZM_WEB_TITLE_PREFIX}{\insrsid4725983 )}{\insrsid12717233
. This title will be used in all browser windows and allows you to distinguish between multiple ZM installations for example.
Ordinarily ZoneMinder will resize the console window to fit the number of monitors displayed. If you are using a tabbed browser this can be a little irritating. A new option }{\insrsid4725983 (}{\insrsid4725983\charrsid4725983 ZM_WEB_RESIZE_CONSOLE}{
\insrsid4725983 ) }{\insrsid12717233 has been added to control this behaviour.
FEATURE \endash Version 1.21.0 added support for events to be labelled with Cause and Notes fields. However these could not be modified directly from the web interface. This has been amended so that an \lquote Edit\rquote link is now presen
t in the events listing. Clicking on this allows you to modify these fields for one or more events so they can be identified as belonging to a particular incident.
There has long been a dichotomy between the functions that can be applied via inte
ractive filters versus background saved filters. This release addresses this to some extent allowing you, for instance, to archive or unarchive matching events, or edit them as described above. This is not a complete solution and it is expected that the f
unctionality will converge further in the future.}{\insrsid12717233
Previously in the c/c++ code accessor functions had to be called to access the value of configuration options. This was expensive when done repeatedly so some classes used cached local variables to
avoid this. The configuration has been rewritten to provide all configuration options as members of the configuration class which are initialised once on startup and then can be accessed directly with no further overhead.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid4617087 \hich\af2\dbch\af0\loch\f2 o\tab}}\pard \s27\qj \fi-357\li714\ri0\sa180\widctlpar\tx720\nooverflow\faroman\ls4\rin0\lin714\itap0\pararsid12717233 {\insrsid4617087 LANGUAGE
\endash Support for the Danish language has now been included. Thanks for forum user \lquote voronwe\rquote for his work on this. Select dk_dk in the languages preferences to use this language.
\endash Events viewed in the events listing view can now be saved locally by clicking on the \lquote Export\rquote b
utton. This creates a tar or zip file of the selected file groups, such as images, videos etc, as well as, optional, HTML pages describing the basic details about the event and frame details. This allows a basic navigation and viewing of the events outsid
e of the regular ZoneMinder interface. }{\insrsid8808309 This format is different, and improved, over that that created in the background filter function and it is expected that these functions will converge at some point.}{\insrsid4617087
\endash Clearing the \lquote Track Motion\rquote checkbox in the Control section of the Monitor configuration would not be saved resulting in this setting being stuck in an \lquote on\rquote state. This has been corrected.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid8808309 \hich\af2\dbch\af0\loch\f2 o\tab}FIX \endash The \lquote Play All\rquote link in the event view allows a sequence of events to be streamed consecutively. This is fin
e in a streamed view but meaningless in the stills view so has been removed.
\endash The \lquote show\rquote trigger command in zmtrigger.pl has been added to allow miscellaneous externally sourced text to be displayed in the image timestamps.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid8808309 \hich\af2\dbch\af0\loch\f2 o\tab}FEATURE \endash Add the \lquote Auto Stop Timeout\rquote
monitor control option to allow finer control of Pan/Tilt/Zoom cameras with support for only basic continuous modes of motion.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid8808309 \hich\af2\dbch\af0\loch\f2 o\tab}}\pard \s27\qj \fi-357\li714\ri0\sa180\widctlpar\tx720\nooverflow\faroman\ls4\rin0\lin714\itap0\pararsid8808309 {\insrsid8808309 LANGUAGE
\endash The German la}{\insrsid2112162 nguage files have been updated.}{\insrsid8808309
\endash Support for control of Axis network cameras has been added. This uses the zmcontrol-axis-v2.pl script and should work with all Axis PTZ network cameras that use version 2 of the Axis API.
\endash The zmaudit.pl script has been modified to be faster and access disk a lot less. Previously it was possible for this script to frequently thrash disks while determining timestamps on directories.
\endash A contributed patch by Ross Melin has been included. This gives you the option of using an alternative mailing method in the zmfilter.pl script if the default method does not work correctly. To use the new method go to Options->Email and set }{
\insrsid2112162\charrsid2112162 ZM_NEW_MAIL_MODULES}{\insrsid2112162 to on.
\endash Previously the ZM_EMAIL_HOST config was not passed to the zmfilter.pl script so hosts other than localhost were not used. This has been fixed.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid16081520 \hich\af2\dbch\af0\loch\f2 o\tab}}{\insrsid16081520 LANGUAGE \endash A translation for the Romanian language has been added. To use it select ro_ro as the language.}{
\endash In previous versions the path to the zms daemon from web pages was in the form of a local web path without hostname. This has been report
ed as not working with certain media players where the hostname is not implied, as with browsers. The paths to the streaming server now always have the hostname prepended so that they are always a full valid url.
\endash An experimental Pelco-P control script has been added to support PTZ cameras that support this protocol.}{\insrsid15291753 This script has not really been tested but is included as a basis for further development or customisation.}{
The zmfilter.pl script now respects the ZM_FAST_DELETE option and will fully delete any events rather than assuming that zmaudit.pl will clear up if it just removes the primary database record.
\endash The montage view layout now correctly utilises the ZM_MAX_MONTAGE_COLS option when determining the dimensions and layout of the montage window.
\endash A contributed patch by forum user \lquote lazyleopard\rquote has been included. This allows a specified number of frames to be discarded to alleviate problems with broken interlaced frames where multiple cameras share one bttv chip}{
\insrsid15291753 and produce a \lquote comb edge\rquote like image}{\insrsid16081520 . To invoke this option go to Options->Config and set ZM_CAPTURES_PER_FRAME to greater than 1, a value of 3 is recommended in the first instance.
\endash Several users have reported problems using the Perl Compatible Regular Expression (PCRE) library, mostly to do with it not being found }{\insrsid8724063 or an incorrect version being used}{\insrsid15291753 . This version allows }{\insrsid8724063
an alternative method of parsing the output from network cameras that does not depend on libpcre at all. Which method is used is controlled by the option Options->Network->}{\insrsid8724063 ZM_NETCAM_REGEXPS}{\insrsid8724063 .
If this option is on then the traditional regular expression based parsing is implemented, provided you have built with libpcre. If the option is off or libpcre is missing then a more basic parsing is used instead.
This new method should be slightly faster as it does not have the overhead of regular expression parsing, however this also makes it slightly more inflexible. If you experience problems using the new method with your netcam then you shoul
d try switching to the regular expression based method, and report the issue via the forums, preferably with a snapshot of the output of your camera.}{\insrsid15291753
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid13441986 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid13441986 Addition of camera control, plus }{\insrsid8454255 several }{\insrsid13441986
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid16190191 FEATURE \endash Added support for Pan/Tilt/Zoom and general camera control.
\endash }{\insrsid11102403 The montage view layout has been modified to allow b}{\insrsid13376619 etter dynamic layout of windows}{\insrsid13441986 .}{\insrsid13376619
Views should now be laid out in a more logical arrangement. This is a relatively temporary change and the montage view will shortly be rewritten to use flowing \lquote div\rquote tags which should add more flexibility and be less complex.}{
\cs36\insrsid13441986 FIX }{\insrsid13441986 \endash }{\insrsid13376619 All}{\cs36\insrsid13376619 stream views now have an \lquote alt\rquote tag to highlight which monitor they should be displaying}{\cs36\insrsid13441986 .
\par {\listtext\pard\plain\s27 \cs36\f2\fs20\lang2057\langfe1033\langfenp1033\insrsid13376619 \hich\af2\dbch\af0\loch\f2 o\tab}}{\cs36\insrsid13376619 FIX \endash Detection of which
markup language to use, HTML or XHTML-MP has now been optimised to ensure theat the test only happens once per session.
\cs36\insrsid13376619 FIX \endash The zmtrigger.pl script had an old, and incorrect, initial section using constants that were no longer valid. This has now been fixed.
\cs36\insrsid13376619 FIX \endash In previous versions it was possible for a
process to die and not be reaped by zmdc.pl. This could have resulted in processes remaining as zombies resulting in them not being restarted after crashing. This has now been fixed so all dying processes will be caught and handled.
\cs36\insrsid10707888 FIX \endash Previously separate \lquote object\rquote and \lquote embed\rquote tags were used for Internet Explorer and non-IE browsers. These have been merged so that browsers will use whichever }{\cs36\insrsid8454255
tag is appropriate.}{\cs36\insrsid8676382 Any player controls that were present should now be hidden as well.}{\cs36\insrsid10707888
\cs36\insrsid8676382 FIX \endash A problem was present whereby the Maximum FPS set in the bandwidth settings was not being respected in the live streams. This is now fixed.
\cs36\insrsid8676382 FIX \endash If users were created with restricted monitor ids, it was sometimes possible that permission errors would still be issued if they tried to view s
treams or other elements associated with monitors in their list. This has now been corrected such that any restrictions are applied correctly.
\par {\listtext\pard\plain\s27 \cs36\f2\fs20\lang2057\langfe1033\langfenp1033\insrsid8676382 \hich\af2\dbch\af0\loch\f2 o\tab}FIX \endash Users created with only \lquote view streams\rquote permissions were presented with a \lquote permission denied\rquote
error in the area of the Watch window normally containing the recent events list. Whilst this was technically correct it was unnecessary and untidy, and has now been changed just to be blank.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1983261 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid11620711 Mostly bug fixes, large and small with a couple of minor features included}{
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1983261 FIX \endash A dependency on the regular expression library was introduced in 1.20.0 which caused some people }{\insrsid12600144
to have build problems. This library has traditionally been is necessary to support network cameras but not otherwise. This situation has now been restored.
\cs36\insrsid12600144 . This option adds }{\cs36\insrsid1983261 a time code onto }{\cs36\insrsid12600144 the url of each }{\cs36\insrsid1983261 stream to prevent it from being cached}{\cs36\insrsid12600144
which had caused some broken image problems with some browsers, notably Mozilla.
UTH before loading user details. This should }{\cs36\insrsid12600144 have been in there in 1.20.0 but was omitted and should }{\cs36\insrsid1983261 fix the issue where streams did not work with authentication off.}{\cs36\insrsid12600144
}{\cs36\insrsid12600144 FIX }{\insrsid12600144 \endash There was some d}{\cs36\insrsid1983261 ebug }{\cs36\insrsid12600144 code left behind in }{\cs36\insrsid1983261 zm_xhtml.php.}{\cs36\insrsid12600144 This was unnecessary and has been removed.
Fixed user sql, added debug and wrapped in check for libcrypto in zm_user.cpp. This should correct bogus loading of user data which may have affected some people. You can also now just bump up the debug level to see what the auth strings being used are.}{
FIX }{\insrsid6365987 \endash The }{\cs36\insrsid6365987 xHTML}{\cs36\insrsid1983261 console }{\cs36\insrsid6365987 page }{\cs36\insrsid1983261 now uses }{\cs36\insrsid6365987 the }{\cs36\insrsid1983261 mobile group as it should}{\cs36\insrsid6365987
FIX }{\insrsid6365987 \endash }{\cs36\insrsid6365987 Modified database u}{\cs36\insrsid1983261 sername to be binary. You need to run the zmalter}{\cs36\insrsid6365987 -1.20.0}{\cs36\insrsid1983261 sql }{\cs36\insrsid6365987 script as usual }{
\cs36\insrsid1983261 to change your Users table to disallow case-inse}{\cs36\insrsid6365987 ns}{\cs36\insrsid1983261 itive checking which may have been breaking some }{\cs36\insrsid6365987 people\rquote s}{\cs36\insrsid1983261 streams.}{
FIX }{\insrsid6365987 \endash }{\cs36\insrsid1983261 Fixed incorrect constant definitions in zmtrigger.pl}{\cs36\insrsid6365987 . This script had not been updated }{\cs36\insrsid4799242 along }{\cs36\insrsid6365987 with the other scripts.
\par {\listtext\pard\plain\s27 \cs36\f2\fs20\lang2057\langfe1033\langfenp1033\insrsid6365987 \hich\af2\dbch\af0\loch\f2 o\tab}FIX }{\insrsid6365987 \endash }{\cs36\insrsid1983261 Fixed bogus double .jpg suffix on diagnostic images, also included them }{
\cs36\insrsid6365987 (if they exist) }{\cs36\insrsid1983261 in frame view}{\cs36\insrsid11620711 .
\par {\listtext\pard\plain\s27 \cs36\f2\fs20\lang2057\langfe1033\langfenp1033\insrsid11620711 \hich\af2\dbch\af0\loch\f2 o\tab}FIX }{\insrsid11620711 \endash }{\cs36\insrsid1983261 Corrected broken check for libcrypto (}{\cs36\insrsid11620711 the }{
\cs36\insrsid1983261 check happened before }{\cs36\insrsid11620711 any }{\cs36\insrsid1983261 definition) causing build problems for some people who do not have MD5 library installed.}{\cs36\insrsid11620711
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid11620711 \hich\af2\dbch\af0\loch\f2 o\tab}}{\insrsid11620711 FIX \endash }{\cs36\insrsid1983261 Added space before -m in zmu command in zm_actions.php}{\cs36\insrsid11620711
\cs36\insrsid11620711 FIX }{\insrsid11620711 \endash Added quotes around}{\cs36\insrsid1983261 brightness etc SQL in zm_actions.php}{\cs36\insrsid11620711 to avoid errors when values are empty.
\cs36\insrsid11620711 FIX }{\insrsid11620711 \endash }{\cs36\insrsid1983261 Added line length to fgets in zm_config.php.z}{\cs36\insrsid11620711 to prevent php warning
\cs36\insrsid11620711 FIX }{\insrsid11620711 \endash }{\cs36\insrsid1983261 Slightly enlarged a couple of window}{\cs36\insrsid11620711 size}{\cs36\insrsid1983261 s in zm_config.php.z}{\cs36\insrsid11620711 to work better with different browsers.
\cs36\insrsid11620711 FEATURE }{\insrsid11620711 \endash }{\cs36\insrsid1983261 Console window now sizes itself according to how many monitors in list}{\cs36\insrsid11620711 , though there is a minimum size}{\cs36\insrsid1983261 .
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid4352231 FEATURE}{\insrsid10423296 \endash }{\insrsid4352231 Certain configuration (Mostly
database settings) is now stored in a new file zm.conf. This means that database access settings can be changed without recompilation. It also allows the creation of ZoneMinder rpms. Watch zoneminder.com for details. Thanks for forum user \lquote oskin
FEATURE \endash }{\insrsid4352231 The WML interface is now deprecated and the XHTML-MP interface is the new supported interface for mobile devices}{\insrsid10423296 .
Monitor groups have now been added allowing subsets of monitors to be viewed independently}{\insrsid10423296 .
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid4352231 \hich\af2\dbch\af0\loch\f2 o\tab}}{\insrsid4352231 FEATURE}{\insrsid10423296 \endash }{\insrsid4352231 A gener
ic external triggering interface has been included via the zmtrigger.pl script.}{\insrsid10423296 }{\insrsid1732201 A new monitor function \lquote Nodect\rquote has been added to support this.}{\insrsid10423296
\endash Interaction between the web pages and the streaming daemons and other utilities has previously been no
t as secure as it could have been and open to possible abuse. This has now been addressed and zms and zmu both now use (optional) authentication strings to validate access. You need to have openssl installed so that the MD5 libraries can be linked. See th
e ZM_AUTH_METHOD and ZM_AUTH_SECRET configuration items for further details.
\endash The maximum daemon restart delay in zmdc.pl was previously fixed at 15 minutes. This may have been too long for some users, for example if power has failed to a camera th
en a 15 minute delay on restoration is not desirable. This maximum is now configurable via the ZM_MAX_RESTART_DELAY configuration item.
FEATURE \endash The web files have been changed to use the newer style autoglobals, e.g. $_SERVER rather than $HTTP_SERVER_VARS. This should enable use on PHP5 without any modification.
\endash The use of two database users has been somewhat redundant for a number of versions now. In 1.20.0 there is only one database user. The zmupdate.pl }{\insrsid14247956 script }{\insrsid927462 unfortunately cannot}{\insrsid11471343 handle the migr
ation }{\insrsid9451376 as it needs to access the database }{\insrsid927462 so you should make a note of the username and password of the privileged user and then re-enter that using}{\insrsid12059199 zmco}{\insrsid1732201 nfig.pl when rebuilding ZM.}{
\insrsid6378949 \endash The zmupdate.pl script previously held a database connection open for days at a time but only used to use it periodically. This has now been changed to be only open while in use.}{\insrsid5850313
\endash Debug output and it\rquote s relationship with environment variables etc was previously broken. This has been tidied up and made much easier to use and understand.
\endash Image capture timeouts used by zmwatch.pl to restart apparently frozen zmc processes were being calculated incorrectly on occasion. This was causing some unnecessary processes to be restarted. This calculation has been fixed.
\endash There was a problem with the interaction between monitor statuses and the status web window. This meant that sometimes the window did not pop to the front, or play the alarm sound, properly. This has been corrected.
\endash Some network cameras send data in a format which was previously not recognised by the regular expression engine. This has been modified to allow these cameras (NC1000 etc) to function with ZoneMinder.
\endash A bug in event streaming when events are of very short duration has been fixed. Thanks to forum user \lquote reza\rquote for spotting this one.
\endash A }{\insrsid5274068 possible exploit in the login page was identified and has now been fixed}{\insrsid10159006 . Thanks }{\insrsid5274068 again }{\insrsid10159006 to forum user \lquote reza\rquote }{\insrsid5274068
highlighting this problem also}{\insrsid10159006 .
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 FIX \endash Sorting event lists by duration was broken and has now been corrected.
\endash The zmfix utility previous corrected file permissions on video device files only. This has been modified to do likewise to the X10 device serial port if enabled.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}FIX \endash The modification suggested by forum user \lquote oskin\rquote has been incorpor
ated into the code to try and reduce or remove video for linux errors.
\endash Added \lquote <<\rquote and \lquote >>\rquote links to the page selector in the events list as suggested by forum }{\insrsid1732201\charrsid13577040 user \lquote }{\cs35\cf1\insrsid1732201\charrsid13577040 unclerichy\rquote }{
\endash Brightness, colour, hue and contrast are now saved persistently for a monitor rather than being reset each time the system is restarted. This feature is based on a patch submitted by forum user \lquote oskin\rquote .
\endash In previous versions the events folder has been keyed by the monitor name. This has caused problems in the pa
st with various characters appearing which are legal in names but not in filesystems. From this version all files related to monitors are keyed on the monitor id rather than the name. To help you navigate through these files the monitor name still exists
but as a link only. Please ensure you run zmupdate.pl to update your events directory.
\endash You may now optionally have thumbnail images in your event lists. To enable this functionality set }{\insrsid1732201\charrsid12404033 ZM_WEB_LIST_THUMBS}{\insrsid1732201 on in Options->Web. You can also control t
he width or height of these thumbnails but should only set one dimension only and leave the other blank or zero.
\endash You can now specify how many image thumbnails appear across and down the page in the event stills listing. In Options->Web set the }{\insrsid1732201\charrsid12404033 ZM_WEB_FRAMES_PER_LINE}{\insrsid1732201 and/or }{
\insrsid1732201 ) for video generation and processing. Recently a new version (0.4.9-pre1) was released
which changed the interface that ZoneMinder uses and so broke compilation. This version will detect which version of ffmpeg you have and compile accordingly.
If you use filters to send event notification emails you can now have them sent in HTML format. This is done automatically if your mail body includes a \lquote <html>\rquote token,
\endash An experimental feature has been added which lets you view several events in sequence. In event listing you can check the events you want to view and then click the \lquote View\rquote
button. This will allow you to navigate through only those events in the normal manner (via Prev and Next links) but also to view them in sequence by clicking on the \lquote Play All\rquote
link. This will replay each event and then automatically move onto the next one. You can stop this progression at any time by pressing \lquote Stop\rquote (which only stops the sequence and not the currently playin
g event). The timing of the replay is done depending on the calculated length of the event (plus one second) and so may not exactly correspond to the real event length. In particular this is unlikely to work if replaying events using MPEG video and buffer
ing players as the timing will likely be incorrect. If you are viewing an event but haven\rquote t checked any in the list the \lquote Play All\rquote button will just work down the current event list.
\endash Previously events have been created even if only one frame has generated an alarm. This has not always been desirable as sometimes glitches and flickers create large numbers of events, however no mechanism existed for limiting this. In this
version you can now specify the minimum number of consecutive alarmed frames that are necessary to create an event. This is the \lquote Alarm Frame Count\rquote
described above. Note that if an alarm is in progress single isolated alarmed frames will still prolong it and the count only applies to the initial frames that would cause the event.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Language fixes and updates.
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 FIX \endash The US English language file was recursively including itself rather than the UK English file as the base language.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}LANGUAGE \endash The Brazilian Portuguese language file detailed in the previous release has actually been included in this one.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}LANGUAGE \endash The Argentinian Spanish, Polish and Italian translations have all been updated with tokens introduced in version 1.19.3.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Minor tweaks, fixes and language updates.
All stills views now use the single image mode of zms rather than spawning off a zmu process to write an image which is then read. This reduces complexity of double buffering significantly and also reduce
s the chance of errors caused by multiple simultaneous image generation.
\endash The generated MIME types when creating streamed video were previously assigned by zms depending on which of a limited number of output formats was specified. This has now be
en changed so that the ffmpeg libavformat library itself now generates these identifiers. The consequence of this is that many more video formats supported by your version of ffmpeg should now be available via zms.
\endash When viewing a single frame of an event you can select a \lquote stats\rquote
link to view the statistics that apply to that frame, if you have the RECORD_EVENT_STATS option switched on. This can be used to help configure your zones for optimal motion detection. Previously only pixel count values we
re displayed here which made it difficult to configure zones configured in percentage terms. These values are now displayed in both pixel and percentage terms to assist in zone configuration. Note that the percentage values are based on the current size o
f the zone so if this is changed then the value displayed will not be applicable at the time of event generation.
\endash When doing motion detection an extra blob, that could never be removed, was sometimes included. This could have caused false triggering and has not been corrected.
\endash A problem was reported whereby when using bulk frame records to reduce database load the last frame record was not written. Replaying the event via the web interface resulting in the event being truncated. A correction has
been made so prevent this and ensure that the last frame of an event is always recorded.
\endash If an analysis daemon terminates abnormally or the host computer crashes then events can be left in a state whereby they effectively have zero length and are useless. A change to zmaudit.pl was made such that any \lquote open\rquote
events such as this which have not been updated for at least five minutes are closed and updated to reflect their actual content so that they may be viewed or saved. Events recovered in this way are named with a \lquote (r)\rquote
\endash In more recent versions of MySQL the password hash generated is 50 characters long, which overflows the previous password field in the database which was only 32 characters long. This field has been extended to 64 characters to accommodate this.
The montage view had an error whereby the refresh timeout for stills was mislabelled causing continuous refresh attempts which rendered the view mostly unusable. The constants in question are now correctly referenced.
The default, bandwidth specific, rate and scales were not always used as the records in the database were misnamed. This is now corrected though you may need to reset the values that were used previously as these will be lost if they had been changed.
\endash It was previously the case that old images could be left in the \lquote images\rquote
directory for a long period, sometimes resulting in incorrectly assuming correct operation. A fix was made to zmaudit.pl which modified the previous clean up of o
ld WAP images so that any old images left in this directory are removed after a short period. Please ensure that if you have customised the web interface and have images you wish to keep that they are not left in the temporary images folder as they will n
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}LANGUAGE \endash Updated versions of the Dutch and Argentinian Spanish translations have been included.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Minor features, fixes and language updates.
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 FEATURE \endash The default replay rate and live and event scale settings are now configurable on a per bandwidth basis rat
her than globally. This allows you to view at full scale when you have high bandwidth and at smaller scales when you do not have so much resource. You will need to re-configure your previous defaults as they will be lost.
\endash Two new filter elements have been added. These are disk blocks and disk percentage. These are event independent and return the amount of disk space used on the event partition in terms of disk blocks or percentage as returned by }{
\i\insrsid1732201\charrsid13107570 df(1)}{\insrsid1732201 . Thus filters using these criteria will either match all events or none at all depending on the disk usage at th
e time of filter execution. The addition of these terms along with the ability to sort and limit filter results now means it is possible to create a filter that will automatically clear out old events once disk usage exceeds a certain value. Included in t
h
e database schemas for both new installations and upgrades is a sample filter called PurgeWhenFull which can be used to do this. It is initially not set to do anything automatically so if you want to use it, you should load it into the filter selection wi
ndow, modify it to your taste and then save it, selecting \lquote auto delete\rquote
. Please note that filters created using disk related terms to delete events should always contain a limit term also otherwise it is possible for all events to match and thus be deleted.
Using a limit ensures that only a small number are affected at any one time.
\endash Filters can now be defined to automatically execute an external script or program of your choosing. This can be specified when the filter is saved. Note that for securi
ty reasons this cannot be just any arbitrary command but must be readable and executable by your web server effective user. The script or program you specify here will be executed in the events root directory once for each event and will be passed one par
ameter containing the relative path to the event directory. This will normally be of the form }{\i\insrsid1732201\charrsid13107570 <MonitorName>/<EventId>}{\insrsid1732201
so it it possible to determine both the monitor and event in question from the path. Note also that a flag is set per event as with other a
uto actions indicating that an executable script has been run on that event and so to exclude it from subsequent matches. However if you have several filters all with executable scripts you will find that only the first gets executed as the flag will be s
et following successful completion and so no further scripts will be run on that event. Successful completion is indicated by the script returning a zero exit status, any other status indicates an error and the }{\i\insrsid1732201 executed }{
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}FIX \endash When viewing a list of frames in an event, the link to the diagnostic image was incorrect. This is now fixed.
\endash The zone definition have been updated so that selecting the various types of zones etc only disables those options you no longer have access to rather than wi
ping them out entirely. This is also true of the zone when saved. Thus you can now more easily change a zone to be temporarily inactive for example and have your previous active settings restored in the future.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}FIX \endash A number of the constants used internally have been renamed to be more consistent. Hopefully nothing is broken!
otential vulnerability in zms by Mark Cox, all non-trivial string and buffer copies are now limited by the maximum size of the destination. Mark has also askedme to include the following notice relating to this, which I am very happy to do.
\cs16\ul\cf2\insrsid1732201 mark@awe.com}}}{\insrsid1732201 >.\~ The Common\line Vulnerabilities and Exposures project (cve.mitre.org) has assigned the\line name CAN-2004-0227 to this issue."
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 LANGUAGE \endash An additional Italian language translation has b
een added. One, by Davide Morelli, was included in 1.19.1 but not announced. However like buses another one has come along, from }{\insrsid1732201\charrsid1666119 Tolmino Muccitell}{\insrsid1732201
i, and so they are both now present. The original translation is accessible by selecting }{\i\insrsid1732201\charrsid1666119 it_it}{\insrsid1732201 as the language whereas the new one is }{\i\insrsid1732201 it_it2}{\insrsid1732201
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}}\pard \s27\qj \fi-357\li714\ri0\sa180\widctlpar\tx720\nooverflow\faroman\ls4\rin0\lin714\itap0\pararsid1732201 {\insrsid1732201 LANGUAGE
\endash A version of Argentinian Spanish by Fernando Diaz has also been included and is accessible by setting your language to }{\i\insrsid1732201 es_ar}{\insrsid1732201
. As with all the language translations I cannot vouch for the completeness or accuracy of the language files so feel free to feedback any updates you think should be made.
age files in this release do not contain any translations of the new, or modified, tokens which have been introduced in this release. All new or modified tokens are included in the language files in English. There will shortly be a point release which inc
ludes these language updates assuming I can get translations of them in a reasonable timescale.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Minor bugfixes and enhancements.
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Ffmpeg Configure Changes. The configure script has been modified to look for the ffmpeg libraries in their instal
led location rather than in a build directory. This is to avoid having to build the library when it might already be installed.
Pcre Configure Changes. The configure script has been modified to look for the pcre.h header file in both /usr/include and /usr/include/pcre rather than just the latter as previously.
Remote Image Parsing. Further improvements have been made to handle additional patterns of images with differing styles of terminations or none at all.
Event Image Numbering. An additional configuration option (ZM_EVENT_IMAGE_DIGITS) has been added to allow the user to define how many significant figures should be used to number individual event images.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Event Filters Bug. Fixed (again) a bug where several fields used in event filters did not generate valid database queries.
Zmu Device Authentication. Removed the previous requirement to pass in a username and password to zmu when just querying a device as this was slightly broken and was unnecessary anyway.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Some major enhancements and bugfixes.
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 MPEG video streaming. ZoneMinder now supports true video streaming if configured with the }{\i\insrsid1732201 \endash with-ffmpeg}{\insrsid1732201 option. This allows one
or both of live or event streaming to be in this format rather than motion JPEG style as before. Note however that is still somewhat experimental and may not work on your system. The reason for this is due to the variation in plugins and video movie form
a
ts. Currently I have got it working well with browsers on Windows platforms using the Windows Media Player plugin and the 'asf' video format. I have also managed to get event streaming working on Mozilla using mplayer (I think) though it jumps in and out
o
f it's place in the window a bit. I would appreciate any feedback or advice on formats and plugins that work on your system. Also note that video streaming tends to get buffered before being displayed. This can result in the 'live' view being several seco
Motion JPEG Capture. Previously image capture from network devices has been limited to single stills capture only. This has now changed and if you entered a remote camera path that returns the }{\i\insrsid1732201 multipart/x-mixed-replace}{
be parsed and images extracted from the stream. This is much faster than before and frame rates can be as fast now with network cameras as with capture cards and video. This feature also has the side-effect that one ZoneMinder installation can use another
NPH Streaming. After months of frustration I have finally figured out why streams were corrupted using Cambozola versions after 0.22. It turned out that apache was injecting characters into the streams which was screwing up the he
aders. I believe this to be because the initial header had no content-length header, as the length is indeterminate. So I have added a zero content length header which I believe fixes the problem though perhaps not in the best way. I have also made the in
s
tallation link the existing zms binary to nph-zms so that you can now use zms in non-parsed-header mode. If it detects it is in this mode then the content-length header is not output, though several other additional ones are. In nph mode the false charact
er injection seems to disappear so I suspect this is a better way to use zms.
Bulk Frame Records. With the recent advent of the 'Record' and 'Mocord' modes a lot of people have started using ZoneMinder as a pseudo-DVR. This meant that a lot of database acti
vity was taking place as each captured frame required its own entry in the database. The frames table has now been reorganised so that 'bulk' frames may be written at defined intervals to reduce this database activity. The records act as markers and indiv
idual frame timings are interpolated in between. Bulk frames are only used when no alarm or motion detection activity is taking place and normal frame records are kept otherwise.
Event List Ordering and Scrolling. It was previously the case that the \lquote Next\rquote and \lquote Prev\rquote
buttons on the event view did not always go to the event that was expected and sometimes disappeared altogether. This behaviour has now been modified and these buttons will now take you to the next and previous events in the list which the event
was selected from. Thus if the list was sorted on ascending scores then the \lquote next\rquote
event is the one below which has a higher score etc. A possibly counterintuitive side effect of this is that as the default list is sorted by descending time the \lquote next\rquote eve
nt is the one below in the list which will actually be earlier and the \lquote previous\rquote event is later. So long as you remember that next and prev refer to the order of the list you should be ok.
Zone Percentage Sizes. Zone motion detection parameters can be def
ined either in terms of total pixels or as a percentage. This percentage was defined relative to the size of the image as a whole. However this was difficult to calculate or estimate especially with several zones of varying sizes. In version 1.19.0 this h
as been changed so that the percentage relates to the size of the zone itself instead. This should make calculations somewhat easier. To convert your existing zones you can run zmupdate.pl with the \endash
z option, though this should be done only once and you should backup your database beforehand in case of error.
Console View System Display. The console display was slight revamped to indicate disk space usage (via the \lquote df\rquote command) on the events partition,
Zone Form Validation. Changes applied in version 1.18.0
to prevent invalidate entries in the zone definition form actually had the opposite effect due to JavaScript treating everything as a string and not a number (e.g. 5 is greater than 123). This is now corrected.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Default Rate and Scales. You can now specify
(in the options dialog) the default scale you would like to view live and event feeds at. You can also give a default rate for viewing event replays.
was possible for frames being sent from the analysis daemon to the frame server to exceed the defined maximum buffer size in which case the write would fail. It is now possible to define a larger size if necessary to prevent this. Note that you may have t
o adjust your system configuration to accommodate this. For further details check the help for the ZM_FRAME_SOCKET_SIZE option.
Filter Name Duplication. Following recent changes to the filters table, several people reported that when saving filters they act
ually got a duplicate. This resulted in several copies of filters all with the same name as the constraint on unique filter names was not present. Well it is now so when upgrading your database all the filters will be renamed from \lquote myfilter\rquote
to \lquote myfilter_<id>\rquote where \lquote <id>\rquote
is the id number in the database (which is then removed). In general the higher the id number the more recent the filter. So you should go through your filter list deleting old copies and then rename the last one back to it\rquote s original name.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Filter Image Attachments. A fix was made to zmfilter.pl to prevent it trying to attach\'e9 alarm images to non-alarm events.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Video Rate Specification. A fix was made to zmvideo.pl that corrected a problem with no default frame being used if none was passed in.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}RBG->BGR Black Screen. Fixed an issue with black screens being reported in RGB24 mode if RGB->BGR invert was not selected.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}A translation for the Dutch (nl_nl) language has been included.
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Filter Monitor Name Bug. A bug was present in the previous release where monitor names where not correctly handled in filters. This is now fixed.
Database Upgrade Change. Users upgrading from releases prior to 1.18.0 please note that now as part of the upgrade process all your filters will have any automatic actions unset. This is
because the previous affinity to a particular monitor has now been removed and you may be left with several filters all doing the same thing to all of the events or have filters which for instance delete events on only one monitor but which now would dele
te them for all of them. It is recommended that you review your list of saved filters and delete duplicates before adding any monitor specific terms and resetting the actions for any that remain.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Major optimisations, important new features and some bugfixes.
Optimisations and Performance Improvements. This release contains several major performance improvements in various areas. The first of these is that image processing for YUV style input formats are now pretty much handled at almost the sa
me speed as native RGB formats. As this is what the capture daemons spend most of their time doing, the improvement helps reduce the amount of CPU time by a significant degree. Application of these changes also highlighted a bug that had existed previousl
y
in YUV conversion which caused incorrect conversions for certain values. The other two main areas of optimisation are in the Blend and Delta image functions. Normally when doing motion detection the analysis daemons spend about 99% of their time comparin
a captured image with the reference image and then blending the two ready for the next capture. Both of these functions have been significantly improved. In previous versions there were two options for calculating image deltas (or differences), a simple
R
GB average and a Y channel calculation. Historically the RGB one was faster however with the optimisations the Y channel calculation (which is more accurate) is now 15-20% faster and so has become the default though you can select either method by the ZM_
Y
_IMAGE_DELTAS configuration option. A new method of image blending has also been added which is up to 6 times faster than the old one which is retained for compatibility and because in some unusual circumstances it may still be more accurate (see the ZM_F
AST_IMAGE_BLENDS option for details). Altogether these optimisations (along with other common sense ones such as not maintaining a reference image in \lquote Record\rquote
mode where it is not used) significantly reduce the CPU load for most systems, especially when ala
rms are not in progress. If an alarm is detected then a lot of file system and database activity takes place which is limited by the speed of these resources so the gain will not be as much.
Remote Authentication. This document has previously indicated tha
t basic authentication for network cameras could be used by entering a hostname of the form of <user>:<pass>@<hostname>. This was not actually the case as the relevant authentication header was never sent. This is now fixed and addresses of this form can
Monitor Independent Filters. Previously filters were closely tied to a monitor and a new filter had to be created for ea
ch monitor. This has now changed and filters can now specify an associated monitor in the same was as other parameters. Links have now been added to the main console view to allow you to view lists of events from all monitors in one and saved filters can
n
ow affected as many or as few monitors as you wish. IMPORTANT: Please note that as part of the upgrade process all your filters will have any automatic actions unset. This is because the previous affinity to a particular monitor has now been removed and y
o
u may be left with several filters all doing the same thing to all of the events or have filters which for instance delete events on only one monitor but which now would delete them for all of them. It is recommended that you review your list of saved fil
ters and delete duplicates before adding any monitor specific terms and resetting the actions for any that remain.
New Filter Operators. Two new filter operators and their inverse have been added. You can now indicate whether a value is in a set of other values, for example \lquote cat\rquote is in the set of \lquote cat, dog, cow, horse\rquote
. You can also use regular expressions so \lquote cat\rquote matches \lquote ^c.*\rquote . The \lquote not in set\rquote and \lquote not matches\rquote operators are also available.
Additional Scales. Enhancements to the scaling algorithm mean that non binary scales are now just as easy to apply, thus new scales such as 0.75x have been added. Others can be easily included if necessary.
Montage Sizing. The montage view allows you to view all of your active cameras in one window. However if your cam
eras are different sizes then this becomes very untidy. You can now constrain the image size of each monitor in this view to a fixed size with the ZM_WEB_MONTAGE_WIDTH and ZM_WEB_MONTAGE_HEIGHT configuration options. Monitor images will be enlarged or red
Compact Montage. The traditional montage view includes individual small menus for each monitor and a status display. This results in a somewhat cluttered display and the refreshing of the status displays may generate more accesses than de
sirable. Using the ZM_WEB_COMPACT_MONTAGE configuration option allows this montage view to only include the monitor streams and one overall menu bar with no status displays.
Monitor Name Constraint. The name given to a monitor is used in file paths and sev
eral other areas. Thus it is important that it follows certain conventions but up until this release these names were unrestricted. The monitor form now limits monitor names to alphanumeric characters plus hyphen and underscore.
ally ZoneMinder has time-stamped each image as it is captured. This ensures that all images have their capture time recorded immediately. However there are several side-effects which may be undesirable. Firstly the time and resource is spent time-stamping
images that are not recorded and which are discarded, secondly the timestamp is included in any motion detection and may potentially trigger an alarm if detection parameters are very sensitive. The third effect is that as the timestamp is added to the ima
ge at it\rquote
s native resolution, if the image is scaled then the timestamp is scaled also. This may not be a problem for enlargement but if the image size is reduced then it may become illegible. This version now allows you, via the ZM_TIMESTAMP_ON_CAPTURE con
figuration option, to indicate whether the timestamps should be added on capture, as before, or only added when the image is viewed or recorded. Setting it to this later value allows timestamps to be added to scaled images. This is little performance impa
Scaleable Stills View. The stills view of a monitor (when streaming is not available or desired) is now scaleable in the same way as the streamed view.
Double Buffered Stills View. The stills view has now been restructured to allow a double b
uffering approach. Thus a new image is loaded in the background and only written to screen when complete. This removes the refresh flicker that means that the screen blanks periodically however uses more JavaScript so may not be suitable for all platforms
. Whether ZoneMinder uses double buffering or not is controlled by the ZM_WEB_DOUBLE_BUFFER configuration option.
Fixed Length Event Bug. A bug was reported whereby the fixed length events that could be specified for use in Record or Mocord mode could somet
imes result in events a multiple of that length. So events that were meant to be 15 minutes long could sometimes be 30 or even 45 minutes. This was especially the case with monitors that had low frame rates. This is now fixed.
Pending Process Bug. A bug was found whereby a process that was scheduled to be started in the future (due to repeated failures) would drop out of the pending queue if a further explicit restart was attempted. This is now fixed.
Strsignal Function. The strsignal function was included from version 1.17.1 however this is not ubiquitous on all distributions. The existence of this function is now tested for by the configure script and it is not used if not present.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}}\pard \s27\qj \fi-357\li714\ri0\sa180\widctlpar\tx720\nooverflow\faroman\ls4\rin0\lin714\itap0\pararsid1732201 {\insrsid1732201 Add Max
Alarm Threshold. Previously the alarm threshold (which is the amount a pixel has to differ from it\rquote s counterpart in the reference image) existed only in a \lquote minimum\rquote
form meaning pixels that were more different matched. A maximum has now been added to assis
t in screening out large changes in brightness. In addition to this a number of new consistency checks have been added to the zone definition form to try and prevent bogus or invalid settings.
Diagnostic Zone Images. A regularly requested feature is that o
f adding extra information to allow diagnostics of the process of image detection. This has previously been somewhat hit and miss but in this version a new configuration option ZM_RECORD_DIAG_IMAGES has been included to allow this. This option will genera
t
e several images for each captured frame in an alarm including each reference image and a series of images containing the image differences at various stages in the process. It is not possible to record these for the image prior to an alarm but those foll
owing it are included and should assist in tuning the zones to provide optimal motion detection.
Event Images Renamed. The capture and analysis images recorded during an event have been renamed from capture-???.jpg to ???-capture, and from analyse-???.jpg t
o ???-analyse.jpg. This is to allow all images (including diagnostic ones) to be associated with the frame sequence number more easily. This means that old events will no longer be able to be viewed as the wrong image will be being searched for. To avoid
this you can use the new \lquote zmupdate.pl\rquote utility to rename all your old images by doing \lquote perl zmupdate.pl \endash r\rquote as an appropriately privileged or root user.
Version checking. ZoneMinder will now optionally check for new versions of itself at zoneminder.com. Thi
s is done with a simple http get and no personal information otherwise than your current version of ZoneMinder is transmitted or recorded. If new versions are found you may be alerted of them via the web interface. This is an initial step towards enhancin
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Force Java. Previously ZoneMinder could be forced to override it\rquote
s detection of browser capabilities to prevent the Cambozola Java applet being used. However sometimes the opposite effect was desired and using the apple
t was preferred to native image handling. This has now been made possible by making the ZM_CAN_STREAM option tri-state allowing \lquote auto\rquote , \lquote yes\rquote or \lquote no\rquote to be used to provide all alternatives.
Alarms Cleared on Exit. In previous versions if an alarm was prese
nt when the analysis daemon (zma) exited the alarm would remain flagged. This had little effect except if the monitor was being watched however it was a bit annoying so any alarm flag is now cleared when this daemon exits.
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Login Bug. A bug was identified whereby an unauthorised user could gain access to the console view of ZoneMinder. This was the only view
available and no access to any camera views or configuration was possible. This bug is now fixed.
New Languages. Two new language files were added. These allow ZoneMinder to use the German (de_de) and Polish (pl_pl) languages.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Language File Format. The fo
rmat of the language file was changed to allow the specification of character set and locale as well as have more flexibility in the calculation of plural forms.
Option Language. The prompts and help text for the options is now also available for translati
on. A guide is included in the language file to allow this if necessary. Currently language translations exclude the options settings as this is a rarely accessed area and contains a great deal of text. The new format allows individual options to be trans
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Language changes and other enhancements.
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Version Numbering. ZoneMinder version numbers have now changed. This is to allow more frequent \lquote point\rquote releases which are expected to happen for instance when
ever new language files are included. Previously all releases had the same version increment so it was difficult to tell the significance of any particular release. Now the version number is in the }{\i\insrsid1732201 x.y.z}{\insrsid1732201
format where a change in }{\i\insrsid1732201 x}{\insrsid1732201 signifies a major fundamental or architectural rework, a change in }{\i\insrsid1732201 y}{\insrsid1732201
will indicate a new release containing incremental feature changes or fixes recommend to all users and a change in }{\i\insrsid1732201 z }{\insrsid1732201 will generally mean minor non-functional or critical modifications which would not be recommend
ed as important to all users. As ZoneMinder has been referred to by the point release up until now, e.g. .15, .16 etc the next number in that sequence has been retained for continuity and to avoid having any ambiguity in version numbers.
Language Support. ZoneMinder now allows specification of system and user specific languages other than UK English. These languages are given in language files named zm_lang_}{\i\insrsid1732201 nn_mm}{\insrsid1732201
.php which can be created from the default zm_lang_en_gb.php file. If your language is not included then please consider doing a translation by checking this file and submitting your changes back for inclusion in future releases.
Syntactic Improvements. Previously setting \lquote NOTICE\rquote errors on in PHP would flag tens or hundreds of violations in the Zone
Minder web files. Whilst not strictly errors this represented sloppy coding and sometimes covered up genuine bugs. All the files have been revisited and revised to ensure that a many of these problems as possible have been eliminated and only the very few
where the fix would be significantly less optimal than the problem remain.
Stream Scaling Resizing. Previously when watching a stream and modifying the scale of the streamed feed only the actual feed would change size and the containing frames and windows
would remain the same. This was fine for changes to smaller scales but problematic for larger scales. This has been changed for that the window and frames will now resize appropriately.
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Run States. Instead of the old \lquote start/stop\rquote links the
current system state is now a link which takes you to a dialog which allows you to start, restart or stop the system. You can also save the current run state which basically takes a snapshot of the current monitor functions and saves that. You can then r
eselect that state later which basically involves resetting the monitors to have these saved functions and then doing a system restart.
New Monitor Functions. Instead of Passive, Active, and X10, the modes are now Monitor (= old Passive) which just allows y
ou to watch the feed, Modect (= old Active) which is MOtion DetECT and which will capture events as previously, Record which continuously records with no analysis and MoCord which is a hybrid of Modect and Record and which will continuously record but als
o
do motion detection and highlight where this has occurred. The Record and Mocord functions both records events whose length in seconds is defined by the 'Section Length' monitor attribute. You can additionally specify a 'Frame Skip' value to tell it to n
X10 Function removed. The X10 mode has been removed and replaced by an indication of whether the monitor is 'continuous' or 'triggered'. This basically just indicates whether it may be controlled outside of
zmdc and zmpkg. Additionally the X10 triggers may now be specified in an X10 section. This has changed to allow for other types of triggers to be added more easily.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Paginated Event listings. The event listings are paginated by default. You can list all of
the events if you like by choosing the appropriate option. There are shortcuts to pages of events at the top of the listing. If these produce strange looking sequences like 1,2, 3, 5, 9, 17, 37 etc this is deliberate and uses an exponential algorithm inte
nded to allow you to quickly navigate through the list to a particular page in the minimum number of clicks.
Variable Frame Rates. Event streams can now be viewed at various rates allowing faster review (if your bandwidth allows) to long events, or slower for more precision.
Scaleable/Variable MPEG generation. Generation of MPEG videos now also allows you to specify the scale relative to the original image and also the frame rate. Again, for long events captured in the perpetua
l recording modes this will allow a faster review of the period the event covers.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Additional stream headers. The stream headers have been changed to hopefully ensure that they are less likely to be cached.
Intelligent Module inclusion. zmfilter.pl now includes Archive::Zip and other modules on an as needed basis so won't complain about them being missing unless they have been explicitly configured to be used.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}SQL Buffer size. Increased SQL buffer size to cope with large pre-event buffers, plus a couple of other buffers have been enlarged.
Incorrect Frame time offsets. The time offsets in alarmed frames were incorrect and based on the time of storage rather than capture. This gave the impression that there was a delay after the first alarmed frame and messed up some streaming timings. Thi
Refined shared memory handling. Fixed zmfilter, zmwatch and zmx10 to allow zero as a valid shared memory id to allow them to keep on working if the segment has been marked for deletion
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Improved time based filters. Filters that include time based clauses now get executed regardless of whether new events are being generated.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Filtering more active. zmfilter is now started in 'Monitor' mode. It does not run in when monitors are completely off however.
Archive images optional. Normally when an alarm is detected a set of raw images is saved along with a mirror set of images containing motion highlighting. This second set can now optionally be disabled.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}zms parameter bug fixed. The streaming server incorrectly parsed and assigned one of it\rquote s arguments. This is now fixed.
\par {\listtext\pard\plain\s27 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}zmu brighness bug. Previously camera brightness was not correctly parsed from command line options passed to zmu.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Various bug fixes from the last release and before.
Bandwidth. A bug was introduced in .14 which caused a corrupted console display and manic refreshes on new installations. This was due to a missing bandwidth setting when no existing cookie was detected. This is now fixed.
Again in .14 a problem occurred for a new release whereby zmconfig wanted to know the database details and but also previously wanted
to access the database before it had asked the questions. This has now been addressed though it does require that zmconfig is run twice initially, once to created the scripts and once to import the configuration into the database.
In association with the previous error, the zm_config_defines.h file was not created in the absence of the database as this was what was used to assign configuration ids. This now takes place regardless of the database.
A bug in zmfilter was pointed out whereby the dynamic loading of the Zip or Tar archive modules depending on a preference actually wasn\rquote t. It was looking for both and loading both at compile time. This has now been modified to be fully runtime.
The database user definitions in the zmvideo script indicated one database user while the database connection used a different one. This prevented any videos being generated.
the zmf frame server and greyscale images. The option to colourise JPEG images is intended to be used to ensure that all JPEG files are written with a 24 bit colourspace as certain tools such as ffmpeg require this. However in the circumstances described
above images written by zma directly were colourised whereas those written by zmf weren\rquote t. A change has been made whereby if set all greyscale JPEG images are colourised in all circumstances.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Major new feature and important bug-fixes.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}}\pard \s15\qj \fi-360\li720\ri0\sa180\widctlpar\tx720\nooverflow\faroman\ls4\rin0\lin720\itap0\pararsid1732201 {\insrsid1732201 Web co
nfiguration. Following many requests and to make ZoneMinder easier to administer the configuration system has been changed slightly. You should now still run zmconfig.pl to specify an initial configuration but you now only need to answer the first few que
s
tions to give a core set of options including the database options. The remainder of configuration options can then be ignored to start with and all but the core options will be written to the database. You can then view and modify these options from the
web interface and apply then without recompilation, which is now only necessary if you change the core configuration.
detection problem was present if fast RGB images deltas (ZM_FAST_RGB_DIFFS) was off. This was an overflow error in the calculation of the Y channel and caused excessive image differences to be calculated. This has now been fixed.
The use of the Term::Readkey perl module in zmaudit.pl has been removed. This module had been removed from zmconfig.pl previously but had lingered in this script.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}A bug was found in zmx10.pl causing a crash if time delayed X10 events were used. This has now been fixed.
binary from zmwatch.pl and zmx10.pl. Previously these scripts had used zmu to determine last image time and alarm state information. The use of this script was a bit overkill and the introduction of user permissions complicated matter slightly so
these scripts now access the shared memory directly.
Shared memory permissions. Following introduction of a user permissions system the previous 777 mode for shared memory was deemed insecure. Consequently from now on shared memory is only accessible from
the owner. This means that zmu will only work when run as root or the web user unless you set it setuid where it should still be secure as it will require authentication.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Beta version of several features and fixes, never generally released.
Changed some of the core video calls to be V4L2 compatible. This primarily involved opening the video devices and memory maps as read/write and not just read-only.
Shared memory has now been rationalised to prevent some common problems. Remember to shutdown the whole ZM package before installing, from this version on it will remove all old shared memory segments.
Fixed not numeric comparison in zmwatch which was causing, or appeared to be causing, some errors.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Fixed zone image map bug for percentage zones. When you had defined a zone in percentag
e terms, the image map used to select it for editing was broken. This is now fixed.
New contrast/brightness etc adjustments feature. This accessible from the Settings link on the monitor window. It's fairly basic at present but should work for most types o
f cameras. If you have any device or driver specific auto-brightness, auto-contrast etc enabled the changes you make may appear to work but may be overridden by the auto feature immediately so check for that if your changes do not appear to be having an e
ffect. Also if you have a number of cameras being multiplexed onto one device then any changes here will probably affect all your cameras.
Added user and access control. If enabled in config (ZM_OPT_USE_AUTH) then y
ou will need to define and login as ZM users. There will be one users already defined, with username 'admin' and password 'admin'. This user is defined will full permissions and clicking on the 'Options' link from the main console window will allow you to
modify and create users with various permission sets which hopefully will satisfy most requirements. These users (except any defined with 'system' edit capability) can be restricted to certain cameras by adding the monitor ids as a comma-separated list (n
o spaces) to the appropriate field. Users limited to specific monitors may not create or delete monitors even if defined with monitor edit permissions.
Some windows now (optionally) use a JavaScript timeout to refresh themselves rather than a refresh header
. Since refresh headers were interrupted if a link of the page was linked there were previously various forced refreshes from child windows to restart the refresh process. By using JS refresh timers which are not interrupted these extraneous refreshes hav
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Mostly bug-fixes with a couple of minor features.
Double first images. Fixed a problem where the first image of an event was being recorded twice. I don\rquote t think this was at the cost of any of the other images but one copy was an extra.
Made zmdc connect more intelligent. On the suggestion of a couple of people I have made the zmdc.pl server spawning and waiting a bit more intelligent. Rather than waiting a fixed (short) amount of time, it now polls every second for a
while, stopping if the connection is made. Thanks to Todd McAnally for the initial suggestion.
Added image view to events lists. Again a partial implementation of a suggested feature. If you click on the score column you will now get a snapshot of the even
t frame with the highest score. This is to enable you to quickly see what the event was about without having to watch the stream or view all the static images.
Make delta times variable precision. A couple of problems had been reported where long events go
t negative durations. This was due to an overflow in a time difference routine. This had been operating on fixed precision allowing high precision for short deltas. This routine has been changed to allow variable precision and events will now have to be s
Fixed round detection problem. Although the existence or otherwise of the \lquote round\rquote function is correctly detected, the appropriate header file with the results of this test was not included which was not helpful. This has been corrected.
OPT_MPEG bug. A bug was reported (by Fernando Diaz) where the results of the ZM_OPT_MPEG configuration variable was not correctly imported into the scripts. This now happens as intended.
Fixed zmvideo.pl event length bug. The zmvideo.pl script which is used to generate video MPEG files tries to calculate the correct frame rate based on the length of the even
t and the number of frames it contains. Previously it did not take account of the pre and post event frames and so passed a much shorter value to the mpeg encoder than it should. This will only have affected short events encoded with ffmpeg but will have
resulted in much faster frame rates than necessary. This has now been corrected to take the whole event length into account.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Orientation. Added option to rotate or invert captured images for cameras mounted at unusual angles.
Fixed filter bug. A bug in the zmfilter.pl script was detected and reported by Ernst Lehmann. This bug basically meant that events were not checked as often as they should
have been and many may have been left out for filters that had no time component. The script has now been updated to reflect Ernst\rquote s suggested changes.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Stylesheet change. Previously the stylesheet didn\rquote t really work very well on Mozilla, Netscape and brows
ers other than IE. This turned out to be because I was using HTML style comments in there instead of C style ones. This has now been corrected so you should see the correct styles.
Zmconfig.pl ReadKey. Thanks to a ridiculously sensible suggestion from Car
lton Thomas this module has been removed from zmconfig.pl. Originally Term::ReadKey was in there for funky single character unbuffered input but that has long since disappeared so just regular perl input methods are used now. This removes one of the most
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Detect linmysqlclient.a. Added better detection script into \lquote configure\rquote top spot when libmysqlclient.a is missing.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Various new features and fixes.
Added stats view \endash If you have the RECORD_EVENT_STATS directive set and are viewing a still image from an event you can now view the statistics recorded for that frame. This tel
ls you why that frame triggered or participated in an alarm. This can be useful in tuning the various motion detection parameters and seeing why events occurred.
As well as the existing greyscale and 24 bit RGB palettes, you can now choose YUV420P and RGB565. Rewrote the palette/colours area a bit to enable support for other palettes in the future if requested. Bear in mind though that YUV palettes are
converted into RGB internally so if you have the choice RGB24 may be faster as it's the 'native' format used within.
Added preclusive zones \endash Added a new zone type, the preclusive zone. For full details see the relevant section above but in brief this is a zone type that if alarmed will actually prevent an alarm. This completes the pantheon of zone types I think.
Fixed Mozilla JavaScript \endash Various JavaScript functionality did not function on Mozilla, Netscape and other browsers. This is now (hopefully) fixed.
Allow image and mpegs to be attached to emails \endash
Added new tokens (%EI1%, %EIM% and %EV%) to the filter emails. This allows the first alarm image, most highly scored alarm image and an alarm MPEG to be attached to alarm notification emails. Use %EV% especially with care!
Fixed possible motion detection bug \endash I found a few double declared local variables left over from the rewrite. This may have affected the motion detection algorithm. Fixed now anyway.
Modified scoring \endash Alarm scoring has been modified to give more granularity for smaller events. This will have the effect of raising the scores for small events while large ones will still be about the same.
Fixed /cgi-bin path problem \endash Previously you could specify the real path to you cgi-bin directory if you have one but not the web path. You can now do both.
Improved video handling in browser \endash The MPEG/video area of the web GUI had been a bit neglected and looked somewhat ugly. This has now been improved to a degree and looks a bit nicer.
Historically ZoneMinder has only supported the Berkeley mpeg encoder which was slow and rather limited. ZoneMinder now supports the ffmpeg encoder as well which is much much faster and makes generation of MPEG videos at realistic frame rates more
of a reality. As ffmpeg has so many options and everyone will probably want a different emphasis you can now also specify additional ffmpeg options via zmconfig.pl.
Colourise greyscale image files \endash In past versions, captured greyscale images were stored
as JPEG files with a corresponding greyscale colourspace. This saved a small amount of space but meant that mpeg_encode had to do a conversion to encode them, and ffmpeg just fell in a heap. Now you can optionally opt to have greyscale images saved as ful
l 24 bit colourspace images (they still look the same) at the price of a small penalty in CPU and disk but allowing you to easily and quickly create MPEG files. This option is one by default but can be switched off if you do not require any MPEG encoding.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}}\pard \s15\qj \fi-360\li720\ri0\sa180\widctlpar\tx720\nooverflow\faroman\ls5\rin0\lin720\itap0\pararsid1732201 {\insrsid1732201 F
ast RGB diffs \endash
Previously ZoneMinder used quite a loose method for calculating the differences between two colour images. This was basically averaging the differences between each of the RGB components to get an overall difference. This is still the defau
lt but by setting ZM_FAST_RGB_DIFFS to 'no' you can now make it calculate the Y (or brightness value) of the pixels and use the difference between those instead. This will be more accurate and responsive to changes but is may be slower especially on old m
a
chines. There is a slight double whammy here if you have a YUV palette for capture and set this option off as the image will be converted to RGB and then partially converted back to get the Y value. This is currently very inefficient and needs to be optim
Fixed STRICT_VIDEO_CONFIG \endash Previously this actually behaved the opposite of what it was supposed to, ie. if you wanted it strict it wasn't and vice versa. Thanks to Dan Merillat for pointing this one out.
Web colour change \endash I thought the old red, green and amber text colours were just a bit too gaudy so I've toned them down a bit. Hope you like them!
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Many bug-fixes and major feature enhancements.
\lquote round\rquote bug - Fixed a problem with the configure script that didn't detect if the 'round' function was already declared before try to do it itself.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Low event id bug - Fixed bug where events with an id of < 1000 were being cleaned up by zmaudit.pl by mistake.
Source file restructuring - The source files have been broken up and renamed
extensively to support the first stage of the code being straightened out. Likewise the class structure has been rationalised somewhat. The php file names have also changed in some cases so it might be best to delete all your php and css files from the z
one minder install directory first as the old ones won't be overwritten and will be left behind.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}}\pard \s15\qj \fi-360\li720\ri0\sa180\widctlpar\tx720\nooverflow\faroman\ls6\rin0\lin720\itap0\pararsid1732201 {\insrsid1732201 New
\lquote montage\rquote view - Added a montage view showing all your cameras simultaneously either streaming or stills. The width of this window (in terms of number of monitors) is a configuration option.
Network camera support - A major change in this version is support for remote or
network cameras. This is currently implemented as series of http grabs of stills rather than being able to break up motion jpeg streams. However frame rates of from 2-10 should be achievable depending on your network proximity to the cameras.
Option BGR->RGB swap - Added the option to switch on or off the inversion of RGB to BGR for local cameras. It is on by default to maintain compatibility with previous releases.
zmu suspend alarm option - Added new -n option to zmu to effectively suspend alarm detectio
n for a monitor. This is intended for short term use and to support PTZ cameras where alarm detection is desired to be suspended while the camera changes orientation or zoom level.
FPS limiting - Added a new option to monitors to add a maximum capture rate
. This allows you to limit the amount of hits a network camera gets or to reduce the system load with many cameras. It also works with multi-port cards and limiting the capture rate on one camera allows the spare FPS to be allocated to other devices. For
i
nstance with two cameras and no throttle, I get about 4FPS each. Throttling one to 2FPS allows the other to operate at 6FPS so you can allocate your capture resources accordingly. This limiting can be disabled while alarms are occurring as a global option
Alarm reference update - Added option to not blend alarmed images into the reference image. See the help in zmconfig.pl for caveats.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Disappearing monitors - Fixed the disappearing monitor problem in the console view where monitors with no e
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Clean and tidy - Cleaned up a load of compiler warnings and miscellanea to ensure a cleaner happier build.
Streamed image headers - Made all headers in streamed images have full CRLF termination which will hopefully now prevent the problems with broken streams that had existed mostly with Mozilla (and hopefully won't break anything else).
Event navigation - Added next, prev, delete & next, delete & prev navigation to events to allow you to quickly review events in sequence as had been requested by a number of people.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}USR blocking \endash The debug USR signals were not being blocked properly leading to nasty effects in zmc mostly.
Previously zmfilter execution was not synchronised with the monitor state or the analysis daemon leading to it sometimes being run unnecessarily. From now on the zmfilter process will only run when a monitor is active and so actually potentia
zmdc short statuses \endash Removed the logging of the short status values that zmdc.pl returns to it\rquote s clients which had been clogging up the log file.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Bugs and pieces - Fixed various bug(ettes) that I came across that that I don't think had been reported or noticed so I don\rquote
Added zmu -q/--query option - There is now a new query option for zmu. When combined with -d it gives the co
nfig of the device and when used with -m it dumps the current settings for the monitor and zones. Mostly useful for bug reporting. The previous version of zmu used with just -d gave this information for a video device by default. This now requires the -q
option also to bring into line with it's -m equivalent.
Can now retag PHP files if necessary - Version 0.9.8 was the first version to use short_open_tags in the PHP files. This caused grief to some people so this script will put them back to the long verion.
Frame and event lengths fractional - A new field has been added to the Frames table. This is 'Delta' and is a fractional number of sec
onds relative to the event start time. This is intended to support the real-time playback of events rather than just 'as fast as possible' or with a configured delay as at present. The event length is now also fractional.
Changed colour depth to bits - Having colour depths expressed in bytes has caused no end of problems. This is now changed to be bits and can be changed via a dropdown to limit what can be entered. Don't forget to run the zmalter script to update your DB.
Renamed terminate to zm_terminate - The use of 'terminate' in zmc.cpp caused a conflict on some systems so renamed it to something more specific.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Zone deletion problem -
A problem was found such that when deleting zones the appropriate daemons were not being asked to restart daemons correctly.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Console changes - The current version number is now displayed in the console. A refresh button has also been added along with a mi
Added delete button enable to checkAll - Using the 'Check All' button in the main monitor window previously did not enable the delete button. This is now fixed.
Reload on click - In previous versions the console window would reload if a monitor
window for example was clicked. Thsi was removed in the last version which meant that sometimes the console never go refreshed as it's timing loop was broken. This functionality has now been reinstated.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Several new features and bug-fixes
ade note - If you have installed 0.9.7 and wish to save your configuration then copy your existing zmconfig.txt file over to your 0.9.8 directory and before running zmconfig.pl.
Added multiple options to zmu - You can now give multiple options to zmu and get all the responses at once. However this is currently in a deterministic order and not related to the order you give them.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Added -v/--verbose option to zmu - Zmu has been made more human friendly though it still remains primarily for daemon use. Giving t
he -v or --verbose option prints out a bit more as a response to each command.
Add -d/--device to zmu - This option is designed to allow you to get your video device working with another application such as xawtv and then use zmu -d to print out the settings it\rquote s using
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}(especially with the -v option). These options can then be used as a starting point for your ZoneMinder configuration.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Added FPS in status field - The status field in the web monitor views now contains an FPS setting as well as the status.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Zmconfig changes - zmconfig handles missing options better and rewrites config file even in non-interactive mode.
Zmwatch now works on image delay and not fps - Previously the zmwatch daemon detected capture daemon failure by trying to use the FPS setting. This was imprecise and prone to false readings. It now uses the time delay since the last captured image.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Added zmpkg.pl and zm scripts - There are now two new scripts
. zmpkg.pl is in charge of starting and stopping ZoneMinder as a whole package and zm is designed to be (optionally) installed into your init.d directory to use ZoneMinder as a service.
Added email and messaging to filters - Filters now allow you to send emails or messages (basically just short emails intended for mobile devices) on alarms. The format and possible content for these emails is in zmconfig_eml.txt and zmconfig_msg.txt.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Made zmdc more aggresive in killing old p
rocesses - The zmdc.pl daeamon will now kill any ZoneMinder processes it finds on startup or shutdown to prevent orphans from being left around.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Configuration changes - Previously there were a lot of files generated by configure. Now only zmconfig.pl is ge
nerated this way and all the other configuration files are created by zmconfig.pl (from .z files) to centralise configuration more.
Fixed cambolzola opt bug - There was a bug in the Cambozola options, I can't remember what it was but it's fixed!
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Retaint ar
guments in zmdc.pl - In some installations zmdc was complaining about tainted arguments from the socket. These are now detainted prior to sending and after receiving.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Forced alarms - You can now force alarms when looking at the monitor window should anythi
ng catch your attention. You have to remember to switch them off as well though.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Looser video configuration - Some video configuration errors can now be ignored via the STRICT_VIDEO_CONFIG option.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Monitor window refresh on alarm - When the monitor window i
s active and an alarm has occurred the most recent alarms list is immediately refreshed to show it.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Revamped to work better with configure scripts
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Added a number of new scripts, see the scripts directory
Added Fast delete to PHP files. This allows the web interface to only delete the event entries themselves for speed and then have the zmaudit script periodically tidy up the rest.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Added event filter to enable bulk viewing, upload or deletion of events according to various attributes. Filter can be saved and edited.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Changed zmu -i option to write to monitor named image file.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Now stores DB times as localtime rather than UTC avoiding daylight saving related bugs.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Fixed bug with inactive zones and added more debug.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Changed main functions to return int.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Added help and usage to zmu.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Fixed browser acceptance problem, more easily defaults to HTML.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Split out the PHP files into a bunch with specific functions rather than one monolithic one.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Fixed NetPBM paths and changed _SERVER to HTTP_SERVER_VARS.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Added HUP signal on zone deletion.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Added NETPBM_DIR and conditional netpbm stuff.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Added conditional sound to alarm on web interface.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}Some of the web views have changed slightly to accommodate the separate events view.
\par {\listtext\pard\plain\s15 \f2\fs20\lang2057\langfe1033\langfenp1033\insrsid1732201 \hich\af2\dbch\af0\loch\f2 o\tab}And much much more, probably...
Seeing as ZoneMinder is so young and has kind of evolved rather than being planned there are a bunch of improvements and enhancements still to do, here is just a sample.
Perhaps split out devices - I think devices should probably be a separate table and class from monitors. Not critical but would represent a better model.
Comments - Needs many more, but that's just me I'm hopeless at commenting things out. I'll get round to it soon though honest! You're lucky to even get this document.
Optimised zones - The zones could do with being sorted out a bit to optimise the processing of overlapping ones, at the moment you can waste resource unless your zones are kept very tidy.
Create zones using server side image maps - This would make it easier to precisely define and see where your zone is going to go. Not critical but handy but a bugger to do.
Zone Definitions - Allow zones to be defined according to a colour coded bitmap or as polygons. Currently all zones are rectangula
r this would add a bit of flexibility. Would need a bit of a rewrite though. This will incur a slight penalty on startup and a very slight one on processing for all reasonably shaped zones.}{\insrsid12454246 Work has already begun on this feature.}{
Automatic device configuration - Video 4 Linux supports various device queries, it should be possible to get most of the device capability information from the device itself. The zmu utility does this now but it's not yet integrated into the web pages.
Extend the API. Well ok it's not really got an API yet but the image data is held in shared memory in a very simple format. In theory you could use the capture dae
mon to gab the images and other things could read them from memory or the analysis daemon could read images from elsewhere. Either way this should be done through an API, and would need a library I think. Also the zmu utility could probably do a whole lot
more to enable other things to manage when the daemons become active etc.
Allow ZoneMinder to 'train' itself by allowing the user to select events that are considered important and to discard those that should be ignored. ZoneMinder will interpolate, add a
bit of magic, and recommend settings that will support this selection automatically thereafter. The hooks for this are already in to some extent.
Add sound support to allow a captured audio channel to be associated with a video device. }{\insrsid12454246 Work on this feature has already begun.}{\insrsid1732201
When opening a link to an event etc from a notification email the window that is opened is just a regular browser window and not in the context of a proper ZoneMinder web interface. Thus it comes up too big usually (not a major is
sue) and also things like 'Delete' don't work as it wants to do things to its parent (which is more of a major issue).
The .sock files used by the *nix sockets I suspect may have the odd permission issue now and again. I think everything recovers from it but it needs checking out.
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 {\insrsid1732201 Probably bucket loads more, just fire them at me.
\f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 Yes, those are tabs in the indents; I like tabs so don't go changing them to spaces please. Also, yes I like my opening braces on their own line most of the time, what's
\par }\pard \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 {\insrsid1732201 Everything else that isn't definitely broken is probably deliberate, or was once anyway.
\par }\pard\plain \s15\qj \li0\ri0\sa180\widctlpar\nooverflow\faroman\rin0\lin0\itap0\pararsid1732201 \f1\fs20\lang2057\langfe1033\cgrid\langnp2057\langfenp1033 {\insrsid1732201 ZoneMinder is released under the GPL, see below.
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
\par This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
