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

Updated for version 1.19.5 

git-svn-id: http://svn.zoneminder.com/svn/zm/trunk@1113 e3e1d417-86f3-4887-817a-d78f3d33393f
This commit is contained in:
stan 2004-09-25 16:37:15 +00:00
parent 1087219546
commit 250370463a
4 changed files with 1599 additions and 1222 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

377
README
View File

@ -1,6 +1,6 @@
20/05/04 ZoneMinder 1.19.4 README
25/09/04 ZoneMinder 1.19.5 README 1
ZoneMinder v1.19.4
ZoneMinder v1.19.5
1. Introduction
@ -127,16 +127,16 @@ directories could be /var/www/html/zm and /var/www/cgi-bin 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 -with-ffmpeg=<path to ffmpeg root> to help configure find
it. This will be /usr/local if you let ffmpeg use it's default
options. 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. Additionally if you have built
ffmpeg with the mp3lame feature turned on you may additionally
need to tell configure where to find that the mp3lame library, to
prevent unresolved dependencies. To do this add the -with-
lame=<path to lame directory>option as well. There are also two
further arguments you can add if your web user and group are not
both 'apache'. These are --with-webuser and --with-webgroup. Type
it if it's not installed in a default location. 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. Additionally if you have built ffmpeg with the mp3lame feature
turned on you may additionally need to tell configure where to
find that the mp3lame library, to prevent unresolved dependencies.
To do this add the -with-lame=<path to lame directory>option as
well. There are also two further arguments you can add if your web
user and group are not both 'apache'. These are --with-webuser and
--with-webgroup. Type
./configure -help
@ -162,11 +162,11 @@ run zmconfig.pl in non-interactive mode by typing
perl ./zmconfig.pl -noi
which will just read your file and do the substitutions with no
questions asked. There are two classes of options, 'core' options
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. Only
dynamically via the `options' 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't access the options
dialog via the web you can append them as parameters to zmconfig
@ -201,7 +201,21 @@ 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.sql and zmalter0.9.10.sql.
zmalter-0.9.9.sql and zmalter0.9.10.sql. Additionally 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
zmupdate.pl -version=<previous version> [--user=<db user> --
pass=<db password>]
where `previous version' releates to the verion 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 `user' and `pass' options allow
you to specify a database user and password with sufficient
privilege to `alter' the structure of the database.
For a new installation the simplest way to create your database
and users is as follows,
@ -215,7 +229,7 @@ grant select,insert,update,delete on <your database name>.* to
password>';
grant select on <your database name>.* to '<your second
username>'@localhost identified by '<your second password>'
username>'@localhost identified by '<your second password>';
quit
@ -323,17 +337,17 @@ viewed and amended if necessary and are as follows.
zmupdate.pl - Currently this script is responsible for checking
whether a new version of ZoneMinder is available and other
miscellaneous actions related to upgrades and migrations.
Eventually it is intended to be a 'one stop shop' for any
upgrades and will execute everything necessary to update your
installation to a new version.
miscellaneous actions related to upgrades and migrations. It is
also intended to be a `one stop shop' for any upgrades and will
execute everything necessary to update your installation to a
new version.
zm - This is the (optional) ZoneMinder init script, see below
for details.
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 utilities but some scripts have a 'VERBOSE'
by the configuration utilities but some scripts have a `VERBOSE'
flag you can set to get more debug out.
At this stage typing 'make install' will install everything to the
@ -357,7 +371,7 @@ chkconfig --add zm
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 'service zm start' or 'service zm stop' etc.
You may need to use the '-levels' parameter to chkconfig to ensure
You may need to use the `-levels' parameter to chkconfig to ensure
that ZoneMinder is started when you need it to.
Now start your web browser and point it at your zm.php and off you
@ -372,7 +386,7 @@ that lets you specify whether anyone that goes to the ZoneMinder
web pages must authenticate 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
'admin' has been created with a password also of 'admin'. You
`admin' has been created with a password also of `admin'. You
should change this password as soon as possible.
Once you've logged in, or if you are running in un-authenticated
@ -380,7 +394,7 @@ 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 'stopped'
indication of the system state which will probably say `stopped'
to start with. This is a link that you can click on to control the
ZoneMinder system as a whole. Below that are various other links
including one detailing the current user (in authenticated mode
@ -422,12 +436,12 @@ error related to permissions run 'zmfix -a' to make sure you can
access all the video devices.
The options are divided into a set of tabs to make it easier to
edit. You do not have to 'save' to change to different tab so you
can make all the changes you require and then click 'Save' at the
edit. You do not have to `save' to change to different tab so you
can make all the changes you require and then click `Save' at the
end. The individual option are explained in a little more detail
below,
'Monitor' Tab
`Monitor' Tab
Name - The name for your monitor. This should be made up of
alphanumeric characters (a-z,A-Z,0-9) and hyphen (-) and
@ -443,30 +457,30 @@ below,
analysis is done and so no alarms or events will be generated,
ú 'Modect' - or MOtion DEteCTtion. All captured images will be
analysed and events generated where motion is detected,
ú 'Record' - In this case continuous events of a fixed length
ú `Record' - 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' - This is a hybrid of Modect and Record and results
ú `Mocord' - 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.
Generally speaking it is best to choose 'Monitor' as an
Generally speaking it is best to choose `Monitor' as an
initial setting here..
Section Length - This specifies the length (in seconds) of any
fixed length events produced when the monitor function is
'Record' or 'Mocord'. Otherwise it is ignored. This should not
`Record' or `Mocord'. 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.
Frame Skip - This setting also applies only to the 'Record' or
'Mocord' functions and specifies how many frames should be
Frame Skip - This setting also applies only to the `Record' or
`Mocord' functions and specifies how many frames should be
skipped in the recorded events. The default setting of zero
results in every captured frame being saved, whereas one would
mean that one frame is skipped between each saved one, two
means that two frames are skipped between each saved one etc.
An alternate way of thinking is that one in every 'Frame Skip
An alternate way of thinking is that one in every `Frame Skip
+ 1' 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 high
@ -474,22 +488,22 @@ being highlighted within those events.
frame rate which will obviously affect the rate at which
frames are saved.
Run Mode - Two choices are available here. 'Continuous' is the
Run Mode - Two choices are available here. `Continuous' 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 'Triggered' means that
automatically restarted. By contrast `Triggered' means that
the decision about whether the daemons should actually be
active is devolved to an external triggering mechanism.
Triggers - This small section lets you select which triggers
will apply if the run mode has been set to 'triggered' above.
will apply if the run mode has been set to `triggered' 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 expected that other triggers
will become available as necessary. You can also just use
'cron' jobs or other mechanisms to actually control the camera
`cron' jobs or other mechanisms to actually control the camera
and keep them completely outside of the ZoneMinder settings.
Source Type - This determines whether the camera is a local
@ -497,7 +511,7 @@ being highlighted within those events.
or a remote network camera or similar. Choosing one or the
other affects which set of options are shown in the next tab.
'Source' Tab (local device)
`Source' Tab (local device)
Device Number/Channel - For a local camera enter the device
number that your camera is attached to. If it is /dev/video0
@ -540,10 +554,10 @@ being highlighted within those events.
the orientation here. 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 'Rotate Right' here then set the height to be 352 and
choose `Rotate Right' here then set the height to be 352 and
width to be 288.
'Source' Tab (remote device)
`Source' Tab (remote device)
Remote Host/Port/Path - For remote cameras use these fields to
enter the full URL of the camera. Basically if your camera is
@ -563,10 +577,10 @@ being highlighted within those events.
Orientation - As per local devices.
'Timestamp' Tab
`Timestamp' Tab
Timestamp Label Format - This relates to the timestamp that is
applied to each frame. It is a 'sprintf' style string. It is
applied to each frame. It is a `sprintf' style string. It is
actually passed through sprintf 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
@ -580,11 +594,11 @@ being highlighted within those events.
the top of the image. To place the timestamp at the bottom of
the image use a value eight less than the image height.
'Buffers' Tab
`Buffers' Tab
Image Buffer Size - 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 'n' images are kept, ready to
the storage space where the last `n' images are kept, ready 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
@ -624,8 +638,29 @@ being highlighted within those events.
that this setting enables you to view a reasonable time frame
pre and post event.
'Misc' Tab
Alarm Frame Count - 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 if you have statistics recording enabled then
currently statistics are not recorded for the first `Alarm
Frame Count'-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.
`Misc' Tab
Event Prefix - By default events are named `Event-<event id>',
however you are free to rename them individually as you wish.
This option lets you modify the event prefix, the `Event-`
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.
Maximum FPS - On some occasions you may have one or more
cameras capable of high capture rates but find that you
generally do not require this performance at all times and
@ -668,7 +703,7 @@ being highlighted within those events.
start with 10 here and adjust it (usually down) later if
necessary.
'X10' Tab
`X10' Tab
Note: This tab and its options will only appear if you have
indicated that your system supports the X10 home automation
@ -676,7 +711,7 @@ being highlighted within those events.
X10 Activation String - The contents of this field determine
when a monitor starts and/or stops being active when running
in 'Triggered; mode and with X10 triggers. The format of this
in `Triggered; mode and with X10 triggers. The format of this
string is as follows,
n : If you simply enter a number then the monitor will be
@ -787,7 +822,7 @@ support them. Once you have one or more monitors you may notice
the '<n> Monitors' title becomes a link which allows you to cycle
through a shot from each of your monitors (unless they are
switched off) and get a streamed or still image from each in turn.
There may also be a link titled 'Montage' which allows you view
There may also be a link titled `Montage' which allows you view
all your enabled cameras 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.
@ -899,9 +934,9 @@ are as follows.
processing time by preventing full analysis of the image.
Units - This setting which details whether certain of the
following settings are in Pixels or Percent, where 'Percent'
following settings are in Pixels or Percent, where `Percent'
refers to a percentage area of the zone itself. In general
'Pixels' is more precise whereas percentages are easier to use
`Pixels' 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 in the correct context. A good tip would be to
@ -933,8 +968,8 @@ are as follows.
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 'AlarmPixels',
'FilteredPixels' and 'Blobs' and depending on which option is
alarm or not. The three options are `AlarmPixels',
`FilteredPixels' and `Blobs' and depending on which option 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
@ -942,14 +977,14 @@ are as follows.
be filtered 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 'blobs'. Blob analysis is the method ZoneMinder has
groups, or `blobs'. Blob analysis is the method ZoneMinder has
always used previously (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 'Blob' setting.
available with the `Blob' setting.
Min/Maximum Alarm Threshold - These setting are used to define
limits for the difference in value between a pixel and its
@ -1040,13 +1075,13 @@ 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 'cooling down', if another alarm is generated in this
monitor is `cooling down', 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 'options' if required.
state. This behaviour can be turned off in `options' if required.
You can also specify 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
@ -1132,7 +1167,7 @@ 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 '-3 day' or similar with easily parseable
type of format to use is `-3 day' or similar with easily parseable
numbers and units are in English.
The other elements you can filter on are all fairly self
@ -1142,12 +1177,12 @@ most filtering on un-archived events. There are also two elements,
Disk Blocks and Disk Percent which don'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 'df' command.
either in blocks or in percentage as returned by the `df' command.
They relate to the amount of disk space used and not the amount
left free. Once your filter is specified, clicking 'submit' will
filter the events according to your specification. As the disk
based elements are not event related directly if you create a
filter and include the term 'DiskPercent > 95' then if your
filter and include the term `DiskPercent > 95' then 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
@ -1276,7 +1311,7 @@ be displayed.
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 '?'
description and the current value. You can also click on the `?'
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
@ -1284,7 +1319,7 @@ 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.
If you have changed the value of an option you should then 'save'
If you have changed the value of an option you should then `save'
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
@ -1295,7 +1330,7 @@ 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.
One of the options you may notice in the 'System' tab allows you
One of the options you may notice in the `System' 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
@ -1305,7 +1340,7 @@ 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 '*' would be what you would enter as a
represented by the `*' 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 availability. On
checking which languages are available it may be that your
@ -1315,7 +1350,7 @@ 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.
As mentioned above, you may also see a 'users' tab in the Options
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 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
@ -1332,26 +1367,26 @@ available. Specifying a language here is done in the same way as
for the system default language described above.
There are also four values that define the user permissions, these
are 'stream', 'events', 'monitors' and 'system' Each can have
values of 'none', 'view' or 'edit' apart from 'stream' which has
no 'edit' setting. These values cover access to the following
areas; 'stream' defines whether a user is allowed to view the
'live' video feeds coming from the cameras. You may wish to allow
are `stream', `events', `monitors' and `system' Each can have
values of `none', `view' or `edit' apart from `stream' which has
no `edit' setting. These values cover access to the following
areas; `stream' defines whether a user is allowed to view the
`live' 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 'none'. The 'events' setting determines whether a user
should be `none'. The `events' setting determines whether a user
can view and modify or delete any retained historical events. The
'monitors' setting specifies whether a user can see the current
monitor settings and change them. Finally the 'system' setting
`monitors' setting specifies whether a user can see the current
monitor settings and change them. Finally the `system' 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-'system' 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 'monitors' edit privileges is limited to
no spaces. If a user with `monitors' 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 'system' privileges then the 'monitors ids' setting
If a user has `system' privileges then the `monitors ids' setting
is ignored and has no effect.'
That's pretty much is it for the tour. You should experiment with
@ -1393,7 +1428,7 @@ Some things to check.
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.
the `options' tab.
o Start simple. Begin with a single monitor and single zone.
You can run the zmc capture daemon from the command line as 'zmc -
@ -1562,7 +1597,96 @@ http://www.zoneminder.com/downloads/noIEClick.reg
7. Change Log
7.1. Release 1.19.4
7.1. Release 1.19.5
Various miscellaneous fixes and features.
o FIX - The US English language file was recursively including
itself rather than the UK English file as the base language.
o LANGUAGE - The Brazilian Portuguese language file detailed in
the previous release has actually been included in this one.
o LANGUAGE - The Argentinian Spanish, Polish and Italian
translations have all been updated with tokens introduced in
version 1.19.3.
o FIX - Sorting event lists by duration was broken and has now
been corrected.
o FEATURE - 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.
o FIX - The modification suggested by forum user `oskin' has
been incorporated into the code to try and reduce or remove video
for linux errors.
o FIX - The remote network camera parsing code has been patched
to try
o FIX - The error reported when a `shmget' call fails has been
changed to include further information about the cause.
o LANGUAGE - Fixed missing semicolon in German language file.
o FEATURE - Added `<<' and `>>' links to the page selector in
the events list as suggested by forum user `unclerichy'.
o FEATURE - 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 `oskin'.
o FEATURE - In previous versions the events folder has been
keyed by the monitor name. This has caused problems in the past
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.
o FEATURE - You may now optionally have thumbnail images in
your event lists. To enable this functionality set
ZM_WEB_LIST_THUMBS on in Options->Web. You can also control the
width or height of these thumbnails but should only set one
dimension only and leave the other blank or zero.
o FEATURE - You can now specify how many image thumbnails
appear across and down the page in the event stills listing. In
Options->Web set the ZM_WEB_FRAMES_PER_LINE and/or
ZM_WEB_FRAME_LINES options.
o FEATURE - ZoneMinder uses ffmpeg
(http://ffmpeg.sourceforge.net/) 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.
o FEATURE - You can now specify a prefix for events generated
by particular monitors. This will replace the default `Event-`
one.
o FEATURE - 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 `<html>' token,
o FEATURE - 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 `View'
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 `Play All' link. This will
replay each event and then automatically move onto the next one.
You can stop this progression at any time by pressing `Stop'
(which only stops the sequence and not the currently playing
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
buffering players as the timing will likely be incorrect. If you
are viewing an event but haven't checked any in the list the `Play
All' button will just work down the current event list.
o FIX - A default php error level excluding notice warnings is
now explicitly set.
o FEATURE - 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
`Alarm Frame Count' 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.
7.2. Release 1.19.4
Language fixes and updates.
o FIX - The US English language file was recursively including
@ -1574,7 +1698,7 @@ o LANGUAGE - The Argentinian Spanish, Polish and Italian
translations have all been updated with tokens introduced in
version 1.19.3.
7.2. Release 1.19.3
7.3. Release 1.19.3
Minor tweaks, fixes and language updates.
o FEATURE - All stills views now use the single image mode of
@ -1591,7 +1715,7 @@ 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.
o FEATURE - When viewing a single frame of an event you can
select a 'stats' link to view the statistics that apply to that
select a `stats' 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 were displayed here
@ -1613,10 +1737,10 @@ recorded.
o FIX - 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 'open' events such as this which
zmaudit.pl was made such that any `open' 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 '(r)' mark
or saved. Events recovered in this way are named with a `(r)' mark
to help identify them.
o FIX - In more recent versions of MySQL the password hash
generated is 50 characters long, which overflows the previous
@ -1631,7 +1755,7 @@ 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.
o FIX - It was previously the case that old images could be
left in the 'images' directory for a long period, sometimes
left in the `images' 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 old WAP
images so that any old images left in this directory are removed
@ -1642,13 +1766,13 @@ deleted.
o FIX - A JavaScript error in the Zone configuration screen was
identified and fixed.
o LANGUAGE - A Brazilian Portuguese translation has been
supplied by Victor Diago and is available by selecting 'pt_br' as
supplied by Victor Diago and is available by selecting `pt_br' as
the language type.
o LANGUAGE - Updated versions of the Dutch and Argentinian
Spanish translations have been included.
7.3. Release 1.19.2
7.4. Release 1.19.2
Minor features, fixes and language updates.
o FEATURE - The default replay rate and live and event scale
@ -1676,7 +1800,7 @@ 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 window, modify it to your
taste and then save it, selecting 'auto delete'. Please note that
taste and then save it, selecting `auto delete'. 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
@ -1752,7 +1876,7 @@ tokens are included in the language files in English. There will
shortly be a point release which includes these language updates
assuming I can get translations of them in a reasonable timescale.
7.4. Release 1.19.1
7.5. Release 1.19.1
Minor bugfixes and enhancements.
o Ffmpeg Configure Changes. The configure script has been
@ -1780,7 +1904,7 @@ o 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.
7.5. Release 1.19.0
7.6. Release 1.19.0
Some major enhancements and bugfixes.
o MPEG video streaming. ZoneMinder now supports true video
@ -1832,16 +1956,16 @@ 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.
o Event List Ordering and Scrolling. It was previously the case
that the 'Next' and 'Prev' buttons on the event view did not
that the `Next' and `Prev' 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 'next' event is the one below which has
ascending scores then the `next' 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
'next' event is the one below in the list which will actually be
earlier and the 'previous' event is later. So long as you remember
`next' event is the one below in the list which will actually be
earlier and the `previous' event is later. So long as you remember
that next and prev refer to the order of the list you should be
ok.
o Zone Percentage Sizes. Zone motion detection parameters can
@ -1855,7 +1979,7 @@ easier. To convert your existing zones you can run zmupdate.pl
with the -z option, though this should be done only once and you
should backup your database beforehand in case of error.
o Console View System Display. The console display was slight
revamped to indicate disk space usage (via the 'df' command) on
revamped to indicate disk space usage (via the `df' command) on
the events partition,
o Zone Form Validation. Changes applied in version 1.18.0 to
prevent invalidate entries in the zone definition form actually
@ -1880,8 +2004,8 @@ filters table, several people reported that when saving filters
they actually 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 'myfilter' to
'myfilter_<id>' where '<id>' is the id number in the database
database all the filters will be renamed from `myfilter' to
`myfilter_<id>' where `<id>' 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
@ -1900,7 +2024,7 @@ deleted when monitor was.
o A translation for the Dutch (nl_nl) language has been
included.
7.6. Release 1.18.1
7.7. Release 1.18.1
Minor bugfixes.
o Filter Monitor Name Bug. A bug was present in the previous
@ -1918,7 +2042,7 @@ 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.
7.7. Release 1.18.0
7.8. Release 1.18.0
Major optimisations, important new features and some bugfixes.
o Optimisations and Performance Improvements. This release
@ -1947,7 +2071,7 @@ Major optimisations, important new features and some bugfixes.
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
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
@ -1981,9 +2105,9 @@ delete duplicates before adding any monitor specific terms and
resetting the actions for any that remain.
o 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 'cat' is in the set of 'cat,
dog, cow, horse'. You can also use regular expressions so 'cat'
matches '^c.*'. The 'not in set' and 'not matches' operators are
in a set of other values, for example `cat' is in the set of `cat,
dog, cow, horse'. You can also use regular expressions so `cat'
matches `^c.*'. The `not in set' and `not matches' operators are
also available.
o Additional Scales. Enhancements to the scaling algorithm mean
that non binary scales are now just as easy to apply, thus new
@ -2043,7 +2167,7 @@ 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.
7.8. Release 1.17.2
7.9. Release 1.17.2
Minor features, bug fixes and additional languages.
o Pending Process Bug. A bug was found whereby a process that
@ -2057,7 +2181,7 @@ distributions. The existence of this function is now tested for by
the configure script and it is not used if not present.
o Add Max Alarm Threshold. Previously the alarm threshold
(which is the amount a pixel has to differ from it's counterpart
in the reference image) existed only in a 'minimum' form meaning
in the reference image) existed only in a `minimum' form meaning
pixels that were more different matched. A maximum has now been
added to assist in screening out large changes in brightness. In
addition to this a number of new consistency checks have been
@ -2081,7 +2205,7 @@ 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
'zmupdate.pl' utility to rename all your old images by doing 'perl
`zmupdate.pl' utility to rename all your old images by doing `perl
zmupdate.pl -r' as an appropriately privileged or root user.
o Version checking. ZoneMinder will now optionally check for
new versions of itself at zoneminder.com. This is done with a
@ -2095,7 +2219,7 @@ it's detection of browser capabilities to prevent the Cambozola
Java applet being used. However sometimes the opposite effect was
desired and using the applet was preferred to native image
handling. This has now been made possible by making the
ZM_CAN_STREAM option tri-state allowing 'auto', 'yes' or 'no' to
ZM_CAN_STREAM option tri-state allowing `auto', `yes' or `no' to
be used to provide all alternatives.
o Alarms Cleared on Exit. In previous versions if an alarm was
present when the analysis daemon (zma) exited the alarm would
@ -2105,7 +2229,7 @@ now cleared when this daemon exits.
o New Languages. Translations for Japanese (ja_jp), French
(fr_fr) and Russian (ru_ru) are now included.
7.9. Release 1.17.1
7.10. Release 1.17.1
Bugfixes and additional languages.
o Login Bug. A bug was identified whereby an unauthorised user
@ -2126,11 +2250,11 @@ accessed area and contains a great deal of text. The new format
allows individual options to be translated piecemeal as the
opportunity arises.
7.10. Release 1.17.0
7.11. Release 1.17.0
Language changes and other enhancements.
o Version Numbering. ZoneMinder version numbers have now
changed. This is to allow more frequent 'point' releases which are
changed. This is to allow more frequent `point' releases which are
expected to happen for instance whenever new language files are
included. Previously all releases had the same version increment
so it was difficult to tell the significance of any particular
@ -2152,7 +2276,7 @@ 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.
o Syntactic Improvements. Previously setting 'NOTICE' errors on
o Syntactic Improvements. Previously setting `NOTICE' errors on
in PHP would flag tens or hundreds of violations in the ZoneMinder
web files. Whilst not strictly errors this represented sloppy
coding and sometimes covered up genuine bugs. All the files have
@ -2171,10 +2295,10 @@ has been corrected.
o Minor Bugs. A number of minor bugs and inconsistencies were
corrected.
7.11. Release 0.9.16
7.12. Release 0.9.16
Major usability enhancement and fixes.
o Run States. Instead of the old 'start/stop' links the current
o Run States. Instead of the old `start/stop' 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
@ -2290,7 +2414,7 @@ correctly parsed from command line options passed to zmu.
o Event window width variable. Event windows now scale to fit
the event image size.
7.12. Release 0.9.15
7.13. Release 0.9.15
Various bug fixes from the last release and before.
o Bandwidth. A bug was introduced in .14 which caused a
@ -2326,7 +2450,7 @@ directly were colourised whereas those written by zmf weren't. A
change has been made whereby if set all greyscale JPEG images are
colourised in all circumstances.
7.13. Release 0.9.14
7.14. Release 0.9.14
Major new feature and important bug-fixes.
o Web configuration. Following many requests and to make
@ -2352,7 +2476,7 @@ been removed. This module had been removed from zmconfig.pl
previously but had lingered in this script.
o A bug was found in zmx10.pl causing a crash if time delayed
X10 events were used. This has now been fixed.
o Removed use of 'zmu' binary from zmwatch.pl and zmx10.pl.
o Removed use of `zmu' 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
@ -2367,7 +2491,7 @@ should still be secure as it will require authentication.
o All SQL buffers in the C++ code have been enlarged. There was
previously an issue with a buffer overflow on certain occasions.
7.14. Release 0.9.13
7.15. Release 0.9.13
Beta version of several features and fixes, never generally
released.
@ -2417,7 +2541,7 @@ restart the refresh process. By using JS refresh timers which are
not interrupted these extraneous refreshes have been mostly
eliminated.
7.15. Release 0.9.12
7.16. Release 0.9.12
Mostly bug-fixes with a couple of minor features.
o Double first images. Fixed a problem where the first image of
@ -2444,7 +2568,7 @@ deltas. This routine has been changed to allow variable precision
and events will now have to be several days long to wrap in this
way.
o Fixed round detection problem. Although the existence or
otherwise of the 'round' function is correctly detected, the
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.
o Fixed monitor rename bug. Renaming a monitor did not
@ -2487,9 +2611,9 @@ installs.
o Delete monitor confirm. Due to some unfortunate accidents by
users, attempts to delete monitors will now require confirmation.
o Detect linmysqlclient.a. Added better detection script into
'configure' top spot when libmysqlclient.a is missing.
`configure' top spot when libmysqlclient.a is missing.
7.16. Release 0.9.11
7.17. Release 0.9.11
Various new features and fixes.
o Added stats view - If you have the RECORD_EVENT_STATS
@ -2572,10 +2696,10 @@ o Web colour change - 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!
7.17. Release 0.9.10
7.18. Release 0.9.10
Many bug-fixes and major feature enhancements.
o Configure 'round' bug - Fixed a problem with the configure
o Configure `round' 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.
@ -2591,7 +2715,7 @@ won't be overwritten and will be left behind.
o Streamed cycle view - The monitor cycle view (the one where
each monitor is displayed sequentially) now supports streams as
well as stills.
o New 'montage' view - Added a montage view showing all your
o New `montage' 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.
@ -2650,7 +2774,7 @@ o 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't
think we need to talk about them here do we.
7.18. Release 0.9.9
7.19. Release 0.9.9
Mainly bug-fixes and minor feature enhancements.
o Added zmu -q/--query option - There is now a new query option
@ -2697,7 +2821,7 @@ 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.
7.19. Release 0.9.8
7.20. Release 0.9.8
Several new features and bug-fixes
o Upgrade note - If you have installed 0.9.7 and wish to save
@ -2762,7 +2886,7 @@ o Monitor window refresh on alarm - When the monitor window is
active and an alarm has occurred the most recent alarms list is
immediately refreshed to show it.
7.20. Release 0.9.7
7.21. Release 0.9.7
Yes, a big jump in release number but a lot of changes too. Now
somewhat more mature, not really an alpha any more, and a lot of
bugs fixed too.
@ -2807,7 +2931,7 @@ o Some of the web views have changed slightly to accommodate
the separate events view.
o And much much more, probably...
7.21. Release 0.0.1
7.22. Release 0.0.1
Initial release, therefore nothing new.
@ -2844,7 +2968,8 @@ like to put a WML interface on to allow you to view event listing
and perhaps the most significant image from each event on your
phone. Also simple management. From version 0.9.7 there is a very
basic crude initial version that probably won't work with your
phone but its there as a testbed.
phone but its there as a testbed. Note, this interface is now in
xHTML, or will be when finally released.
o 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

562
README.html
View File

@ -3,7 +3,7 @@
<head>
<meta http-equiv=Content-Type content="text/html; charset=windows-1252">
<meta name=Generator content="Microsoft Word 10 (filtered)">
<title>ZoneMinder v1.19.0</title>
<title>ZoneMinder v1.19.5</title>
<style>
<!--
@ -14,6 +14,9 @@
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
@ -171,6 +174,8 @@ p.StyleCommandLeft175cm, li.StyleCommandLeft175cm, div.StyleCommandLeft175cm
font-size:10.0pt;
font-family:Arial;
font-style:italic;}
span.name1
{color:black;}
ins
{text-decoration:none;}
span.msoIns
@ -197,7 +202,7 @@ ul
<div class=Section1>
<p class=MsoTitle><u>ZoneMinder v1.19.4</u></p>
<p class=MsoTitle><u>ZoneMinder v1.19.5</u></p>
<h1 style='text-indent:-22.7pt;page-break-before:auto'><span style='text-decoration:
none'>1.<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -252,8 +257,8 @@ useful out of it please let me know.</p>
running and find it useful then please feel free to visit <a
href="http://www.zoneminder.com/donate.html">http://www.zoneminder.com/donate.html</a>
where any donations will be appreciated and will help to fund future
improvements of ZoneMinder. This would be especially appreciated if you use ZoneMinder
as part of your business or to protect your property.</p>
improvements of ZoneMinder. This would be especially appreciated if you use
ZoneMinder as part of your business or to protect your property.</p>
<h1 style='text-indent:-22.7pt'><span style='text-decoration:none'>2.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><u>Requirements</u></h1>
@ -272,13 +277,13 @@ the netpbm utilities in a very limited way to generate thumbnails under certain
circumstances though this can be modified.</p>
<p class=MsoPlainText>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 much. The web interface uses PHP and so 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 more
details see later in this document.</p>
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 much. The web interface uses PHP and so 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 more details see later in this document.</p>
<p class=MsoPlainText>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
@ -314,9 +319,9 @@ directory to which you want to install the PHP files, and <i>--with-cgidir</i>
is the directory to which you want to install CGI files. These directories
could be <i>/var/www/html/zm</i> and <i>/var/www/cgi-bin</i> 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>–with-ffmpeg=&lt;path to ffmpeg
root&gt;</i> to help configure find it. This will be /usr/local if you let ffmpeg
use it’s default options. Note, you have to make sure you have installed the ffmpeg
installed the ffmpeg tools. You can then also use <i>–with-ffmpeg=&lt;path to
ffmpeg root&gt;</i> to help configure find it if it’s not installed in a
default location. 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. Additionally if you have built ffmpeg with the mp3lame feature
turned on you may additionally need to tell configure where to find that the
@ -341,9 +346,9 @@ Type</p>
prompt you by asking you various questions. For most questions typing '?' will
give you additional 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 you just want to rerun the substitutions
you can run zmconfig.pl in non-interactive mode by typing</p>
various files to substitute the information in them. If you run it again it will
remember your answers from. If you just want to rerun the substitutions you can
run zmconfig.pl in non-interactive mode by typing</p>
<p class=MsoPlainText><i>perl ./zmconfig.pl -noi</i></p>
@ -383,7 +388,19 @@ 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.sql and zmalter0.9.10.sql.</p>
zmalter-0.9.8.sql, zmalter-0.9.9.sql and zmalter0.9.10.sql. Additionally 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</p>
<p class=MsoPlainText><i>zmupdate.pl –version=&lt;previous version&gt; [--user=&lt;db
user&gt; --pass=&lt;db password&gt;]</i></p>
<p class=MsoPlainText>where ‘previous version’ releates to the verion 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 ‘user’ and ‘pass’ options allow you to specify a database user and
password with sufficient privilege to ‘alter’ the structure of the database.</p>
<p class=MsoPlainText>For a new installation the simplest way to create your
database and users is as follows,</p>
@ -398,17 +415,17 @@ first password&gt;';</i></p>
<p class=MsoPlainText><i>grant select on &lt;your database name&gt;.* to
'&lt;your second username&gt;'@localhost identified by '&lt;your second
password&gt;'</i></p>
password&gt;';</i></p>
<p class=MsoPlainText><i>quit</i></p>
<p class=MsoPlainText><i>mysqladmin reload</i></p>
<p class=MsoPlainText>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 on a different machine
than that which ZoneMinder is running on then use the hostname of the remote
machine instead of localhost.</p>
<p class=MsoPlainText>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 on a different
machine than that which ZoneMinder is running on then use the hostname of the
remote machine instead of localhost.</p>
<p class=MsoPlainText>Then just type <i>'make'</i> and off you go.</p>
@ -418,36 +435,37 @@ style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span
<p class=MsoPlainText>Once the build has completed you should have several
shiny new binaries. I will now briefly describe what each of them does.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zmc</b> - 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.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zmc</b> - 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.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zma</b> - This is the ZoneMinder
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.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zma</b> - This is the
ZoneMinder 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.</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).</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).</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>
<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>
<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
@ -461,14 +479,15 @@ 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.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zmpkg.pl</b> - 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.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zmpkg.pl</b> - 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.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zmdc.pl</b> - 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.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zmdc.pl</b> - 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.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zmfilter.pl</b> - This
script controls the execution of saved filters and will be started and stopped
@ -501,9 +520,9 @@ to cause this so this script makes sure that nothing important gets missed.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zmupdate.pl</b> – Currently
this script is responsible for checking whether a new version of ZoneMinder is
available and other miscellaneous actions related to upgrades and migrations.
Eventually it is intended to be a ‘one stop shop’ for any upgrades and will
execute everything necessary to update your installation to a new version.</p>
available and other miscellaneous actions related to upgrades and migrations. It
is also intended to be a ‘one stop shop’ for any upgrades and will execute
everything necessary to update your installation to a new version.</p>
<p class=MsoPlainText style='margin-left:18.0pt'><b>zm</b> - This is the
(optional) ZoneMinder init script, see below for details.</p>
@ -543,8 +562,8 @@ and off you go.</p>
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><u>Tutorial</u></h1>
<p class=MsoPlainText>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
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
authenticate 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 ‘admin’ has been created with a password also of ‘admin’.
@ -583,10 +602,10 @@ fill in.</p>
<p class=MsoPlainText>To help you get started on the video configuration the
best thing is to us a tool like 'xawtv' (<a href="http://bytesex.org/xawtv/">http://bytesex.org/xawtv/</a>)
to get a picture you're happy with, and to check your camera works. Then run 'zmu
-d &lt;device_no&gt; -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 then enter these values into the video related
to get a picture you're happy with, and to check your camera works. Then run
'zmu -d &lt;device_no&gt; -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 then 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
@ -594,8 +613,8 @@ permissions run 'zmfix -a' to make sure you can access all the video devices.</p
<p class=MsoPlainText>The options are divided into a set of tabs to make it
easier to edit. You do not have to ‘save’ to change to different tab so you can
make all the changes you require and then click ‘Save’ at the end. The
individual option are explained in a little more detail below,</p>
make all the changes you require and then click ‘Save’ at the end. The individual
option are explained in a little more detail below,</p>
<p class=MonitorTab>‘Monitor’ Tab</p>
@ -784,8 +803,26 @@ 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 view a reasonable time frame pre and post event.</p>
<p class=MonitorOption><b>Alarm Frame Count</b> – 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 if you have statistics recording enabled then currently statistics are not
recorded for the first ‘Alarm Frame Count’-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.</p>
<p class=MonitorTab>‘Misc’ Tab</p>
<p class=MonitorOption><b>Event Prefix</b> – By default events are named ‘Event-&lt;event
id&gt;’, however you are free to rename them individually as you wish. This
option lets you modify the event prefix, the ‘Event-‘ 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. </p>
<p class=MonitorOption><b>Maximum FPS</b> – On some occasions you may have one
or more cameras capable of high capture rates but find that you generally do
not require this performance at all times and would prefer to lighten the load
@ -854,8 +891,7 @@ given number of seconds.</p>
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.</p>
definition it similarly inverts the mode, i.e. the OFF signal activates the monitor.</p>
<p class=MsoPlainText style='margin-left:36.0pt'><u>n-&lt;seconds&gt;</u> : As
per the previous mode except that the monitor will activate itself after the
@ -878,13 +914,13 @@ 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 sent 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 allows 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.</p>
ON signal when going into alarm state and the OFF signal 30 seconds later
regardless of state. The combination of the X10 instruction allows 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.</p>
<p class=MsoPlainText>Finally, click 'Save' to add your monitor.</p>
@ -910,8 +946,7 @@ 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 ’Monitor’,
which will ensure that one or more appropriate daemons are started
automatically.</p>
which will ensure that one or more appropriate daemons are started automatically.</p>
<p class=MsoPlainText>Having a device status of red or orange does not
necessarily constitute an error if you have deliberately disabled a monitor or
@ -983,10 +1018,10 @@ 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>
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
@ -1016,16 +1051,16 @@ little and see what works for you.</p>
zone type is the opposite of Active. In this zone type no alarms will ever be
reported. You can create 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.</p>
relate to what you are trying to monitor. An Inactive zone can overlay other
zone types and will be processed first.</p>
<p class=MsoPlainText style='margin-left:27.0pt'>I mentioned 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 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
<p class=MsoPlainText style='margin-left:27.0pt'>I mentioned 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
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
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>
@ -1038,17 +1073,17 @@ with or if you change image sizes frequently. If you change this setting all
appropriate values below are redisplayed in 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 Point 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 necessary sizes rather easier.</p>
errors, as ZoneMinder in general is not at home to Mr Floating Point 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 necessary sizes rather easier.</p>
<p class=MsoPlainText style='margin-left:27.0pt'><b>Min/Maximum X/Y</b> -
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 maxima are at the bottom right rather
than in a Cartesian style.</p>
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 maxima are at the bottom right
rather than in a Cartesian style.</p>
<p class=MsoPlainText style='margin-left:27.0pt'><b>Alarm Colour </b>- The
option after that allows you to specify what colour you'd like any alarms this
@ -1172,28 +1207,28 @@ expect very brief events. Alternatively you can decrease the refresh interval
for this window in the configuration though having too frequently 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
'All' will give you a full list  and 'Archive' will take you to the event
archive for this monitor, more on this  later. Clicking on any of the column
headings will sort the events appropriately.</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 'All' will
give you a full list  and 'Archive' will take you to the event archive for this
monitor, more on this  later. Clicking on any of the column headings will sort
the events appropriately.</p>
<p class=MsoPlainText>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 per alarm frame as well as the maximum score
that any alarm frame had.</p>
This column lists the average score per alarm frame as well as the maximum
score that any alarm frame had.</p>
<p class=MsoPlainText>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 be much less than 100 but it does give a simple indication of how
major the event was.</p>
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 be much less than 100 but it does give a simple indication of how major the
event was.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>5.4.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Filtering
@ -1338,13 +1373,13 @@ Berkeley MPEG encoder or the faster and new ffmpeg encoder. Either of these
will generate a short video, 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 file 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.</p>
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 file 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.</p>
<p class=MsoPlainText>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
@ -1390,15 +1425,15 @@ assist in creating language files for specific languages. To specify a language
you will have to give 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 ‘*’ 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 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>
which languages are available look for files named zm_lang_*.php in the
ZoneMinder build directory where the parts represented by the ‘*’ 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 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>
<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
@ -1452,7 +1487,7 @@ style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span
<p class=MsoPlainText>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 <a href="http://www.zoneminder.com/faq.html">http://www.zoneminder.com/faq.html</a>
and then the forums at http://<a href="http://www.zoneminder.com/forums">www.zoneminder.com/forums</a>.html
and then the forums at <a href="http://www.zoneminder.com/forums">http://www.zoneminder.com/forums.html</a>
first and see if anyone has had the same problem in the past. If not then feel
free to get in touch and I'll see if I can suggest something else. The best
places to look for errors are in the system error log (normally /var/log/messages
@ -1464,9 +1499,9 @@ you some kind of tip off.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-36.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>Device configuration. If you can't get your cameras to work in 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;
</span></span>Device configuration. If you can't get your cameras to work in
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
@ -1488,13 +1523,13 @@ up afterwards!</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-36.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>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 prevent 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.</p>
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 prevent 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.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-36.0pt'><span
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -1640,10 +1675,10 @@ memory than when it started.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-36.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>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 www.zoneminder.com.</p>
</span></span>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 www.zoneminder.com.</p>
<p class=MsoPlainText>Also, if you are using IE under Windows and get lots of
annoying clicks when various windows refresh then you'll need to edit your
@ -1658,6 +1693,145 @@ Log </u></h1>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.1.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
1.19.5</h2>
<p class=MsoPlainText>Various miscellaneous fixes and features.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – The US English language file was recursively including
itself rather than the UK English file as the base language.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><span style='font-family:
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>LANGUAGE – The Brazilian Portuguese language file detailed in the
previous release has actually been included in this one.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><span style='font-family:
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>LANGUAGE – The Argentinian Spanish, Polish and Italian translations
have all been updated with tokens introduced in version 1.19.3.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – Sorting event lists by duration was broken and has now been
corrected.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – 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.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – The modification suggested by forum user ‘oskin’ has been
incorporated into the code to try and reduce or remove video for linux errors.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – The remote network camera parsing code has been patched to
try </p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – The error reported when a ‘shmget’ call fails has been
changed to include further information about the cause.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><span style='font-family:
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>LANGUAGE – Fixed missing semicolon in German language file.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – Added ‘&lt;&lt;’ and ‘&gt;&gt;’  links to the page
selector in the events list as suggested by forum user ‘<a name=""></a><span
class=name1>unclerichy’</span><span class=name1><b><span style='font-size:8.5pt;
font-family:Verdana'>.</span></b></span></p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – 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 ‘oskin’.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – In previous versions the events folder has been keyed
by the monitor name. This has caused problems in the past 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.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – You may now optionally have thumbnail images in your
event lists. To enable this functionality set ZM_WEB_LIST_THUMBS on in
Options-&gt;Web. You can also control the width or height of these thumbnails but
should only set one dimension only and leave the other blank or zero.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – You can now specify how many image thumbnails appear
across and down the page in the event stills listing. In Options-&gt;Web set
the ZM_WEB_FRAMES_PER_LINE and/or ZM_WEB_FRAME_LINES options.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – ZoneMinder uses ffmpeg (<a
href="http://ffmpeg.sourceforge.net/">http://ffmpeg.sourceforge.net/</a>) 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.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – You can now specify a prefix for events generated by particular
monitors. This will replace the default ‘Event-‘ one.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – 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 ‘&lt;html&gt;’ token,</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – 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 ‘View’ 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 ‘Play All’ link. This will
replay each event and then automatically move onto the next one. You can stop
this progression at any time by pressing ‘Stop’ (which only stops the sequence
and not the currently playing 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 buffering players as the
timing will likely be incorrect. If you are viewing an event but haven’t
checked any in the list the ‘Play All’ button will just work down the current
event list.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 default php error level excluding notice warnings is now
explicitly set.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 – 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 ‘Alarm Frame Count’ 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.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.2.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
1.19.4</h2>
<p class=MsoPlainText>Language fixes and updates.</p>
@ -1674,10 +1848,10 @@ previous release has actually been included in this one.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><span style='font-family:
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>LANGUAGE – The Argentinian Spanish, Polish and Italian
translations have all been updated with tokens introduced in version 1.19.3.</p>
</span></span>LANGUAGE – The Argentinian Spanish, Polish and Italian translations
have all been updated with tokens introduced in version 1.19.3.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.2.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.3.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
1.19.3</h2>
@ -1781,7 +1955,7 @@ by Victor Diago and is available by selecting
</span></span>LANGUAGE – Updated versions of the Dutch and Argentinian Spanish
translations have been included.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.3.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.4.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
1.19.2</h2>
@ -1918,7 +2092,7 @@ language files in English. There will shortly be a point release which includes
these language updates assuming I can get translations of them in a reasonable
timescale.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.4.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.5.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
1.19.1</h2>
@ -1928,8 +2102,8 @@ style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Ffmpeg Configure Changes. The configure script has been modified
to look for the ffmpeg libraries in their installed location rather than in a
build directory. This is to avoid having to build the library when it might
already be installed.</p>
build directory. This is to avoid having to build the library when it might already
be installed.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><span style='font-family:
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -1965,7 +2139,7 @@ in event filters did not generate valid database queries.</p>
pass in a username and password to zmu when just querying a device as this was
slightly broken and was unnecessary anyway.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.5.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.6.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
1.19.0</h2>
@ -2012,10 +2186,10 @@ disappear so I suspect this is a better way to use zms.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><span style='font-family:
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>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 activity was taking place as each captured frame
required its own entry in the database. The frames table has now been
</span></span>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 activity 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 individual frame timings
are interpolated in between. Bulk frames are only used when no alarm or motion
@ -2121,7 +2295,7 @@ deleted when monitor was.</p>
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>A translation for the Dutch (nl_nl) language has been included.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.6.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.7.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
1.18.1</h2>
@ -2145,7 +2319,7 @@ 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.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.7.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.8.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
1.18.0</h2>
@ -2290,7 +2464,7 @@ sometimes 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.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.8.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.9.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
1.17.2</h2>
@ -2372,7 +2546,7 @@ bit annoying so any alarm flag is now cleared when this daemon exits.</p>
</span></span>New Languages. Translations for Japanese (ja_jp), French (fr_fr)
and Russian (ru_ru) are now included.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.9.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.10.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
1.17.1</h2>
@ -2387,14 +2561,14 @@ bug is now fixed.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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 Languages. Two new language files were added. These allow ZoneMinder
to use the German (de_de) and Polish (pl_pl) languages.</p>
</span></span>New Languages. Two new language files were added. These allow
ZoneMinder to use the German (de_de) and Polish (pl_pl) languages.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><span style='font-family:
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Language File Format. The format 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.</p>
to allow the specification of character set and locale as well as have more
flexibility in the calculation of plural forms.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><span style='font-family:
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -2405,7 +2579,7 @@ 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>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.10.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.11.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
1.17.0</h2>
@ -2464,7 +2638,7 @@ corrected.</p>
</span></span>Minor Bugs. A number of minor bugs and inconsistencies were
corrected.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.11.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.12.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
0.9.16</h2>
@ -2482,8 +2656,8 @@ the monitors to have these saved functions and then doing a system restart.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><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
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
@ -2495,9 +2669,9 @@ value to tell it to not record 'n' frames at a time, when not alarmed.</p>
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>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.</p>
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.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><span style='font-family:
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -2518,8 +2692,8 @@ monitoring at a higher screen size where the frame is not adjusted properly.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><span style='font-family:
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>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.</p>
rates allowing faster review (if your bandwidth allows) to long events, or
slower for more precision.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><span style='font-family:
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -2552,8 +2726,7 @@ missing unless they have been explicitly configured to be used.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><span style='font-family:
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>Adaptive Watchdog. zmwatch now more adaptive to actual frame
rates.</p>
</span></span>Adaptive Watchdog. zmwatch now more adaptive to actual frame rates.</p>
<p class=BullettedChar style='text-indent:-35.7pt'><span style='font-family:
"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -2662,7 +2835,7 @@ parsed from command line options passed to zmu.</p>
</span></span>Event window width variable. Event windows now scale to fit the
event image size.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.12.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.13.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
0.9.15</h2>
@ -2717,7 +2890,7 @@ written by zma directly were colourised whereas those written by
A change has been made whereby if set all greyscale JPEG images are colourised
in all circumstances.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.13.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.14.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
0.9.14</h2>
@ -2779,7 +2952,7 @@ style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&n
</span></span>All SQL buffers in the C++ code have been enlarged. There was
previously an issue with a buffer overflow on certain occasions.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.14.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.15.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
0.9.13</h2>
@ -2851,7 +3024,7 @@ from child windows to restart the refresh process. By using JS refresh timers
which are not interrupted these extraneous refreshes have been mostly
eliminated.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.15.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.16.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
0.9.12</h2>
@ -2960,7 +3133,7 @@ style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&n
</span></span>Detect linmysqlclient.a. Added better detection script into
‘configure’ top spot when libmysqlclient.a is missing.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.16.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.17.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
0.9.11</h2>
@ -3077,7 +3250,7 @@ style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&n
colours were just a bit too gaudy so I've toned them down a bit. Hope you like
them!</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.17.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.18.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
0.9.10</h2>
@ -3203,7 +3376,7 @@ style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&n
that that I don't think had been reported or noticed so I don’t think we need
to talk about them here do we.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.18.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.19.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
0.9.9</h2>
@ -3278,7 +3451,7 @@ 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.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.19.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.20.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
0.9.8</h2>
@ -3330,17 +3503,17 @@ up correctly in zmcfg.h.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-36.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>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.</p>
</span></span>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.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-36.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 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.</p>
designed to be (optionally) installed into your init.d directory to use
ZoneMinder as a service.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-36.0pt'><span
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -3401,7 +3574,7 @@ style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&n
active and an alarm has occurred the most recent alarms list is immediately
refreshed to show it.</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.20.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.21.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
0.9.7</h2>
@ -3520,7 +3693,7 @@ separate events view.</p>
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span>And much much more, probably...</p>
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.21.<span
<h2 style='text-indent:-21.75pt'><span style='text-decoration:none'>7.22.<span
style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; </span></span>Release
0.0.1</h2>
@ -3577,7 +3750,8 @@ style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&n
to put a WML interface on to allow you to view event listing and perhaps the
most significant image from each event on your phone. Also simple management.
From version 0.9.7 there is a very basic crude initial version that probably won't
work with your phone but its there as a testbed.</p>
work with your phone but its there as a testbed. Note, this interface is now in
xHTML, or will be when finally released.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-36.0pt'><span
style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
@ -3592,9 +3766,9 @@ style='font-family:"Courier New"'>o<span style='font:7.0pt "Times New Roman"'>&n
image data is held in shared memory in a very simple format. In theory you
could use the capture daemon 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.</p>
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.</p>
<p class=MsoPlainText style='margin-left:36.0pt;text-indent:-36.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.

1882
README.rtf
View File

File diff suppressed because it is too large Load Diff