ZaneYork
/
zoneminder
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated with further fix. 

git-svn-id: http://svn.zoneminder.com/svn/zm/trunk@1488 e3e1d417-86f3-4887-817a-d78f3d33393f
This commit is contained in:
stan 2005-07-14 09:04:15 +00:00
parent 5197eaee55
commit 0380f76a14
4 changed files with 1224 additions and 1216 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
README
View File

@ -1,4 +1,4 @@
12/07/05 ZoneMinder 1.21.3 README 1
14/07/05 ZoneMinder 1.21.3 README 2
@ -83,9 +83,9 @@
12.8. Release 1.19.4
41
12.9. Release 1.19.3
41
12.10. Release 1.19.2
42
12.10. Release 1.19.2
43
12.11. Release 1.19.1
44
12.12. Release 1.19.0
@ -103,7 +103,7 @@
12.18. Release 0.9.16
50
12.19. Release 0.9.15
51
52
12.20. Release 0.9.14
52
12.21. Release 0.9.13
@ -111,25 +111,25 @@
12.22. Release 0.9.12
53
12.23. Release 0.9.11
54
55
12.24. Release 0.9.10
56
12.25. Release 0.9.9
57
12.26. Release 0.9.8
57
58
12.27. Release 0.9.7
59
12.28. Release 0.0.1
59
60
13. To Do 60
13. To Do 61
14. Bugs 61
14. Bugs 62
15. Non-Bugs 62
15. Non-Bugs 63
16. License 63
16. License 64
Introduction
Welcome to ZoneMinder, the all-in-one Linux GPL'd security
@ -2588,6 +2588,9 @@ o FIX - The bogus deletion of events by zmaudit has finally
been completely fixed.
o FIX - Fixed a problem where Axis PTZ controls sometimes
caused the camera to move in an incorrect direction.
o FIX - Fixed an issue where the 'goto preset' command did
not pass the appropriate preset number (and so defaulted to 1)
for the Axis, Panasonic and VISCA protocols.
o FIX - A problem existed where renaming monitors did not
rename the symbolic link to the events directory. Thanks to
forum user 'tommy' for suggesting the fix to this issue.

387
README.html
View File

@ -480,13 +480,13 @@ style='color:windowtext;display:none;text-decoration:none'>41</span></a></span><
style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext;
text-decoration:none'>    </span>Release 1.19.3<span style='color:windowtext;
display:none;text-decoration:none'>. </span><span
style='color:windowtext;display:none;text-decoration:none'>41</span></a></span></p>
style='color:windowtext;display:none;text-decoration:none'>42</span></a></span></p>
<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc108949070">12.10.<span
style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext;
text-decoration:none'>  </span>Release 1.19.2<span style='color:windowtext;
display:none;text-decoration:none'>. </span><span
style='color:windowtext;display:none;text-decoration:none'>42</span></a></span></p>
style='color:windowtext;display:none;text-decoration:none'>43</span></a></span></p>
<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc108949071">12.11.<span
style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext;
@ -540,7 +540,7 @@ style='color:windowtext;display:none;text-decoration:none'>50</span></a></span><
style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext;
text-decoration:none'>  </span>Release 0.9.15<span style='color:windowtext;
display:none;text-decoration:none'>. </span><span
style='color:windowtext;display:none;text-decoration:none'>51</span></a></span></p>
style='color:windowtext;display:none;text-decoration:none'>52</span></a></span></p>
<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc108949080">12.20.<span
style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext;
@ -564,7 +564,7 @@ style='color:windowtext;display:none;text-decoration:none'>53</span></a></span><
style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext;
text-decoration:none'>  </span>Release 0.9.11<span style='color:windowtext;
display:none;text-decoration:none'>. </span><span
style='color:windowtext;display:none;text-decoration:none'>54</span></a></span></p>
style='color:windowtext;display:none;text-decoration:none'>55</span></a></span></p>
<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc108949084">12.24.<span
style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext;
@ -582,7 +582,7 @@ style='color:windowtext;display:none;text-decoration:none'>57</span></a></span><
style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext;
text-decoration:none'>  </span>Release 0.9.8<span style='color:windowtext;
display:none;text-decoration:none'>. </span><span
style='color:windowtext;display:none;text-decoration:none'>57</span></a></span></p>
style='color:windowtext;display:none;text-decoration:none'>58</span></a></span></p>
<p class=MsoToc2><span class=MsoHyperlink><a href="#_Toc108949087">12.27.<span
style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext;
@ -594,31 +594,31 @@ style='color:windowtext;display:none;text-decoration:none'>59</span></a></span><
style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext;
text-decoration:none'>  </span>Release 0.0.1<span style='color:windowtext;
display:none;text-decoration:none'>. </span><span
style='color:windowtext;display:none;text-decoration:none'>59</span></a></span></p>
style='color:windowtext;display:none;text-decoration:none'>60</span></a></span></p>
<p class=MsoToc1><span class=MsoHyperlink><a href="#_Toc108949089">13.<span
style='font-family:"Times New Roman";color:windowtext;font-weight:normal;
text-decoration:none'>       </span>To Do<span style='color:windowtext;
display:none;text-decoration:none'>.. </span><span
style='color:windowtext;display:none;text-decoration:none'>60</span></a></span></p>
style='color:windowtext;display:none;text-decoration:none'>61</span></a></span></p>
<p class=MsoToc1><span class=MsoHyperlink><a href="#_Toc108949090">14.<span
style='font-family:"Times New Roman";color:windowtext;font-weight:normal;
text-decoration:none'>       </span>Bugs<span style='color:windowtext;
display:none;text-decoration:none'>. </span><span
style='color:windowtext;display:none;text-decoration:none'>61</span></a></span></p>
style='color:windowtext;display:none;text-decoration:none'>62</span></a></span></p>
<p class=MsoToc1><span class=MsoHyperlink><a href="#_Toc108949091">15.<span
style='font-family:"Times New Roman";color:windowtext;font-weight:normal;
text-decoration:none'>       </span>Non-Bugs<span style='color:windowtext;
display:none;text-decoration:none'>. </span><span
style='color:windowtext;display:none;text-decoration:none'>62</span></a></span></p>
style='color:windowtext;display:none;text-decoration:none'>63</span></a></span></p>
<p class=MsoToc1><span class=MsoHyperlink><a href="#_Toc108949092">16.<span
style='font-family:"Times New Roman";color:windowtext;font-weight:normal;
text-decoration:none'>       </span>License<span style='color:windowtext;
display:none;text-decoration:none'>. </span><span
style='color:windowtext;display:none;text-decoration:none'>63</span></a></span></p>
style='color:windowtext;display:none;text-decoration:none'>64</span></a></span></p>
<h1><span style='text-decoration:none'>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><u><a name="_Toc108949040">Introduction</a></u></h1>
@ -661,8 +661,7 @@ 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 of 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.</p>
that will alarm if various thresholds are exceeded in conjunction with other zones.</p>
<p class=MsoPlainText>ZoneMinder is fresh off the keyboard and so comes with no
warranty whatsoever, please try it, send your feedback and if you get anything
@ -720,8 +719,8 @@ Please let me know if your camera works and is not listed. You do need to have
Video4Linux installed. I've not got too many machines so I've only really used
it on various RedHat/Fedora distributions, which seem to have everything there
by default I think. SlackWare does need a bit more tinkering than other
distributions; 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
distributions; 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.</p>
<h1><a name="_Toc108949042"><span style='text-decoration:none'>3.<span
@ -747,28 +746,28 @@ 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.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zmf</b> - 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’t running or dies then the
Analysis daemon just writes them itself.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zmf</b> - 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’t running or dies then the Analysis
daemon just writes them itself.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zms</b> - 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). A non-parsed header version
of zms, called nph-zms, is also installed and may be used instead depending on
your web server configuration.</p>
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). A non-parsed header version of zms,
called nph-zms, is also installed and may be used instead depending on your web
server configuration.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zmu</b> - This is the
ZoneMinder Utility. It's basically a handy command line interface to several
useful functions. It’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.</p>
ZoneMinder Utility. It's basically a handy command line interface to several useful
functions. It’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.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zmfix</b> - This is a small
binary that exists only to ensure that the video device files can be read by
@ -847,11 +846,11 @@ style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&
</span></span>'action' is 'on', 'off', 'cancel' or ‘show’ where 'on' forces an
alarm condition on, 'off' forces an alarm condition off and 'cancel' negates
the previous 'on' or 'off'. The ‘show’ action merely updates some auxiliary
text which can optionally be displayed in the images captured by the monitor.
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 which automatically 'cancel's the previous
action after that number of seconds.</p>
text which can optionally be displayed in the images captured by the monitor. 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 which automatically 'cancel's the previous action after that number
of seconds.</p>
<p class=MsoPlainText style='margin-top:0cm;margin-right:0cm;margin-bottom:
3.0pt;margin-left:53.85pt;text-indent:-17.85pt'><span style='font-family:Symbol'>·<span
@ -959,16 +958,15 @@ substitutions you can run zmconfig.pl in non-interactive mode by typing</p>
<p class=MsoPlainText><i>perl ./zmconfig.pl -noi</i></p>
<p class=MsoPlainText>which will just read your file (and later on the
database) and do the substitutions with no questions asked. There are two
classes of options, ‘core’ 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 ‘options’ section of the web interface. You only need to
complete the first set with zmconfig at this stage. If you want to change just
a few options and can’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,</p>
<p class=MsoPlainText>which will just read your file (and later on the database)
and do the substitutions with no questions asked. There are two classes of
options, ‘core’ 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 ‘options’ section of the web interface. You only need to complete the
first set with zmconfig at this stage. If you want to change just a few options
and can’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,</p>
<p class=MsoPlainText><i>perl ./zmconfig.pl ZM_STRICT_VIDEO_CONFIG</i></p>
@ -1138,8 +1136,8 @@ README are installed to the systems default document folder.</p>
<p class=MsoPlainText style='margin-left:18.0pt'>The packaged version of Zone
Minder installs all binarys to /usr/lib/zm including the web pages. So don’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:</p>
web server. The web pages for Apache are aliased by zm.conf in the
apache/conf.d directory which vary depending on your distribution:</p>
<p class=MsoPlainText style='margin-left:18.0pt'>Fedora Core:
/etc/httpd/conf.d/zm.conf</p>
@ -1660,9 +1658,9 @@ 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.</p>
<p class=MsoPlainText>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.</p>
<p class=MsoPlainText>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.</p>
<p class=MsoPlainText>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
@ -1698,17 +1696,18 @@ it's something obvious.</p>
up to support them. Once you have one or more monitors you may notice the
'&lt;n&gt; Monitors' title becomes a link. 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 can 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 ‘Mobile’ has a
special meaning (see Mobile Devices below). There may also be a ‘Cycle’ link
which allows you to cycle through a shot from each of your monitors (in the
selected group unless they are switched off) and get a streamed or still image
from each in turn. Similarly if you see a link titled ‘Montage’ it will allow
you view all your active enabled cameras (in the selected group) 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. </p>
certain monitors to view. For instance you may only wish to view outdoor
monitors while indoors. You can 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
‘Mobile’ has a special meaning (see Mobile Devices below). There may also be a
‘Cycle’ link which allows you to cycle through a shot from each of your
monitors (in the selected group unless they are switched off) and get a
streamed or still image from each in turn. Similarly if you see a link titled
‘Montage’ it will allow you view all your active enabled cameras (in the
selected group) 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. </p>
<h2><a name="_Toc108949049"><span style='text-decoration:none'>8.2.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Defining
@ -1734,9 +1733,9 @@ you like, though it isn't used much except for logging and debugging.</p>
the more important concepts in ZoneMinder and there are five to choose from.</p>
<p class=MsoPlainText style='margin-left:36.0pt'><u>Active</u> : 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. </p>
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. </p>
<p class=MsoPlainText style='margin-left:36.0pt'><u>Inclusive</u> : This zone
type can be used for any zones that you want to trigger an alarm only if at
@ -1756,11 +1755,11 @@ 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 covering 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.</p>
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.</p>
<p class=MsoPlainText style='margin-left:36.0pt'><u>Preclusive</u> : This zone
type is relatively recent. It is called a Preclusive zone because if it is
@ -1781,9 +1780,9 @@ 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 any motion just hops from
one Preclusive zone to another. As always, the best way is to experiment a
Obviously careful placement is required to ensure that they do not cancel any
genuine alarms or that they are not so close together that any 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.</p>
<p class=MsoPlainText style='margin-left:36.0pt'><u>Inactive </u>: This final
@ -1798,8 +1797,8 @@ 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 area. 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
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 situated within Active areas are they are
processed first and if small may actually save processing time by preventing
full analysis of the image.</p>
@ -1943,10 +1942,10 @@ a sound file in the configuration, 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 possible 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 refreshing may impact on
performance.</p>
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 refreshing may
impact on performance.</p>
<p class=MsoPlainText>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
@ -2002,8 +2001,8 @@ that spot. You can also use direct image control for relative motion when the
area of the image you click on 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 ‘dead’ zone in the
middle of the image.</p>
until a short distance away from the centre, resulting in a ‘dead’ zone in the middle
of the image.</p>
<h2><a name="_Toc108949052"><span style='text-decoration:none'>8.5.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Filtering
@ -2130,8 +2129,8 @@ score.</p>
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 the various images that make up the event. If you have the
full size window where you can see the image in all its detail and scroll through
the 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 on Delete will erase it from the
@ -2213,10 +2212,10 @@ ZoneMinder build directory where the parts represented by the
you would enter as a language. This is slightly unwieldy and will probably be
improved in future to make it easier to determine language availability. 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
elements are given in the zm_lang_en_gb.php file along with a few notes to help
you understand the format.</p>
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 elements are given in the zm_lang_en_gb.php file along with a few
notes to help you understand the format.</p>
<p class=MsoPlainText>As mentioned above, you may also see a ‘users’ tab in the
Options area. In this section you will see a list of the current users defined
@ -2225,12 +2224,12 @@ 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 different 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 default language described above.</p>
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 different 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 default language described above.</p>
<p class=MsoPlainText>There are also four values that define the user
permissions, these are ‘stream’, ‘events’, ‘monitors’ and ‘system’ Each can
@ -2263,9 +2262,9 @@ Control</u></a></h1>
<p class=MsoPlainText>Version 1.21.0 of ZoneMinder introduced 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 problem.</p>
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 problem.</p>
<p class=MsoPlainText><span class=name1><b>1) Definition of Capabilities</b></span><span
class=name1> </span>– <span class=name1>For each camera model you use, an entry
@ -2308,15 +2307,15 @@ Capabilities</a></h2>
<p class=MsoPlainText><span style='color:black'>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 Control tab of the Monitor configuration
dialog and select ‘Edit’ 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. 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
capabilities table there are a large number of settings and tabs, the mean and
use of these are briefly explained below.</span></p>
table. To do this you need to go to the Control tab of the Monitor
configuration dialog and select ‘Edit’ 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. 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 capabilities table there are a large number of settings and
tabs, the mean and use of these are briefly explained below.</span></p>
<p class=MonitorTab style='margin-bottom:3.0pt'>‘Main’ Tab</p>
@ -2534,8 +2533,8 @@ specified.</p>
<p class=MsoPlainText style='margin-top:0cm;margin-right:0cm;margin-bottom:
3.0pt;margin-left:1.0cm'><b><span style='color:black'>--address=&lt;address&gt;
</span></b>– This is the control address 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.</p>
usually be a hostname or ip address for network cameras or a simple numeric camera
id for other cameras.</p>
<p class=MsoPlainText style='margin-top:0cm;margin-right:0cm;margin-bottom:
3.0pt;margin-left:1.0cm'><b><span style='color:black'>--autostop=&lt;timeout&gt;
@ -2729,9 +2728,9 @@ specifically please let me know and I would be pleased to hear about it.</p>
<p class=MsoPlainText>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 ‘Mobile’ already defined then that group
will always be effective, if not then all monitors available to the logged in
user will be visible,</p>
Instead if there is a group called ‘Mobile’ already defined then that group will
always be effective, if not then all monitors available to the logged in user will
be visible,</p>
<p class=MsoPlainText>&nbsp;</p>
@ -2760,8 +2759,8 @@ ZoneMinder, firstly make sure that you have the correct settings. Use xawtv or
something like that to check for settings that work and then run zmu -d
&lt;device_no&gt; -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
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 ‘options’ tab.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-18.0pt'><span
@ -2893,8 +2892,8 @@ 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’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.</p>
with greyscale and if you can't get anything to work let me know and I'll try
and add it.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -2932,10 +2931,10 @@ 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 streamed
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 caps 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
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 caps 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 apparent leak is not consuming any more
memory than when it started.</p>
@ -2980,6 +2979,12 @@ style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>FIX – Fixed a problem where Axis PTZ controls sometimes caused
the camera to move in an incorrect direction.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>FIX – Fixed an issue where the ‘goto preset’ command did not pass
the appropriate preset number (and so defaulted to 1) for the Axis, Panasonic
and VISCA protocols.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>FIX – A problem existed where renaming monitors did not rename
@ -3016,8 +3021,8 @@ support Iris control.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>FIX – Fixed a nasty problem in zmaudit which meant that older events
sometimes didn’t get tidied up and deleted properly.</p>
</span></span>FIX – Fixed a nasty problem in zmaudit which meant that older
events sometimes didn’t get tidied up and deleted properly.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -3097,9 +3102,9 @@ incident.</p>
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>FEATURE – There has long been a dichotomy between the functions
that can be applied via interactive 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 functionality will converge
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 functionality will converge
further in the future.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
@ -3125,8 +3130,8 @@ 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 outside of
the regular ZoneMinder interface. 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.</p>
that that created in the background filter function and it is expected that these
functions will converge at some point.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -3847,8 +3852,8 @@ re-configure your previous defaults as they will be lost.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>FEATURE – Filters can now include a specification of the preferred
sort order of the results.</p>
</span></span>FEATURE – Filters can now include a specification of the
preferred sort order of the results.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -3991,8 +3996,8 @@ rather than just the latter as previously.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Remote Image Parsing. Further improvements have been made to
handle additional patterns of images with differing styles of terminations or none
at all.</p>
handle additional patterns of images with differing styles of terminations or
none at all.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -4040,8 +4045,8 @@ displayed. This can result in the 'live' view being several seconds delayed.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>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>multipart/x-mixed-replace</i>
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>multipart/x-mixed-replace</i>
MIME type then this will 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
@ -4139,9 +4144,9 @@ 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 ‘myfilter’ to
‘myfilter_&lt;id&gt;’ where ‘&lt;id&gt;’ 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’s original name.</p>
(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’s original name.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -4211,26 +4216,26 @@ that image processing for YUV style input formats are now pretty much handled
at almost the same 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 previously 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 comparing 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 RGB
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_FAST_IMAGE_BLENDS
option for details). Altogether these optimisations (along with other common
sense ones such as not maintaining a reference image in ‘Record’ mode where it
is not used) significantly reduce the CPU load for most systems, especially
when alarms 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.</p>
highlighted a bug that had existed previously 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 comparing 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 RGB 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_FAST_IMAGE_BLENDS option for details). Altogether these optimisations (along
with other common sense ones such as not maintaining a reference image in
‘Record’ mode where it is not used) significantly reduce the CPU load for most
systems, especially when alarms 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.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -4374,9 +4379,9 @@ added to the zone definition form to try and prevent bogus or invalid settings.<
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Diagnostic Zone Images. A regularly requested feature is that of
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.
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 generate 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
@ -4454,8 +4459,8 @@ style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
also available for translation. 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 translated piecemeal as the opportunity
arises.</p>
The new format allows individual options to be translated piecemeal as the
opportunity arises.</p>
<h2><a name="_Toc108949077"><span style='text-decoration:none'>12.17.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
@ -4475,9 +4480,9 @@ rework, a change in <i>y</i> will indicate a new release containing incremental
feature changes or fixes recommend to all users and a change in <i>z </i>will
generally mean minor non-functional or critical modifications which would not
be recommended 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.</p>
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.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -4533,12 +4538,12 @@ the monitors to have these saved functions and then doing a system restart.</p>
<p class=BullettedChar><span style='font-family:"Courier New"'>o<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>New Monitor Functions. Instead of Passive, Active, and X10, the modes
are now Monitor (= old Passive) which just allows you 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 also do
motion detection and highlight where this has occurred. The Record and Mocord
</span></span>New Monitor Functions. Instead of Passive, Active, and X10, the
modes are now Monitor (= old Passive) which just allows you 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 also 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 not record 'n' frames at a time, when not alarmed.</p>
@ -4870,12 +4875,12 @@ was broken. This is now fixed.</p>
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>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 of 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 effect. Also if you have
a number of cameras being multiplexed onto one device then any changes here
will probably affect all your cameras.</p>
should work for most types of 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 effect. Also if you have a number of
cameras being multiplexed onto one device then any changes here will probably
affect all your cameras.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -4942,10 +4947,10 @@ long to wrap in this way.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Fixed round detection problem. Although the existence or otherwise
of the ‘round’ 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. </p>
</span></span>Fixed round detection problem. Although the existence or
otherwise of the ‘round’ 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. </p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -4966,8 +4971,8 @@ based on the length of the event 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.</p>
faster frame rates than necessary. This has now been corrected to take the
whole event length into account.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -5036,15 +5041,15 @@ style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&n
</span></span>New video palette support – 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. </p>
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. </p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Added preclusive zones – 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
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.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-18.0pt'><span
@ -5151,9 +5156,9 @@ style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&n
</span></span>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 zone minder install directory first as the
old ones won't be overwritten and will be left behind.</p>
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 zone minder install directory first
as the old ones won't be overwritten and will be left behind.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -5277,9 +5282,9 @@ directory was not created on install, this has been fixed.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>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.</p>
</span></span>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.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-18.0pt'><span
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

BIN
README.pdf
View File

Binary file not shown.

2028
README.rtf
View File

File diff suppressed because it is too large Load Diff