From 36972a65cb034a5ea296a77004c03da58ae30445 Mon Sep 17 00:00:00 2001
From: stan ^C`8>2@9#hMHC{9(&GRcFCiL7qow2@NI~i{@{i@jIx7kBSCN0LrjM+p
zKds}#*V7?4aATXuKTtn|8pb-DLzOMu?bIzql34Hs7v4ejpx#bC6s30)mZI_=-rGx9
zx{r>tpS#bbPaLE$xPYTy(OC}>l@hxCf`}vZC(J)e+JIx|d7P1Sg4akN{ys}cd4cM8
z{y o
+FIX – The console view has been optimised to speed up display by
+up to a factor of ten. o
FIX – Scaling of stills event views has now been rationalised to
@@ -3770,9 +3775,9 @@ style='font:7.0pt "Times New Roman"'>
FEATURE – Monitors can now be defined with a default scale. This
allows you to reduce the viewing size of a monitor that might be capturing at a
large image size. This works in conjunction with the bandwidth specific scaling
-so if you bandwidth setting is 50% and your monitor is also 50% then at that
-bandwidth you will be viewing at 25%. This is to ensure that all monitors
-maintain relative scaling at all bandwidths.
o @@ -3784,10 +3789,10 @@ style='font:7.0pt "Times New Roman"'> FEATURE – In the past there has been some confusion about what the ‘prev’ and ‘next’ options do when scrolling through events. They actually move to the previous or next event in the list from which the event was -selected rather than in chronological order. Previously this order was -descending date/time in most cases meaning that the previous event would be one -that occurred after the current event. In order to prevent this confusion and -allow users to define a default order which they prefer there are now two more +selected rather than in chronological order. Previously this order was descending +date/time in most cases meaning that the previous event would be one that +occurred after the current event. In order to prevent this confusion and allow +users to define a default order which they prefer there are now two more options in Options->System called ZM_EVENT_SORT_FIELD and ZM_EVENT_SORT_ORDER which allow you to choose your own sort type and order. The default for these is now date/time ascending meaning oldest first which is @@ -4068,16 +4073,16 @@ fixed.
o -LANGUAGE – A translation for the Romanian language has been added. -To use it select ro_ro as the language.
+LANGUAGE – A translation for the Romanian language has been +added. To use it select ro_ro as the language.o FIX – In previous versions the path to the zms daemon from web pages was in the form of a local web path without hostname. This has been -reported as not working with certain media players where the hostname is not implied, -as with browsers. The paths to the streaming server now always have the -hostname prepended so that they are always a full valid url.
+reported as not working with certain media players where the hostname is not +implied, as with browsers. The paths to the streaming server now always have +the hostname prepended so that they are always a full valid url.o @@ -4109,16 +4114,16 @@ style='font:7.0pt "Times New Roman"'> been included. This allows a specified number of frames to be discarded to alleviate problems with broken interlaced frames where multiple cameras share one bttv chip and produce a ‘comb edge’ like image. To invoke this option go to -Options->Config and set ZM_CAPTURES_PER_FRAME to greater than 1, a value of -3 is recommended in the first instance.
+Options->Config and set ZM_CAPTURES_PER_FRAME to greater than 1, a value of 3 +is recommended in the first instance.o FEATURE – Several users have reported problems using the Perl Compatible Regular Expression (PCRE) library, mostly to do with it not being -found or an incorrect version being used. This version allows an alternative -method of parsing the output from network cameras that does not depend on -libpcre at all. Which method is used is controlled by the option +found or an incorrect version being used. This version allows an alternative method +of parsing the output from network cameras that does not depend on libpcre at +all. Which method is used is controlled by the option Options->Network->ZM_NETCAM_REGEXPS. If this option is on then the traditional regular expression based parsing is implemented, provided you have built with libpcre. If the option is off or libpcre is missing then a more @@ -4308,8 +4313,7 @@ zm_config.php.z to work better with different browsers.
o -FIX – Defined empty array in html_view_states to prevent php -warnings.
+FIX – Defined empty array in html_view_states to prevent php warnings.o @@ -4566,8 +4570,8 @@ 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.
+progress single isolated alarmed frames will still prolong it and the count +only applies to the initial frames that would cause the event.o @@ -4721,9 +4725,9 @@ style='font:7.0pt "Times New Roman"'> blocks and disk percentage. These are event independent and return the amount of disk space used on the event partition in terms of disk blocks or percentage as returned by df(1). Thus filters using these criteria will either -match all events or none at all depending on the disk usage at the time of filter -execution. The addition of these terms along with the ability to sort and limit -filter results now means it is possible to create a filter that will +match all events or none at all depending on the disk usage at the time of +filter execution. The addition of these terms along with the ability to sort +and limit filter results now means it is possible to create a filter that will automatically clear out old events once disk usage exceeds a certain value. Included in the database schemas for both new installations and upgrades is a sample filter called PurgeWhenFull which can be used to do this. It is @@ -4747,8 +4751,8 @@ the form <MonitorName>/<EventId> so it it possible to determine both the monitor and event in question from the path. Note also that a flag is set per event as with other auto actions indicating that an executable script has been run on that event and so to exclude it from -subsequent matches. However if you have several filters all with executable -scripts you will find that only the first gets executed as the flag will be set +subsequent matches. However if you have several filters all with executable scripts +you will find that only the first gets executed as the flag will be set following successful completion and so no further scripts will be run on that event. Successful completion is indicated by the script returning a zero exit status, any other status indicates an error and the executed flag will @@ -4825,9 +4829,9 @@ should be made.
style='font:7.0pt "Times New Roman"'> NOTE – None of the non-English language files in this release do not contain any translations of the new, or modified, tokens which have been -introduced in this release. All new or modified tokens are included in the -language files in English. There will shortly be a point release which includes -these language updates assuming I can get translations of them in a reasonable +introduced in this release. All new or modified tokens are included in the language +files in English. There will shortly be a point release which includes these +language updates assuming I can get translations of them in a reasonable timescale.o Pcre Configure Changes. The configure script has been modified to -look for the pcre.h header file in both /usr/include and /usr/include/pcre rather -than just the latter as previously.
+look for the pcre.h header file in both /usr/include and /usr/include/pcre +rather than just the latter as previously.o @@ -4856,9 +4860,9 @@ none at all.
o -Event Image Numbering. An additional configuration option (ZM_EVENT_IMAGE_DIGITS) -has been added to allow the user to define how many significant figures should -be used to number individual event images.
+Event Image Numbering. An additional configuration option +(ZM_EVENT_IMAGE_DIGITS) has been added to allow the user to define how many +significant figures should be used to number individual event images.o @@ -4993,9 +4997,9 @@ for the ZM_FRAME_SOCKET_SIZE option.
o Filter Name Duplication. Following recent changes to the 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 +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 (which is then removed). In general the higher the id number the more recent @@ -5070,8 +5074,8 @@ 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 +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 @@ -5080,8 +5084,8 @@ 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 +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 @@ -5107,8 +5111,8 @@ style='font:7.0pt "Times New Roman"'> Monitor Independent Filters. Previously filters were closely tied to a monitor and a new filter had to be created for each monitor. This has now changed and filters can now specify an associated monitor in the same was as -other parameters. Links have now been added to the main console view to allow -you to view lists of events from all monitors in one and saved filters can now +other parameters. Links have now been added to the main console view to allow you +to view lists of events from all monitors in one and saved filters can now affected as many or as few monitors as you wish. IMPORTANT: Please note that as part of the upgrade process all your filters will have any automatic actions unset. This is because the previous affinity to a particular monitor has now @@ -5137,9 +5141,8 @@ style='font:7.0pt "Times New Roman"'> Montage Sizing. The montage view allows you to view all of your active cameras in one window. However if your cameras are different sizes then this becomes very untidy. You can now constrain the image size of each monitor -in this view to a fixed size with the ZM_WEB_MONTAGE_WIDTH and -ZM_WEB_MONTAGE_HEIGHT configuration options. Monitor images will be enlarged or -reduced as necessary.
+in this view to a fixed size with the ZM_WEB_MONTAGE_WIDTH and ZM_WEB_MONTAGE_HEIGHT +configuration options. Monitor images will be enlarged or reduced as necessary.o @@ -5163,17 +5166,17 @@ style='font:7.0pt "Times New Roman"'> Timestamp Change. Traditionally ZoneMinder has time-stamped each image as it is captured. This ensures that all images have their capture time recorded immediately. However there are several side-effects which may be -undesirable. Firstly the time and resource is spent time-stamping images that are -not recorded and which are discarded, secondly the timestamp is included in any -motion detection and may potentially trigger an alarm if detection parameters -are very sensitive. The third effect is that as the timestamp is added to the -image at it’s native resolution, if the image is scaled then the timestamp is -scaled also. This may not be a problem for enlargement but if the image size is -reduced then it may become illegible. This version now allows you, via the -ZM_TIMESTAMP_ON_CAPTURE configuration option, to indicate whether the -timestamps should be added on capture, as before, or only added when the image -is viewed or recorded. Setting it to this later value allows timestamps to be -added to scaled images. This is little performance impact either way.
+undesirable. Firstly the time and resource is spent time-stamping images that +are not recorded and which are discarded, secondly the timestamp is included in +any motion detection and may potentially trigger an alarm if detection +parameters are very sensitive. The third effect is that as the timestamp is +added to the image at it’s native resolution, if the image is scaled then the +timestamp is scaled also. This may not be a problem for enlargement but if the +image size is reduced then it may become illegible. This version now allows +you, via the ZM_TIMESTAMP_ON_CAPTURE configuration option, to indicate whether +the timestamps should be added on capture, as before, or only added when the +image is viewed or recorded. Setting it to this later value allows timestamps +to be added to scaled images. This is little performance impact either way.o @@ -5287,10 +5290,10 @@ style='font:7.0pt "Times New Roman"'> Release 1.17.1
o @@ -5430,8 +5433,8 @@ slower for more precision.
style='font:7.0pt "Times New Roman"'> Scaleable/Variable MPEG generation. Generation of MPEG videos now also allows you to specify the scale relative to the original image and also -the frame rate. Again, for long events captured in the perpetual recording modes -this will allow a faster review of the period the event covers. +the frame rate. Again, for long events captured in the perpetual recording +modes this will allow a faster review of the period the event covers.o @@ -5451,9 +5454,9 @@ processes.
o -Intelligent Module inclusion. zmfilter.pl now includes Archive::Zip -and other modules on an as needed basis so won't complain about them being -missing unless they have been explicitly configured to be used.
+Intelligent Module inclusion. zmfilter.pl now includes +Archive::Zip and other modules on an as needed basis so won't complain about +them being missing unless they have been explicitly configured to be used.o @@ -5581,11 +5584,11 @@ fixed.
o -Again in .14 a problem occurred for a new release whereby -zmconfig wanted to know the database details and but also previously wanted to -access the database before it had asked the questions. This has now been -addressed though it does require that zmconfig is run twice initially, once to -created the scripts and once to import the configuration into the database.
+Again in .14 a problem occurred for a new release whereby zmconfig +wanted to know the database details and but also previously wanted to access +the database before it had asked the questions. This has now been addressed +though it does require that zmconfig is run twice initially, once to created +the scripts and once to import the configuration into the database.o @@ -5616,10 +5619,10 @@ style='font:7.0pt "Times New Roman"'> A problem was found if using the zmf frame server and greyscale images. The option to colourise JPEG images is intended to be used to ensure that all JPEG files are written with a 24 bit colourspace as certain tools such -as ffmpeg require this. However in the circumstances described above images written -by zma directly were colourised whereas those written by zmf weren’t. A change -has been made whereby if set all greyscale JPEG images are colourised in all -circumstances.
+as ffmpeg require this. However in the circumstances described above images +written by zma 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.o -Y channel bug. When using colour cameras a motion detection problem -was present if fast RGB images deltas (ZM_FAST_RGB_DIFFS) was off. This was an -overflow error in the calculation of the Y channel and caused excessive image -differences to be calculated. This has now been fixed.
+Y channel bug. When using colour cameras a motion detection +problem was present if fast RGB images deltas (ZM_FAST_RGB_DIFFS) was off. This +was an overflow error in the calculation of the Y channel and caused excessive +image differences to be calculated. This has now been fixed.o @@ -5666,8 +5669,8 @@ style='font:7.0pt "Times New Roman"'> 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 matter slightly so these scripts now -access the shared memory directly.
+introduction of user permissions complicated matter slightly so these scripts +now access the shared memory directly.o @@ -5750,7 +5753,8 @@ style='font:7.0pt "Times New Roman"'> themselves rather than a refresh header. Since refresh headers were interrupted if a link of the page was linked there were previously various forced refreshes from child windows to restart the refresh process. By using JS refresh timers -which are not interrupted these extraneous refreshes have been mostly eliminated.
+which are not interrupted these extraneous refreshes have been mostly +eliminated.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 +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 pantheon of zone types I think.
o +allowing you to easily and quickly create MPEG files. This option is one by default +but can be switched off if you do not require any MPEG encoding.
o
@@ -6331,8 +6335,8 @@ style='font:7.0pt "Times New Roman"'>
o
Added Fast delete to PHP files. This allows the web interface to
-only delete the event entries themselves for speed and then have the zmaudit script
-periodically tidy up the rest.
o
@@ -6374,8 +6378,8 @@ style='font:7.0pt "Times New Roman"'>
o
-Split out the PHP files into a bunch with specific functions
-rather than one monolithic one.
o
diff --git a/README.pdf b/README.pdf
index b307fd939c78c8ec7a65749798a4f88c7bbfd881..1edab8a7cf323d44db42a0032c823088c1622263 100644
GIT binary patch
delta 151772
zcmZshV{j(j+wF756Wg|Jn-kl%?cA|#+nLx-Cbn&x6HjoS|MQ+x=hXY2{?zqbd-blX
z`a{=Ry({8Sf5oFFkg>AsG5)l&H#2g!@-{OiVrCR4;$-GzW&BCR%FN2b!Ne#}#L2{{
zK*Ykr&8SMm%EZON&621g3Ch8oSU?G6Ct~`~MPv^T^Y0B4GaDz@|6m-<9RHoMuyXuQ
z#?JEpVH_;~!^_FV_Fqi@|8C66#PYx4|HGJ>nE$((m6MhAzcV%#&i^q88#@zg`t1lf
zUUEMG7L0?7DR~A!D8g;RWXjFVZE9*{V#LB~!o IsSdN*8A@HNIQtuA>fU^R3A=>B3X29l_nU^!I
zzt;g}yUO^M?Bg6)O8NnIdA!CTA*L_l`N8gFYw|}BTCX5fsi`?YXy=rnvu79jIQY`Y
z0r_|F90jkXDA^VeiLce~oXDfp)+CZs-do69JMVaFQBq*2eQcpcn(i=5!;39%&)vX;
zuFwU^O5vd}(b|oS{bOKrY>x=~>nC?O95#Td>_!>p%aSd}b9lfv%}4nT>UX;Lb_se`
zybuL^hX?szH*Up_-hP&g);GoHK76g-@K{E}+bmkJA3V{(=^$+x6`F^hn&vXc#5DBM
zi>uBFUrQ^hyeYpHK5f8&3x6lbYI^nDR68
zidE78Fojy^Ghtz9^E7sl6Y8x&B(jJi_CSoWVhyPPS}`baOyY*ZOt2)Da2gTfj0poc
z0OdOHRTvbL1tH}SHO!!a1AvK96T|_eDuxbZ#4)Hbiw;MBrlAK@NnmPJU@TY{s2t;v
zX@m>+-i|0ZxN0)
J_nTFpVKSCf5^Wp!
zm$n`ijhH!t6I;K9U*B_I>&bkp2M`GQ16IrkCcx59;stYdS~8HRGBP6qft}D$%}o8I
zhmx0}PIhw@W8?LwTgcqU7&ne+;exb!dN2&_0+-HZ?k?3f<%EzP?AZX*+M;U&m#L}v
ze1q|C&?dd3(6(%8JlF|wv0{u_y_0XCsKvUB?Ocj{HLo-Wgwtes7**5p7f)ZqS%Aes
z!c6?xvoSdHRUhN*N353-zcHpiqn?e0lRP%d8>iHxY7j4UEA1i0IB1kWsIonw#n{*;
zi&<89Ior^0|B6N$4Hen;_u1N-oex{-@WIfaduV7|QvX=U)*F^^784BXolH!-rf_M1L~d-%3eHuBCg7Lf54g1$db
zAO7rQ*Q8L4lVE`Fj-@PS^4R&qI2Lm|wtg&-nG%eyH}FsN@|UQ|=%w^O6FZ=*UH!qy
z@RKYPwpa#BldoqVdY^Z%o|c84b`Tncsxwk?0v^17(9GAMpaMQ{jFV-NJX(V@vr3@H
z*+P=z%yC`RRjOxYW^#Oqe&>oqWrvKsG%4jG?
ZQz<4U&KqiUtgj*ZkWrQxI906?Qt0lW4row{I52xbIY0
p
zZz%a-9&G*US$b~Imldx25#K=n-7Fp*(VnpGk*;hcO=wGHoktjq-3~lX{3}J^oei5L
zT?ro)00pw5#UhF)X^k<4JJ?ykfvgp-Ix&mjdn(gsrP&-Qh#AJt#j6$>Y?V?z7$kVe
zP_sy48T*eUuTVO|od9;eG7B{F+Yrm=6w*@cVulb7qVt%D!p98)mTZFg)FDrC6rbOt
zOj8zU1hUPg$>8yd8k&fqYMJ=}sr)+yk|odBv-1ysMAZl9*bx2*NY5l*jOOgsYrcgr9`}?&v<8wY
zcp@w=AL9Yw=@6|ab@Mn;C%Ioem5RJ%x!9E5HHp<*2nOztv@e^M>?$y%hh&r(-c*XMw6j6dT