From 0380f76a14110cb674961c6cf33a3d9bdb8727a0 Mon Sep 17 00:00:00 2001
From: stan
12.11.50< style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext; text-decoration:none'> Release 0.9.1551
+style='color:windowtext;display:none;text-decoration:none'>5212.20.53< style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext; text-decoration:none'> Release 0.9.1154
+style='color:windowtext;display:none;text-decoration:none'>5512.24.57< style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext; text-decoration:none'> Release 0.9.857
+style='color:windowtext;display:none;text-decoration:none'>5812.27.59< style='font-size:12.0pt;font-family:"Times New Roman";color:windowtext; text-decoration:none'> Release 0.0.159
+style='color:windowtext;display:none;text-decoration:none'>60 +style='color:windowtext;display:none;text-decoration:none'>61 +style='color:windowtext;display:none;text-decoration:none'>62 +style='color:windowtext;display:none;text-decoration:none'>63 +style='color:windowtext;display:none;text-decoration:none'>64ZoneMinder is fresh off the keyboard and so comes with no warranty whatsoever, please try it, send your feedback and if you get anything @@ -720,8 +719,8 @@ Please let me know if your camera works and is not listed. You do need to have Video4Linux installed. I've not got too many machines so I've only really used it on various RedHat/Fedora distributions, which seem to have everything there by default I think. SlackWare does need a bit more tinkering than other -distributions; there is a document on the web site describing what users have -had to do to get it working. Please give me feedback on other distributions not +distributions; there is a document on the web site describing what users have had +to do to get it working. Please give me feedback on other distributions not listed on the site.
zmf - 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.
+zmf - 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.
zms - This is the ZoneMinder Streaming server. The web interface connects with this to get -real-time or historical streamed images. It runs only when a live monitor -stream or event stream is actually being viewed and dies when the event -finishes or the associate web page is closed. If you find you have several zms -processes running when nothing is being viewed then it is likely you need a -patch for apache (see the Troubleshooting section). A non-parsed header version -of zms, called nph-zms, is also installed and may be used instead depending on -your web server configuration.
+real-time or historical streamed images. It runs only when a live monitor stream +or event stream is actually being viewed and dies when the event finishes or +the associate web page is closed. If you find you have several zms processes +running when nothing is being viewed then it is likely you need a patch for +apache (see the Troubleshooting section). A non-parsed header version of zms, +called nph-zms, is also installed and may be used instead depending on your web +server configuration.zmu - 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.
+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.zmfix - This is a small binary that exists only to ensure that the video device files can be read by @@ -847,11 +846,11 @@ style='font:7.0pt "Times New Roman"'> &
'action' is 'on', 'off', 'cancel' or ‘show’ where 'on' forces an alarm condition on, 'off' forces an alarm condition off and 'cancel' negates the previous 'on' or 'off'. The ‘show’ action merely updates some auxiliary -text which can optionally be displayed in the images captured by the monitor. -Ordinarily you would use 'on' and 'cancel', 'off' would tend to be used to -suppress motion based events. Additionally 'on' and 'off' can take an -additional time offset, e.g. on+20 which automatically 'cancel's the previous -action after that number of seconds. +text which can optionally be displayed in the images captured by the monitor. Ordinarily +you would use 'on' and 'cancel', 'off' would tend to be used to suppress motion +based events. Additionally 'on' and 'off' can take an additional time offset, +e.g. on+20 which automatically 'cancel's the previous action after that number +of seconds.·
perl ./zmconfig.pl -noi which will just read your file (and later on the
-database) and do the substitutions with no questions asked. There are two
-classes of options, ‘core’ options which much be specified with zmconfig which
-detail things such as database passwords which are compiled into ZoneMinder and
-other options with are stored in the database and which can be modified
-dynamically via the ‘options’ section of the web interface. You only need to
-complete the first set with zmconfig at this stage. If you want to change just
-a few options and can’t access the options dialog via the web you can append
-them as parameters to zmconfig and it will just ask you about those. So for
-example, which will just read your file (and later on the database)
+and do the substitutions with no questions asked. There are two classes of
+options, ‘core’ options which much be specified with zmconfig which detail
+things such as database passwords which are compiled into ZoneMinder and other
+options with are stored in the database and which can be modified dynamically
+via the ‘options’ section of the web interface. You only need to complete the
+first set with zmconfig at this stage. If you want to change just a few options
+and can’t access the options dialog via the web you can append them as
+parameters to zmconfig and it will just ask you about those. So for example, perl ./zmconfig.pl ZM_STRICT_VIDEO_CONFIG
The packaged version of Zone Minder installs all binarys to /usr/lib/zm including the web pages. So don’t worry when you do not see any files installed to the root directory for your -web server. The web pages for Apache are aliased by zm.conf in the apache/conf.d -directory which vary depending on your distribution:
+web server. The web pages for Apache are aliased by zm.conf in the +apache/conf.d directory which vary depending on your distribution:Fedora Core: /etc/httpd/conf.d/zm.conf
@@ -1660,9 +1658,9 @@ and some of its vital statistics. Most columns are also links and you get to other functions of ZoneMinder by choosing the appropriate one. Describing them left to right, they are as follows. -The first column is the Id, clicking on this gives you the -opportunity to edit any of the settings you have just defined your monitor to -have.
+The first column is the Id, clicking on this gives you +the opportunity to edit any of the settings you have just defined your monitor +to have.
The next column is the Name column, clicking on this will give you the watch window where you can view a live feed from your camera along @@ -1698,17 +1696,18 @@ it's something obvious.
up to support them. Once you have one or more monitors you may notice the '<n> Monitors' title becomes a link. Clicking on this link will open up a window which allows you to assign your monitors to groups. These let you select -certain monitors to view. For instance you may only wish to view outdoor monitors -while indoors. You can also choose to view all of them. If you choose a group -then your selection will be remembered via a cookie and will be used until you -change it. You can call your groups anything you like, though ‘Mobile’ has a -special meaning (see Mobile Devices below). There may also be a ‘Cycle’ link -which allows you to cycle through a shot from each of your monitors (in the -selected group unless they are switched off) and get a streamed or still image -from each in turn. Similarly if you see a link titled ‘Montage’ it will allow -you view all your active enabled cameras (in the selected group) simultaneously. -Be aware however that this can consume large amounts of bandwidth and CPU so -should not be used continuously unless you have resource to burn. +certain monitors to view. For instance you may only wish to view outdoor +monitors while indoors. You can also choose to view all of them. If you choose +a group then your selection will be remembered via a cookie and will be used +until you change it. You can call your groups anything you like, though +‘Mobile’ has a special meaning (see Mobile Devices below). There may also be a +‘Cycle’ link which allows you to cycle through a shot from each of your +monitors (in the selected group unless they are switched off) and get a +streamed or still image from each in turn. Similarly if you see a link titled +‘Montage’ it will allow you view all your active enabled cameras (in the +selected group) simultaneously. Be aware however that this can consume large +amounts of bandwidth and CPU so should not be used continuously unless you have +resource to burn.Active : This is the -zone type you'll use most often, and which will be set for your default zone. -This means that this zone will trigger an alarm on any events that occur within -it that meet the selection criteria.
+zone type you'll use most often, and which will be set for your default zone. This +means that this zone will trigger an alarm on any events that occur within it +that meet the selection criteria.Inclusive : This zone type can be used for any zones that you want to trigger an alarm only if at @@ -1756,11 +1755,11 @@ zone if no alarms have already been triggered in Active zones. This is the most specialised of the zone types and you may never use it but in its place it is very useful. For instance in the camera covering my garden I keep watch for a hedgehog that visits most nights and scoffs the food out of my cats bowls. By -creating a sensitive Exclusive zone in that area I can ensure that a hedgehog alarm -will only trigger if there is activity in that small area. If something much -bigger occurs, like someone walking by it will trigger a regular alarm and not -one from the Exclusive zone. Thus I can ensure I get alarms for big events and -also special small events but not the noise in between.
+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.Preclusive : This zone type is relatively recent. It is called a Preclusive zone because if it is @@ -1781,9 +1780,9 @@ alarm thresholds. They should be situated in areas of the image that are less likely to have motion occur such as high on a wall or in a corner. Should a general illumination change occur they would be triggered at least as early as any Active zones and prevent any other zones from generating an alarm. -Obviously careful placement is required to ensure that they do not cancel any genuine -alarms or that they are not so close together that any motion just hops from -one Preclusive zone to another. As always, the best way is to experiment a +Obviously careful placement is required to ensure that they do not cancel any +genuine alarms or that they are not so close together that any motion just hops +from one Preclusive zone to another. As always, the best way is to experiment a little and see what works for you.
Inactive : This final @@ -1798,8 +1797,8 @@ Inactive zones may be overlaid on other zones to blank out areas however as a general principle you should try and make zones abut each other as much as possible and do not overlap. This helps avoid repeated duplicate processing of the same area. For instance an Inclusive zone overlaying an Active zone when -all other settings are the same will always trigger when the Active zone does -which somewhat defeats the object of the exercise. One exception to this is +all other settings are the same will always trigger when the Active zone does which +somewhat defeats the object of the exercise. One exception to this is Preclusive zones. These may be situated within Active areas are they are processed first and if small may actually save processing time by preventing full analysis of the image.
@@ -1943,10 +1942,10 @@ a sound file in the configuration, which will be played when an alarm occurs to alert you to the fact if you are not in front of your computer. This should be a short sound of only a couple of seconds ideally. Note that as the status is refreshed every few seconds it is possible for this not to alert you to every -event that takes place, so you shouldn't rely on it for this purpose if you expect -very brief events. Alternatively you can decrease the refresh interval for this -window in the configuration though having too frequent refreshing may impact on -performance. +event that takes place, so you shouldn't rely on it for this purpose if you +expect very brief events. Alternatively you can decrease the refresh interval +for this window in the configuration though having too frequent refreshing may +impact on performance.Below the status is a list of recent events that have occurred, by default this is a listing of just the last 10 but clicking on @@ -2002,8 +2001,8 @@ that spot. You can also use direct image control for relative motion when the area of the image you click on defines the direction and the distance away from the centre of the image determines the speed. As it is not always very easy to estimate direction near the centre of the image, the active area does not start -until a short distance away from the centre, resulting in a ‘dead’ zone in the -middle of the image.
+until a short distance away from the centre, resulting in a ‘dead’ zone in the middle +of the image.As mentioned above, you may also see a ‘users’ tab in the Options area. In this section you will see a list of the current users defined @@ -2225,12 +2224,12 @@ you do not delete the admin user unless you have created another fully privileged user to take over the same role. Each user is defined with a name and password (which is hidden) as well as an enabled setting which you can use to temporarily enable or disable users, for example a guest user for limited -time access. As well as that there is a language setting that allows you to -define user specific languages. Setting a language here that is different than -the system language will mean that when that user logs in they will have the -web interface presented in their own language rather than the system default, -if it is available. Specifying a language here is done in the same way as for -the system default language described above.
+time access. As well as that there is a language setting that allows you to define +user specific languages. Setting a language here that is different than the +system language will mean that when that user logs in they will have the web +interface presented in their own language rather than the system default, if it +is available. Specifying a language here is done in the same way as for the +system default language described above.There are also four values that define the user permissions, these are ‘stream’, ‘events’, ‘monitors’ and ‘system’ Each can @@ -2263,9 +2262,9 @@ Control
Version 1.21.0 of ZoneMinder introduced a new feature, allowing you to control cameras from the web interface and to some extent automatically. Pan/Tilt/Zoom (PTZ) cameras have a wide range of capabilities -and use a large number of different protocols making any kind of generic control -solution potentially very difficult. To address this ZoneMinder uses two key -approaches to get around this problem.
+and use a large number of different protocols making any kind of generic +control solution potentially very difficult. To address this ZoneMinder uses +two key approaches to get around this problem.1) Definition of Capabilities – For each camera model you use, an entry
@@ -2308,15 +2307,15 @@ Capabilities
If you have a camera that
supports PTZ controls and wish to use it with ZoneMinder then the first thing
you need to do is ensure that it has an accurate entry in the capabilities
-table. To do this you need to go to the Control tab of the Monitor configuration
-dialog and select ‘Edit’ where it is listed by the Control Type selection box.
-This will bring up a new window which lists, with a brief summary, the existing
-capabilities. To edit an existing capability to modify select the Id or Name of
-the capability in question, or click on the Add button to add a new control
-capability. Either of these approaches will create a new window, in familiar
-style, with tabs along the top and forms fields below. In the case of the
-capabilities table there are a large number of settings and tabs, the mean and
-use of these are briefly explained below.
‘Main’ Tab
@@ -2534,8 +2533,8 @@ specified.--address=<address> – This is the control address from the monitor definition. This will -usually be a hostname or ip address for network cameras or a simple numeric -camera id for other cameras.
+usually be a hostname or ip address for network cameras or a simple numeric camera +id for other cameras.--autostop=<timeout> @@ -2729,9 +2728,9 @@ specifically please let me know and I would be pleased to hear about it.
As support for cookies in mobile devices is patchy at best, the groups feature is not fully implemented in the XHTML-MP views. -Instead if there is a group called ‘Mobile’ already defined then that group -will always be effective, if not then all monitors available to the logged in -user will be visible,
+Instead if there is a group called ‘Mobile’ already defined then that group will +always be effective, if not then all monitors available to the logged in user will +be visible,@@ -2760,8 +2759,8 @@ ZoneMinder, firstly make sure that you have the correct settings. Use xawtv or something like that to check for settings that work and then run zmu -d <device_no> -q -v to get the settings. If you can't get them to work with that then the likelihood is they won't work with ZoneMinder. Also check the -system logs (usually /var/log/messages) for any video configuration errors. If -you get some and you're sure they're not a problem then switch off +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.
+with greyscale and if you can't get anything to work let me know and I'll try +and add it.
o @@ -2932,10 +2931,10 @@ little odd but I think what it happening is that as zms picks images out of the shared memory ring buffer to display, as each slot is read the size of that bit of memory is added to the shared memory total for the process. As streamed images are not read consecutively it's a semi-random process so initially most -of the buffer slots are new and the shared memory size grows then as time goes -on the remaining unaccessed slots reduce until once all have been read the -shared memory use caps out at the same size as the actual segment. This is what -I would have expected it to be in the first place, but it seems to do it +of the buffer slots are new and the shared memory size grows then as time goes on +the remaining unaccessed slots reduce until once all have been read the shared +memory use caps out at the same size as the actual segment. This is what I +would have expected it to be in the first place, but it seems to do it incrementally. Then once this total is hit it grows no further. As it's shared memory anyway and already in use this apparent leak is not consuming any more memory than when it started.
@@ -2980,6 +2979,12 @@ style='font:7.0pt "Times New Roman"'> FIX – Fixed a problem where Axis PTZ controls sometimes caused the camera to move in an incorrect direction. +o +FIX – Fixed an issue where the ‘goto preset’ command did not pass +the appropriate preset number (and so defaulted to 1) for the Axis, Panasonic +and VISCA protocols.
+o FIX – A problem existed where renaming monitors did not rename @@ -3016,8 +3021,8 @@ support Iris control.
o -FIX – Fixed a nasty problem in zmaudit which meant that older events -sometimes didn’t get tidied up and deleted properly.
+FIX – Fixed a nasty problem in zmaudit which meant that older +events sometimes didn’t get tidied up and deleted properly.o @@ -3097,9 +3102,9 @@ incident.
style='font:7.0pt "Times New Roman"'> FEATURE – There has long been a dichotomy between the functions that can be applied via interactive filters versus background saved filters. -This release addresses this to some extent allowing you, for instance, to archive -or unarchive matching events, or edit them as described above. This is not a -complete solution and it is expected that the functionality will converge +This release addresses this to some extent allowing you, for instance, to +archive or unarchive matching events, or edit them as described above. This is +not a complete solution and it is expected that the functionality will converge further in the future.o +that that created in the background filter function and it is expected that these +functions will converge at some point.
o @@ -3847,8 +3852,8 @@ re-configure your previous defaults as they will be lost.
o -FEATURE – Filters can now include a specification of the preferred -sort order of the results.
+FEATURE – Filters can now include a specification of the +preferred sort order of the results.o @@ -3991,8 +3996,8 @@ rather than just the latter as previously.
o Remote Image Parsing. Further improvements have been made to -handle additional patterns of images with differing styles of terminations or none -at all.
+handle additional patterns of images with differing styles of terminations or +none at all.o @@ -4040,8 +4045,8 @@ displayed. This can result in the 'live' view being several seconds delayed.
o Motion JPEG Capture. Previously image capture from network -devices has been limited to single stills capture only. This has now changed and -if you entered a remote camera path that returns the multipart/x-mixed-replace +devices has been limited to single stills capture only. This has now changed +and if you entered a remote camera path that returns the multipart/x-mixed-replace MIME type then this will be parsed and images extracted from the stream. This is much faster than before and frame rates can be as fast now with network cameras as with capture cards and video. This feature also has the side-effect @@ -4139,9 +4144,9 @@ duplicate. This resulted in several copies of filters all with the same name as the constraint on unique filter names was not present. Well it is now so when upgrading your database all the filters will be renamed from ‘myfilter’ to ‘myfilter_<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 original name.
+(which is then removed). In general the higher the id number the more recent +the filter. So you should go through your filter list deleting old copies and +then rename the last one back to it’s original name.o @@ -4211,26 +4216,26 @@ that image processing for YUV style input formats are now pretty much handled at almost the same speed as native RGB formats. As this is what the capture daemons spend most of their time doing, the improvement helps reduce the amount of CPU time by a significant degree. Application of these changes also -highlighted a bug that had existed previously in YUV conversion which caused incorrect -conversions for certain values. The other two main areas of optimisation are in -the Blend and Delta image functions. Normally when doing motion detection the -analysis daemons spend about 99% of their time comparing a captured image with -the reference image and then blending the two ready for the next capture. Both -of these functions have been significantly improved. In previous versions there -were two options for calculating image deltas (or differences), a simple RGB -average and a Y channel calculation. Historically the RGB one was faster -however with the optimisations the Y channel calculation (which is more -accurate) is now 15-20% faster and so has become the default though you can -select either method by the ZM_Y_IMAGE_DELTAS configuration option. A new -method of image blending has also been added which is up to 6 times faster than -the old one which is retained for compatibility and because in some unusual -circumstances it may still be more accurate (see the ZM_FAST_IMAGE_BLENDS -option for details). Altogether these optimisations (along with other common -sense ones such as not maintaining a reference image in ‘Record’ mode where it -is not used) significantly reduce the CPU load for most systems, especially -when alarms are not in progress. If an alarm is detected then a lot of file -system and database activity takes place which is limited by the speed of these -resources so the gain will not be as much.
+highlighted a bug that had existed previously in YUV conversion which caused +incorrect conversions for certain values. The other two main areas of +optimisation are in the Blend and Delta image functions. Normally when doing +motion detection the analysis daemons spend about 99% of their time comparing a +captured image with the reference image and then blending the two ready for the +next capture. Both of these functions have been significantly improved. In +previous versions there were two options for calculating image deltas (or +differences), a simple RGB average and a Y channel calculation. Historically +the RGB one was faster however with the optimisations the Y channel calculation +(which is more accurate) is now 15-20% faster and so has become the default +though you can select either method by the ZM_Y_IMAGE_DELTAS configuration +option. A new method of image blending has also been added which is up to 6 +times faster than the old one which is retained for compatibility and because +in some unusual circumstances it may still be more accurate (see the +ZM_FAST_IMAGE_BLENDS option for details). Altogether these optimisations (along +with other common sense ones such as not maintaining a reference image in +‘Record’ mode where it is not used) significantly reduce the CPU load for most +systems, especially when alarms are not in progress. If an alarm is detected +then a lot of file system and database activity takes place which is limited by +the speed of these resources so the gain will not be as much.o
@@ -4374,9 +4379,9 @@ added to the zone definition form to try and prevent bogus or invalid settings.<
o
Diagnostic Zone Images. A regularly requested feature is that of
-adding extra information to allow diagnostics of the process of image detection.
-This has previously been somewhat hit and miss but in this version a new
-configuration option ZM_RECORD_DIAG_IMAGES has been included to allow this.
+adding extra information to allow diagnostics of the process of image
+detection. This has previously been somewhat hit and miss but in this version a
+new configuration option ZM_RECORD_DIAG_IMAGES has been included to allow this.
This option will generate several images for each captured frame in an alarm
including each reference image and a series of images containing the image
differences at various stages in the process. It is not possible to record
@@ -4454,8 +4459,8 @@ style='font:7.0pt "Times New Roman"'>
also available for translation. A guide is included in the language file to
allow this if necessary. Currently language translations exclude the options
settings as this is a rarely accessed area and contains a great deal of text.
-The new format allows individual options to be translated piecemeal as the opportunity
-arises.
o @@ -4533,12 +4538,12 @@ the monitors to have these saved functions and then doing a system restart.
o -New Monitor Functions. Instead of Passive, Active, and X10, the modes -are now Monitor (= old Passive) which just allows you to watch the feed, Modect -(= old Active) which is MOtion DetECT and which will capture events as -previously, Record which continuously records with no analysis and MoCord which -is a hybrid of Modect and Record and which will continuously record but also do -motion detection and highlight where this has occurred. The Record and Mocord +New Monitor Functions. Instead of Passive, Active, and X10, the +modes are now Monitor (= old Passive) which just allows you to watch the feed, +Modect (= old Active) which is MOtion DetECT and which will capture events as previously, +Record which continuously records with no analysis and MoCord which is a hybrid +of Modect and Record and which will continuously record but also do motion +detection and highlight where this has occurred. The Record and Mocord functions both records events whose length in seconds is defined by the 'Section Length' monitor attribute. You can additionally specify a 'Frame Skip' value to tell it to not record 'n' frames at a time, when not alarmed.
@@ -4870,12 +4875,12 @@ was broken. This is now fixed. style='font-family:"Courier New"'>o New contrast/brightness etc adjustments feature. This accessible from the Settings link on the monitor window. It's fairly basic at present but -should work for most types of cameras. If you have any device or driver -specific auto-brightness, auto-contrast etc enabled the changes you make may -appear to work but may be overridden by the auto feature immediately so check -for that if your changes do not appear to be having an effect. Also if you have -a number of cameras being multiplexed onto one device then any changes here -will probably affect all your cameras. +should work for most types of cameras. If you have any device or driver specific +auto-brightness, auto-contrast etc enabled the changes you make may appear to +work but may be overridden by the auto feature immediately so check for that if +your changes do not appear to be having an effect. Also if you have a number of +cameras being multiplexed onto one device then any changes here will probably +affect all your cameras.o @@ -4942,10 +4947,10 @@ long to wrap in this way.
o -Fixed round detection problem. Although the existence or otherwise -of the ‘round’ function is correctly detected, the appropriate header file with -the results of this test was not included which was not helpful. This has been -corrected.
+Fixed round detection problem. Although the existence or +otherwise of the ‘round’ function is correctly detected, the appropriate header +file with the results of this test was not included which was not helpful. This +has been corrected.o @@ -4966,8 +4971,8 @@ based on the length of the event and the number of frames it contains. Previously it did not take account of the pre and post event frames and so passed a much shorter value to the mpeg encoder than it should. This will only have affected short events encoded with ffmpeg but will have resulted in much -faster frame rates than necessary. This has now been corrected to take the whole -event length into account.
+faster frame rates than necessary. This has now been corrected to take the +whole event length into account.o @@ -5036,15 +5041,15 @@ style='font-family:"Courier New"'>o&n New video palette support – As well as the existing greyscale and 24 bit RGB palettes, you can now choose YUV420P and RGB565. Rewrote the palette/colours area a bit to enable support for other palettes in the future -if requested. Bear in mind though that YUV palettes are converted into RGB internally -so if you have the choice RGB24 may be faster as it's the 'native' format used -within.
+if requested. Bear in mind though that YUV palettes are converted into RGB +internally so if you have the choice RGB24 may be faster as it's the 'native' +format used within.o Added preclusive zones – Added a new zone type, the preclusive -zone. For full details see the relevant section above but in brief this is a -zone type that if alarmed will actually prevent an alarm. This completes the +zone. For full details see the relevant section above but in brief this is a zone +type that if alarmed will actually prevent an alarm. This completes the pantheon of zone types I think.
o&n Source file restructuring - The source files have been broken up and renamed extensively to support the first stage of the code being straightened out. Likewise the class structure has been rationalised somewhat. -The php file names have also changed in some cases so it might be best to delete -all your php and css files from the zone minder install directory first as the -old ones won't be overwritten and will be left behind.
+The php file names have also changed in some cases so it might be best to +delete all your php and css files from the zone minder install directory first +as the old ones won't be overwritten and will be left behind.o @@ -5277,9 +5282,9 @@ directory was not created on install, this has been fixed.
o -Can now retag PHP files if necessary - Version 0.9.8 was the -first version to use short_open_tags in the PHP files. This caused grief to -some people so this script will put them back to the long verion.
+Can now retag PHP files if necessary - Version 0.9.8 was the first +version to use short_open_tags in the PHP files. This caused grief to some +people so this script will put them back to the long verion.o
diff --git a/README.pdf b/README.pdf
index 5d5a4fb7a3a6651b8c813f8e3e4d4050c2ee7f4d..6690b6f4b2cf0871a91d17e34c1047191c8d8509 100644
GIT binary patch
delta 153364
zcmbSxW0+>kvS!(~-K8$u=(26wHorobU0;{oW!tvh)n(hZrqAAc?sI1D%rp1S`jsm(
z W@)MZ8LKYW;Wqk03$8
zJ$PmEOS9O39D$lq%O}LD)IF++NLdUZ?+bBjW{GfmgqE@{T@_(EN2N{2#?Ga;93#72
z*TYJ)5Sp15A9%V#>;f`%!D|x9`@w91;Xveyx9kBSfL1yLl;CroEfo*EfQNeZLpvh=W
zfc3ozJQ&L?ciSM#w4Ek=V7
7Vf>gwu~=2?Q=qqf`;9355bJfh-k>ass$^
zWUd33qGzRw&tgBDaAn&KvXfFyvaV_{Ax*OYC~^Z2ca^_!BBu<9ngt>~NtfJl=z=0E
z(-MB!Qno41m1q_oSEJ1Vm2Yf|^k}Gr8&?FZ%H9V!u6%y4$x@bF5u;C=moQ__d@cSgEP@+s!I&6`wml~VD^fsrU
z{UWUuiv=r#9PoDNcnZX^tz;0kikxT+BMeUHKmR7$_C94Y*lt4H=H6*w*7AU>YnGOK
zB6yVH=J=iC&Pt`&@$3?%bGUfZ!@{;5oukVj%nt*>Bq7A48w>%Yzt`~o@5~;xA;aH^
z>vY5an9Kinx`6vny5O(#+CS+6Mx!y%>-ra?I|PWWl9Ye);ZP3$z$$WQCP+AP@KR?FPd`>^7@9;UMc;*0t}y819ssuK={W^vU@k#4$X{J
zgftUS7!>;H>Vz#a-~9z#7vvkE;ZBOr_0q1nf;Wp4gXx3`dgmMHw5Tp0G@I{@$bxed
z_pMaGIJ(pV^?aH6CU#uBZkfL7`3hbxt07mMP~iJ!+HM}BmoK#fr=^iY`NyZI*I7C(
zh^Zr}0Xs7-wiOoYaPXY>;7XH9$dj?>Zu3X*r*Vn=h;SP%(_jnfUHB(NhB4>Ahl1@P
zu%*&o)rI?M%u&S(`3t<~rg0cf*#om1t$p0Nr6s}Q&O?*^_)$x!J=1$HsTGaUe+~6T
z@YOpu+CQH3Od~>@oAtJ56TRfKAmK9Gz++$Y0mkRJGjX<+vGv9af@<2JAFP=8fp*CI
zJzQ$#-fHX&>o`YvN!K=i@@wM{r7UGd@wT}l8b%98St<)iYV*3sVrEOgH5=-nS=sxF
zP|31dJ*#Z_JLsTx5jYQNJsA_~F}(#1$0A?DHWRobBUWstaxK2#@L{e9X;2JUnEK%k
zK&hdlcjdH(@gb!=m#i(bg1fo^?*VhKFMq55oq@NEsL&}TgErK;D%GjJhv<7Ewi(9q
zOwiXK%hx}XQWh4gE37@9v}}BWWu4{?R*pA48{{C!Q&LRYMlmdnWS}s{TT_qvKdc+^
zl7>sAECauTgUz)D8N`+e)J0k28HVHL0&L!EPiQWtZ^qO+r-Gu+DMoa$idntB$)f7W
zLim7XXHB)8exWQ2>ql)BI&5gOVB%gcRO$RKtsA(@bZ-AbaFZT8`-5{*#<0vHK>a+3
zF7tiyK9eW$ssv?p@|PBl47PR9`IPKnPE|#BHcgqB4hU*6-ZB*>=qHYEu)vSrV?Y;7
z+4Rk887L}a9d%dQ68An%@N8f&=qNr-KcNHUiG_bZ6sMpPQEMr{V#2YnC8Cm}T03Vd
z=B&`jJokA8nX8 <@MvblW?Xg^Z^6j96di|gMYUv*1N6>YHka<%wmi=DLz4r7XB`99*jge!4OJqkYV;om!k4RrM792t$oMmKmS{obYSZLUdVM8V|2@?rA^
z
$6e>SOKyicP=EB-5tMcB@Q*$0Dj18*k*%q!Su5Yx|w8?
zjJ9oj)=oGOgb*A!cFVB9#y-;9GU_FJdcSc{R>yt5i)%SW0&@lC9R&n3;;GKCGN|*Q
z<7#w!f#v}Eyul$=OLkZCS47c8^SwJq_PzZW49hluGfB6R1CkHr#EwOas8m`8t?Yv_GU_3>
zEsHUTZ*-%vn9}kv3=|4ihz8Jqf8g%*(6Spmy5bVpZKkK!(vPea6y~v)fSf