ZoneMinder Wiki - User contributions [en]

MobileDevices

2015-01-11T14:42:05Z

Gkmac: Undo SPAM revision 6516 by Erictenne (talk)

Please Post Your Device Model

== Working Under Normal ZM interface ==
'''Motorola'''
Rizer Z3 (opera mini only)

'''Apple'''
iPhone 3G
iPhone 2G (WiFi tested)

'''Nokia'''
N810

Android 2.2
with swf mpeg streaming

== Working Under Xhtml ==
http://example.com/zm/index.php?format=xhtml

Version newer than 1.23.3 use: http://example.com/zm/index.php?skin=mobile

'''Motorola''' Rizer Z3, V300,V330,Razer

'''Blackberry''' Perl

'''HTC''' ProTouch II

== Working under XML Interface ==

XML Plugin is available with 1.24.3 onwards, or as a separate download for 1.24.1 and 1.24.2 from http://www.eyezm.com
It is intended for use with the eyeZm iPhone Application, but can be used with any other custom programs as well.

http://example.com/zm/index.php?skin=xml...

'''Apple'''
iPhone and iPod Touch on iOS 4+

== Not Working ==

http://192.168.0.254/Set?Func=VDelivery&Kind=1&640framerate=30

UDP Technology NCP3200v2

2014-10-10T11:03:18Z

Gkmac: Add kernel 3.14 patch that allows 16 channel input

[[File:Ncp3200v2front.jpg|right|500px|thumb|NCP3200v2 capture card - front view]]
== Introduction ==
The UDP Technology NCP3200v2 is a PCI card with 16 video inputs and 8 Conexant Fusion 878A (also known as BT878) chips.

Manufacturers website: http://www.udptechnology.com/products/PC/NCP3200V2.html

The card has 2 DE-15 (VGA shaped) sockets. Each is fitted with a cable which branches out into 8 yellow BNC connectors which are labelled <tt>VIDEO 1(9)</tt>, <tt>VIDEO 2(10)</tt> and so on up to <tt>VIDEO 8(16)</tt>.

== Linux usage ==
The card is not properly supported with the bttv driver, but it is possible at present to use 4 of the 16 video inputs without having to patch the kernel.

Alternatively there is an experimental patch for 3.14 kernels which should allow all 16 video inputs to be used.

=== Using an unpatched kernel for 4 inputs ===
To use the card with an unpatched kernel, create the file <tt>/etc/modprobe.d/bttv.conf</tt> with the line below.
options bttv gbuffers=32 card=158,158,158,158,158,158,157,157
This tells the driver that a Geovision GV-800 card is present but unlike the GV-800 the "master" card needs to be the ''last'' 2 numbers, as the multiplexers are controlled by the last 2 detected 878A chips.

Using the above, the 4 working inputs will be spread across the /dev/video's as shown in the table below. All these inputs are on the bottom socket furthest from the yellow RCA connector.

Changing the device channel on any of the inputs will have no effect.
{| border="1" cellspacing="0" align="center"
|-
! Path
! Socket
|-
| /dev/video0
|rowspan="2"| <tt>VIDEO 4(12)</tt>
|-
| /dev/video1
|-
| /dev/video2
|rowspan="2"| <tt>VIDEO 3(11)</tt>
|-
| /dev/video3
|-
| /dev/video4
|rowspan="2"| <tt>VIDEO 2(10)</tt>
|-
| /dev/video5
|-
| /dev/video6
|rowspan="2"| <tt>VIDEO 1(9)</tt>
|-
| /dev/video7

|}

=== Patching the kernel for 16 video inputs ===
At present there is a patch that is suitable for 3.14 kernels only. Patches suitable for other kernel versions may be added later.

With this patch, all 8 /dev/video's can be switched to any of the 16 inputs by changing the device channel. Device channels 0 to 7 are on the bottom socket furthest from the yellow RCA connector, channel 0 corresponds to <tt>VIDEO 1(9)</tt>, channel 1 is <tt>VIDEO 2(10)</tt> and so on. Device channels 8 to 15 are on the top socket next to the yellow RCA connector, channel 8 corresponds to <tt>VIDEO 1(9)</tt>, channel 9 is <tt>VIDEO 2(10)</tt> and so on.

The card numbers to put into <tt>/etc/modprobe.d/bttv.conf</tt> will be different across each kernel version.

==== Patch for 3.14 kernel ====
options bttv gbuffers=32 card=166,166,166,166,166,166,165,165
<pre>
diff -uNrp kernel-3.14.orig/drivers/media/pci/bt8xx/bttv-cards.c kernel-3.14.new/drivers/media/pci/bt8xx/bttv-cards.c
--- kernel-3.14.orig/drivers/media/pci/bt8xx/bttv-cards.c 2014-10-09 18:47:03.413696227 +0100
+++ kernel-3.14.new/drivers/media/pci/bt8xx/bttv-cards.c 2014-10-09 18:47:21.471991344 +0100
@@ -80,6 +80,9 @@ static void phytec_muxsel(struct bttv *b
static void gv800s_muxsel(struct bttv *btv, unsigned int input);
static void gv800s_init(struct bttv *btv);

+static void udp3200_muxsel(struct bttv *btv, unsigned int input);
+static void udp3200_init(struct bttv *btv);
+
static void td3116_muxsel(struct bttv *btv, unsigned int input);

static int terratec_active_radio_upgrade(struct bttv *btv);
@@ -2855,6 +2858,46 @@ struct tvcard bttv_tvcards[] = {
.tuner_type = TUNER_ABSENT,
.tuner_addr = ADDR_UNSET,
},
+ [BTTV_BOARD_UDP_NCP3200] = {
+ /* UDP Technology NCP3200v2 has 8 Conexant Fusion 878A:
+ * 2 video inputs per BT878A = 16 video inputs
+ * These are the last 2 BT878A chips of the NCP3200v2. These are
+ * "master" chips and they control the video inputs through 2
+ * analog multiplexers (MT8816P) via some GPIO pins. The
+ * slaves should use card type 0xa6 (following this one).
+ */
+ .name = "UDP Technology NCP3200v2 (master)",
+ .video_inputs = 16,
+ .tuner_type = TUNER_ABSENT,
+ .tuner_addr = ADDR_UNSET,
+ .svhs = NO_SVHS,
+ .gpiomask = 0xf107f,
+ .no_gpioirq = 1,
+ .muxsel = MUXSEL(2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2),
+ .pll = PLL_28,
+ .no_msp34xx = 1,
+ .no_tda7432 = 1,
+ .muxsel_hook = udp3200_muxsel,
+ },
+ [BTTV_BOARD_UDP_NCP3200_SL] = {
+ /* UDP Technology NCP3200v2 has 8 Conexant Fusion 878A:
+ * 2 video inputs per BT878A = 16 video inputs
+ * The 6 other BT878A chips are "slave" chips of the NCP3200v2
+ * and should use this card type.
+ */
+ .name = "UDP Technology NCP3200v2 (slave)",
+ .video_inputs = 16,
+ .tuner_type = TUNER_ABSENT,
+ .tuner_addr = ADDR_UNSET,
+ .svhs = NO_SVHS,
+ .gpiomask = 0x00,
+ .no_gpioirq = 1,
+ .muxsel = MUXSEL(2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2),
+ .pll = PLL_28,
+ .no_msp34xx = 1,
+ .no_tda7432 = 1,
+ .muxsel_hook = udp3200_muxsel,
+ },

};

@@ -3407,6 +3450,9 @@ void bttv_init_card2(struct bttv *btv)
case BTTV_BOARD_GEOVISION_GV800S:
gv800s_init(btv);
break;
+ case BTTV_BOARD_UDP_NCP3200:
+ udp3200_init(btv);
+ break;
}

/* pll configuration */
@@ -4842,6 +4888,73 @@ static void gv800s_init(struct bttv *btv
master[btv->c.nr+3] = btv;
}

+/*
+ * UDP Technology NCP3200v2 functions
+ *
+ * adapted from GeoVision GV-800(S), reuses gv800s_write
+ *
+ * Each of the 4 cards (controllers) use this function.
+ * The controller using this function selects the input through the GPIO pins
+ * of the "master" card. A pointer to this card is stored in master[btv->c.nr].
+ *
+ * The parameter 'input' is the requested camera number (0-15) on the controller.
+ * The map array has the address of each input.
+ *
+ * After getting the input address, the function then writes the appropriate
+ * data to the analog switch, and housekeeps the local copy of the switch
+ * information.
+ */
+static void udp3200_muxsel(struct bttv *btv, unsigned int input)
+{
+ struct bttv *mctlr;
+ int xaddr, yaddr;
+ static unsigned int map[16] = { 0, 1, 2, 3, 4, 5, 8, 9,
+ 10, 11, 12, 13, 6, 7, 14, 15 };
+ input = input%16;
+ mctlr = master[btv->c.nr];
+ if (mctlr == NULL) {
+ /* do nothing until the "master" is detected */
+ return;
+ }
+ yaddr = (mctlr->c.nr - btv->c.nr) >> 1;
+ xaddr = map[input];
+
+ /* Check if the controller/camera pair has changed, ignore otherwise */
+ if (mctlr->sw_status[yaddr] != xaddr) {
+ /* disable the old switch, enable the new one and save status */
+ gv800s_write(mctlr, mctlr->sw_status[yaddr], yaddr, 0);
+ mctlr->sw_status[yaddr] = xaddr;
+ gv800s_write(mctlr, xaddr, yaddr, 1);
+ }
+}
+
+/* UDP Technology NCP3200v2 "master" chip init */
+static void udp3200_init(struct bttv *btv)
+{
+ int ix;
+
+ gpio_inout(0xf107f, 0xf107f);
+ gpio_write(1<<19); /* reset the analog MUX */
+ gpio_write(0);
+
+ /* Preset camera 0 to the 4 controllers */
+ for (ix = 0; ix < 4; ix++) {
+ btv->sw_status[ix] = ix;
+ gv800s_write(btv, ix, ix, 1);
+ }
+
+ if (btv->c.nr < 6)
+ return;
+ /*
+ * Store the "master" controller pointer in the master
+ * array for later use in the muxsel function.
+ */
+ master[btv->c.nr-6] = btv;
+ master[btv->c.nr-4] = btv;
+ master[btv->c.nr-2] = btv;
+ master[btv->c.nr] = btv;
+}
+
/* ----------------------------------------------------------------------- */
/* motherboard chipset specific stuff */

diff -uNrp kernel-3.14.orig/drivers/media/pci/bt8xx/bttv.h kernel-3.14.new/drivers/media/pci/bt8xx/bttv.h
--- kernel-3.14.orig/drivers/media/pci/bt8xx/bttv.h 2014-10-09 18:46:56.564825771 +0100
+++ kernel-3.14.new/drivers/media/pci/bt8xx/bttv.h 2014-10-09 18:47:14.579115295 +0100
@@ -188,6 +188,8 @@
#define BTTV_BOARD_ADLINK_MPG24 0xa2
#define BTTV_BOARD_BT848_CAP_14 0xa3
#define BTTV_BOARD_CYBERVISION_CV06 0xa4
+#define BTTV_BOARD_UDP_NCP3200 0xa5
+#define BTTV_BOARD_UDP_NCP3200_SL 0xa6

/* more card-specific defines */
#define PT2254_L_CHANNEL 0x10
</pre>

Change History

2014-10-03T18:02:37Z

Gkmac: Undo SPAM revision 6419 by Erictenne (talk)

==Change History aka ChangeLog==
===Release 1.25.0 - 2011/08/26===
Major release focused primarily on total revamp of logging and debug.
* FEATURE - Logging and debug have been completely refreshed and now (by default) log entries are stored in the database. Classic skin now features a 'log' view which uses the stored database entries and combines the output of all components in one place. This view can be filtered or exported and dynamically updates as new entries are created. The 'Debug' options tab is now renamed to 'Logging' and includes several new settings. All components have been tidied up and use consistent interface for all logging and error reporting. The system also monitors the frequency of warnings and errors to produce an overall indication of system health.
* FEATURE - Events can now be uploaded using SFTP instead of regular FTP. This allows for more secure and flexible uploading. The FTP options tab is now renamed Upload and contains additional options.
* FIX - Fixed Local File Inclusion (LFI) vulnerability. Please note a patch for this is also available for 1.24.4 which the 1.24.4 tarball also contains for recent downloads.
* FIX - Fixed issue with video generation failing in background filters when using absolute event paths.
* FIX - Fixed problem with 'in set' clauses in filters when run in the background.
* FIX - Fixed issue with deleted events not always getting cleaned up from file system.
* FIX - Fixed problem with some IP cameras using single images and not issuing a Content-length header.
* LANGUAGE - Spanish translation has been updated.
* MISC - Updated to use 1.3.x Mootools javascript libraries.
* MISC - Removed support for very old versions of ffmpeg libraries.

===Release 1.24.4 - 2011/05/30===
Follow-up release. Contains mostly upgrade and convenience improvements as well as a small number of important config and system management fixes.
* FEATURE - Changed all system components to use JSON syntax for serialization. This removes the dependency on the rarely supported PHP::Serialization perl module. Basic JSON encoding and decoding functionality is included where support packages are not installed. Please note that it is critical that you run zmupdate.pl in order to convert your saved filters.
* FEATURE - The zmupdate.pl now automatically determines the version to upgrade from where possible. This removes the necessity to supply the -v parameter in most cases.
* FEATURE - The classic view console and zmpkg.pl scripts now both detect and report when code and database versions do not match. The system will not start if this is the case and the version number in the console will be highlighted red.
* FEATURE - Temporary directories are recreated on startup if necessary.
* FIX - Fixed issue where someconfiguration was given blank values causing various bogus config messages and javascript errors in the web interface.
* FIX - Protect system temporary and log directories from change of ownership on install and deletion attempts on uninstall.
* FIX - Manage memory connection handles to avoid exhaustion. Thanks for forum user mastertheknife for tracking this one down.
* TRIVIAL - Further information has been added to the WEB_x_SCALE_THUMBS config options to indicate that the appropriate PHP graphics package needs to be installed for this functionality to work.

===Release 1.24.3 - 2011/05/16===
Long delayed point release. Brought up-to-date to work with new versions of ffmpeg etc. A number of new features are included and several important bugfixes. A new contributed iPhone skin is also included.
* FEATURE - Add config (Options -> Config -> V4L2_CAPTURE_FIELDS) to allow better control of interlacing (or not) of Video4Linux2 cameras. Currently only on a global basis.
* FEATURE - Added ability to move to PTZ presets from mobile view.
* FEATURE - Added contributed iPhone interface (thanks to user Jai Dhar). Use skin 'EyeZM' to try
* FEATURE - Added more camera presets
* FEATURE - Added new Panic debug call for entirely unexpected occurances. Changed some Fatal calls to Panic, only the latter generate stack traces or core dumps.
* FEATURE - Allow specification of RUNDIR, TMPDIR and LOGDIR as environment variables to configure. This allows completely partitioned installs provided user permissions etc are correctly set up
* FEATURE - Changed build procedure to make it easier to import values from config.
* FEATURE - Ensure that paths specified as arguments to configure are correctly propagated to all elements of the system
* FEATURE - Event path now no longer is required to be under web root, so can be placed outside of web root altogether to prevent image browsing by unauthenticated users.
* FEATURE - Now works with current ffmpeg git snapshot
* FEATURE - Improved event functions (thanks for user John Resig for contribution).
* FEATURE - Mapped memory (versus shared) is now the default.
* FEATURE - Modified to handle systems where only Video4Linux2 is installed, with no V4L1
* FEATURE - Streaming detection and control is now on a bandwidth basis rather than global.
* FEATURE - If a monitor group is selected and a new monitor added, it will automatically be added to that group.
* FEATURE - Improved process control and tidying on monitor creation and deletion.
* FEATURE - Audit functionality now checks for greater range of DB inconsistencies.
* FEATURE - Database config changes are now automatically applied on system restart.
* FEATURE - The zmdc.pl script has now been restructured be more reliable.
* FEATURE - Configuration is now regenerated automatically on running 'configure' script.
* FEATURE - Video generation and download is more reliable with additional HTTP headers.
* FEATURE - Updated to latest 1.2 branch of mootools
* FEATURE - Included sample apache, logrotate and syslog configuration files in misc directory
* FIX - Changed default signal loss detection colour
* FIX - Changed name of memory map files to not be hidden files.
* FIX - Changed names of jpeg memory function to not clash with new 'official' functions for the same kind of operation
* FIX - Corrected some compiler warnings
* FIX - Corrected some obscure failure scenarios in zmaudit
* FIX - Corrected some request queueing issues in Ajax calls
* FIX - Fixed detection issues with zmfilter when archiving to zip files
* FIX - Fixed issue on USB cameras where failure to query crop settings was fatal.
* FIX - Fixed issue where events could sometimes be created with unitialiased time, so would appear to be from 1970 (or 1969 if West of 0 degrees Lat).
* FIX - Fixed issue with libgcrypt complaining about application not initialising library.
* FIX - Fixed minor issues with trigger connections and channels
* FIX - Fixed some DB column dimensions to better match real world values
* FIX - Fixed various minor HTML errors
* FIX - For HTTP 1.0 remote cameras, do not send 1.1 headers
* FIX - For HTTP remote cameras, failure to fetch image is not necessarily fatal to process
* FIX - Improved alarm handling in montage view
* FIX - Improved detection of signal loss in cameras.
* FIX - Improved functioning of web PTZ controls
* FIX - Fixed issue with unarchiving events.
* FIX - Improved layout and window size of options related web windows.
* FIX - Modified some buffer lengths to not use BUFSIZ which is platform dependent
* FIX - Corrected some instances in scripts where custom shell execution methods were called
* FIX - Now checks for more external libraries during configure
* FIX - Removed custom typedefs and use ones from stdint where applicable
* FIX - Replaced some deprecated PHP function calls with more recent equivalents
* FIX - Removed some redundant configuration
* FIX - Updated some calls to ffmpeg deprecated functions
* FIX - Updated to match ffmpeg updates
* FIX - Removed support for PHP version 4.1.0 and older
* FIX - Ffmpeg monitors now detects camera restart or disconnection more reliably.
* LANGUAGE - Added Estonian translation, thanks to user Seston
* LANGUAGE - Updates to Italian translation
* TRIVIAL - Changed some die calls to error_log to capture reasons

===Release 1.24.2 - 2009/06/29===
Point release with usual mix of new features and fixes and tweaks.
* FEATURE - Added facility to probe when adding new monitors. This will potentially detect attached local devices and network cameras (of major manufacturers) and suggest sensible defaults.
* FEATURE - SDP parsing of MPEG streams etc is now done in ZoneMinder rather than ffmpeg. This means that more information can be deduced so the monitor sub path parameter is now longer necessary.
* FEATURE - Added support for different Video4Linux versions to zmu
* FEATURE - Added patch contributed to improve performance under IE and also better detection of stream termination in zms.
* FEATURE - Added better support for localised installs by allowing scripts to reference local copies of the perl modules instead of the system ones if required.
* FEATURE - Added incremental naming scheme for new monitors, plus more sensible defaults
* FEATURE - Updated to use version 1.2.1 of Mootools.
* FIX - Various RTSP/RTP fixes to improve reliability and crash resistance.
* FIX - Fixed problem with run states not correctly starting when coming out of states with disabled cameras.
* FIX - Removed some troublesome references to #defines from ffmpeg that were causing issues for people with different versions.
* FIX - Corrected local camera presets to account for Video4Linux versions
* FIX - Corrected various layout issues in montage and event stills views.
* FIX - Addressed various issues with Ajax and communications with stream processes
* FIX - Added contributed patch to reset camera settings to saved values on restart
* FIX - Corrected various outstanding PHP warnings.
* FIX - Various minor web issues and misformatting corrected.
* LANGUAGE - Fixed issue with trailing white-space in language files causing issues with headers.
* LANGUAGE - Added cn-zh Chinese language file.

===Release 1.24.1 - 2009/02/23===
Wrap-up release addressing a number of issues discovered in 1.24.0 plus a handful of new features.
* FEATURE - Allows shortcut logins on any page of web interface via passing of 'auth' hash as currently passed to zms. This must be explicitly enabled via AUTH_HASH_LOGINS option, read the help text of that option for more details.
* FEATURE - Changed exit message on forced aborts, issues addr2line command to execute when exiting abnormally to logs.
* FEATURE - Added V4L_MULTI_BUFFER option to control amount of buffering used by capture cards with multiple inputs per chip. Please read the option help text for more information.
* FEATURE - Improved debug on event creation and closing to make clearer why/when events are starting and stopping.
* FEATURE - Improved buffer overrun handling to detect and output when this is caused by analysis daemon not processing images.
* FIX - Multiple updates to Video 4 Linux 2 handling for analog cameras.
* FIX - Fixed issue with greyscale analog cameras not functioning properly.
* FIX - Fixed problem with EXTRA_DEBUG_TARGET not working properly for some targets.
* FIX - Issue with RTSP basic authentication not picking up supplied username and password properly corrected.
* FIX - Added missing guard ifdefs in zm-debug.h to prevent multiple inclusion.
* FIX - Fixed problem with cleanup of mapped memory files.
* FIX - Fixed problem with event exports.
* FIX - Fixed various issues when defining new control presets.
* FIX - Fixed options mismatch Video 4 Linux versions when defining new monitors.
* FIX - Fixed problem with monitor reordering on console page.
* FIX - Fixed problem with logins on 'mobile' skin.
* TRIVIAL - Improved debug emitted on capture failures.
* TRIVIAL - Options are now listed without the leading ZM_ as was a bit redundant.
* TRIVIAL - Moved DUMP_CORES option to Debug section.

===Release 1.24.0 - 2009/02/09===
Major architectural changes and security fixes.
* FEATURE : Completely rewritten web GUI. Although it looks pretty much the same the file organisation is completely different. Every page is now xHTML and much cleaner with all styling done via CSS. This will also allow support for other custom interfaces (skins) in future.
* FEATURE : Supports MPEG4 input from cameras. Currently only tested with Axis and ACTi cameras but only because those are the only ones I have been able to access. May well work with other cameras. Supports UDP RTP unicast and mulicast, RTP over RTSP and RTP over RTSP over HTTP.
* FEATURE : Includes new 'ffmpeg' camera type. This essentially passes the path you configure directly to ffmpeg and uses whatever it squirts out. This can be used as an alternate method for some MPEG cameras, MPJPEG cameras, video files or basically anything that ffmpeg will understand. ZM does not do any interpretation of the path but just passes it to ffmpeg so if it doesn't work for a particular source then there isn't much I can do about it. I recommend trying with ffplay to test that ffmpeg likes the stream before trying to use it with ZM.
* FEATURE : Optional use of mapped memory instead of shared memory. This is a different, though related, method of sharing memory between processes. From the help for ZM_PATH_MEM ''ZoneMinder has historically used IPC shared memory for shared data between processes. This has its advantages and limitations. This version of ZoneMinder can use an alternate method, mapped memory, instead which can be enabled with the --enable--mmap directive to configure. This requires less system configuration and is generally more flexible. However it requires each shared data segment to map onto a filesystem file. This option indicates where those mapped files go. You should ensure that this location has sufficient space for these files and for the best performance it should be a tmpfs file system or ramdisk otherwise disk access may render this method slower than the regular shared memory one.''
* FEATURE : Uses Video for Linux version 2 if present on your system. Monitors can be configured to use version 1 if preferred though. Video for Linux 2 is an enhanced and improved video API allowing better control and functionality for video devices and will be used by default if present unless disabled.
* FEATURE The Notes fields in events is kept up-to-date with triggered zones as events progress. So all zones that contributed at any time etc will be listed allowing searches for activity in zones. Previously only the initial zone (or other trigger) was included in the event.
* FEATURE : Added change to better detect if the zms stream is closed at the client end.
* FEATURE : Improved the reporting in zmdc.pl of the correct status when a ZM process exists or crashes.
* FEATURE : Improved header and library detection in configure.
* FEATURE : Made javascript in watch view more robust if communications interrupted with server.
* FEATURE : An additional option is now available to 'configure'. You can pass the MySQL engine type via the MYSQL_ENGINE=<engine> variable on the command line. If absent this defaults to MyISAM which has always been used previously. Other engines may offer better performance in some scenarios but ZM has not been extensively tested with any other than MyISAM, though I am trialling InnoDB now. Using engines that offer row locking (e.g. InnoDB) may help when you have a large number of events in a system and the auditing or other regular activities may otherwise lock the tables resulting in delays to the storage of frames for new events etc if the queries take a significant amount of time to execute.
* SECURITY : Fixed all known security vulnerabilities from earlier versions.
* TRIVIAL : Made some config descriptions less wordy.

===Release 1.23.3 - 2008/04/27===
Import security fixes and other minor changes.
* SECURITY : Fixed a number of potential vulnerabilities in remote script execution that could allow an authenticated ZoneMinder user to create and run arbitrary code on your system as the web user.
* FEATURE : Revamped the DVR events view to allow better navigation between events. Also reinstated the ability to delete events directly from the DVR live feed view.
* FEATURE : After a number of requests, added pagination navigation to the bottom of the event lists as well as the top.
* FIX : Now compiles with -Wall to show more warnings. As a result many compiler warnings and other misc issues addressed.
* FIX : Fixed an issue where filter queries were sometimes urlencoded twice meaning that clicking onto subsequent pages from a filtered view lost the filter and displayed all events instead of ust the filtered set.
* FIX : Fixed an issue where scrolling between the monitors in the xHTML mobile interface was broken when scrolling past the first one.
* FIX : Fixed an issue in the trigger and X.10 scripts where transitions from tape mode to alarm were not detected and triggered. This occured if you were running cameras in modect mode.
* FIX : Fixed a problem with incorrect specification in the installed Purge When Full filter for new installations.
* FIX : Fixed a problem in zmtrack.pl which was still using the old style PTZ control commands.
* FIX : Fixed an issue in the xHTML mobile interface where the default screen size was not being correctly interpreted meaning images overflowed the screen.

===Release 1.23.2 - 2008/02/24===
Further updates and fixes to issues in 1.23.1 and 1.23.0.
* FEATURE : Having been dropped for 1.23.0 the openssl library is now available as a build option for system that do not support gnutls, which remains the preferred, and default, option. To use openssl instead of gnutls, include the following 'ZM_SSL_LIB=openssl' on your configure line.
* FEATURE : Made Ajax request timeout configurable for DVR interfaces (Options->* B/W->ZM_WEB_*_AJAX_TIMEOUT).
* FEATURE : Added simple monitor presets for Veo Observer and BlueNet Video Server.
* FIX : Fixed an issue when using deep file storage where event files were being sometimes erroneously deleted by the audit process.
* FIX : Interactive filters were sometimes not being run correctly due to some old filter code having not been migrated properly.
* FIX : Various xHTML view issues and errors were fixed.
* FIX : Fixed an error when reloading linked monitor. The number of zones instead of the number of monitors was being used.
* FIX : The diagonal arrows in the PTZ views contained an issue which mean that they did not always work. This has been fixed.
* FIX : Version 1.23.1 shipped with a misnamed PurgeWhenFull filter (xPurgeWhenFull), this version renames it to avoid confusion.
* FIX : Recent versions included a PurgeWhenFull filter in the old filter format meaning it was a bit useless. If found this is now corrected to the new format.
* FIX : Fixed a mislabelling of a function parameter in a header file that caused the latest g++ to complain.
* LANGUAGE : Updated Hungarian language translation
* LANGUAGE : Updated German language translation

===Release 1.23.1 - 2008/01/13===
Minor updates and fixes to issues in 1.23.0.
* FEATURE : Added checkbox in monitor specification view allowing height to be calculated automatically from width (or vice versa) according to preset aspect ratio if desired. This is preset to 4:3 but can be amended globally via the Options->Config->ZM_DEFAULT_ASPECT_RATIO setting. Aside from 4:3 which is the usual for network and analog cameras another common setting is 11:9 for CIF (352x288) based sources.
* FIX : Fixed several related issues with PTZ protocol fields in the database and associated control and scripts.
* FIX : Fixed an issue whereby incorrect #defines were used to check for gnutls settings. This meant that hash based authentication stopped working.
* FIX : Fixed issue where video generation failed if the deeep storage format was selected.
* FIX : Fixed problem with streaming historical events when the relevant monitor was no longer active.
* LANGUAGE : Changed 'Archive' when used as a noun to 'Archived' to avoid ambiguity with 'Archive' the verb.
* LANGUAGE : Removed duplicate language tokens in some language files that were overiding translated versions with untranslated ones.
* LANGUAGE : Update Hungarian language translation.

===Release 1.23.0 - 2007/12/23===
Major new features and other improvements.
* FEATURE : Added optional DVR functionality (Web->ZM_WEB_DVR_STREAMING) in new CSS and Ajax based views. This allows you to pause, rewind, digitally zoom and pan on live streams and replayed events. Due to lag issues this really only works well on mpjpeg streaming and not so good with mpeg streams. This feature should be considered beta only and the streams and control may not always be reliable. For this feature, and for more features in future releases, you will need to install the Mootools javascript library in your ZM webdir. Mootools can be downloaded from http://mootools.net/ and you should select all components for now, with any compression type. You should ensure this file is named or soft linked to mootools.js.
* FEATURE : ZM can now optionally use a deep file storage tree to avoid the 32k limit on files per directory (Paths->ZM_USE_DEEP_STORAGE) This should only be set on initial install, changing it to a different setting will almost certainly lose all your events. There is currently no migration of events backs and forth between formats though I plan to create a script at a later date if time allows.
* FEATURE : Added specific alarm file quality setting (Images->ZM_JPEG_ALARM_FILE_QUALITY) that if set to a higher quality than the regular one (Images->ZM_JPEG_FILE_QUALITY) then it is used when saving images when in alarmed state.
* FEATURE : Image timestamp tokens have changed. They are now %N for monitor name (previously first %%s) and %Q for show text (previously second %%s). There is also a new %f token which is the fractional part of the seconds in the timestamp.
* FEATURE : Monitors can now be configured to suspend motion detection for a set number of frames if maximum alarmed pixels/filter pixels/blob counts are exceeded. This helps limit alarms caused by sudden large scale lighting changes for example.
* FEATURE : PTZ control functionality is now in the form of a perl library for each protocol used by a single script rather than lots of scripts. This is easier to maintain and use and will allow support for protocols that require some state persistence between commands. Performance and responsiveness is also much improved by direct socket connections to the script.
* FEATURE : Filters have been enhanced and largely rewritten behind the scenes. Little functional effect yet but makes it easier to add future improvements and manage filters generally.
* FEATURE : If you include the jscalendar javascript calendar (http://www.dynarch.com/projects/calendar/) in your ZM web dir in a 'calendar' subdirectory then filter date/time dialogs will use a popup calendar for easier date selection.
* FEATURE : The monitor alarm colour (indicating loss of signal) is now defined on a per monitor basis. The previous setting is not migrated so you should check all your local monitors if you have changed this.
* FEATURE : Users can optionally be set to be able to change their own language and passwords (Config->ZM_USER_SELF_EDIT)
* FEATURE : Filters can now check for system load
* FEATURE : Image/event details are now written to the JPEG file header of saved images. I'm not sure this is done in the same way as other packages however so feedback would be welcome.
* FEATURE : The mysql database connection port can now be specified along with the host in the format host:port
* FEATURE : WML support has now been removed as superseded by xHTML mobile profile.
* FEATURE : Due to licensing issues openssl support has now been replaced by gnutls.
* FEATURE : Updated to support latest ffmpeg. This update is not compatible with previous svn versions so you should update your ffmpeg to the latest version prior to building ZM. Other 'released' versions of ffmpeg should be fine though these are very out of date nowadays. Also added libswscale support to avoid using deprecated img_convert function. The ffmpeg configure line should be ''./configure --enable-gpl --enable-swscaler'' to enable this support.
* FEATURE : The Konqueror browser native streaming is now supported.
* FIX : Unprivileged users can no longer edit the zone settings, even though changes were not saved before anyway.
* FIX : Fixed ffmpeg support for latest CVS builds, also added libswscale support to avoid using deprecated img_convert function.
* FIX : Fixed monitor preset bug
* FIX : Fixed issue with immediate action filters not working properly.
* FIX : Fixed issue with incorrect line ending causing problems with some web cameras.
* FIX : Removed unneccessary duplicate indexes from some tables in the database.
* FIX : Removed 'bashisms' in a couple of the scripts.
* FIX : Turned off debugging X10 perl module to reduce log pollution.
* LANGUAGE : Added Hungarian language support
* LANGUAGE : Added Romanian language support
* LANGUAGE : Added Hebrew language support

===Release 1.22.3 - 2006/11/23===
Mostly bug fixes with a couple of minor feature additions.
* FEATURE : Filters can now be used to execute actions such as emailing or deleting events directly without being saved as a background automatic filter.
* FEATURE : New X.10 device control screens have been added to the HTML and xHTML pages. These screen allow manual on/off control of X.10 devices.
* FEATURE : The xHTML screen have been overhauled and simplified in terms of styling.
* FEATURE : The selection of markup, between HTML and xHTML was previously automatic only. This has been amended to all an url parameter to be passed on the initial screen to select the format for that session. So zm.php?format=xHTML will force the xHTML markup to be used even if selected from a traditional browser.
* FEATURE : You can now specify an http proxy to use for ZM update checking.
* FEATURE : You can now specify more than one monitor to use the same video input without frame rate penalty.
* FEATURE : You can now add labels to PTZ camera presets to aid in remembering what they are. These presets are displayed as a tool tip when mousing over the preset numbers.
* FEATURE : The timestamp displayed on images can now contain newlines. Use the \n (a ‘slash’ followed by an ‘n’) to represent that.
* FEATURE : The perl scripts will not respond to HUP signals by closing and reopening their logs. This can be used by logrotate to ensure that the ZoneMinder do not keep growing forever. You can use zmpkg.pl logrot to send a HUP signal to all scripts.
* FIX : The stills event view now shows all frames, not just those stored in the database. Scrolling between frames is also now fixed.
* FIX : Fixed long outstanding but in zmaudit.pl causing the most recent event to sometimes get deleted erroneously.
* FIX : Fixed a bug in the scaling routines that sometimes resulted in garbled or slanted images.
* FIX : Fixed the format used in HTTP communications with network cameras to ensure that line endings use both CR and LF where appropriate.
* FIX : Added some additional SQL finish calls to free up memory from long select statements.
* FIX : When ZM reloaded monitors live, the Linked Monitors field was omitted. This has been fixed.
* FIX : Fixed an issue causing devide by zero errors in zmpatch.pl
* FIX : Fixed an issue with quotes in saved filters.
* FIX : Fixed an issue in zmfilter.pl where filters on Weekdays were not executed correctly.
* FIX : Fixed an issue with saved filters using the Cause or Notes events fields.
* FIX : Fixed a problem with zmfilter.pl where the flag indicating that an event had had a video created was not set.
* FIX : Fixed issue with user specific language selections not being effective.
* FIX : Fixed issue with compiling with latest ffmpeg distribution.
* FIX : All open file descriptors are now close when the perl scripts daemonise themselves. This means that ZM should not lock up open socket addresses or stop apache from restarting as occasionally happened before.
* FIX : Hyphens are now allow in remote host names.
* FIX : The timeline view can now display events with newlines in the Notes field.
* FIX : Some perl errors were not being reported to logs. These have been changed to use the debug library.
* FIX : Fixed an issue where some jpeg format errors were not caught by the debug library and so not reported in the appropriate logs.

===Release 1.22.2 - 2006/05/26===
Mostly bug fixes with a couple of minor feature additions.
* FEATURE : Long events generated by Record or MoCord modes previously were not able to be reviewed until they had finished. This has changed and the event record is now updated whenever a bulk frame is generated. In most cases this will mean that the event will become replayable soon after commencing, and the record will be updated one or twice a minute.
* FEATURE : The event replay view now has some basic details about the event included as a header to the window.
* FEATURE : Weekday selection in filters is now implemented via drop down selections and not day indices.
* FEATURE : Focus is now automatically set to the username field of the login screen when the page is opened.
* FEATURE : The Fatal debug call now calls ‘abort’ to generate a back trace (if enabled).
* FEATURE : Added system status view, primarily for use by other utilities.
* FIX : Fixed an issue with an sql error concerning AlarmMaxFPS showing up when selecting monitor presets.
* FIX : Fixed the missing ‘images’ token in non-English language files.
* FIX : Added missing zone sensitivity preset.
* FIX : Fixed a problem with a missing field in the sigcontext structure on some distributions. This caused a build error when stack tracing was on.
* FIX : Fixed a problem in zmpkg.pl where one of the ‘su’ tests was missing a quote.
* FIX : Removed inclusion of Device::SerialPort perl module from zmcontrol script for IP cameras.
* FX : Added /usr/local/bin to PATH in zmupdate.pl
* FIX : Errors in shared memory access via the perl modules now invalidate the id, causing subsequent accesses to revalidate the id. Previously access would continue to invalid segments on error even if a new valid segment existed.
* FIX : All outstanding ‘assert’ calls have been replaced by more useful and informative error messages.
* FIX : Fixed a problem in some browsers where zone co-ordinates could be defined to have extents outside of the legal range for the size of image.
* FIX : Settings (e.g. paths) in zm.conf may now contain spaces.
* FIX : Fixed an issue with weekday handling in filters not being handled correctly.
* FIX : Fixed the event stills image view to correct a problem with some broken images.
* FIX : Zones were not being correctly resized when a monitor had its dimensions amended. In some circumstances this could result in a zone outside of the legal range and thereafter crashes.
* FIX : Fixed a problem with the montage and cycle views forgetting the current selected group if stills views were selected and then streams reselected.
* FIX : Corrected some typos in zmtrigger.pl to do with the showtext functions.
* FIX : Added more sanity checking in various places to ensure that zones are valid before processing.
* FIX : Increased the valid card channel range to 0-15 from -3.
* FIX : Corrected a problem with zmfilter.pl causing sql errors when running saved filters that used the monitor name.
* LANGUAGE : Added initial Chinese Big5 language translation.
===Release 1.22.1 - 2006/04/27===
A few important features plus some minor enhancements, usability updates and bug fixes.
* FEATURE : Monitors can now be linked so activity on one, triggers events on another. This allows area wide surveillance by enabling one key monitor to control several others, though they can still be configured to detect motion themselves.
* FEATURE : Events can now have more than one cause. Previously if an event was triggered by motion, other stimuli would be ignored. Now if an event is caused by both motion and a linked monitor (perhaps covering the same field of view), this is indicated in the ‘cause’ field of the event. Note that the cause of event is established on the first alarmed frame, so if motion is detected and then one frame later an trigger is detected, only the motion will be recorded as the cause as the monitor will be in an alarmed state by the time the second cause arrives.
* FEATURE : The event Notes/Description field is now more useful. If an event is triggered by motion, this field contains a record or which zone detected the motion. If an event was triggered by a linked monitor then the monitor in question is recorded and so on. This allows filtering on more specific indicators.
* FEATURE : All temporary files such as thumbnail images, now go in the ‘images’ directory rather than in the specific event directory. They are then periodically removed by zmaudit when over a certain age. This means that if you are archiving off event directories you will not end up copying a load of thumbnails and smaller images of various sizes. The treatment of thumbnails etc has also been rationalised in general.
* FEATURE : The groups view has been further modified to make group modification use the same paradigm as the rest of the web interface. This has also simplified it somewhat.
* FEATURE : All views where you need to select a list of monitor ids now give you the choice of using a selector that lists the monitor names and not just their ids.
* FEATURE : The zmdc.pl script that controls the ZoneMinder daemons has been modified to make it clearer in the logs when a process has crashed, exited abnormally (i.e. with a non-zero status) or normally. An abnormal exit is not necessarily a bad thing, whereas a crash always is.
* FEATURE : The average difference of all alarmed pixels is now available in event statistics. Note that this is the mean of the differences between a pixel and it’s counterpart in the reference image, but only for pixels where this difference is inside the pixel difference thresholds specified in the zone configuration. In other words it is not the mean difference of all pixels, just those that initially contributed to an alarm. This allows you to determine the effects of modifying the thresholds by seeing what effect that has on the mean difference.
* FEATURE : The zmfix utility now corrects permission on any active PTZ control devices, .e.g. serial port devices, as well as video devices.
* FEATURE : The zmpkg.pl control script now has the ability to use ‘sudo’ to execute commands as the web user and will only fall back to ‘su’ if this fails. This should allow it to be more compatible across distributions.
* FEATURE : Deleting events will now ask for a confirmation before proceeding.
* FEATURE : Black and White settings for Axis cameras have been added to the monitor presets.
* FEATURE : Settings for Gadspot cameras have been added to the monitor presets.
* FEATURE : Most dates now use strftime to make them locale aware. This should help avoid some of the problems associated with dates for languages other than English. Ultimately these formats will probably be moved to be configurable but for now they can be found defined in zm_config.php for general formats or zm_html_view_timeline.php for timeline specific ones.
* FEATURE : The global ‘ZM_NO_MAX_FPS_ON_ALARM’ option has been replaced by a ‘Maximum Alarm FPS’ settings for each monitor. This means that you can now choose whether to limit the frame rate when an alarm occurs on a per monitor basis and can configure monitors to have a higher frame rate but not unlimited whereas previously it was the normal frame or unlimited with no facility for more precise configuration.
* FEATURE : Added facility for executing binaries to dump a backtrace to the logs on receipt of a fatal signal. This should help debugging should any crashes occur. However it does depend on those facilities being available on the host system. If they are not then this feature will be disabled. It can also be disabled via the --enable-crashtrace=no option to configure.
* FEATURE : Configuration of local monitors now includes more drop down selectors to guide users towards sensible values.
* FEATURE : Some scripts have been modified or added to make creation of rpms or other packages easier.
* FIX : The monitor creation/modification dialog previously had virtually no validation, allowing creation of monitors with bogus, meaningless or dangerous properties. This has been corrected to impose meaningful and valid settings.
* FIX : The Zone presets included in 1.22.0 were set to be a little too sensitive. They have been amended to make them have more of a range of sensitivity.
* FIX : Scripts are able to use a local zm.conf file in the current directory in preference to the installed system one. This is most useful for zmupdate.pl but can apply to all scripts for testing. Previously this local file was used silently which may cause some confusion. A warning is now emitted if the installed zm.conf file is being overridden by a local one.
* FIX : The zmu tool crashed when querying zones. This has been fixed and more useful output emitted, including the dimensions of the zones.
* FIX : The ‘message’ email address was sometimes ignored and the ‘email’ address used instead. This has been corrected.
* FIX : The zm_action.php file was a bit broken 1.22.0 particular when creating and deleting monitors. This has been fixed and the file has been tidied up to make it easier to maintain and understand.
* FIX : Some references were maintained to free’ mysql query data. This has been fixed to use copies.
* FIX : Problems with incorrect JPEG quality settings had crept back in so the wrong setting, or even default settings were being used and the appropriate setting was being ignored.
* FIX : The capture daemon for remote cameras will not exit in a more graceful and controlled manner when it is unable to fetch remote images.
* FIX : Editing the camera control capabilities was broken in 1.22.0 meaning changes were not being saved. This is now fixed.
* FIX : There was a missing terminating character in the configuration for the default email and message formats. This resulted in these fields being blank. These configuration options have now been split into subject and body formats for both to make them easier to maintain..
* FIX : Saving run states omitted the ‘enabled’ flag meaning that the saved value was not correct. This has been fixed.
* FIX : Some configuration was moved to a category which had no tab in the Options window and so became inaccessible except directly via the database. This has been resolved, and the categories restructured slightly to be more appropriate.
* FIX : Some web forms have been modified to use ‘post’ rather than ‘get’ allowing more data to be passed without error for large operations.
* FIX : A number of minor video generation issues have been fixed.
* FIX : The zone polygon editing view should now work on all browsers including Internet Explorer.
* FIX : A number of xHTML syntactical errors have been found and fixed in the xHTML view files.
* FIX : A problem with the incorrect specification of the preset to return to if auto-tracking motion has been found and fixed.
* FIX : A crash in zmu when using the ‘-l’ options has been corrected.
* FIX : When viewing events from the timeline view, the filter used to select them is now passed meaning that scrolling between events now behaves as expected.
* FIX : Where necessary %f formats in sprintf have been changed to %F to ensure ffmpeg compatible, and non-locate aware, floating point formats are used. This fix is only effective for php versions 4.3.10 and later.
* FIX : Fixed an issue where deleting the last page of events generated an empty page.
* FIX : Fixed a problem where the stills view for Record’ed or Mocord’ed events did not display correctly.
* FIX : Fixed a problem with loaded filters being unable to be edited to have more or fewer terms.
* FIX : Fixed the script debugging library to not try and interpret % characters in debug as formatting.
* FIX : Fixed (hopefully) an issue where md5.h was incorrectly identified by configure as being missing.
* LANGUAGE : The two existing Italian language files have been merged into one and updated.
* LANGUAGE : A new Swedish translation has been added.
===Release 1.22.0 - 2006/01/18===
Major architectural changes as well as a whole raft of other enhancements and fixes.
* FEATURE : Zones can now be (virtually) any shape of polygon. This means that triangular, octagonal, duo decahedrons etc are now supported. The only exceptions to this are self-intersecting shapes which will be flagged. This adds a lot more flexibility to the definition of zones. Zones can be drawn semi-interactively.
* FEATURE : Certain preset zones settings are now supplied to allow quicker configuration of zones. These are intended to be a guide only, and not definitive settings but form a useful starting point.
* FEATURE : The zmpkg.pl scripts now attempts to determine the supported syntax of the ‘su’ command so it should work even with distributions like Slackware that don’t support the --shell option. Previously this required a hand edit.
* FEATURE : Some common perl functionality has been moved to perl modules which have been included. This also allows other scripts to use the ZoneMinder modules to create additional functionality particularly in the area of triggering. All scripts have been converted to use these modules.
* FEATURE : A (small currently) number of monitor presets have been added to the monitor configuration view. This allows quicker initial configuration of certain (mostly network) cameras without having to know all the paths. Contributions detailing other cameras will be gratefully accepted.
* FEATURE : Signal loss on locally attached video sources is now detected. This will create a short Signal Lost event on signal loss, followed by a Signal Reacquired event when it comes back. While the signal is lost no recording will take place in any mode.
* FEATURE : The zmtrigger.pl script has been completed revamped to support both incoming and outgoing triggers. Certain example triggers and connections have been included in the trigger modules but this is intended to be an example only and to provide a basis for users to customise and add their own functionality. Users will also be able to contribute modules tailored to specific external systems.
* FEATURE : More configuration has been moved to the zm.conf file. All components now use this file for initial configuration. Scripts may also use a local copy, in the same directory, to allow overrides etc.
* FEATURE : The zmconfig.pl script is no more! Building now only requires the ‘configure’ step and then make etc. Database parameters can be supplied to the configure script.
* FEATURE : The configure script now includes more system compatibility checking including checks for required and optional perl modules.
* FEATURE : Generation and management of thumbnail images is now improved. Thumbnail images (and any that are not directly created for the event) are now stored in the images directory under the web root, where zmaudit will periodically remove them.
* FEATURE : All libjpeg output is now trapped and handled as regular format debug.
* FEATURE : Some jpeg data is cached on first use instead of being regenerated each time. This should speed up jpeg handling to some degree.
* FEATURE : Event data can be optionally saved to COM fields in the jpeg file header.
* FEATURE : A system summary command has been added to zmu.
* FEATURE : Filtering can now be done on the event id field.
* FEATURE : Filtering can now be done on the event description field.
* FEATURE : The ‘check all’ on event lists etc is now a toggle checkbox.
* FEATURE : In Mocord mode, events can now be forced to close when the event has reached the section length even if an alarm is in progress. Previously this would have resulted in an extended event.
* FEATURE : The ‘groups’ view has been overhauled and rationalised.
* FEATURE : A default event replay rate has been added.
* FEATURE : Videos can now be created from filters.
* FEATURE : Added tokens for event cause (%EC%) and description (%ED%) for filter generated emails. The %ED% token was previously used for event length, this has now changed to %EL%. You will need to update any filters that use this token to use the new value.
* FEATURE : There is now a separate auto-execute checkbox from filters to allow definition of a script but not execution if this is not desired.
* FEATURE : When filters are loaded, a hint appears to indicate what automatic function options they have been saved with.
* FEATURE : Improved the behaviour of the automatic PTZ stop feature when using Pelco type PTZ cameras.
* FEATURE : The configure script now allows an option to compile all debug out from the binaries.
* FEATURE : The configure script now takes a generic ‘extra libs’ option to allow specification of any extra libraries that may be required for compilation due to additional ffmpeg options etc. The mp3lame option has been removed.
* FEATURE : Mime support for streaming has been enhanced to allow easy configuration of additional formats of data streaming. The streaming daemons themselves have also been improved to support the generation of other stream formats.
* FEATURE : The handling of video viewing via the ‘video’ view has been improved to allow embedded viewing of videos as well as easy saving locally.
* FEATURE : The alarm sound that can be configured to play when viewing a monitor with a current alarm has now been improved to not depend on the refreshing of the status which resulted in clipped audio.
* FEATURE : Script debug now follows the same format as all debug and uses the syslog facility. This means that all important messages go into the /var/log/messages file (or equivalent). This can be modified by redirecting the local1 facility in syslog.conf to go elsewhere, or be ignored, if so desired.
* FEATURE : A new raw streaming format has been added for live monitor streams. This produces a low cpu impact raw rgb feed.
* FEATURE : A zm.pid file is now placed in /var/run/zm when ZoneMinder is running, and removed when stopped. This can be used by other elements to check the status of ZoneMinder. The pid in the file is that of the master zmdc.pl server instance.
* FEATURE : The continuous/triggered settings for monitors have now been removed. They have been replaced by an Enabled flag that indicates whether a monitor is actually doing the task assigned to it. This can be used by scripts to disable or enable monitors depending on external triggers without having to change the Function or start and stop daemons. The state of this flag is now saved in ‘run states’ to allow ZoneMinder to be started with some monitors initially disabled.
* FEATURE : Restructured zmfilter.pl to better handle filters and ensure that auto functions are performed in a logical sequence (e.g. not deleted before being archived).
* FEATURE : Added link to Zones configuration to the live watch view.
* FEATURE : The event link in the xHTML interface now goes somewhere useful.
* FEATURE : Reformatted a number of xHTML views to use tables for better layout.
* FEATURE : The default reference image blend percentage has been changed to 7% to persist events slightly longer.
* FEATURE : The monitor configuration view has been re-organised slightly and some fields have moved between tabs.
* FEATURE : When motion is detected the centre of the region of motion is written to shared memory, where is can be used for tracking. This can now optionally be a simple median of the motion extents or (in blob mode) a weighted centre for better location of irregularly shaped events.
* FEATURE : Added event progress and navigation bar to event view (currently not on IE). This allows partial replay of events and an indication of how far through the event it is. This is off by default for low bandwidth settings as the image replay tends not to be able to keep up.
* FEATURE : Added --with-libarch to configure for 64 bit builds. This allows an alternative library path to be specified for 64 bit versions of system libraries.
* FEATURE : Made zmaudit optional and with a configurable delay. Systems with large numbers of events may wish to turn zmaudit off and run manually at off peak hours or increase the execution interval.
* FEATURE : All logging now done via Debug.pm. This helps bring script logging more into line with that in the binaries. The process is not yet complete however.
* FEATURE : Language selection now a dropdown showing available languages.
* FEATURE : The zmcontrol-kx-hcm10.pl script has been renamed to the more generic zmcontrol-panasonic-ip.pl script as it should work with all Panasonic IP cameras.
* FEATURE : Added PTZ control script for Neu-Fusion NCS370 IP cameras.
* FEATURE : The rather awkward emailed and message format which included both the subject and body has gone and been replaced by individual options for the subject and body. Your previous setting should be preserved during the upgrade.
* FIX : The zms script has been corrected to accept any authentication method regardless of what has been configured to be used.
* FIX : The zmc processes now exit if any 4xx error is reported from remote network image sources.
* FIX : The experimental zmtrack.pl script was broken and didn’t work. This has now been corrected.
* FIX : Versions 0.4.8, 0.4.9-pre1 and CVS ffmpeg are now supported correctly.
* FIX : A problem with event statistics not always being output was fixed.
* FIX : A problem with the JPEG file quality setting being ignored was fixed.
* FIX : A problem with brackets in filters has been fixed.
* FIX : The console view previously could spawn instances of zmdc.pl when ZM wasn’t running. This has now been corrected.
* FIX : The console view has been optimised to speed up display by up to a factor of ten.
* FIX : Scaling of stills event views has now been rationalised to not ever be smaller than 100% as the image is always sent at at least this resolution.
* FIX : A problem with zmaudit.pl mishandling recovered events has been fixed.
* FIX : Fixed number of minor memory access issues.
* FIX : Fixed ‘undefined pid’ error in zmdc.pl.
* FIX : Changed a bunch of Info calls to Debug to reduce log clutter.
* FIX : Fixed a couple of problems with the authentication relay methods in zms.
* FIX : Fixed issue with control permissions whereby a user also needed monitor edit permissions to be able to control a monitor.
* FIX : Logs created by root are chowned to web user to help prevent permission issues.
* FIX : Problems with different type sizes when accessing shared memory on 64 bit systems have been fixed.
* FIX : The zmvideo script now quotes filenames correctly and so won't die if they have unusual characters in them.
* FIX : Fixed issue with streaming events with out of sequence frames causing immense timeouts.
* FIX : Most mysql queries in the web interface did not have their result resources freed. This was untidy but generally did not have any deleterious consequences. However all queries are now properly freed.
* FIX : Password handling in the user configuration form was a bit ugly. This has been tidied up.
* FIX : Some configuration has had default values changed.
* LANGUAGE : A Czech translation has been included. Thanks for user ‘’ for this file.
===Release 1.21.4 - 2005/11/11===
A whole bunch of improvements and fixes.
* FEATURE : The video generation interface has been redesigned and expanded. This allows you to see what videos have been generated previously and manage, view or download them. You can also specify more precisely what input and output options to pass to ffmpeg and what video formats you want to support. These options are available from the Options->Tools view.
* FEATURE : Historical video is now supported from the XHTML mobile device interface allowing you to replay previous events etc.
* FEATURE : A new timeline view has been added. This is an enhanced graphic activity view that represents events as colour coded bars on a time based chart. Passing your mouse over the activity will display images and details from the events in the chart. You are able to choose whether you see this view or the traditional events view as a default. Since this view can be a large file and dynamic loading of event images can be bandwidth intensive this preference can be specific on a bandwidth specific basis. The option to switch between the traditional list and the timeline view is available at all times however. IMPORTANT NOTE: This view is a beta version only and due to extensive use of CSS currently only renders correctly on FireFox type browsers. Even then as it can use huge numbers of elements it is possible it may degrade or crash your browser. Specifically Internet Explorer seems to get totally confused and renders some elements twice and others in the wrong place etc. I hope to remedy this situation for the next release but for now using this view with IE is not recommended.
* FIX : References to the video device files are now expressed as full file paths rather than just numbers. This allows files other than /dev/videoX to be used easily.
* FIX : Integration with all versions of ffmpeg, including CVS, is now supported. At least until the next ffmpeg interface change anyway!
* FEATURE : Monitors can now use a file path as a video source. This allows you to use scripts such as wget or other webcam type applications to generate your images which can then be fed into ZoneMinder as a monitor and analysed and archived etc.
* FEATURE : Users can now be defined with a maximum bandwidth setting. This prevents low privilege users from swamping the system with lots of high bandwidth streaming.
* FEATURE : Debug levels for the binaries can now be controlled in a limited fashion from the Options screen. For more details see the help on the Options->Tools->ZM_EXTRA_DEBUG* options.
* FEATURE : The user authentication methods have been revised to separate authentication at the web front end from authentication at back end streaming. Thus there are now several more authentication options to allow more fine control. The most significant of these ZM_AUTH_TYPE now offers a choice of ‘remote’ authentication which allows you to use a third party authentication scheme such as http basic authentication and have that users name passed via the REMOTE_USER environment variable. Providing there is a user of that name known to ZoneMinder they will be automatically logged in. Be warned however that there is no facility for this user to log out so ensure that you do not lock yourself into a low privilege account. Also you may need to remove user cookies when you change authentication methods.
* FEATURE : Users now have a ‘control’ permission which determines whether they are able to control PTZ style cameras. As with the other permissions there are three levels, None, View and Edit. Unlike some of the other options it may not be obvious what levels do what. The ‘None’ level bars access to any control functionality, the ‘View’ level permits users to actually control the positioning and settings of a camera (rather than just look at them which is what might be expected) and the ‘Edit’ level allows users to modify the various control capabilities.
* FIX : A bug was fixed where the streamed images were using the quality settings for saved files.
* FIX : Jpeg errors are now reported via the generic ZoneMinder error and debug mechanism rather than just to standard output as is the default in libjpeg.
* FIX : The time taken to load and refresh the console view has been reduced. This is especially significant where you may have lots of monitors.
* FIX : Paths to the control scripts were hard coded with a full path. This broke the packaged ZoneMinder distributions so the paths are now relative to the ZM_PATH_BIN config unless they start with a ‘/’.
* FIX : The masks used for shared memory have now been refined to prevent invalid values from causing duplicates.
* FEATURE : Monitors can now be re-ordered from the console view to allow you to choose how you would like them arranged.
* FEATURE : Motion detection can now be temporarily disabled from the watch view. This is most useful with PTZ type cameras where you can switch off motion detection whilst repositioning the camera. Just don’t forget to switch it back on again afterwards!
* FEATURE : A default scale per bandwidth setting can now be defined. This allows you to reduce the size of streams etc on slow connections.
* 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.
* FEATURE : The choice of streaming versus stills views as default can now be specified per bandwidth setting.
* 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 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 opposite to the previous default and you will need to update these options to retain the previous behaviour. Note also that this ordering applies only to event lists and not the ‘last x events’ in the watch window which are still newest first.
* FIX : A curious problem with logging in on PHP 4.4 has now been fixed.
* FEATURE : Following requests and some confusion about how often filters are executed versus reloaded from the database, this is now a configurable options (Options->System-> ZM_FILTER_EXECUTE_INTERVAL). Please read the help on this option for guidance on what values to use.
* FEATURE : A ‘Filters’ button has been added to the main console view allowing easier access to the filters view.
* FEATURE : Support for the HTTPS protocol has been added allowing streaming etc to function over secure links.
* FEATURE : The layout and functionality of the XHTML screens has been enhanced to make them more useful overall.
* FEATURE : Following virtual extinction of donations I have added a small one time nag screen which invites you to donate to ZoneMinder after a month of use. That’s all it does and once dismissed you will never see it again!
* LANGUAGE : A lot of new tokens have been added. These have been included in all the language files in English. It would be appreciated if anyone who is able to edit their zm_lang_xx_yy.php language files and translate these tokens could email them back to me so I can include them in future releases.
===Release 1.21.3 - 2005/07/14===
Additional bug fix release.
* FIX : Images from rotated monitors had been broken in a previous release. This has been corrected.
* FIX : The bogus deletion of events by zmaudit has finally been completely fixed.
* FIX : Fixed a problem where Axis PTZ controls sometimes caused the camera to move in an incorrect direction.
* 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.
* FIX : A problem existed where renaming monitors did not rename the symbolic link to the events directory. Thanks to forum user ‘tommy’ for suggesting the fix to this issue.
* FIX : The README document has been restructured slightly to make it easier to find the information you require. This includes the addition of an Upgrading section to clarify the process of upgrading from a previous version.
===Release 1.21.2 - 2005/06/23===
Minor-ish bug fixes to the 1.21.1 release.
* FIX : If the defined image timestamp format for a monitor contained only time directives and no %%s directives then the timestamp was not included in the image at all.
* FIX : An ugly divide by zero error was present on new installations where no monitors had yet been defined.
* FIX : The Pelco-D protocol control script did not properly support Iris control.
* FIX : Fixed a nasty problem in zmaudit which meant that older events sometimes didn’t get tidied up and deleted properly.
* FIX : Fixed an issue with the multi-part jpeg streams having frame boundaries output at the end of each image and not the beginning. Apart from this not being ideal semantically it also meant that ZM had trouble parsing it’s own output!
* FEATURE : Some of the scripts have a new debug format that is more similar to the one used in the binaries.
===Release 1.21.1 - 2005/06/23===
Menage of various new features and bug fixes.
* FIX : The HTTP refresh method of updating the Cycle view was broken. This is now fixed.
* FIX : There was an arbitrary limit on the size of a blob due to the dimensioning of the field in the database. This has been increased to allow all possible blob sizes to be accounted for.
* FIX : On some platforms there is no definition of the ‘round’ function. Previous versions of ZM have detected this and included one if no other is present. However changes in 1.21.0 meant that this did not always happen and the function went undefined. This has been corrected.
* FEATURE : Support has been added to allow monitors to be defined as mirrored. Thus images can now be flipped horizontally or vertically before processing as well as rotated as in previous versions.
* FIX : Made the ‘Options’ link only appear if the user has sufficient permissions.
* FIX : Fixed issue where the PTZ control function to set camera presets never passed the preset number so preset 1 was always used.
* FEATURE : A custom title can now be added via the normal Options dialog (ZM_WEB_TITLE_PREFIX). This title will be used in all browser windows and allows you to distinguish between multiple ZM installations for example.
* FEATURE : Ordinarily ZoneMinder will resize the console window to fit the number of monitors displayed. If you are using a tabbed browser this can be a little irritating. A new option (ZM_WEB_RESIZE_CONSOLE) has been added to control this behaviour.
* FEATURE : Version 1.21.0 added support for events to be labelled with Cause and Notes fields. However these could not be modified directly from the web interface. This has been amended so that an ‘Edit’ link is now present in the events listing. Clicking on this allows you to modify these fields for one or more events so they can be identified as belonging to a particular incident.
* 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 further in the future.
* FEATURE : Previously in the c/c++ code accessor functions had to be called to access the value of configuration options. This was expensive when done repeatedly so some classes used cached local variables to avoid this. The configuration has been rewritten to provide all configuration options as members of the configuration class which are initialised once on startup and then can be accessed directly with no further overhead.
* LANGUAGE : Support for the Danish language has now been included. Thanks for forum user ‘voronwe’ for his work on this. Select dk_dk in the languages preferences to use this language.
* FEATURE : Events viewed in the events listing view can now be saved locally by clicking on the ‘Export’ button. This creates a tar or zip file of the selected file groups, such as images, videos etc, as well as, optional, HTML pages describing the basic details about the event and frame details. This allows a basic navigation and viewing of the events outside of the regular ZoneMinder interface. This format is different, and improved, over that that created in the background filter function and it is expected that these functions will converge at some point.
* FIX : Clearing the ‘Track Motion’ checkbox in the Control section of the Monitor configuration would not be saved resulting in this setting being stuck in an ‘on’ state. This has been corrected.
* FIX : The ‘Play All’ link in the event view allows a sequence of events to be streamed consecutively. This is fine in a streamed view but meaningless in the stills view so has been removed.
* FEATURE : The ‘show’ trigger command in zmtrigger.pl has been added to allow miscellaneous externally sourced text to be displayed in the image timestamps.
* FEATURE : Add the ‘Auto Stop Timeout’ monitor control option to allow finer control of Pan/Tilt/Zoom cameras with support for only basic continuous modes of motion.
* LANGUAGE : The German language files have been updated.
* FEATURE : Support for control of Axis network cameras has been added. This uses the zmcontrol-axis-v2.pl script and should work with all Axis PTZ network cameras that use version 2 of the Axis API.
* FEATURE : The zmaudit.pl script has been modified to be faster and access disk a lot less. Previously it was possible for this script to frequently thrash disks while determining timestamps on directories.
* FEATURE : A contributed patch by Ross Melin has been included. This gives you the option of using an alternative mailing method in the zmfilter.pl script if the default method does not work correctly. To use the new method go to Options->Email and set ZM_NEW_MAIL_MODULES to on.
* FIX : Previously the ZM_EMAIL_HOST config was not passed to the zmfilter.pl script so hosts other than localhost were not used. This has been fixed.
* LANGUAGE : A translation for the Romanian language has been added. To use it select ro_ro as the language.
* 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.
* FIX : Monitors that are inactive no longer have an active link for streaming as this has no real purpose.
* FEATURE : An experimental Pelco-P control script has been added to support PTZ cameras that support this protocol. This script has not really been tested but is included as a basis for further development or customisation.
* FIX : The zmfilter.pl script now respects the ZM_FAST_DELETE option and will fully delete any events rather than assuming that zmaudit.pl will clear up if it just removes the primary database record.
* FIX : The montage view layout now correctly utilises the ZM_MAX_MONTAGE_COLS option when determining the dimensions and layout of the montage window.
* FEATURE : A contributed patch by forum user ‘lazyleopard’ has been included. This allows a specified number of frames to be discarded to alleviate problems with broken interlaced frames where multiple cameras share one bttv chip 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.
* 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 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 basic parsing is used instead. This new method should be slightly faster as it does not have the overhead of regular expression parsing, however this also makes it slightly more inflexible. If you experience problems using the new method with your netcam then you should try switching to the regular expression based method, and report the issue via the forums, preferably with a snapshot of the output of your camera.
===Release 1.21.0 - 2005/03/22===
Addition of camera control, plus several bugfixes.
* FEATURE : Added support for Pan/Tilt/Zoom and general camera control.
* FIX : The montage view layout has been modified to allow better dynamic layout of windows. Views should now be laid out in a more logical arrangement. This is a relatively temporary change and the montage view will shortly be rewritten to use flowing ‘div’ tags which should add more flexibility and be less complex.
* FIX : All stream views now have an ‘alt’ tag to highlight which monitor they should be displaying.
* FIX : Detection of which markup language to use, HTML or XHTML-MP has now been optimised to ensure that the test only happens once per session.
* FIX : Some constants were defined unquoted, this has now been corrected.
* FIX : The zmtrigger.pl script had an old, and incorrect, initial section using constants that were no longer valid. This has now been fixed.
* FIX : The regular expression patterns used to parse the zm.conf file have been modified to ensure that they should always work.
* FIX : In previous versions it was possible for a process to die and not be reaped by zmdc.pl. This could have resulted in processes remaining as zombies resulting in them not being restarted after crashing. This has now been fixed so all dying processes will be caught and handled.
* FIX : The frame view has been restructured to ensure that it has a consistent look and does not display unwanted wrapping.
* FIX : A couple of remnant hard coded text elements have been replaced with tokens as they should have been originally.
* FIX : Previously separate ‘object’ and ‘embed’ tags were used for Internet Explorer and non-IE browsers. These have been merged so that browsers will use whichever tag is appropriate. Any player controls that were present should now be hidden as well.
* FIX : A problem was present whereby the Maximum FPS set in the bandwidth settings was not being respected in the live streams. This is now fixed.
* FIX : If users were created with restricted monitor ids, it was sometimes possible that permission errors would still be issued if they tried to view streams or other elements associated with monitors in their list. This has now been corrected such that any restrictions are applied correctly.
* FIX : Users created with only ‘view streams’ permissions were presented with a ‘permission denied’ error in the area of the Watch window normally containing the recent events list. Whilst this was technically correct it was unnecessary and untidy, and has now been changed just to be blank.
===Release 1.20.1 - 2005/02/04===
Mostly bug fixes, large and small with a couple of minor features included.
* FIX : A dependency on the regular expression library was introduced in 1.20.0 which caused some people to have build problems. This library has traditionally been is necessary to support network cameras but not otherwise. This situation has now been restored.
* FEATURE : Added ZM_RAND_STREAM option. This option adds a time code onto the url of each stream to prevent it from being cached which had caused some broken image problems with some browsers, notably Mozilla.
* FIX : Made zms check ZM_OPT_AUTH before loading user details. This should have been in there in 1.20.0 but was omitted and should fix the issue where streams did not work with authentication off.
* FIX : There was some debug code left behind in zm_xhtml.php. This was unnecessary and has been removed.
* FIX : Fixed user sql, added debug and wrapped in check for libcrypto in zm_user.cpp. This should correct bogus loading of user data which may have affected some people. You can also now just bump up the debug level to see what the auth strings being used are.
* FIX : The xHTML console page now uses the mobile group as it should have in 1.20.0
* FIX : Modified database username to be binary. You need to run the zmalter-1.20.0 sql script as usual to change your Users table to disallow case-insensitive checking which may have been breaking some people’s streams.
* FIX : Fixed incorrect constant definitions in zmtrigger.pl. This script had not been updated along with the other scripts.
* FIX : Fixed bogus double .jpg suffix on diagnostic images, also included them (if they exist) in frame view.
* FIX : Corrected broken check for libcrypto (the check happened before any definition) causing build problems for some people who do not have MD5 library installed.
* FIX : Added permissions mode to mkdir in zm_actions.php to remove php warning.
* FIX : Added space before -m in zmu command in zm_actions.php
* FIX : Added quotes around brightness etc SQL in zm_actions.php to avoid errors when values are empty.
* FIX : Added line length to fgets in zm_config.php.z to prevent php warning
* FIX : Slightly enlarged a couple of window sizes in zm_config.php.z to work better with different browsers.
* FIX : Defined empty array in html_view_states to prevent php warnings.
* FEATURE : Console window now sizes itself according to how many monitors in list, though there is a minimum size.
* FIX : Corrected bug in zmfilter.pl.z which meant that images were not always correctly uploaded.
===Release 1.20.0 - 2005/01/20===
Improved and added features, several minor bug fixes.
* FEATURE : Certain configuration (Mostly database settings) is now stored in a new file zm.conf. This means that database access settings can be changed without recompilation. It also allows the creation of ZoneMinder rpms. Watch zoneminder.com for details. Thanks for forum user ‘oskin’ for his work on this.
* FEATURE : The WML interface is now deprecated and the XHTML-MP interface is the new supported interface for mobile devices.
* FEATURE : Monitor groups have now been added allowing subsets of monitors to be viewed independently.
* FEATURE : A generic external triggering interface has been included via the zmtrigger.pl script. A new monitor function ‘Nodect’ has been added to support this.
* FEATURE : Interaction between the web pages and the streaming daemons and other utilities has previously been not as secure as it could have been and open to possible abuse. This has now been addressed and zms and zmu both now use (optional) authentication strings to validate access. You need to have openssl installed so that the MD5 libraries can be linked. See the ZM_AUTH_METHOD and ZM_AUTH_SECRET configuration items for further details.
* FEATURE : The maximum daemon restart delay in zmdc.pl was previously fixed at 15 minutes. This may have been too long for some users, for example if power has failed to a camera then a 15 minute delay on restoration is not desirable. This maximum is now configurable via the ZM_MAX_RESTART_DELAY configuration item.
* FEATURE : The web files have been changed to use the newer style autoglobals, e.g. $_SERVER rather than $HTTP_SERVER_VARS. This should enable use on PHP5 without any modification.
* FIX : The use of two database users has been somewhat redundant for a number of versions now. In 1.20.0 there is only one database user. The zmupdate.pl script unfortunately cannot handle the migration as it needs to access the database so you should make a note of the username and password of the privileged user and then re-enter that using zmconfig.pl when rebuilding ZM.
* FIX : The zmupdate.pl script previously held a database connection open for days at a time but only used to use it periodically. This has now been changed to be only open while in use.
* FIX : Debug output and it’s relationship with environment variables etc was previously broken. This has been tidied up and made much easier to use and understand.
* FIX : A number of SQL queries have been analysed and optimised to run much faster.
* FIX : The monitor status was not always being reported correctly in the monitor watch window. This has been corrected.
* FIX : Image numbering in the zmf daemon was sometimes wrong if more or less than three significant digits were used. This has been corrected.
* FIX : Image capture timeouts used by zmwatch.pl to restart apparently frozen zmc processes were being calculated incorrectly on occasion. This was causing some unnecessary processes to be restarted. This calculation has been fixed.
* FIX : Complete DOCTYPE headers were added to HTML output and some HTML was tidied up to be more compliant.
* FIX : There was a problem with the interaction between monitor statuses and the status web window. This meant that sometimes the window did not pop to the front, or play the alarm sound, properly. This has been corrected.
* FIX : Some network cameras send data in a format which was previously not recognised by the regular expression engine. This has been modified to allow these cameras (NC1000 etc) to function with ZoneMinder.
* FIX : A bug in event streaming when events are of very short duration has been fixed. Thanks to forum user ‘reza’ for spotting this one.
* FIX : A possible exploit in the login page was identified and has now been fixed. Thanks again to forum user ‘reza’ highlighting this problem also.
===Release 1.19.5 - 2004/09/26===
Various miscellaneous fixes and features.
* FIX : Sorting event lists by duration was broken and has now been corrected.
* 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.
* FIX : The modification suggested by forum user ‘oskin’ has been incorporated into the code to try and reduce or remove video for linux errors.
* FIX : The remote network camera parsing code has been patched to try
* FIX : The error reported when a ‘shmget’ call fails has been changed to include further information about the cause.
* LANGUAGE : Fixed missing semicolon in German language file.
* FEATURE : Added ‘<<’ and ‘>>’ links to the page selector in the events list as suggested by forum user ‘unclerichy’.
* 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’.
* 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.
* 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.
* 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.
* 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.
* FEATURE : You can now specify a prefix for events generated by particular monitors. This will replace the default ‘Event-‘ one.
* 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,
* 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.
* FIX : A default php error level excluding notice warnings is now explicitly set.
* 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.
===Release 1.19.4 - 2004/05/20===
Language fixes and updates.
* FIX : The US English language file was recursively including itself rather than the UK English file as the base language.
* LANGUAGE : The Brazilian Portuguese language file detailed in the previous release has actually been included in this one.
* LANGUAGE : The Argentinian Spanish, Polish and Italian translations have all been updated with tokens introduced in version 1.19.3.
===Release 1.19.3 - 2004/05/06===
Minor tweaks, fixes and language updates.
* FEATURE : All stills views now use the single image mode of zms rather than spawning off a zmu process to write an image which is then read. This reduces complexity of double buffering significantly and also reduces the chance of errors caused by multiple simultaneous image generation.
* FEATURE : The generated MIME types when creating streamed video were previously assigned by zms depending on which of a limited number of output formats was specified. This has now been changed so that the ffmpeg libavformat library itself now generates these identifiers. The consequence of this is that many more video formats supported by your version of ffmpeg should now be available via zms.
* FEATURE : When viewing a single frame of an event you can 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 which made it difficult to configure zones configured in percentage terms. These values are now displayed in both pixel and percentage terms to assist in zone configuration. Note that the percentage values are based on the current size of the zone so if this is changed then the value displayed will not be applicable at the time of event generation.
* FIX : When doing motion detection an extra blob, that could never be removed, was sometimes included. This could have caused false triggering and has not been corrected.
* FIX : A problem was reported whereby when using bulk frame records to reduce database load the last frame record was not written. Replaying the event via the web interface resulting in the event being truncated. A correction has been made so prevent this and ensure that the last frame of an event is always recorded.
* 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 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 to help identify them.
* FIX : In more recent versions of MySQL the password hash generated is 50 characters long, which overflows the previous password field in the database which was only 32 characters long. This field has been extended to 64 characters to accommodate this.
* FIX : The montage view had an error whereby the refresh timeout for stills was mislabelled causing continuous refresh attempts which rendered the view mostly unusable. The constants in question are now correctly referenced.
* FIX : The default, bandwidth specific, rate and scales were not always used as the records in the database were misnamed. This is now corrected though you may need to reset the values that were used previously as these will be lost if they had been changed.
* FIX : It was previously the case that old images could be 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 after a short period. Please ensure that if you have customised the web interface and have images you wish to keep that they are not left in the temporary images folder as they will now be deleted.
* FIX : A JavaScript error in the Zone configuration screen was identified and fixed.
* LANGUAGE : A Brazilian Portuguese translation has been supplied by Victor Diago and is available by selecting ‘pt_br’ as the language type.
* LANGUAGE : Updated versions of the Dutch and Argentinian Spanish translations have been included.
===Release 1.19.2 - 2004/04/22===
Minor features, fixes and language updates.
* FEATURE : The default replay rate and live and event scale settings are now configurable on a per bandwidth basis rather than globally. This allows you to view at full scale when you have high bandwidth and at smaller scales when you do not have so much resource. You will need to re-configure your previous defaults as they will be lost.
* FEATURE : Filters can now include a specification of the preferred sort order of the results.
* FEATURE : Filters can now include a specification to limit the results to a predefined maximum
* FEATURE : Two new filter elements have been added. These are disk blocks and disk percentage. These are event independent and return the amount of disk space used on the event partition in terms of disk blocks or percentage as returned by 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 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 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 filters created using disk related terms to delete events should always contain a limit term also otherwise it is possible for all events to match and thus be deleted. Using a limit ensures that only a small number are affected at any one time.
* FEATURE : Filters can now be defined to automatically execute an external script or program of your choosing. This can be specified when the filter is saved. Note that for security reasons this cannot be just any arbitrary command but must be readable and executable by your web server effective user. The script or program you specify here will be executed in the events root directory once for each event and will be passed one parameter containing the relative path to the event directory. This will normally be of 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 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 not be set.
* FIX : In some circumstances temporary diagnostic images were being saved instead of highlighted analysis images. This is now corrected.
* FIX : When viewing a list of frames in an event, the link to the diagnostic image was incorrect. This is now fixed.
* FIX : The Archive link from the monitor watch window has been fixed. Previously this generated a bogus window.
* FIX : The zone definition have been updated so that selecting the various types of zones etc only disables those options you no longer have access to rather than wiping them out entirely. This is also true of the zone when saved. Thus you can now more easily change a zone to be temporarily inactive for example and have your previous active settings restored in the future.
* FIX : Selecting an event from the list generated by a filter that included a Monitor Name term did not previously work properly. This is now fixed.
* FIX : A number of the constants used internally have been renamed to be more consistent. Hopefully nothing is broken!
* FIX : Following notification of a potential vulnerability in zms by Mark Cox, all non-trivial string and buffer copies are now limited by the maximum size of the destination. Mark has also askedme to include the following notice relating to this, which I am very happy to do.
"This issue was discovered by Mark J Cox <mark@awe.com>. The Common
Vulnerabilities and Exposures project (cve.mitre.org) has assigned the
name CAN-2004-0227 to this issue."
* LANGUAGE : An additional Italian language translation has been added. One, by Davide Morelli, was included in 1.19.1 but not announced. However like buses another one has come along, from Tolmino Muccitelli, and so they are both now present. The original translation is accessible by selecting it_it as the language whereas the new one is it_it2. I would prefer if they were merged as two versions of one language is not easy to maintain when I don’t know what the differences mean!
* LANGUAGE : A version of Argentinian Spanish by Fernando Diaz has also been included and is accessible by setting your language to es_ar. As with all the language translations I cannot vouch for the completeness or accuracy of the language files so feel free to feedback any updates you think should be made.
* 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 timescale.
===Release 1.19.1 - 2004/03/24===
Minor bugfixes and enhancements.
* 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.
* Pcre Configure Changes. The configure script has been modified to look for the pcre.h header file in both /usr/include and /usr/include/pcre rather than just the latter as previously.
* Remote Image Parsing. Further improvements have been made to handle additional patterns of images with differing styles of terminations or none at all.
* Event Image Numbering. An additional configuration option (ZM_EVENT_IMAGE_DIGITS) has been added to allow the user to define how many significant figures should be used to number individual event images.
* Frame Listing Timestamp Bug. Fixed a bug where in the event frame listing view the timestamps were not correctly displayed.
* Event Filters Bug. Fixed (again) a bug where several fields used in event filters did not generate valid database queries.
* Zmu Device Authentication. Removed the previous requirement to pass in a username and password to zmu when just querying a device as this was slightly broken and was unnecessary anyway.
===Release 1.19.0 - 2004/03/18===
Some major enhancements and bugfixes.
* MPEG video streaming. ZoneMinder now supports true video streaming if configured with the --with-ffmpeg option. This allows one or both of live or event streaming to be in this format rather than motion JPEG style as before. Note however that is still somewhat experimental and may not work on your system. The reason for this is due to the variation in plugins and video movie formats. Currently I have got it working well with browsers on Windows platforms using the Windows Media Player plugin and the 'asf' video format. I have also managed to get event streaming working on Mozilla using mplayer (I think) though it jumps in and out of it's place in the window a bit. I would appreciate any feedback or advice on formats and plugins that work on your system. Also note that video streaming tends to get buffered before being displayed. This can result in the 'live' view being several seconds delayed.
* 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 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 that one ZoneMinder installation can use another as a remote video source.
* NPH Streaming. After months of frustration I have finally figured out why streams were corrupted using Cambozola versions after 0.22. It turned out that apache was injecting characters into the streams which was screwing up the headers. I believe this to be because the initial header had no content-length header, as the length is indeterminate. So I have added a zero content length header which I believe fixes the problem though perhaps not in the best way. I have also made the installation link the existing zms binary to nph-zms so that you can now use zms in non-parsed-header mode. If it detects it is in this mode then the content-length header is not output, though several other additional ones are. In nph mode the false character injection seems to disappear so I suspect this is a better way to use zms.
* Bulk Frame Records. With the recent advent of the 'Record' and 'Mocord' modes a lot of people have started using ZoneMinder as a pseudo-DVR. This meant that a lot of database 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 detection activity is taking place and normal frame records are kept otherwise.
* Event List Ordering and Scrolling. It was previously the case 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 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 that next and prev refer to the order of the list you should be ok.
* Zone Percentage Sizes. Zone motion detection parameters can be defined either in terms of total pixels or as a percentage. This percentage was defined relative to the size of the image as a whole. However this was difficult to calculate or estimate especially with several zones of varying sizes. In version 1.19.0 this has been changed so that the percentage relates to the size of the zone itself instead. This should make calculations somewhat easier. To convert your existing zones you can run zmupdate.pl with the -z option, though this should be done only once and you should backup your database beforehand in case of error.
* Console View System Display. The console display was slight revamped to indicate disk space usage (via the ‘df’ command) on the events partition,
* Zone Form Validation. Changes applied in version 1.18.0 to prevent invalidate entries in the zone definition form actually had the opposite effect due to JavaScript treating everything as a string and not a number (e.g. 5 is greater than 123). This is now corrected.
* Default Rate and Scales. You can now specify (in the options dialog) the default scale you would like to view live and event feeds at. You can also give a default rate for viewing event replays.
* More Rates. Additional faster rates have been included, up to 100 times.
* Frame Buffer Size. Previously it was possible for frames being sent from the analysis daemon to the frame server to exceed the defined maximum buffer size in which case the write would fail. It is now possible to define a larger size if necessary to prevent this. Note that you may have to adjust your system configuration to accommodate this. For further details check the help for the ZM_FRAME_SOCKET_SIZE option.
* Filter Name Duplication. Following recent changes to the filters table, several people reported that when saving filters they 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 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.
* Filter Form. Problem were reported with the filtering form where several selections generated SQL errors. This is now fixed.
* Filter Image Attachments. A fix was made to zmfilter.pl to prevent it trying to attaché alarm images to non-alarm events.
* Video Rate Specification. A fix was made to zmvideo.pl that corrected a problem with no default frame being used if none was passed in.
* RBG->BGR Black Screen. Fixed an issue with black screens being reported in RGB24 mode if RGB->BGR invert was not selected.
* Monitor Deletion. Fixed a problem with event files not being deleted when monitor was.
* A translation for the Dutch (nl_nl) language has been included.
===Release 1.18.1 - 2004/02/21===
Minor bugfixes.
* Filter Monitor Name Bug. A bug was present in the previous release where monitor names where not correctly handled in filters. This is now fixed.
* Database Upgrade Change. Users upgrading from releases prior to 1.18.0 please note that now as part of the upgrade process all your filters will have any automatic actions unset. This is because the previous affinity to a particular monitor has now been removed and you may be left with several filters all doing the same thing to all of the events or have filters which for instance delete events on only one monitor but which now would delete them for all of them. It is recommended that you review your list of saved filters and delete duplicates before adding any monitor specific terms and resetting the actions for any that remain.
===Release 1.18.0 - 2004/02/20===
Major optimisations, important new features and some bugfixes.
* Optimisations and Performance Improvements. This release contains several major performance improvements in various areas. The first of these is that image processing for YUV style input formats are now pretty much handled at almost the 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.
* Remote Authentication. This document has previously indicated that basic authentication for network cameras could be used by entering a hostname of the form of <user>:<pass>@<hostname>. This was not actually the case as the relevant authentication header was never sent. This is now fixed and addresses of this form can now be used.
* Filter Date Parsing. The zmfilter.pl date parsing now correctly reports when dates or times which it cannot parse are used.
* 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 affected as many or as few monitors as you wish. IMPORTANT: Please note that as part of the upgrade process all your filters will have any automatic actions unset. This is because the previous affinity to a particular monitor has now been removed and you may be left with several filters all doing the same thing to all of the events or have filters which for instance delete events on only one monitor but which now would delete them for all of them. It is recommended that you review your list of saved filters and delete duplicates before adding any monitor specific terms and resetting the actions for any that remain.
* 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 also available.
* Additional Scales. Enhancements to the scaling algorithm mean that non binary scales are now just as easy to apply, thus new scales such as 0.75x have been added. Others can be easily included if necessary.
* Montage Sizing. The montage view allows you to view all of your active cameras in one window. However if your 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.
* Compact Montage. The traditional montage view includes individual small menus for each monitor and a status display. This results in a somewhat cluttered display and the refreshing of the status displays may generate more accesses than desirable. Using the ZM_WEB_COMPACT_MONTAGE configuration option allows this montage view to only include the monitor streams and one overall menu bar with no status displays.
* Monitor Name Constraint. The name given to a monitor is used in file paths and several other areas. Thus it is important that it follows certain conventions but up until this release these names were unrestricted. The monitor form now limits monitor names to alphanumeric characters plus hyphen and underscore.
* 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.
* Scaleable Stills View. The stills view of a monitor (when streaming is not available or desired) is now scaleable in the same way as the streamed view.
* Double Buffered Stills View. The stills view has now been restructured to allow a double buffering approach. Thus a new image is loaded in the background and only written to screen when complete. This removes the refresh flicker that means that the screen blanks periodically however uses more JavaScript so may not be suitable for all platforms. Whether ZoneMinder uses double buffering or not is controlled by the ZM_WEB_DOUBLE_BUFFER configuration option.
* Fixed Length Event Bug. A bug was reported whereby the fixed length events that could be specified for use in Record or Mocord mode could 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.
===Release 1.17.2 - 2004/02/06===
Minor features, bug fixes and additional languages.
* Pending Process Bug. A bug was found whereby a process that was scheduled to be started in the future (due to repeated failures) would drop out of the pending queue if a further explicit restart was attempted. This is now fixed.
* Strsignal Function. The strsignal function was included from version 1.17.1 however this is not ubiquitous on all distributions. The existence of this function is now tested for by the configure script and it is not used if not present.
* 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 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 added to the zone definition form to try and prevent bogus or invalid settings.
* 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. 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 these for the image prior to an alarm but those following it are included and should assist in tuning the zones to provide optimal motion detection.
* Event Images Renamed. The capture and analysis images recorded during an event have been renamed from capture-???.jpg to ???-capture, and from analyse-???.jpg to ???-analyse.jpg. This is to allow all images (including diagnostic ones) to be associated with the frame sequence number more easily. This means that old events will no longer be able to be viewed as the wrong image will be being searched for. To avoid this you can use the new ‘zmupdate.pl’ utility to rename all your old images by doing ‘perl zmupdate.pl -r’ as an appropriately privileged or root user.
* Version checking. ZoneMinder will now optionally check for new versions of itself at zoneminder.com. This is done with a simple http get and no personal information otherwise than your current version of ZoneMinder is transmitted or recorded. If new versions are found you may be alerted of them via the web interface. This is an initial step towards enhancing and automating the upgrade process.
* Force Java. Previously ZoneMinder could be forced to override 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 be used to provide all alternatives.
* Alarms Cleared on Exit. In previous versions if an alarm was present when the analysis daemon (zma) exited the alarm would remain flagged. This had little effect except if the monitor was being watched however it was a bit annoying so any alarm flag is now cleared when this daemon exits.
* New Languages. Translations for Japanese (ja_jp), French (fr_fr) and Russian (ru_ru) are now included.
===Release 1.17.1 - 2004/01/21===
Bugfixes and additional languages.
* Login Bug. A bug was identified whereby an unauthorised user could gain access to the console view of ZoneMinder. This was the only view available and no access to any camera views or configuration was possible. This bug is now fixed.
* New Languages. Two new language files were added. These allow ZoneMinder to use the German (de_de) and Polish (pl_pl) languages.
* 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.
* Option Language. The prompts and help text for the options is now 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.
===Release 1.17.0 - 2004/01/15===
Language changes and other enhancements.
* Version Numbering. ZoneMinder version numbers have now 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 release. Now the version number is in the x.y.z format where a change in x signifies a major fundamental or architectural rework, a change in y will indicate a new release containing incremental feature changes or fixes recommend to all users and a change in z will generally mean minor non-functional or critical modifications which would not be recommended as important to all users. As ZoneMinder has been referred to by the point release up until now, e.g. .15, .16 etc the next number in that sequence has been retained for continuity and to avoid having any ambiguity in version numbers.
* Language Support. ZoneMinder now allows specification of system and user specific languages other than UK English. These languages are given in language files named zm_lang_nn_mm.php which can be created from the default zm_lang_en_gb.php file. If your language is not included then please consider doing a translation by checking this file and submitting your changes back for inclusion in future releases.
* Syntactic Improvements. Previously setting ‘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 been revisited and revised to ensure that a many of these problems as possible have been eliminated and only the very few where the fix would be significantly less optimal than the problem remain.
* Stream Scaling Resizing. Previously when watching a stream and modifying the scale of the streamed feed only the actual feed would change size and the containing frames and windows would remain the same. This was fine for changes to smaller scales but problematic for larger scales. This has been changed for that the window and frames will now resize appropriately.
* Mmap Return Value. A problem identified by users in the forum relating to checking of return values from the mmap function call has been corrected.
* Minor Bugs. A number of minor bugs and inconsistencies were corrected.
===Release 0.9.16 - 2003/12/16===
Major usability enhancement and fixes.
* 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 current monitor functions and saves that. You can then reselect that state later which basically involves resetting the monitors to have these saved functions and then doing a system restart.
* New Monitor Functions. Instead of Passive, Active, and X10, the modes are now Monitor (= old Passive) which just allows 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.
* 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.
* Paginated Event listings. The event listings are paginated by default. You can list all of the events if you like by choosing the appropriate option. There are shortcuts to pages of events at the top of the listing. If these produce strange looking sequences like 1,2, 3, 5, 9, 17, 37 etc this is deliberate and uses an exponential algorithm intended to allow you to quickly navigate through the list to a particular page in the minimum number of clicks.
* Scaleable Streams. Event and monitor streams can now be scaled to a certain extent allowing you to view at a different resolution than that captured. This area may be somewhat incomplete especially in terms of monitoring at a higher screen size where the frame is not adjusted properly.
* Variable Frame Rates. Event streams can now be viewed at various rates allowing faster review (if your bandwidth allows) to long events, or slower for more precision.
* Scaleable/Variable MPEG generation. Generation of MPEG videos now also allows you to specify the scale relative to the original image and also the frame rate. Again, for long events captured in the perpetual recording modes this will allow a faster review of the period the event covers.
* Tabbed Monitor options. Specification and modification of monitors is now in a tabbed form for easier navigation.
* Additional stream headers. The stream headers have been changed to hopefully ensure that they are less likely to be cached.
* Maximum process restart delay. zmdc.pl now has an upper limit (15 minutes) to the time it waits before restarting continuously crashing processes.
* 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.
* Adaptive Watchdog. zmwatch now more adaptive to actual frame rates.
* Fixed zmfilter CPU sucking bug. zmfilter.pl will now restart on failure to read shared memory. Previously this could go into a nasty CPU sucking loop!
* New zmconfig options. zmconfig.pl has a new option to run with no database if necessary
* File reorganisation. Various administrative file changes and reorganisations.
* Compiler warnings. Various tweaks and modifications to reduce compiler and memory warnings.
* SQL Buffer size. Increased SQL buffer size to cope with large pre-event buffers, plus a couple of other buffers have been enlarged.
* Incorrect Frame time offsets. The time offsets in alarmed frames were incorrect and based on the time of storage rather than capture. This gave the impression that there was a delay after the first alarmed frame and messed up some streaming timings. This has been fixed.
* Event Frame listing. You can now view details of the frames captured such as their time and score etc by clicking on the scores in the events views.
* Refined shared memory handling. Fixed zmfilter, zmwatch and zmx10 to allow zero as a valid shared memory id to allow them to keep on working if the segment has been marked for deletion
* Frame daemon stability. Changed image buffer in zmf to be static rather than dynamic. This has made zmf much more stable.
* MPEG overwrite option. Fixed the 'Overwrite' checkbox in video generation to actually overwrite the video. Modded the page slightly also.
* Daemon control improved. Changing between monitor functions, e.g. Modect, Mocord etc now restarts the correct daemons.
* Improved time based filters. Filters that include time based clauses now get executed regardless of whether new events are being generated.
* Audit daemon started unconditionally. zmaudit is now started regardless of the setting of FAST_DELETES as zmfilter depends on it being there.
* Filtering more active. zmfilter is now started in 'Monitor' mode. It does not run in when monitors are completely off however.
* Stills paged. The stills view of events is now paginated for easier navigation.
* Archive images optional. Normally when an alarm is detected a set of raw images is saved along with a mirror set of images containing motion highlighting. This second set can now optionally be disabled.
* Settings in auth mode. Control of camera brightness, contrast etc did not previously work when running in authorised mode. This is now fixed.
* zms parameter bug fixed. The streaming server incorrectly parsed and assigned one of it’s arguments. This is now fixed.
* zmu brighness bug. Previously camera brightness was not correctly parsed from command line options passed to zmu.
* Event window width variable. Event windows now scale to fit the event image size.
===Release 0.9.15 - 2003/07/10===
Various bug fixes from the last release and before.
* Bandwidth. A bug was introduced in .14 which caused a corrupted console display and manic refreshes on new installations. This was due to a missing bandwidth setting when no existing cookie was detected. This is now fixed.
* Again in .14 a problem occurred for a new release whereby zmconfig wanted to know the database details and but also previously wanted to access the database before it had asked the questions. This has now been addressed though it does require that zmconfig is run twice initially, once to created the scripts and once to import the configuration into the database.
* In association with the previous error, the zm_config_defines.h file was not created in the absence of the database as this was what was used to assign configuration ids. This now takes place regardless of the database.
* The SQL to create the Users table was mistakenly omitted from the .12 database upgrade script this has now been corrected.
* A bug in zmfilter was pointed out whereby the dynamic loading of the Zip or Tar archive modules depending on a preference actually wasn’t. It was looking for both and loading both at compile time. This has now been modified to be fully runtime.
* The database user definitions in the zmvideo script indicated one database user while the database connection used a different one. This prevented any videos being generated.
* 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.
===Release 0.9.14 - 2003/07/08===
Major new feature and important bug-fixes.
* Web configuration. Following many requests and to make ZoneMinder easier to administer the configuration system has been changed slightly. You should now still run zmconfig.pl to specify an initial configuration but you now only need to answer the first few questions to give a core set of options including the database options. The remainder of configuration options can then be ignored to start with and all but the core options will be written to the database. You can then view and modify these options from the web interface and apply then without recompilation, which is now only necessary if you change the core configuration.
* Following a number of requests the .sock file directory is now configurable in zmconfig.
* 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.
* The use of the Term::Readkey perl module in zmaudit.pl has been removed. This module had been removed from zmconfig.pl previously but had lingered in this script.
* A bug was found in zmx10.pl causing a crash if time delayed X10 events were used. This has now been fixed.
* 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.
* Shared memory permissions. Following introduction of a user permissions system the previous 777 mode for shared memory was deemed insecure. Consequently from now on shared memory is only accessible from the owner. This means that zmu will only work when run as root or the web user unless you set it setuid where it should still be secure as it will require authentication.
* All SQL buffers in the C++ code have been enlarged. There was previously an issue with a buffer overflow on certain occasions.
===Release 0.9.13===
Beta version of several features and fixes, never generally released.
* Following a number of requests the .sock file directory is now configurable in zmconfig.
* Changed some of the core video calls to be V4L2 compatible. This primarily involved opening the video devices and memory maps as read/write and not just read-only.
* Shared memory has now been rationalised to prevent some common problems. Remember to shutdown the whole ZM package before installing, from this version on it will remove all old shared memory segments.
* Fixed not numeric comparison in zmwatch which was causing, or appeared to be causing, some errors.
* Fixed zone image map bug for percentage zones. When you had defined a zone in percentage terms, the image map used to select it for editing was broken. This is now fixed.
* New contrast/brightness etc adjustments feature. This accessible from the Settings link on the monitor window. It's fairly basic at present but should work for most types 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.
* Some redundant window scrollbars removed.
* Added user and access control. If enabled in config (ZM_OPT_USE_AUTH) then you will need to define and login as ZM users. There will be one users already defined, with username 'admin' and password 'admin'. This user is defined will full permissions and clicking on the 'Options' link from the main console window will allow you to modify and create users with various permission sets which hopefully will satisfy most requirements. These users (except any defined with 'system' edit capability) can be restricted to certain cameras by adding the monitor ids as a comma-separated list (no spaces) to the appropriate field. Users limited to specific monitors may not create or delete monitors even if defined with monitor edit permissions.
* Some windows now (optionally) use a JavaScript timeout to refresh themselves rather than a refresh header. Since refresh headers were interrupted if a link of the page was linked there were previously various forced refreshes from child windows to restart the refresh process. By using JS refresh timers which are not interrupted these extraneous refreshes have been mostly eliminated.
===Release 0.9.12 - 2003/06/08===
Mostly bug-fixes with a couple of minor features.
* Double first images. Fixed a problem where the first image of an event was being recorded twice. I don’t think this was at the cost of any of the other images but one copy was an extra.
* Made zmdc connect more intelligent. On the suggestion of a couple of people I have made the zmdc.pl server spawning and waiting a bit more intelligent. Rather than waiting a fixed (short) amount of time, it now polls every second for a while, stopping if the connection is made. Thanks to Todd McAnally for the initial suggestion.
* Added image view to events lists. Again a partial implementation of a suggested feature. If you click on the score column you will now get a snapshot of the event frame with the highest score. This is to enable you to quickly see what the event was about without having to watch the stream or view all the static images.
* Make delta times variable precision. A couple of problems had been reported where long events got negative durations. This was due to an overflow in a time difference routine. This had been operating on fixed precision allowing high precision for short deltas. This routine has been changed to allow variable precision and events will now have to be several days long to wrap in this way.
* 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 monitor rename bug. Renaming a monitor did not correctly modify the events directory to reflect this. This has now been fixed.
* OPT_MPEG bug. A bug was reported (by Fernando Diaz) where the results of the ZM_OPT_MPEG configuration variable was not correctly imported into the scripts. This now happens as intended.
* Fixed zmvideo.pl event length bug. The zmvideo.pl script which is used to generate video MPEG files tries to calculate the correct frame rate based on the length of the 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.
* Fixed remote camera memory leak. A memory leak was reported when capturing with remote cameras, this is now fixed.
* Orientation. Added option to rotate or invert captured images for cameras mounted at unusual angles.
* Fixed filter bug. A bug in the zmfilter.pl script was detected and reported by Ernst Lehmann. This bug basically meant that events were not checked as often as they should have been and many may have been left out for filters that had no time component. The script has now been updated to reflect Ernst’s suggested changes.
* Stylesheet change. Previously the stylesheet didn’t really work very well on Mozilla, Netscape and browsers other than IE. This turned out to be because I was using HTML style comments in there instead of C style ones. This has now been corrected so you should see the correct styles.
* Zmconfig.pl ReadKey. Thanks to a ridiculously sensible suggestion from Carlton Thomas this module has been removed from zmconfig.pl. Originally Term::ReadKey was in there for funky single character unbuffered input but that has long since disappeared so just regular perl input methods are used now. This removes one of the most irritating features about ZoneMinder installs.
* Delete monitor confirm. Due to some unfortunate accidents by users, attempts to delete monitors will now require confirmation.
* Detect linmysqlclient.a. Added better detection script into ‘configure’ top spot when libmysqlclient.a is missing.
===Release 0.9.11 - 2003/04/25===
Various new features and fixes.
* Added stats view : If you have the RECORD_EVENT_STATS directive set and are viewing a still image from an event you can now view the statistics recorded for that frame. This tells you why that frame triggered or participated in an alarm. This can be useful in tuning the various motion detection parameters and seeing why events occurred.
* Tabulated events : The main events view is now tabulated to look a bit nicer.
* 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.
* 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.
* Fixed Mozilla JavaScript : Various JavaScript functionality did not function on Mozilla, Netscape and other browsers. This is now (hopefully) fixed.
* Allow image and mpegs to be attached to emails : Added new tokens (%EI1%, %EIM% and %EV%) to the filter emails. This allows the first alarm image, most highly scored alarm image and an alarm MPEG to be attached to alarm notification emails. Use %EV% especially with care!
* Fixed possible motion detection bug : I found a few double declared local variables left over from the rewrite. This may have affected the motion detection algorithm. Fixed now anyway.
* Modified scoring : Alarm scoring has been modified to give more granularity for smaller events. This will have the effect of raising the scores for small events while large ones will still be about the same.
* Fixed /cgi-bin path problem : Previously you could specify the real path to you cgi-bin directory if you have one but not the web path. You can now do both.
* Improved video handling in browser : The MPEG/video area of the web GUI had been a bit neglected and looked somewhat ugly. This has now been improved to a degree and looks a bit nicer.
* Added ffmpeg support : Historically ZoneMinder has only supported the Berkeley mpeg encoder which was slow and rather limited. ZoneMinder now supports the ffmpeg encoder as well which is much much faster and makes generation of MPEG videos at realistic frame rates more of a reality. As ffmpeg has so many options and everyone will probably want a different emphasis you can now also specify additional ffmpeg options via zmconfig.pl.
* Colourise greyscale image files : In past versions, captured greyscale images were stored as JPEG files with a corresponding greyscale colourspace. This saved a small amount of space but meant that mpeg_encode had to do a conversion to encode them, and ffmpeg just fell in a heap. Now you can optionally opt to have greyscale images saved as full 24 bit colourspace images (they still look the same) at the price of a small penalty in CPU and disk but allowing you to easily and quickly create MPEG files. This option is one by default but can be switched off if you do not require any MPEG encoding.
* Fast RGB diffs : Previously ZoneMinder used quite a loose method for calculating the differences between two colour images. This was basically averaging the differences between each of the RGB components to get an overall difference. This is still the default but by setting ZM_FAST_RGB_DIFFS to 'no' you can now make it calculate the Y (or brightness value) of the pixels and use the difference between those instead. This will be more accurate and responsive to changes but is may be slower especially on old machines. There is a slight double whammy here if you have a YUV palette for capture and set this option off as the image will be converted to RGB and then partially converted back to get the Y value. This is currently very inefficient and needs to be optimised.
* Fixed STRICT_VIDEO_CONFIG : Previously this actually behaved the opposite of what it was supposed to, ie. if you wanted it strict it wasn't and vice versa. Thanks to Dan Merillat for pointing this one out.
* Web colour change : 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!
===Release 0.9.10 - 2003/04/11===
Many bug-fixes and major feature enhancements.
* 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.
* Low event id bug - Fixed bug where events with an id of < 1000 were being cleaned up by zmaudit.pl by mistake.
* Source file restructuring - The source files have been broken up and renamed extensively to support the first stage of the code being straightened out. Likewise the class structure has been rationalised somewhat. The php file names have also changed in some cases so it might be best to delete all your php and css files from the zone minder install directory first as the old ones won't be overwritten and will be left behind.
* Streamed cycle view - The monitor cycle view (the one where each monitor is displayed sequentially) now supports streams as well as stills.
* 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.
* Network camera support - A major change in this version is support for remote or network cameras. This is currently implemented as series of http grabs of stills rather than being able to break up motion jpeg streams. However frame rates of from 2-10 should be achievable depending on your network proximity to the cameras.
* Option BGR->RGB swap - Added the option to switch on or off the inversion of RGB to BGR for local cameras. It is on by default to maintain compatibility with previous releases.
* zmu suspend alarm option - Added new -n option to zmu to effectively suspend alarm detection for a monitor. This is intended for short term use and to support PTZ cameras where alarm detection is desired to be suspended while the camera changes orientation or zoom level.
* FPS limiting - Added a new option to monitors to add a maximum capture rate. This allows you to limit the amount of hits a network camera gets or to reduce the system load with many cameras. It also works with multi-port cards and limiting the capture rate on one camera allows the spare FPS to be allocated to other devices. For instance with two cameras and no throttle, I get about 4FPS each. Throttling one to 2FPS allows the other to operate at 6FPS so you can allocate your capture resources accordingly. This limiting can be disabled while alarms are occurring as a global option in zmconfig.pl.
* Alarm reference update - Added option to not blend alarmed images into the reference image. See the help in zmconfig.pl for caveats.
* Disappearing monitors - Fixed the disappearing monitor problem in the console view where monitors with no events were randomly not being shown.
* Clean and tidy - Cleaned up a load of compiler warnings and miscellanea to ensure a cleaner happier build.
* Streamed image headers - Made all headers in streamed images have full CRLF termination which will hopefully now prevent the problems with broken streams that had existed mostly with Mozilla (and hopefully won't break anything else).
* Expire streams - Added expiry headers to streamed images so they will always display fully.
* Event navigation - Added next, prev, delete & next, delete & prev navigation to events to allow you to quickly review events in sequence as had been requested by a number of people.
* USR blocking : The debug USR signals were not being blocked properly leading to nasty effects in zmc mostly.
* zmfilter execution : Previously zmfilter execution was not synchronised with the monitor state or the analysis daemon leading to it sometimes being run unnecessarily. From now on the zmfilter process will only run when a monitor is active and so actually potentially generating alarms.
* zmdc short statuses : Removed the logging of the short status values that zmdc.pl returns to it’s clients which had been clogging up the log file.
* 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.
===Release 0.9.9 - 2003/03/11===
Mainly bug-fixes and minor feature enhancements.
* Added zmu -q/--query option - There is now a new query option for zmu. When combined with -d it gives the config of the device and when used with -m it dumps the current settings for the monitor and zones. Mostly useful for bug reporting. The previous version of zmu used with just -d gave this information for a video device by default. This now requires the -q option also to bring into line with it's -m equivalent.
* Added creation of events directory - Previously the 'events' directory was not created on install, this has been fixed.
* Can now retag PHP files if necessary - Version 0.9.8 was the first version to use short_open_tags in the PHP files. This caused grief to some people so this script will put them back to the long verion.
* Frame and event lengths fractional - A new field has been added to the Frames table. This is 'Delta' and is a fractional number of seconds relative to the event start time. This is intended to support the real-time playback of events rather than just 'as fast as possible' or with a configured delay as at present. The event length is now also fractional.
* Corrected extraneous Width to be Height - The last version of zmu included a Width comment which should have been height.
* Changed colour depth to bits - Having colour depths expressed in bytes has caused no end of problems. This is now changed to be bits and can be changed via a dropdown to limit what can be entered. Don't forget to run the zmalter script to update your DB.
* Renamed terminate to zm_terminate - The use of 'terminate' in zmc.cpp caused a conflict on some systems so renamed it to something more specific.
* Zone deletion problem - A problem was found such that when deleting zones the appropriate daemons were not being asked to restart daemons correctly.
* Console changes - The current version number is now displayed in the console. A refresh button has also been added along with a minor reorg.
* Added delete button enable to checkAll - Using the 'Check All' button in the main monitor window previously did not enable the delete button. This is now fixed.
* Reload on click - In previous versions the console window would reload if a monitor window for example was clicked. Thsi was removed in the last version which meant that sometimes the console never go refreshed as it's timing loop was broken. This functionality has now been reinstated.
===Release 0.9.8 - 2003/01/26===
Several new features and bug-fixes
* Upgrade note - If you have installed 0.9.7 and wish to save your configuration then copy your existing zmconfig.txt file over to your 0.9.8 directory and before running zmconfig.pl.
* Added multiple options to zmu - You can now give multiple options to zmu and get all the responses at once. However this is currently in a deterministic order and not related to the order you give them.
* Added -v/--verbose option to zmu - Zmu has been made more human friendly though it still remains primarily for daemon use. Giving the -v or --verbose option prints out a bit more as a response to each command.
* Add -d/--device to zmu - This option is designed to allow you to get your video device working with another application such as xawtv and then use zmu -d to print out the settings it’s using
* (especially with the -v option). These options can then be used as a starting point for your ZoneMinder configuration.
* Added FPS in status field - The status field in the web monitor views now contains an FPS setting as well as the status.
* Zmconfig changes - zmconfig handles missing options better and rewrites config file even in non-interactive mode.
* Fixed config problems in zmcfg.h - Some config was not being set up correctly in zmcfg.h.
* 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.
* 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.
* Fixed bug in Scan mode - The monitor cycle or scan mode had stopped working properly due to images not being generated. This is now fixed.
* Revamped the console window slightly - The console window has now been reformatted slightly to give more and better information including server load.
* Added email and messaging to filters - Filters now allow you to send emails or messages (basically just short emails intended for mobile devices) on alarms. The format and possible content for these emails is in zmconfig_eml.txt and zmconfig_msg.txt.
* Made zmdc more aggresive in killing old processes - The zmdc.pl daeamon will now kill any ZoneMinder processes it finds on startup or shutdown to prevent orphans from being left around.
* Configuration changes - Previously there were a lot of files generated by configure. Now only zmconfig.pl is generated this way and all the other configuration files are created by zmconfig.pl (from .z files) to centralise configuration more.
* Fixed cambolzola opt bug - There was a bug in the Cambozola options, I can't remember what it was but it's fixed!
* Retaint arguments in zmdc.pl - In some installations zmdc was complaining about tainted arguments from the socket. These are now detainted prior to sending and after receiving.
* Forced alarms - You can now force alarms when looking at the monitor window should anything catch your attention. You have to remember to switch them off as well though.
* Looser video configuration - Some video configuration errors can now be ignored via the STRICT_VIDEO_CONFIG option.
* 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.
===Release 0.9.7 - 2003/01/12===
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.
* Added zmconfig.pl script to help with configuration.
* Revamped to work better with configure scripts
* Monitors now have more configuration options, including some that were statically defined before such as location and format of the image timestamps.
* Removed Alarms table from schema as not required, never was actually...
* Added a number of new scripts, see the scripts directory
* Added Fast delete to PHP files. This allows the web interface to only delete the event entries themselves for speed and then have the zmaudit script periodically tidy up the rest.
* Added event filter to enable bulk viewing, upload or deletion of events according to various attributes. Filter can be saved and edited.
* Added last event id to shared memory for auto-filtering etc.
* Changed zmu -i option to write to monitor named image file.
* Made shared memory management somewhat more sensible.
* Now stores DB times as localtime rather than UTC avoiding daylight saving related bugs.
* Fixed bug with inactive zones and added more debug.
* Changed main functions to return int.
* Added help and usage to zmu.
* Fixed browser acceptance problem, more easily defaults to HTML.
* Split out the PHP files into a bunch with specific functions rather than one monolithic one.
* Fixed NetPBM paths and changed _SERVER to HTTP_SERVER_VARS.
* Added HUP signal on zone deletion.
* Added NETPBM_DIR and conditional netpbm stuff.
* Removed hard coded window sizes, all popup window dimensions can be specified in zmconfig.php
* Changed form methods to 'get' from 'post' to avoid resubmit warnings all the time.
* Added conditional sound to alarm on web interface.
* Fixed syntax error when adding default monitor.
* Some of the web views have changed slightly to accommodate the separate events view.
* And much much more, probably...
===Release 0.0.1 - 2002/09/25===
Initial release, therefore nothing new.

Zms-inetd

2014-10-03T18:02:17Z

Gkmac: Undo SPAM revision 6418 by Erictenne (talk)

'''zms-inetd''' is an [http://en.wikipedia.org/wiki/Inetd inetd]-wrapper for the ZMS (Zoneminder Streaming Server), so ZMS can work "standalone".

* '''Author''': Kurt Zankl <kz@xon.uni.cc>
* '''Inspiration''': http://www.debian-administration.org/articles/371
* '''Requirements''': bash, inetd
* '''License''': GNU General Public License, Version 2

== Motivation ==

I'm using Zoneminder with [http://nginx.net/ Nginx Httpd], which doesnt support simple CGI (just FastCGI). So I needed a leightweight solution to make ZMS work without any extra software. This script depends only on inetd and bash.

=== Installation ===

Just copy and paste the zms-inetd-script from below (Section "Script") into a text file and save it, for example, as <code>/usr/local/bin/zms-inetd</code>. Don't forget to make it executable (<code>chmod 755 /usr/local/bin/zms-inetd</code>).

=== /etc/services ===

As for every inetd-service you have to define a port number in /etc/services:
zms-inetd 85/tcp # Zoneminder ZMS inetd-wrapper

=== /etc/inetd.conf ===

Of course also an entry in the inetd configuration is needed. Please adapt this to your needs (user [= www], path):
zms-inetd stream tcp nowait www /usr/local/bin/zms-inetd zms-inetd

=== Path to zm.conf ===

Set the ZMCONF variable in the shell-script appropriate.

=== Zoneminder-Configuration ===

The last step is to adjust the web path (URL) to ZMS. This is done through the ZM-Webinterface > Options > Paths > Web path to zms streaming server (ZM_PATH_ZMS). According to the configuration above this would be:
<nowiki>http://<server>:85/<anypath></nowiki>
It doesn't matter which path you specifiy as zms-inetd will always proxy to the ZMS cgi-binary for security reasons.

== Further thoughts ==

=== Make it transparent ===

In combination with Nginx its propably useful not to point ZM directly to the zms-inetd port, but mask it with a reverse proxy configuration in Nginx. That should avoid some problems if you want to reverse proxy the whole ZM installation (eg: from intranet to the internet).

Example:
location /zm/zms-inetd {
proxy_pass <nowiki>http://127.0.0.1:85;</nowiki>
}

Of course you have to adjust the cgi-bin path (ZM_PATH_ZMS) appropriate (eg: <code>/zm/zms-inetd</code>).

=== Other use cases for zms-inetd ===

Another scenario where zms-inetd perhaps could also be used is a leightweight or embedded system, just running ZMS. For example the [http://busybox.net/ busybox] multibinary offers an inetd and a shell. Due the fact that zms-inetd is not heavily integrated with bash it should not be too hard to adapt it to ash (default shell in busybox).

== Script ==
<pre><nowiki>#!/bin/bash
#
# Inetd-wrapper for ZMS (Zoneminder Streaming Server)
#
# Version: 2007-09-27
# Author: Kurt Zankl <kz@xon.uni.cc>
# Inspiration: http://www.debian-administration.org/articles/371
# Requirements: bash, inetd
# License: GNU General Public License, Version 2
#
# /etc/services:
# zms-inetd 85/tcp # Zoneminder ZMS inetd-wrapper
#
# /etc/inetd.conf:
# zms-inetd stream tcp nowait www-data /usr/local/bin/zms-inetd zms-inetd
#
# ZM Options / Paths / Web path to zms streaming server:
# ZM_PATH_ZMS = http://<server>:85/<anypath>
#

# configuration
ZMCONF="/usr/local/etc/zm.conf"
CGIBIN="zms"

# error handler
function errormsg {
echo "HTTP/1.0 500 Internal Server Error"
echo "Content-Type: text/html"
echo
echo "<title>ERROR</title><h1>ERROR</h1>"
echo -e "<pre>$1</""pre>"
exit 1
}

# get request
read REQUEST
# skip headers
HEADER="nothing"; while [ "$HEADER" != $'\r' -a -n "$HEADER" ]; do read HEADER; done

# read ZM configuration
[ -r $ZMCONF ] || errormsg "Error reading Zoneminder configuration \"$ZMCONF\""
. $ZMCONF
ZMS="$ZM_PATH_CGI/$CGIBIN"
[ -x $ZMS ] || errormsg "Error finding ZMS executable \"$ZMS\""

# check request
[ -z "$REQUEST" ] && errormsg "Request is empty"

# split request
URL="${REQUEST#GET }"
URL="${URL% HTTP/*}"
QUERY="${URL#*\?}"
URL="${URL%%\?*}"

# check query
[ "$QUERY" == "$URL" ] && errormsg "Invalid query"

# execute ZMS
# (STDERR output is discarded as this confuses MPEG streaming clients)
export QUERY_STRING="$QUERY"
echo "HTTP/1.0 200 OK"
"$ZMS" 2>/dev/null
echo
exit 0</nowiki></pre>

Trendnet

2014-10-03T18:02:02Z

Gkmac: Undo SPAM revision 6417 by Erictenne (talk)

= TV-IP100 =
Trendnet TV-IP100 works ok.
http://x.x.x.x/video.cgi

= TV-IP100W-N =
great little wireless camera with digital zoom

Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@x.x.x.x (admin:admin is the default user/pass)
Remote Host Port: 80
Remote Host Path: /MJPEG.CGI

=TV-IP110 & TV-IP110W=

Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: <username>:<password>@x.x.x.x
Remote host Port: 80
Remote Host Path: /cgi/mjpg/mjpg.cgi
Remote Image Colors: 24 bit color
Capture Width: 640
Capture Height: 480

The capture height and width can be changed using the camera's web interface by modifying the "Video Quality" setting.
VGA = 640 x 480
QVGA = 320 x 240
QQVGA = 160 x 120

= TV-IP201P and TV-IP201W =
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@x.x.x.x (admin:admin is the default user/pass and 192.168.0.30 is the default IP)
Remote Host Port: 80
Remote Host Path: /goform/capture

= TV-IP252P =
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@x.x.x.x (admin:admin is the default)
Remote Host Port: 80
Remote Host Path: cgi/mjpg/mjpg.cgi

=TV-IP262P and TV-IP262PI=
The TV-IP262P and PI are megapixel indoor fixed position cameras with has night vision via IR for up to 12m. The PI model supports Power over Ethernet (PoE).

for mjpeg:
Source Type: Remote
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@<IP address of camera>
Remote Host Port: 80
Remote Host Path: cgi/mjpg/mjpg.cgi

You can also get higher framerates using mpeg4 with ffmpeg or h.264, but I was getting the occasional false motion detect due to image noise and/or video smearing with this. I cannot find a way to force the camera to use tcp. The resolution here must match the resolution you have selected in the camera.

Source Type: Ffmpeg
Maximum FPS: empty
Alarm Maximum FPS: empty
Source Path: rtsp://user:pass@<IP Address of Camera>/mpeg4 or rtsp://user:pass@<IP Address of Camera>/h264
Capture width (pixels): *see below*
Capture height (pixels): *see below*

:{| class="wikitable"
|+ Resolution / Frame Rate:
|-
!Camera Setting
!Resolution
!Max frame rate
|-
|SXGA || (1280 x 1024) || up to 15fps
|-
|720p || (1280 x 720) || up to 15fps
|-
|VGA || (640 x 480) || up to 30fps
|-
|QVGA || (320 x 240) || up to 30fps
|-
|QQVGA || (160 x 120) || up to 30fps
|}

You can use 3GPP instead of mpeg4 if you enable it in the camera, but the image quality is horrible and it isn't useful for motion detection. If you change the image with in the camera settings, change the width and height above to match. The frame rate should be left blank and set only in the camera settings via. the camera's admin interface.

= TV-IP300 =
Just remember to turn 1.0 in ZM_HTTP_VERSION in the Options > Network tab. In the x.x.x.x/cgi-bin/video.jpg gives 352 x 240 jpg.

= TV-IP301 =
This camera sends the wrong mime/type and is not compatible with ZoneMinder natively but can be made to work.

http://www.zoneminder.com/forums/viewtopic.php?t=7320

=TV-IP310PI=
This appears to be the same camera as '''Hikvision DS-2CD2032-I''' and some individuals have found their firmware to be interchangeable.

'''For h.264/MPEG4 configuration'''

Remote Protocol: ffmpeg
Source path: rtsp://user:pass@<camera ip address>/streaming/Channels/1

'''For MJPEG configuration'''

Remote Protcol: ffmpeg
Source Path: rtsp://user:pass@<camera ip address>/streaming/Channels/2

The "Frame Rate" in the camera's web interface is not accurate. All my tests with VLC indicated that whatever frame rate you choose in the camera will be doubled in the actual feed. I use 8 FPS, but the feed picked up by VLC is 16 FPS and ZM indicate 8.** FPS. Until I increased the Maximum FPS setting in ZM to at least 16 I was losing a portion of the frame and generally having bad video performance.

=TV-IP322P=
[[File:tvip322p.jpg]]
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: <username>:<password>@<local ip/domain name>
Remote host Port: 80
Remote Host Path: /cgi/mjpg/mjpg.cgi
Remote Image Colors: 24 bit color
Capture Width: 1280
Capture Height: 1024
This is the config that worked for me hope it helps.

= TV-IP400 / TV-IP400W =
These are cheap but fun Pan Tilt Zoom IP cameras and are now also supported by ZoneMinder.

New Driver and instructions for ZM 1.23.x :
http://www.sfpeter.com/2008/07/31/new-trendnet-tv-ip400w-controller-for-zoneminder-123x/

Older Driver and instructions for 1.22.x:
http://www.sfpeter.com/2007/08/14/controlling-the-trendnet-tv-ip400w-camera-with-zoneminder/
The above link is missing the "Move" tab when creating the control. You need to select "Can Move", "Can Move Diagonally" and "Can Move Relative".

= TV-IP410 and TV-IP410W =
These are cheap but fun Pan Tilt Zoom IP cameras and are now also supported by ZoneMinder.
Look at http://www.dubuque.k12.ia.us/it/zoneminder.html

Remote Host Path: /cgi/jpg/image.cgi --> is not very fast...

Better use /cgi/mjpg/mjpg.cgi --> 20 Frames/s much more fun ;)

= TV-IP422 =

[http://trendnet.com/products/proddetail.asp?prod=150_TV-IP422&cat=152 TRENDnet TV-IP422]

Info from [http://thierry-jaouen.fr/dokuwiki/doku.php?id=serveur_zoneminder#tv-ip422 thierry-jaouen.fr] (in French)

JPEG stills streaming seems to be very slow.

'''General'''
{| border="1"
! Tab/Label
! MJPEG Stream
! JPEG Stills
|-
| colspan="3" | '''Source'''
|-
| Remote Host Name
| colspan="2" align="center" | [<USER>:<PASS>@]'''<CAM IP/HOSTNAME>'''
|-
| Remote Host Port
| colspan="2" align="center" | 80
|-
| Remote Host Path
| /cgi/mjpg/mjpg.cgi (not "/mjpeg.cgi" because of its broken MIME type)
| /cgi/jpg/image.cgi
|}

= TV-IP501P =
This camera works just like the IP400 without the PTZ contols.

Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@x.x.x.x (admin:admin is the default user/pass)
Remote Host Port: 80
Remote Host Path: /MJPEG.CGI

= TV-IP501W =

the Trendnet IP501W works. Here are the settings

Source Type: Remote

Remote Protocol: HTTP

Remote Method: Simple

Remote Host Name: username:password@IP-address

Remote Host Port: 80

Remote Path: /video.cgi

=TV-IP512P=

[[Image:TV-IP512P.jpg]]

HTTP
Source Type: Remote
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 80 (Default)
Remote Host Path: /video/mjpg.cgi (for mjpeg stream)
Remote Host Path: /image/jpeg.cgi (for a single jpeg frame)

RTSP
Source Type: ffmpeg
Source Path: rtsp://user:pass@<IP Address of Camera>/play1.sdp (or play2.sdp)

ZoneMinder 1.24.2 (Haven't tried earlier versions)

RTSP works with ffmpeg as above pulling 30fps when camera set to 30fps for that Profile.

Alternatively, the monitor can be configured:

Source Type: Remote
Remote Protocol: RTSP
Remote Method: RTP/Unicast
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 554
Remote Host Path: /play1.sdp

When using the above ffmpeg RTSP and camera is set to Night Mode using the 30fps setting fps drop to 15fps in the dark as per the warning that this may happen at low light levels.

=TV-IP512WN=
The TV-IP512WN is pretty much the same device as TV-IP512P. It features an additional WLAN interface and can be used with the same settings as the [[Trendnet#TV-IP512P|TV-IP512P]].

=TV-IP522P=
Warning: even though this is a 'MegaPixel' camera, it has a very wide-angle lens so the image detail isn't very high. Furthermore, replacement 1/2" lenses seem to be hard to find.

ZM configuration is similar to TV-IP512P (above) except the 522 has multiple video profiles, which should be specified as

Remote Host Path: /video/mjpg.cgi?profileid=1

(1, 2, or 3, depending on the desired profile)

Also be sure to set Capture Width and Capture Height appropriately.

MPEG and RTSP were not tested but the camera does support them.

=TV-IP551WI=

HTTP
Source Type: Remote
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 80 (Default)
Remote Host Path: /video/mjpg.cgi (for mjpeg stream)
Remote Host Path: /image/jpeg.cgi (for a single jpeg frame)

=TV-IP572PI=
The TV-IP572PI is a wired network only indoor camera that supports Power over Ethernet (PoE) and night viewing mode (to 7.5 meters) with 4 IR LED's. (The TV-IP572P does not have the night viewing mode, but is otherwise identical).

It supports 5fps 1280x800 simple HTTP image capture using:

Source Type: Remote
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 80
Remote Host Path: /image/jpeg.cgi OR /video/mjpg.cgi

It supports higher framerate H.264 capture via RTSP using Ffmpeg:

Source Type: Ffmpeg
Maximum FPS: empty
Alarm Maximum FPS: empty
Source Path: rtsp://user:pass@<IP Address of Camera>/play1.sdp
Capture width (pixels): 1280
Capture height (pixels): 720

You must leave the FPS limits off when using H.264 capture. Note that play1.sdp (as well as play2.sdp, and play3.sdp) are user-configurable on the web interface of the camera. 1280x800 video at 30 frames per second can overload a simple Zoneminder server, especially if you have multiple cameras. Loads of 0.9 have been observed on an older NetBurst-based 3.4GHz Xeon using the factory defaults on the camera. Rather than ratchet down the FPS on Zoneminder's end (which causes weird issues when capturing H.264) you should do so at the camera. A more reasonable load of 0.3 has been observed on the aforementioned Xeon with play1.sdp configured as follows: H.264, 1280x800, 10FPS, CBR, 2 Mbps. Of course, your mileage may vary. You can also reduce the resolution with the camera's settings if you're after a higher frame rate - be sure to match the resolution on Zoneminder's end.

=TV-IP651W(I)=

The TV-IP651W is a network indoor PTZ camera. The WI model supports night viewing mode with 4 IR LED's. Can be used wired or wireless with 802.11n.

HTTP
Source Type: Remote
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 80 (Default)
Remote Host Path: /video/mjpg.cgi (for mjpeg stream)
Remote Host Path: /image/jpeg.cgi (for a single jpeg frame)

Resolution, mjpeg compression, and frame rate can all be controlled via configuration options in the web setup.

(Tested on zoneminder v1.25.0.)

'''
== WARNING! ==
'''
The home position of the Trendnet TV-IP651W(I) camera ''is not settable'', and as a result will always return to its default home position upon any reason for a reboot (power failure, crash, etc.). As a result, this camera should be considered unusable for any security use above a simple baby monitor.

=TV-IP672P and TV-IP672PI=
The TV-IP672PI is a network indoor PTZ camera that supports Power over Ethernet (PoE) and night viewing mode (to 7.5 meters) with 6 IR LED's. (The TV-IP672P does not have the night viewing mode, but is otherwise identical.) Can be used wired or wireless.

It supports 5fps 1280x800 simple HTTP image capture using:

Source Type: Remote
Remote Protocol: HTTP
Remote Method: Simple
Remote Host Name: user:pass@<IP Address of Camera>
Remote Host Port: 80
Remote Host Path: /image/jpeg.cgi OR /video/mjpg.cgi

It supports higher framerate H.264 capture via RTSP using ffmpeg:

Source Type: Ffmpeg
Maximum FPS: empty
Alarm Maximum FPS: empty
Source Path: rtsp://user:pass@<IP Address of Camera>/play1.sdp
Capture width (pixels): 1280
Capture height (pixels): 800

You must leave the FPS limits off on Zoneminder when using H.264 capture. play1.sdp (as well as play2.sdp, and play3.sdp) are user-configurable via the web interface of the camera. If rate limiting is necessary, it should be accomplished via the camera's config rather than Zoneminder's. You may reduce the resolution via the camera's video config if you're after a high frame rate with low Zoneminder load, but be sure to mirror the resolution in the Zoneminder config.

(Tested on zoneminder v1.25.0.)

For PTZ and IR control you need the [[TV-IP672PI_Control_Script]] and these settings:

Under control capability:

Main: name it (suggest TVIP672PI), type is FFMPEG, protocol is TVIP672PI
Move: Can move, can move diagonally, can move mapped, can move relative
Pan: Can pan
Tilt: Can tilt
Presets: Has presets, num presets 20, has home preset (don't set presets via camera's web server, only set via ZM.)

Under control tab in the monitor itself:

Controllable
Control type is the name you gave it in control capability above
Control device is the password you use to authenticate to the camera (see script comments if you need to change the username from "admin")
Control address is the camera's ip address AND web port. example: 192.168.1.1:80

(PTZ script tested on zoneminder 1.26.5)

=TV-IP751WIC=
(Copied from TV-IP551WC and updated.)

http://www.trendnet.com/products/proddetail.asp?prod=225_TV-IP751WIC&cat=179

HTTP
Source Type: Remote
<strike>Remote Host Name: user:pass@<IP Address of Camera></strike>
Remote Host Name: <IP Address of Camera>
Remote Host Port: 80 (Default)
Remote Host Path: /video/mjpg.cgi (for mjpeg stream)
Remote Host Path: /image/jpeg.cgi (for a single jpeg frame)

- tested on zm v1.25.0, Kubuntu 12.04LTS 
- user:pass not working within zm, but does from browser. 
- works fine with authentication turned off. 
- http://www.lavrsen.dk/foswiki/bin/view/Motion/TrendNet seems to indicate that authentication is not going to work. (At least in Motion, but if not in Motion I assume likely not in zm, either.) 

[[Category:Cameras]]
[[Category:Network Cameras]]

Bt878 4chip 8inputs

2014-10-03T18:01:28Z

Gkmac: Undo SPAM revision 6415 by Erictenne (talk)

== Noname with 4 bt878 chips and 8 inputs ==

* tip: also check [[Pico2000]] related card info;

When using all channels you'll get around 5 fps.
Warning it takes a long time to boot using this card you must proceed with security. Maybe settings are bad. But it is working OK.

== Configuration ==

''/etc/modprobe.conf''
<pre>
options bttv card=0,0,0,0 tuner=4,4,4,4
</pre>

If your driver is compiled into the kernel, add the following to be passed onto the kernel from LILO or GRUB.
<pre>
bttv.card=0,0,0,0 bttv.tuner=4,4,4,4
</pre>

* A list of card types and tuner types can be found in the Linux kernel sources under Documentation
<pre>
http://linuxtv.org/hg/v4l-dvb/file/tip/linux/Documentation/video4linux
</pre>

== Photos ==

[[Image:Bt878_4chip_8inputs_1.jpg|200px]]
[[Image:Bt878_4chip_8inputs_2.jpg|200px]]

FAQ

2014-10-03T18:01:07Z

Gkmac: Undo SPAM revision 6414 by Erictenne (talk)

== ZoneMinder Frequently Asked Questions ==

This is the FAQ page. Feel free to contribute any FAQs that you think are missing.

===How can I stop ZoneMinder filling up my disk?===

Recent versions of ZoneMinder come with a filter you can use for this purpose already included. However '''by default it is not enabled for event deletion'''.

The filter is called ''PurgeWhenFull'' and to find it, choose one of the event counts from the console page, for instance events in the last hour, for one of your monitors.

This will bring up an event listing and a filter window.

In the filter window there is a drop down select box labeled 'Use Filter', that lets your select a saved filter. Select 'PurgeWhenFull' and it will load that filter.

Make any modifications you might want, such as the percentage full you want it to kick in, or how many events to delete at a time (it will repeat the filter as many times as needed to clear the space, but will only delete this many events each time to get there).

Then click on 'Save' which will bring up a new window. Make sure the 'Automatically delete' box is checked and press save to save your filter. This will then run in the background to keep your disk within those limits.

After you've done that, you changes will automatically be loaded into zmfilter within a few minutes.

Check the <tt>zmfilter.log</tt> file to make sure it is running as sometimes missing perl modules mean that it never runs but people don't always realize.

PURGE BY AGE

To delete events that are older than 7 days, create a new filter with "Date" set to "less than" and a value of "-7 days", sort by "date/time" in "asc"ending order, then enable the checkbox "delete all matches".

Save with 'Run Filter In Background' enabled to have it run automatically.

Optional skip archived events: click on the plus sign next to -7 days to add another condition. "and" "archive status" equal to "unarchived only".

Optional slow delete: limit the number of results to 3. If you have a large backlog of events that would be deleted, this can hard spike the CPU usage for a long time. Limiting the number of results to only the first three each time the filter is run spreads out the delete processes over time, dramatically lessening the CPU load.

There are two methods for ZM to remove files when they are deleted that can be found in Options under the System tab ZM_OPT_FAST_DELETE and ZM_RUN_AUDIT.

ZM_OPT_FAST_DELETE:

Normally an event created as the result of an alarm consists of entries in one or more database tables plus the various files associated with it. When deleting events in the browser it can take a long time to remove all of this if your are trying to do a lot of events at once. It is recommended that you set this option which means that the browser client only deletes the key entries in the events table, which means the events will no longer appear in the listing, and leaves the zmaudit daemon to clear up the rest later.

ZM_RUN_AUDIT:

The zmaudit daemon exists to check that the saved information in the database and on the file system match and are consistent with each other. If an error occurs or if you are using 'fast deletes' it may be that database records are deleted but files remain. In this case, and similar, zmaudit will remove redundant information to synchronize the two data stores. This option controls whether zmaudit is run in the background and performs these checks and fixes continuously. This is recommended for most systems however if you have a very large number of events the process of scanning the database and file system may take a long time and impact performance. In this case you may prefer to not have zmaudit running unconditionally and schedule occasional checks at other, more convenient, times.

ZM_AUDIT_CHECK_INTERVAL:

The zmaudit daemon exists to check that the saved information in the database and on the files system match and are consistent with each other. If an error occurs or if you are using 'fast deletes' it may be that database records are deleted but files remain. In this case, and similar, zmaudit will remove redundant information to synchronize the two data stores. The default check interval of 900 seconds (15 minutes) is fine for most systems however if you have a very large number of events the process of scanning the database and file system may take a long time and impact performance. In this case you may prefer to make this interval much larger to reduce the impact on your system. This option determines how often these checks are performed.

===What does a 'Can't shmget: Invalid argument' error in my logs mean? and my cameras won't display video at higher resolutions.===

This error is discussed in the README in the following excerpt:-
''...this is caused by an attempt to allocate an amount of shared memory greater than your system can handle. The size it requests is based on the following formula, <tt>ring buffer size x image width x image height x 3 (for 24 bit images) + a bit of overhead</tt>.

So, for example:
<pre>384x288 capture resolution, that makes: 110 592 pixels
in 24 bit color that's x24 = 2 654 208 bits per frame
by 80 frames ring buffer x80 = 212 336 640 bits per camera
by 4 cameras x4 = 849 346 560 bits.
Plus 10% overhead = 934 281 216 bits
That's 116 785 152 bytes, and
= 114 048 kB, respectively 111.38 MB.
If my shared memory is set to 134 217 728, which is exactly 128MB,
that means I shouldn't have any problem.
(Note that 1 byte = 8 bits and 1kbyte = 1024bytes, 1MB = 1024 kB)</pre>

If for instance you were using 24bit 640x480 then this would come to about 92Mb if you are using the default buffer size of 100. If this is too large then you can either reduce the image or buffer sizes or increase the maximum amount of shared memory available. If you are using RedHat then you can get details on how to change these settings at http://www.redhat.com/docs/manuals/database/RHDB-2.1-Manual/admin_user/kernel-resources.html .

You should be able to use a similar procedure with other distributions to modify the shared memory pool without kernel recompilations though in some cases this may be necessary. Note, this error also sometimes occurs if you have an old shared memory segment lying around from a previous run that is too small. Use the ipcs and ipcrm system commands to check and remove it if necessary.'"

You can often find out how many 4KB shared memory pages are available by typing the following :-
<pre># cat /proc/sys/kernel/shmall
2097152</pre>

In recent kernels the shmall is set to 2097152 memory pages multiplied by 4096 bytes per page for a total of 8 GB of shared memory available. You only need to increase the shmall value if you have a computer with more than 8GB of memory and wish to use more of it for shared memory usage, such as large databases.

The most shared memory bytes you can allocate in one go :-
<pre># cat /proc/sys/kernel/shmmax
33554432</pre>

In recent kernels the shmmax is set to 33554432 bytes for only 32 MB of maximum shared memory allocatable at a time, hardly enough for ZoneMinder to go above 320 x 240 x 24-bit resolution at 40 frames in the buffer if it is using the /dev/shm shared memory device, so this value needs to be increased. If you are using ZoneMinder with the memory mapped (mmap) compile time option then this doesn't affect you.

To change the value to 128 MB temporarily during this kernel execution type (for example) :-
<pre>echo 536870912 >/proc/sys/kernel/shmmax</pre>

'''Be sure to restart ZoneMinder after this.'''
However be aware that sometimes you will only need to change the shmmax value as shmall is often large enough. Also changing these values in this way is only effective until your machine is rebooted.

To change them permanently you will need to edit <tt>/etc/sysctl.conf</tt> and add the following lines (for example) :-
<pre>kernel.shmmax = 536870912</pre>

Or if your distribution has the <tt>/etc/sysctl.d/</tt> folder you can create a file in this folder without modifying the <tt>/etc/sysctl.d</tt> so you won't lose the changes during distro upgrades :-
<pre>echo kernel.shmmax = 536870912 >/etc/sysctl.d/60-kernel-shm.conf</pre>

To load these settings in the sysctl.conf file type:
<pre>sysctl -p</pre>

To check your shared memory settings type:
<pre>ipcs -l</pre>

Note that with Megapixel cameras like the Axis 207mw becoming cheaper and more attractive, the above memory settings are not adequate. To get Zoneminder working with a full 1280x1024 resolution camera in full color, increase <tt>134217728</tt> (128 MB) to, for example, <tt>268435456</tt> (256 MB) and multiple this value by each camera.

These changes will now also be set the next time your machine is restarted.

Versions 1.24.x of ZoneMinder also allows you to use an alternate method of shared memory allocation, [http://en.wikipedia.org/wiki/Mmap mapped memory]. This requires less configuration and can be simpler to use. Mapped memory allows you to use a special type of file as the placeholder for your memory and this file is 'mapped' into memory space for easy and fast access.

To enable mapped memory in ZoneMinder you need add add the --enable--mmap=yes switch to your configure line. By default mapped memory files are created in /dev/shm which on most distributions is a dedicated pseudo-partition containing memory formatted as a filesystem. If your system uses a different path then this can be changed in ZoneMinder in Options->paths->PATH_MAP. It uses a filesystem type called [http://en.wikipedia.org/wiki/Tmpfs tmpfs]. If you type 'df' you should see this area and the size of memory it currently allows. It is important that you do not use a disk based filesystem for your memory mapped files as this will cause memory access to be extremely slow. ZoneMinder creates files called .zm.mmap.<monitor id> in the mapped memory filesystem.

Mapped memory is subject to the same limitations in terms of total memory as using more traditional shared memory but does not require any configuration per allocation or chunk. In future versions of ZoneMinder this will be the default shared memory storage method.

<div id="AlternateSharedMemory" style="width:80%; border:2px solid #8a8588; background:#faf5ff; vertical-align:top; margin-top: 6px; padding: 4px;">
Another good article about shared memory settings http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.uprun.doc/doc/t0008238.htm .
It made a statement that conflicted with those in the Redhat article but they fixed a [http://www.zoneminder.com/forums/viewtopic.php?t=9692 long standing memory issue on FC6], so give them a try.

'''The essential difference was that the kernel.shmall setting is NOT in a direct memory setting in KB but in pages of memory. it is Max Pages of memory'''

'''For example:''' If you want to allocate a maximum memory setting to 8GB you have to convert it to the number of pages (or segments).
with a page size of 4096.
*kernel.shmall = 8000x1024x1024/4096
<pre>kernel.shmall = 2097152</pre>
NOT 8388608000 as would be suggested in the RedHat article linked above.

shmmax is the max amount to allocate in one request -
this is is an actual memory size (as opposed to pages) set to 4GB
<pre>kernel.shmmax = 4294967296</pre>

The <tt>/etc/sysctl.conf</tt> would have these lines
<pre>kernel.shmall = 2097152
kernel.shmmax = 4294967296</pre>

As above, reload your sysctl.conf with <tt>sysctl -p</tt> and check that the settings are correct with <tt>ipcs -l</tt>.
</div>

===I have enabled motion detection but it is not always being triggered when things happen in the camera view===

ZoneMinder uses zones to examine images for motion detection. When you create the initial zones you can choose from a number of preset values for sensitivity etc. Whilst these are usually a good starting point they are not always suitable for all situations and you will probably need to tweak the values for your specific circumstances. The meanings of the various settings are described in the documentation (http://www.zoneminder.com/wiki/index.php/Documentation#Defining_Zones) however if you believe you have sensible settings configured then there are two diagnostic approaches you can use.

====Event Statistics====
The first technique is to use event statistics. Firstly you should ensure they are switched on in Options->Logging->RECORD_EVENT_STATS. This will then cause the raw motion detection statistics for any subsequently generated events to be written to the DB. These can then be accessed by first clicking on the Frames or Alarm Frames values of the event from any event list view in the web gui. Then click on the score value to see the actual values that caused the event. Alternatively the stats can be accessed by clicking on the 'Stats' link when viewing any individual frame. The values displayed there correspond with the values that are used in the zone configuration and give you an idea of what 'real world' values are being generated.

Note that if you are investigating why events 'do not' happen then these will not be saved and so won't be accessible. The best thing to do in that circumstance is to make your zone more sensitive so that it captures all events (perhap even ones you don't want) so you can get an idea of what values are being generated and then start to adjust back to less sensitive settings if necessary. You should make sure you test your settings under a variety of lighting conditions (e.g. day and night, sunny or dull) to get the best feel for that works and what doesn't.

Using statistics will slow your system down to a small degree and use a little extra disk space in the DB so once you are happy you can switch them off again. However it is perfectly feasible to keep them permanently on if your system is able to cope which will allow you to review your setting periodically.

====Diagnostic Images====
The second approach is to use diagnostic images which are saved copies of the intermediate images that ZM uses when determining motion detection. These are switched on and off using Options->Logging->RECORD_DIAG_IMAGES.

There are two kinds of diagnostic images which are and are written (and continuously overwritten) to the top level monitor event directory. If an event occurs then the files are additionally copied to the event directory and renamed with the appropriate frame number as a prefix.

The first set are produced by the monitor on the image as a whole. The diag-r.jpg image is the current reference image against which all individual frames are compared and the diag-d.jpg image is the delta image highlighting the difference between the reference image and the last analysed image. In this images identicial pixels will be black and the more different a pixel is the whiter it will be. Viewing this image and determining the colour of the pixels is a good way of getting a feel for the pixel differences you might expect (often more than you think).

The second set of diag images are labelled as diag-<zoneid>-<stage>.jpg where zoneid is the id of the zone in question (Smile) and the stage is where in the alarm check process the image is generated from. So if you have several zones you can expect to see multiple files. Also these files are only interested in what is happening in their zone only and will ignore anything else outside of the zone. The stages that each number represents are as follows,

# Alarmed Pixels - This image shows all pixels in the zone that are considered to be alarmed as white pixels and all other pixels as black.
# Filtered Pixels - This is as stage one except that all pixels removed by the filters are now black. The white pixels represent the pixels that are candidates to generate an event.
# Raw Blobs - This image contains all alarmed pixels from stage 2 but aggrageted into blobs. Each blob will have a different greyscale value (between 1 and 254) so they can be difficult to spot with the naked eye but using a colour picker or photoshop will make it easier to see what blob is what.
# Filtered Blobs - This image is as stage 3 but under (or over) sized blobs have been removed. This is the final step before determining if an event has occurred, just prior to the number of blobs being counted. Thus this image forms the basis for determining whether an event is generated and outlining on alarmed images is done from the blobs in this image.

Using the above images you should be able to tell at all stages what ZM is doing to determine if an event should happen or not. They are useful diagnostic tools but as is mentioned elsewhere they will massively slow your system down and take up a great deal more space. You should never leave ZM running for any length of time with diagnostic images on.

===Why can't ZoneMinder capture images (either at all or just particularly fast) when I can see my camera just fine in xawtv or similar?===

With capture cards ZoneMinder will pull images as fast as it possibly can unless limited by configuration. ZoneMinder (and any similar application) uses the frame grabber interface to copy frames from video memory into user memory. This takes some time, plus if you have several inputs sharing one capture chip it has to switch between inputs between captures which further slows things down.

On average a card that can capture at 25fps per chip PAL for one input will do maybe 6-10fps for two, 1-4fps for three and 1-2 for four. For a 30fps NTSC chip the figures will be correspondingly higher. However sometimes it is necessary to slow down capture even further as after an input switch it may take a short while for the new image to settle before it can be captured without corruption.

When using xawtv etc to view the stream you are not looking at an image captured using the frame grabber but the card's video memory mapped onto your screen. This requires no capture or processing unless you do an explicit capture via the J or ctrl-J keys for instance. Some cards or drivers do not support the frame grabber interface at all so may not work with ZoneMinder even though you can view the stream in xawtv. If you can grab a still using the grab functionality of xawtv then in general your card will work with ZoneMinder.

===Why can't I see streamed images when I can see stills in the Zone window etc?===

This issue is normally down to one of two causes

1) You are using Internet Explorer and are trying to view multi-part jpeg streams. IE does not support these streams directly, unlike most other browsers. You will need to install Cambozola or another multi-part jpeg aware pluging to view them. To do this you will need to obtain the applet from the Downloads page and install the cambozola.jar file in the same directly as the ZoneMinder php files. Then find the ZoneMinder Options->Images page and enable ZM_OPT_CAMBOZOLA and enter the web path to the .jar file in ZM_PATH_CAMBOZOLA. This will ordinarily just be cambozola.jar. Provided (Options / B/W tabs) WEB_H_CAN_STREAM is set to auto and WEB_H_STREAM_METHOD is set to jpeg then Cambozola should be loaded next time you try and view a stream.

'''NOTE''': If you find that the Cambozola applet loads in IE but the applet just displays the version # of Cambozola and the author's name (as opposed to seeing the streaming images), you may need to chmod (''-rwxrwxr-x'') your (''usr/share/zoneminder/'') cambozola.jar:

$ sudo chmod 775 cambozola.jar

Once I did this, images started to stream for me.

2) The other common cause for being unable to view streams is that you have installed the ZoneMinder cgi binaries (zms and nph-zms) in a different directory than your web server is expecting. Make sure that the --with-cgidir option you use to the ZoneMinder configure script is the same as the CGI directory configure for your web server. If you are using Apache, which is the most common one, then in your httpd.conf file there should be a line like <pre>ScriptAlias /cgi-bin/ "/var/www/cgi-bin/"</pre> where the last directory in the quotes is the one you have specified. If not then change one or the other to match. Be warned that configuring apache can be complex so changing the one passed to the ZoneMinder configure (and then rebuilding and reinstalling) is recommended in the first instance. If you change the apache config you will need to restart apache for the changes to take effect. If you still cannot see stream reliably then try changing Options->Paths->ZM_PATH_ZMS to just use zms if nph-zms is specified, or vice versa. Also check in your apache error logs.

===I have several monitors configured but when I load the Montage view in FireFox why can I only see two? or, Why don't all my cameras display when I use the Montage view in FireFox?===

By default FireFox only supports a small number of simultaneous connections. Using the montage view usually requires one persistent connection for each camera plus intermittent connections for other information such as statuses.

You will need to increase the number of allowed connections to use the montage view with more than a small number of cameras. Certain FireFox extensions such as FasterFox may also help to achieve the same result.

To resolve this situation, follow the instructions below:

<pre>Enter about:config in the address bar

scroll down to
browser.cache.check_doc_frequency 3
change the 3 to a 1

browser.cache.disk.enable True -> False
network.http.max-connections-per-server -> put a value of 100
network.http.max-persistent-connections-per-proxy -> 100 again
network.http.max-persistent-connections-per-server -> 100 again
</pre>

===Why is ZoneMinder using so much CPU?===

The various elements of ZoneMinder can be involved in some pretty intensive activity, especially while analysing images for motion. However generally this should not overwhelm your machine unless it is very old or underpowered.

There are a number of specific reasons why processor loads can be high either by design or by accident. To figure out exactly what is causing it in your circumstances requires a bit of experimentation.

The main causes are.

# Using a video palette other than greyscale or RGB24. This can cause a relatively minor performace hit, though still significant. Although some cameras and cards require using planar palettes ZM currently doesn't support this format internally and each frame is converted to an RGB representation prior to processing. Unless you have compelling reasons for using YUV or reduced RGB type palettes such as hitting USB transfer limits I would experiment to see if RGB24 or greyscale is quicker. Put your monitors into 'Monitor' mode so that only the capture daemons are running and monitor the process load of these (the 'zmc' processes) using top. Try it with various palettes to see if it makes a difference.
# Big image sizes. A image of 640x480 requires at least four times the processing of a 320x240 image. Experiment with different sizes to see what effect it may have. Sometimes a large image is just two interlaced smaller frames so has no real benefit anyway. This is especially true for analog cameras/cards as image height over 320 (NTSC) or 352 PAL) are invariably interlaced.
# Capture frame rates. Unless there's a compelling reason in your case there is often little benefit in running cameras at 25fps when 5-10fps would often get you results just as good. Try changing your monitor settings to limit your cameras to lower frame rates. You can still configure ZM to ignore these limits and capture as fast as possible when motion is detected.
# Run function. Obviously running in Record or Mocord modes or in Modect with lots of events generates a lot of DB and file activity and so CPU and load will increase.
# Basic default detection zones. By default when a camera is added one detection zone is added which covers the whole image with a default set of parameters. If your camera covers a view in which various regions are unlikely to generate a valid alarm (ie the sky) then I would experiment with reducing the zone sizes or adding inactive zones to blank out areas you don't want to monitor. Additionally the actual settings of the zone themselves may not be optimal. When doing motion detection the number of changed pixels above a threshold is examined, then this is filter, then contiguous regions are calculated to see if an alarm is generated. If any maximum or minimum threshold is exceeded according to your zone settings at any time the calculation stops. If your settings always result in the calculations going through to the last stage before being failed then additional CPU time is used unnecessarily. Make sure your maximum and minimumzone thresholds are set to sensible values and experiment by switching RECORD_EVENT_STATS on and seeing what the actual values of alarmed pixels etc are during sample events.
# Optimise your settings. After you've got some settings you're happy with then switching off RECORD_EVENT_STATS will prevent the statistics being written to the database which saves some time. Other settings which might make a difference are ZM_FAST_RGB_DIFFS, ZM_OPT_FRAME_SERVER and the JPEG_xxx_QUALITY ones.

I'm sure there are other things which might make a difference such as what else you have running on the box and memory sizes (make sure there's no swapping going on). Also speed of disk etc will make some difference during event capture and also if you are watching the whole time then you may have a bunch of zms processes running also.

I think the biggest factors are image size, colour depth and capture rate. Having said that I also don't always know why you get certains results from 'top'. For instance if I have a 'zma' daemon running for a monitor that is capturing an image. I've commented out the actual analysis so all it's doing is blending the image with the previous one. In colour mode this takes ~11 milliseconds per frame on my system and the camera is capturing at ~10fps. Using 'top' this reports the process as using ~5% of CPU and permanently in R(un) state. Changing to greyscale mode the blending takes ~4msec (as you would expect as this is roughly a third of 11) but top reports the process as now with 0% CPU and permanently in S(leep) state. So an actual CPU resource usage change of a factor of 3 causes huge differences in reported CPU usage. I have yet to get to the bottom of this but I suspect it's to do with scheduling somewhere along the line and that maybe the greyscale processing will fit into one scheduling time slice whereas the colour one won't but I have no evidence of this yet!

===Why is the timeline view all messed up?===

The timeline view is a new view allowing you to see a graph of alarm activity over time and to quickly scan and home in on events of interest. However this feature is highly complex and still in beta. It is based extensively on HTML div tags, sometimes lots of them. Whilst FireFox is able to render this view successfully other browsers, particular Internet Explorer do not seem able to cope and so present a messed up view, either always or when there are a lot of events.
Using the timeline view is only recommended when using FireFox, however even then there may be issues.

This function has from time to time been corrupted in the SVN release or in the stable releases, try and reinstall from a fresh download.

===How much Hard Disk Space / Bandwidth do I need for ZM?===
Please see [http://www.jpwilson.eu/ZM_Utils/ZM%20storage%20calc%20sheet.xls Storage Calc] in excel format

Or go to [http://www.axis.com/products/video/design_tool/index.htm this link] for the Axis bandwidth calculator. Although this is aimed at Axis cameras it still produces valid results for any kind of IP camera.

As a quick guide I have 4 cameras at 320x240 storing 1 fps except during alarm events. After 1 week 60GB of space in the volume where the events are stored (/var/www/html/zm) has been used.

===When I try and run ZoneMinder I get lots of audit permission errors in the logs and it won't start===
Many Linux distributions nowadays are built with security in mind. One of the latest methods of achieving this is via SELinux (Secure Linux) which controls who is able to run what in a more precise way then traditional accounting and file based permissions ([http://en.wikipedia.org/wiki/Selinux]).
If you are seeing entries in your system log like:

Jun 11 20:44:02 kernel: audit(1150033442.443:226): avc: denied { read } for pid=5068
comm="uptime" name="utmp" dev=dm-0 ino=16908345 scontext=user_u:system_r:httpd_sys_script_t
tcontext=user_u:object_r:initrc_var_run_t tclass=file

then it is likely that your system has SELinux enabled and it is preventing ZoneMinder from performaing certain activities. You then have two choices. You can either tune SELinux to permit the required operations or you can disable SELinux entirely which will permit ZoneMinder to run unhindered. Disabling SELinux is usually performed by editing its configuration file (e.g., <tt>/etc/selinux/config</tt>) and then rebooting. However if you run a public server you should read up on the risks associated with disabled Secure Linux before disabling it.

Note that SELinux may cause errors other than those listed above. If you are in any doubt then it can be worth disabling SELinux experimentally to see if it fixes your problem before trying other solutions.

=== How do I enable ZoneMinder's security? ===
In the console, click on Options. Check the box next to "ZM_OPT_USE_AUTH". You will immediately be asked to login. The username is 'admin' and the password is 'admin'.

'''To Manage Users:''' 
In main console, go to '''Options->Users'''.

* You may also consider to use the web server security, for example, htaccess files under Apache scope; You may even use this as an additional/redundant security on top of Zoneminders built-in security features;

=== Why does ZM stop recording once I have 32000 events for my monitor? ===
This is a limitation of the ext3 filesystem that most Linux distributions use. One directory cannot hold more than 32k approx files.

Version of ZM from 1.23.0 onwards allow you to have a deeper filesystem with fewer files per individual directory. As well as not being susceptible to the 32k limit this is also somewhat faster. However it is relatively and although few issues have been reported thus far it should be considered in beta for now. Also, it is currently not possible to migrate saved events between the different storage formats so is only suitable for new installations or if you do not mind losing saved events.

So if you do not want to use the deeper filesystem option
(Options->Paths->ZM_USE_DEEP_STORAGE), for now you have to reduce the
number of events or store your images (e.g. /var/lib/zoneminder) on a
partition that uses a different filesystem such as ext4 or reiserfs.

You can read about the lack of a limit in the number of
sub-directories in the ext4 filesystem at:
http://kernelnewbies.org/Ext4
and see what tools may assist in your use of this filesystem in:
http://ext4.wiki.kernel.org/index.php/Ext4_Howto
Note that while GParted 0.5.2 recognizes ext4 partitions, at least in
some circumstances it does not succeed in formatting a partition for
the ext4 filesystem. Also, if you search for ext3 or reiserfs on the
forums you will find various threads on this issue with guidance on
how to convert.

== Managing system load ''(with IP Cameras in mind)'' ==

=== Introduction ===
Zoneminder is a superb application in every way, but it does a job that needs a lot of horsepower especially when using multiple IP cameras. IP Cams require an extra level of processing to analogue cards as the jpg or mjpeg images need to be decoded before analysing. This needs grunt. If you have lots of cameras, you need lots of grunt.

Why do ZM need so much grunt?
Think what Zoneminder is actually doing. In modect mode ZM is:
1. Fetching a jpeg from the camera. (Either in single part or multipart stream)
2. Decoding the jpeg image.
3. Comparing the zoned selections to the previous image or images and applying rules.
4. If in alarm state, writing that image to the disk and updating the mysql database.

If you're capturing at five frames per second, the above is repeated five times every second, multiplied by the number of cameras. Decoding the images is what takes the real power from the processor and this is the main reason why analogue cameras which present an image ready-decoded in memory take less work.

=== How do I know if my computer is overloaded? ===
If your CPU is running at 100% all the time, it's probably overloaded (or running at exact optimisation). If the load is consistently high (over 10.0 for a single processor) then Bad Things happen - like lost frames, unrecorded events etc. Occasional peaks are fine, normal and nothing to worry about.

Zoneminder runs on Linux, Linux measures system load using "load", which is complicated but gives a rough guide on what the computer is doing at any given time. Zoneminder shows Load on the main page (top right) as well as disk space. Typing "uptime" on the command line will give a similar guide, but with three figures to give a fuller measure of what's happening over a period of time but for the best guide to see what's happening, install "htop" - which gives easy to read graphs for load, memory and cpu usage.

A load of 1.0 means the processor has "just enough to do right now". Also worth noting that a load of 4.0 means exactly the same for a quad processor machine - each number equals a single processor's workload. A very high load can be fine on a computer that has a stacked workload - such as a machine sending out bulk emails, or working its way through a knotty problem; it'll just keep churning away until it's done. However - Zoneminder needs to process information in real time so it can't afford to stack its jobs, it needs to deal with them right away.

For a better and full explanation of Load: http://en.wikipedia.org/wiki/Load_%28computing%29

=== My load is too high, how can I reduce it? ===
Zoneminder is /very/ tweakable and it's possible to tune it to compromise. The following are good things to try, in no particular order;

Change the jpeg libraries. In most distributions Linux uses standard jpeg libraries which although fine for most things, don't use the MMX functions in nearly all modern processors. Check whether your cpu supports mmx by running "cpuid |grep MMX" which should give you a line or two along the lines of "MMX instructions". If so, give the libs a try. Most people report their load halves simply by using these libs. You may be able to experience substantial Zoneminder performance boosts now by merely upgrading your operating system, without having to download libraries and compile your own binaries, etc. as described in the forum thread linked below. Some distributions, e.g. Fedora 14 now include library code to utilize the instruction set extensions available in your processor:

http://fedoraproject.org/wiki/Fedora_14_Alpha_release_notes#Faster_JPEG_Compression.2FDecompression

"The replacement of libjpeg with libjpeg-turbo brings speed improvements to a wide range of applications when handling images in JPEG format ..."

http://fedoraproject.org/wiki/Releases/14/Schedule

still states "2010-11-02 final release".

CentOS 6.4 now has libjpeg-turbo built in as the default jpeg library allowing the best results out of the box.

http://libjpeg-turbo.virtualgl.org/

provides some history on its project page. If you seek confirmation for which library is in use, you may consider querying e.g. while running on a prior distribution:
<pre>
[u@who ~]$ rpm -q --whatprovides libjpeg
libjpeg-6b-46.fc12.i686
[u@who ~]$
</pre>
and comparing the response to querying when the higher-performance library is available:
<pre>
[u@who ~]$ rpm -q --whatprovides libjpeg
libjpeg-turbo-1.0.1-1.fc14.x86_64
[u@who ~]$
</pre>
As noted in other forum postings, some zoneminder camera and usage configurations may not make much use of jpeg processing (e.g. some webcams), and thus obtain little performance benefit. Otherwise, you should be able to select one or more of:
* running more cameras,
* running existing cameras at higher image resolutions,
* running cameras at a faster frame rate,
* saving MoDect images with higher quality,
* having more CPU cycles available for any non-Zoneminder workload, etc.

http://www.zoneminder.com/forums/viewtopic.php?t=6419 gives more info on the download-the-library-yourself, compile-your-own-Zoneminder binary, etc. approach if needed. Nobody's posted there to say it broke their system... Yet.

If your camera allows you to change image size, think whether you can get away with smaller images. Smaller pics = less load. 320x240 is usually ok for close-up corridor shots.

Go Black and White. Colour pictures use twice to three times the CPU, memory and diskspace but give little benefit to identification.

Reduce frames per second. Halve the fps, halve the workload. If your camera supports fps throttling (Axis do), try that - saves ZM having to drop frames from a stream. 2-5 fps seems to be widely used.

Experiment with using jpeg instead of mjpeg. Some users have reported it gives better performance, but YMMV.

Tweak the zones. Keep them as small and as few as possible. Stick to one zone unless you really need more.

Schedule. If you are running a linux system at near capacity, you'll need to think carefully about things like backups and scheduled tasks. updatedb - the process which maintains a file database so that 'locate' works quickly, is normally scheduled to run once a day and if on a busy system can create a heavy increase on the load. The same is true for scheduled backups, especially those which compress the files. Re-schedule these tasks to a time when the cpu is less likely to be busy, if possible - and also use the "nice" command to reduce their priority. (crontab and /etc/cron.daily/ are good places to start)

Reduce clutter on your PC. Don't run X unless you really need it, the GUI is a huge overhead in both memory and cpu.

More expensive options:

Increase RAM. If your system is having to use disk swap it will HUGELY impact performance in all areas. Again, htop is a good monitor - but first you need to understand that because Linux is using all the memory, it doesn't mean it needs it all - linux handles ram very differently to Windows/DOS and caches stuff. htop will show cached ram as a different colour in the memory graph. Also check that you're actually using a high memory capable kernel - many kernels don't enable high memory by default.

Faster CPU. Simple but effective. Zoneminder also works very well with multiple processor systems out of the box (if SMP is enabled in your kernel). The load of different cameras is spread across the processors.

Try building Zoneminder with processor specific instructions that are optimised to the system it will be running on, also increasing the optimisation level of GCC beyond -O2 will help.
<pre>
./configure CFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp" CXXFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp"
</pre>
The above command is optimised for an Athlon XP cpu so you will need to use the specific processor tag for your cpu, also the compiler optimisation has been increased to -O3.

You also need to put in your normal ./configure commands as if you were compiling with out this optimisation.

A further note is that the compile must be performed on the system that Zoneminder will be running on as this optimisation will make it hardware specific code.

Processor specific commands can be found in the GCC manual along with some more options that may increase performanc.
<pre>
http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options
</pre>

The below command has been used to compile Zoneminder on a Athlon XP system running CentOS 5.5 and along with the libjpeg-turbo modification to reduce the CPU load in half, libjpeg-turbo reduced the load by 1/3 before the processor optimisation.
<pre>
./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin CFLAGS="-g -O3 -march=athlon-xp -mtune=athlon-xp" CXXFLAGS="-D__STDC_CONSTANT_MACROS -g -O3 -march=athlon-xp -mtune=athlon-xp" --enable-mmap --sysconfdir=/etc/zm
</pre>

The following command has been used to compile Zoneminder 1.25 on a CentOS 6.0 system, the native command should choose the processor automatically during compile time, this needs to be performed on the actual system!!.

<pre>
CFLAGS="-g -O3 -march=native -mtune=native" CXXFLAGS="-D__STDC_CONSTANT_MACROS -g -O3 -march=native -mtune=native" ./configure --with-webdir=/var/www/html/zm --with-cgidir=/var/www/cgi-bin --with-webuser=apache --with-webgroup=apache ZM_DB_HOST=localhost ZM_DB_NAME=zm ZM_DB_USER=your_zm_user ZM_DB_PASS=your_zm_password ZM_SSL_LIB=openssl
</pre>

=== What about disks and bandwidth? ===

In most modern pc-based servers, disk I/O is more than adequate for the speeds involved in capturing from multiple cameras in most scenarios.

A typical 100mbit LAN will cope with most setups easily. If you're feeding from cameras over smaller or internet links, obviously fps will be much lower.

Disk and Bandwidth calculators are referenced on the Zoneminder wiki here: http://www.zoneminder.com/wiki/index.php/FAQ#How_much_Hard_Disk_Space_.2F_Bandwidth_do_I_need_for_ZM.3F

== Building ZoneMinder ==

=== When running configure I am getting a lot of messages about not being able to compile the ffmpeg libraries ===

If you see output from configure that looks like this

<pre>checking libavcodec/avcodec.h usability... no
checking libavcodec/avcodec.h presence... yes
configure: WARNING: libavcodec/avcodec.h: present but cannot be compiled
configure: WARNING: libavcodec/avcodec.h: check for missing
prerequisite headers?
configure: WARNING: libavcodec/avcodec.h: see the Autoconf documentation
configure: WARNING: libavcodec/avcodec.h: section "Present But
Cannot Be Compiled"
configure: WARNING: libavcodec/avcodec.h: proceeding with the compiler's
result
configure: WARNING: ## ------------------------------------- ##
configure: WARNING: ## Report this to support@zoneminder.com ##
configure: WARNING: ## ------------------------------------- ##</pre>

then it is caused not by the ZoneMinder build system but ffmpeg itself. However there is a workaround you can use which is to add

CPPFLAGS=-D__STDC_CONSTANT_MACROS

to the ZoneMinder ./configure command which should solve the issue. However this is not a proper 'fix' as such, which can only come from the ffmpeg project itself.

=== I cannot build ZoneMinder and am getting lots of undefined C++ template errors===

This is almost certainly due to the 'ccache' package which attempts to speed up compilation by caching compiled objects. Unfortunately one of the side effects is that it breaks the GNU g++ template resolution method that ZoneMinder uses in building by prevent files getting recompiled. The simplest way around this is to remove the ccache package using your distros package manager.

=== How do I build for X10 support? ===

You do not need to rebuild ZM for X10 support. You will need to install the perl module and switch on X10 in the options, then restart. Installing the perl module is covered in the README amongst other places but in summary, do:

perl -MCPAN -eshell
install X10::ActiveHome
quit

== Extending ZoneMinder ==

=== How can I get ZM to do different things at different times of day or week? ===
If you want to configure ZoneMinder to do motion detection during the day and just record at night, for example, you will need to use ZoneMinder 'run states'. A run state is a particular configuration of monitor functions that you want to use at any time.

To save a run state you should first configure your monitors for Modect, Record, Monitor etc as you would want them during one of the times of day. Then click on the running state link at the top of the Console view. This will usually say 'Running' or 'Stopped'. You will then be able to save the current state and give it a name, 'Daytime' for example. Now configure your monitors how you would want them during other times of day and save that, for instance as 'Nighttime'.

Now you can switch between these two states by selecting them from the same dialog you saved them, or from the command line from issue the command ''zmpkg.pl <run state>'', for example ''zmpkg.pl Daytime''.

The final step you need to take, is scheduling the time the changes take effect. For this you can use [http://en.wikipedia.org/wiki/Cron cron]. A simple entry to change to the Daylight state at at 8am and to the nighttime state at 8pm would be as follows,
<pre>0 8 * * * root /usr/local/bin/zmpkg.pl Daytime
0 20 * * * root /usr/local/bin/zmpkg.pl Nighttime</pre>

On Ubuntu 7.04 and possibly others, look in /usr/bin not just /usr/local/bin for the zmpkg.pl file.

Although the example above describes changing states at different times of day, the same principle can equally be applied to days of the week or other more arbitrary periods.

For an alternative method of time controlling ZoneMinder, forum user 'voronwe' has created a more interactive calendar style integration. Details of this can be found in this [http://www.zoneminder.com/forums/viewtopic.php?t=6519 forum thread]. If you would like to find out more about this contribution please post on this thread.

=== How can I use ZoneMinder to trigger something else when there is an alarm? ===
ZoneMinder includes a perl API which means you can create a script to interact with the ZM shared memory data and use it in your own scripts to react to ZM alarms or to trigger ZM to generate new alarms. Full details are in the README or by doing 'perldoc ZoneMinder', 'perldoc ZoneMinder::SharedMem' etc.
Below is an example script that checks all monitors for alarms and when one occurs, prints a message to the screen. You can add in your own code to make this reaction a little more useful.

<pre>#!/usr/bin/perl -w

use strict;

use ZoneMinder;

$| = 1;

zmDbgInit( "myscript", level=>0, to_log=>0, to_syslog=>0, to_term=>1 );

my $dbh = DBI->connect( "DBI:mysql:database=".ZM_DB_NAME.";host=".ZM_DB_HOST, ZM_DB_USER, ZM_DB_PASS );

my $sql = "select M.*, max(E.Id) as LastEventId from Monitors as M left join Events as E on M.Id = E.MonitorId where M.Function != 'None' group by (M.Id)";
my $sth = $dbh->prepare_cached( $sql ) or die( "Can't prepare '$sql': ".$dbh->errstr() );

my $res = $sth->execute() or die( "Can't execute '$sql': ".$sth->errstr() );
my @monitors;
while ( my $monitor = $sth->fetchrow_hashref() )
{
push( @monitors, $monitor );
}

while( 1 )
{
foreach my $monitor ( @monitors )
{
next if ( !zmMemVerify( $monitor ) );

if ( my $last_event_id = zmHasAlarmed( $monitor, $monitor->{LastEventId} ) )
{
$monitor->{LastEventId} = $last_event_id;
print( "Monitor ".$monitor->{Name}." has alarmed\n" );
#
# Do your stuff here
#
}
}
sleep( 1 );
}</pre>

==Trouble Shooting==
Here are some things that will help you track down whats wrong.
This is also how to obtain the info that we need to help you on the forums.

===What logs should I check for errors?===
ZoneMinder creates its own logs and are usually located in the <tt>/tmp</tt> directory.

The ZoneMinder logs for the RPM packages are located in <tt>/var/log/zm</tt>.

Depending on your problem errors can show up in any of these logs but, usually the logs of interest are <tt>zmdc.log</tt> and <tt>zmpkg.log</tt> if ZM is not able to start.

Now since ZM is dependent on other components to work, you might not find errors in ZM but in the other components.
Other logs of interest are:<tt>
*/var/log/messages and/or /var/log/syslog
*/var/log/dmesg
*/var/log/httpd/error_log</tt> (RedHat/Fedora) or <tt>/var/log/apache2/error_log
*/var/log/mysqld.log</tt> (Errors here don't happen very often but just in case)

If ZM is not functioning, you should always be able to find an error in at least one of these logs. Use the [[tail]] command to get info from the logs. This can be done like so:

tail -f /var/log/messages /var/log/httpd/error_log /var/log/zm/zm*.log

This will append any data entered to any of these logs to your console screen (<tt>-f</tt>). To exit, hit [ctrl -c].

More verbose logging for the ZoneMinder binaries is available by enabling the debug option from the control panel and will be placed in the path you have configured for the debug logs. Output can be limited to a specific binary as described in the Debug options page under the "?" marks.

===How can I trouble shoot the hardware and/or software?===
Here are some commands to get information about your hardware. Some commands are distribution dependent.
* <tt>[[lspci]] -vv</tt> -- Returns lots of detailed info. Check for conflicting interrupts or port assignments. You can sometimes alter interrupts/ ports in bios. Try a different pci slot to get a clue if it is HW conflict (comand provided by the pciutils package).
* <tt>[[scanpci]] -v</tt> -- Gives you information from your hardware EPROM
* <tt>[[lsusb]] -vv</tt> -- Returns lots of detail about USB devices (camand provided by usbutils package).
* <tt>[[dmesg]]</tt> -- Shows you how your hardware initialized (or didn't) on boot-up. You will get the most use of this.
* <tt>[[v4l-info]]</tt> -- to see how driver is talking to card. look for unusual values.
* <tt>[[modinfo bttv]]</tt> -- some bttv driver stats.
* <tt>[[zmu]] -m 0 -q -v</tt> -- Returns various information regarding a monitor configuration.
* <tt>[[ipcs]] </tt> -- Provides information on the ipc facilities for which the calling process has read acccess.
* <tt>[[ipcrm]] </tt> -- The ipcrm command can be used to remove an IPC object from the kernel.
* <tt>cat /proc/interrupts</tt> -- This will dispaly what interrupts your hardware is using.

===Why is it that when monitoring a camera, the top portion of the image is cutoff and appears at the bottom of the image, with a line seperating the top from the bottom?===

=== Why am I getting a 403 access error with my web browser when trying to access http //localhost/zm? ===

The apache web server needs to have the right permissions and configuration to be able to read the Zoneminder files. Check the forums for solution, and edit the apache configuration and change directory permissions to give apache the right to read the Zoneminder files. Depending on your Zoneminder configuration, you would use the zm user and group that Zoneminder was built with, such as wwwuser and www.

=== Why am I getting broken images when trying to view events? ===

Zoneminder and the Apache web server need to have the right permissions. Check this forum topic and similar ones:
http://www.zoneminder.com/forums/viewtopic.php?p=48754#48754

===Why is the image from my color camera appearing in black and white?===
If you recently upgraded to zoneminder 1.26, there is a per camera option that defaults to black and white and can be mis-set if your upgrade didn't happen right. See this thread: http://www.zoneminder.com/forums/viewtopic.php?f=30&t=21344

This may occur if you have a NTSC analog camera but have configured the source in ZoneMinder as PAL for the Device Format under the source tab. You may also be mislead because zmu can report the video port as being PAL when the camera is actually NTSC. Confirm the format of your analog camera by checking it's technical specifications, possibly found with the packaging it came in, on the manufacturers website, or even on the retail website where you purchased the camera. Change the Device Format setting to NTSC and set it to the lowest resolution of 320 x 240. If you have confirmed that the camera itself is NTSC format, but don't get a picture using the NTSC setting, consider increasing the shared memory '''kernel.shmall''' and '''kernel.shmmax''' settings in /etc/sysctl.conf to a larger value such as 268435456. This is also the reason you should start with the 320x240 resolution, so as to minimize the potential of memory problems which would interfere with your attempts to troubleshoot the device format issue. Once you have obtained a picture in the monitor using the NTSC format, then you can experiment with raising the resolution.

===Why do I only see blue screens with a timestamp when monitoring my camera?===
If this camera is attached to a capture card, then you may have selected the wrong Device Source or Channel when configuring the monitor in the ZoneMinder console. If you have a capture card with 2 D-sub style inputs(looks like a VGA port) to which you attach a provided splitter that splits off multiple cables, then the splitter may be attached to the wrong port. For example, PV-149 capture cards have two D-sub style ports labeled as DB1 and DB2, and come packaged with a connector for one of these ports that splits into 4 BNC connecters. The initial four video ports are available with the splitter attached to DB1.

===Why do I only see black screens with a timestamp when monitoring my camera?===
In the monitor windows where you see the black screen with a timestamp, select settings and enter the Brightness, Contrast, Hue, and Color settings reported for the device by '''zmu -d <device_path> -q -v'''. 32768 may be appropriate values to try for these settings. After saving the settings, select Settings again to confirm they saved successfully.

===I am getting messages about a backtrace in my logs, what do I do?===
If you are seeing entries in your log like the following
<pre>Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6 [0x3347230210]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6(memset+0xce) [0x334727684e]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x40ee9a]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x419946]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma [0x4213cf]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma(cos+0x35c) [0x404674]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /lib64/libc.so.6(__libc_start_main+0xf4) [0x334721da44]]
Jan 11 20:25:22 localhost zma_m2[19051]: ERR [Backtrace: /usr/local/bin/zma(cos+0xd1) [0x4043e9]]
Jan 11 20:25:22 localhost zma_m2[19051]: INF [Backtrace complete]</pre>
then you can help diagnose the problem by running a special command to translate the hex addresses into helpful information. This command is called addr2line and you can type 'man addr2line' for more information.
Basically addr2line takes two sets of parameters, the first is the name of the binary file, and the second is a list of addresses. Both of these pieces of information are displayed in the logs. The filename is the first part after the 'Backtrace:' tag, in this case /usr/local/bin/zma, though it may well be different in your case. Some of the lines refer to libraries rather than the zma executable but those can be ignored for now, the important part is noting which ZM binary is involved. The binary file is passed in following the -e flag. The addresses to pass to addr2line are those contained in the '[]' pairs. Again you can ignore those that are on a line that refers to a library but it will not hurt if you include them.
So in the example above, the command would be <pre>addr2line -e /usr/local/bin/zma 0x40ee9a 0x419946 0x4213cf 0x404674 0x4043e9</pre>
This should then dump out a more symbolic list containing source file names and line numbers, and it is this information which will be helpful if posted to the forums. Sometimes addr2line fails to produce useful output. This is usually because either the problem is so severe that it has corrupted the stack and prevented useful information from being displayed, or that you have either compiled ZM without the -g flag for debug, or you have stripped the binaries of symbol information after installation. This this case you would need to rebuild temporarily with debug enabled for the information to be useful.

This error some times happens when a linked camera looses its link or it is corrupted by the user or some other system event, try deleting the affected cameras and recreating them in the Zoneminder console.

===How do I repair the MySQL Database?===
There is two ways to go about this. In most cases you can run from the command prompt ->
* mysqlcheck --all-databases --auto-repair -p'''your_database_password''' -u '''your_databse_user'''

If that does not work then you will have to make sure that ZoneMinder is stopped then run the following (nothing should be using the database while running this and you will have to adjust for your correct path if it is different). ->
* myisamchk --silent --force --fast --update-state -O key_buffer=64M -O sort_buffer=64M -O read_buffer=1M -O write_buffer=1M /var/lib/mysql/*/*.MYI

===How do I repair the MySQL Database when the cli fails?===
In Ubuntu, the commands listed above do not seem to work. However, actually doing it by hand from within MySQL does. (But that is beyond the scope of this document) But that got me thinking... And phpmyadmin does work. Bring up a terminal.
sudo apt-get install phpmyadmin

Now go to http://zoneminder_IP/ and stop the ZM service. Continue to http://zoneminder_IP/phpmyadmin and select the zoneminder database. Select and tables marked 'in use' and pick the action 'repare' to fix. Restart the zoneminder service from the web browser. Remove or disable the phpmyadmin tool, as it is not always the most secure thing around, and opens your database wide to any skilled hacker.
sudo apt-get remove phpmyadmin

===I upgraded by distribution and ZM stopped working===
Some possibilties (Incomplete list and subject to correction)
#[[/usr/local/bin/zmfix: /usr/lib/libmysqlclient.so.15: version `MYSQL_5.0' not found (required by /usr/local/bin/zmfix)]] :: Solution: Recompile and reinstall Zoneminder.
Any time you update a major version that ZoneMinder depends on, you need to recompile ZoneMinder.

===Zoneminder doesn't start automatically on boot===
Check the list for log entries like "zmfix[766]: ERR [Can't connect to server: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)] ".
What can happen is that zoneminder is started too quickly after Mysql and tries to contact the database server before it's ready. Zoneminder gets no answer and aborts.
August 2010 - Ubuntu upgrades seem to be leaving several systems in this state. One way around this is to add a delay to the zoneminder startup script allowing Mysql to finish starting.
"Simply adding 'sleep 15' in the line above 'zmfix -a' in the /etc/init.d/zoneminder file fixed my ZoneMinder startup problems!" - credit to Pada.

=== Remote Path setup for Panasonic and other Camera ===
On adding or editing the source you can select the preset link for the parameters for the specified camera . In version 1.23.3 presets for BTTV,Axis,Panasonic,GadSpot,VEO, and BlueNet are available . Selecting the presets ZM fills up the required value for the remote path variable

=== Why do I get repeated/ mixed/unstable/ blank monitors on bt878-like cards (a.k.a. PICO 2000) ===

Please have a check at [[Pico2000]];

===What causes "Invalid JPEG file structure: two SOI markers" from zmc (1.24.x)===

Some settings that used to be global only are now per camera. On the Monitor Source tab, if you are using Remote Protocol "HTTP" and Remote Method "Simple", try changing Remote Method to "Regexp".

== Miscellaneous ==
=== I see ZoneMinder is licensed under the GPL. What does that allow or restrict me in doing with ZoneMinder? ===

The ZoneMinder license is described at the end of the documentation and consists of the following section

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty
of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

This means that ZoneMinder is licensed under the terms described [http://www.gnu.org/copyleft/gpl.html here]. There is a comprehensive FAQ covering the GPL at http://www.gnu.org/licenses/gpl-faq.html but in essence you are allowed to redistribute or modify GPL licensed software provided that you release your distribution or modifications freely under the same terms. You are allowed to sell systems based on GPL software. You are not allowed to restrict or reduce the rights of GPL software in your distribution however. Of course if you are just making modifications for your system locally you are not releasing changes so you have no obligations in this case. I recommend reading the GPL FAQ for more in-depth coverage of this issue.

=== Can I use ZoneMinder as part of my commercial product? ===

The GPL license allows you produce systems based on GPL software provided your systems also adhere to that license and any modifications you make are also released under the same terms. The GPL does not permit you to include ZoneMinder in proprietary systems (see http://www.gnu.org/licenses/gpl-faq.html#GPLInProprietarySystem for details). If you wish to include ZoneMinder in this kind of system then you will need to license ZoneMinder under different terms. This is sometimes possible and you will need to contact me for further details in these circumstances.

Bt878 4chip 8inputs

2014-09-14T14:15:30Z

Gkmac: Undo SPAM revision 6391 by Erictenne (talk)

Bt878 4chip 8inputs

2014-09-12T22:31:11Z

Gkmac: Undo SPAM revision 6383 by Erictenne (talk)

Hardware Compatibility List

2014-07-07T09:27:11Z

Gkmac: Undo SPAM revision 6297 by Erictenne (talk)

Zoneminder will work with almost any capture card that is supported by the linux kernel. You may find additional details about supported hardware in the part of the forums. Also if you find something in the forums that is missing from the wiki ADD IT.

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[UDP Technology NCP3200v2]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

[[KesCom PG104]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== Network Cameras ==
For Network Cams to work they need to be able to stream MJPEG without the requirement of activex controls. If you see the requirement for the camera calls for IE then there is a good chance it may not work. The other option is to grab JPEG images if the camera supports that option which will work but at a lower frame rate.

Any network camera that allows access to single JPEG image grabs or '''some but not all''' multi-part JPEG feeds.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[AirLive AirCam OD325HD]]

* [[Amovision AM-Q630M]]

* [[Anran VGB101-IP]]

* [[Apexis]] (APM-J011-WS, APM-J012-WS, possibly others)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[B-QTECH]] H.264 Camera

* [[BSTI]] Some

* [[Cisco]] some

* [[D-Link]] Most

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Grandstream]] Grandstream (GXV-3672-FHD & GXV-3672-FHD-36 tested)

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, possibly others)

* [[Level One]] some

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Messoa]] (NCR870, probably others)

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k (some)

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* [[PLANET]] some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

*[[Logitech 700 series]] some

*[[Ubiqiti]] some

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

*[[Edimax]] some

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== Network Digitizers ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source.

* [[Synectics E100]] encoder
*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: [[Logitech QuickCam Express]], QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the [http://www.zoneminder.com/forums/viewforum.php?f=10 HCL]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

Synectics E100

2014-07-06T17:50:36Z

Gkmac: Undo SPAM revision 6280 by Kristof (talk)

ZoneMinder seems to work with the [http://www.synx.com/ Synectics] E100 encoder.

The encoder supports two streams. The first one is at
rtsp://HOST:8554/01
and the second is at
rtsp://HOST:8555/01-2

To put these into ZoneMinder, add a monitor with:

Source Type: Ffmpeg
Source Path: rtsp://HOST:8554/01 (for the first stream)
Capture Width: 720 (for D1 resolution)
Capture Height: 576 (for D1 resolution)

Tip: to find the right width and height, open the stream URI in VLC and go to Tools > Codec Info.

On Ubuntu 11.10, it was necessary to install x264:
sudo apt-get install x264
for H.264 support.

Bt878 4chip 8inputs

2014-07-06T17:50:13Z

Gkmac: Undo SPAM revision 6281 by Kristof (talk)

LinkDelight CCTV H.264 4CH DVR Card

2014-07-06T17:49:11Z

Gkmac: Undo SPAM revision 6282 by Kristof (talk)

CCTV H.264 4CH DVR Card Real-time 100/120FPS Audio/video Capture Security Card (SKU: ESC09)

As found on eBay: [[http://www.ebay.ca/itm/CCTV-H-264-4CH-DVR-Card-Real-time-100-120FPS-Video-Audio-Connection-Cable?item=330647829755&cmd=ViewItem]]
Cost: around 22 $US

= Features =

This HD Digital Video Recording Card is installed to your computer host and the coming adapter cable connected with camera, to achieved host working as DVR and watch the camera image in LCD display. This DVR card is 4 channels, so it support 4pcs cameras and you can see 4 camera images in LCD display simultaneously.

* Video compression adopts advanced H.264
* Support widescreen display, including 1024*768 and above
* 4CH video 4CH audio, coming with 4ch video/audio connection cable
* Support smart mobile phone view, Windows mobile, Symbian mobile, IPhone
* Support Windows 2000 /2003 / XP / Vista / Windows 7 OS
* Support 4 split-screens playback and convenient to search recording files
* Support net remote preview, playback, record, PTZ control
* Support manual record, timer record and motion detection record
* PTZ: support multi-protocol, RS232/485, highspeed dome control software
* Support motion detection alarm & video lost alarm
* Security: multi-lever password, user right option, system keyboard lock

''Kindly Note:'' This cable isn’t compatible with the system of Window7 64bit

= Features =

<table border="1" cellpadding="1" cellspacing="1">
<tr>
<td colspan="2" width="176">Model </td>
<td width="324">4004 </td>
</tr>
<tr>
<td rowspan="4" width="70">Video </td>
<td width="105">Format </td>
<td width="324">NTSC / PAL </td>
</tr>
<tr>
<td width="105">Compression </td>
<td width="324">H ． 264 </td>
</tr>
<tr>
<td width="105">Input </td>
<td width="324">4CH BNC </td>
</tr>
<tr>
<td width="105">Output </td>
<td width="324">VGA </td>
</tr>
<tr>
<td colspan="2" width="176">Audio </td>
<td width="324">4CH AV </td>
</tr>
<tr>
<td colspan="2" width="176">Support OS </td>
<td width="324">Windows 2000 /2003 / XP / Vista / Windows 7 </td>
</tr>
<tr>
<td rowspan="3" width="70">Display </td>
<td width="105">Frame rate </td>
<td width="324">NTSC:120fps, PAL: 100fps </td>
</tr>
<tr>
<td width="105">Resolution </td>
<td width="324">352×288 320×288 704×576 </td>
</tr>
<tr>
<td width="105">Split screen </td>
<td width="324">1 、 4 、 cycle </td>
</tr>
<tr>
<td rowspan="4" width="70">Record </td>
<td width="105">Frame rate </td>
<td width="324">NTSC:120fps, PAL: 100fps </td>
</tr>
<tr>
<td width="105">Resolution </td>
<td width="324">352×288 320×288 704×576 </td>
</tr>
<tr>
<td width="105">Recording Mode </td>
<td width="324">Manual, Time, Motion Detection </td>
</tr>
<tr>
<td width="105">Mode </td>
<td width="324">1/8—8 times speed playback optional </td>
</tr>
<tr>
<td rowspan="4" width="70">Net Function </td>
<td width="105">Transmission mode </td>
<td width="324">LAN / PSTN / ISDN / ADSL </td>
</tr>
<tr>
<td width="105">Transmission protocol </td>
<td width="324">UDP/TCP </td>
</tr>
<tr>
<td width="105">Connection Mode </td>
<td width="324">Clients software/ IE Browse/Smart phone client software </td>
</tr>
<tr>
<td width="105">Main functions </td>
<td width="324">Remote preview 、 Video playback 、 Remote control </td>
</tr>
<tr>
<td rowspan="2" width="70">Alert </td>
<td width="105">type </td>
<td width="324">Motion detection, Video loss </td>
</tr>
<tr>
<td width="105">Linkage </td>
<td width="324">Channel record 、 Sound alerts </td>
</tr>
<tr>
<td rowspan="3" width="70">Others </td>
<td width="105">PTZ </td>
<td width="324">Support multi-protocol,RS232/485,highspeed dome control software </td>
</tr>
<tr>
<td width="105">Back up </td>
<td width="324">USB 、 Network 、 CD-RW 、 DVD-RW </td>
</tr>
<tr>
<td width="105">security </td>
<td width="324">Multi-lever password, user right option, system keyboard lock </td>
</tr>
<tr>
<td colspan="2" width="176">Net Weight </td>
<td width="324">52g </td>
</tr>
</table>

= ZoneMinder =

I was able to make this card under Ubuntu 12.04 server with a minimal amount of fuss. The Card is based on a Techwell 6800 Chipset, and I was able to find the appropriate Linux Drivers at this site:

Drivers: [[http://gitorious.org/tw68/tw68-v2|TW68-V2 Drivers]]

Installation:

<pre>
mkdir techwell
cd techwell/
git clone git://gitorious.org/tw68/tw68-v2.git
tw68-v2/
make
sudo make install
sudo modprobe tw68
lsmod|grep tw
dmesg
</pre>

I'm sorry I haven't kept a copy of the whole session. After compiling and "loading" the tw68 modules, you need to check that the modules are actually loaded (lsmod|grep tw). You should have the following output:

<pre>
~$ lsmod |grep tw
tw68 44633 2
videodev 86588 3 tw68
videobuf_dma_sg 18786 1 tw68
videobuf_core 25409 2 tw68,videobuf_dma_sg
btcx_risc 13400 1 tw68
</pre>

Issuing the dmesg command, you should see 4 "video devices" found, labeled from /dev/video0 to /dev/video3... Each video device is tied to an input from the card.

I haven't bothered yet with the "audio" part of it, so I can't tell you if that works or not. If you're able to test it, please update this wiki page to let others know...

'''Although I do get a lot of messages in dmesg, concerning "[261734.936103] tw6810[0]/0: [c5c8bb40/1] timeout - dma=0x05f8a000", the capture does work well.'''

[10/26/2012]
I found that if you're using two cards you can end up with some really nasty artifacts that manifest themselves as white horizontal lines on the feeds, after doing some calculations finding myself close to saturating PCI bus, I found these instructions on the [http://www.zoneminder.com/wiki/index.php/Videocards_with_Philips_saa7134_chipset phillips] page:

<pre>
Do not forget to to increase "shared memory" at the end of /etc/sysctl.conf with
kernel.shmall = 134217728
kernel.shmmax = 134217728

cause your card supports 640x480 pixel with 24 bit depth and thats more than 112Mbyte ;-)
</pre>

doing this allows me to run 8 cams @ 12fps full 640x480 without artifacts

= Zoneminder configuration =

The following screenshots show how I configured the device in my zoneminder:

[[File:LD_CCTV_ZM1.jpg]]

[[File:LD_CCTV_ZM2.jpg]]

= Observations =

I currently have zoneminder installed on an Intel Atom 525 with 4 GB of RAM. This same system has the "LinkDelight CCTV H.264 4CH DVR Card" installed on it and monitoring 2 CCTV cameras at around ~20fps each (@ 640x480), with ~30 % Cpu Usage across the 4 "cores".

Mind you, it is also receiving a video stream from an IP camera @ 15 fps (640x480). I haven't enable any motion detection yet.

All-in-all it's a nice, cheap card that works for me.

Grandtec Grand X Guard

2014-07-06T17:48:46Z

Gkmac: Undo SPAM revision 6283 by Kristof (talk)

These cards a relatively inexpensive by using one Brooktree (bt) video capture chip shared for a number of inputs. The upside is low cost, downside is performance.
* [http://adrian-fh98.web.unair.ac.id/ Informasi] 27 fps
* Using 1 source you get 25 fps
* Using 2 source you get 5 fps each (10 fps total)
* Using 4 sources you get 2.5 fps each (10 fps total)
...and so on.
if you use more than 1 source, total FPS is 10/12

Please note that this will only show up as one video input (''/dev/video0'' for me). You will use channels of the input to access the multiple ports.

; bttv supported card types
: 57 -> GrandTec 'Grand Video Capture' (Bt848) [4344:4142]
: 77 -> GrandTec Multi Capture Card (Bt878)
: 103 -> Grand X-Guard / Trust 814PCI [0304:0102]

== GrandTec Grand X-Guard 4P (GXG-4000)==
Autodetected correctly and confirmed working with bttv driver.

== GrandTec Grand X-Guard 9P (GXG-9000)==
Confirmed working under ZoneMinder 1.22 (probably earlier). bttv driver 0.9.17 incorrectly detects this as a card type 57. You need to edit modprobe.conf (see below), then do a rmmod bttv and modprobe bttv to get it to work correctly.

''/etc/modprobe.conf''
<pre>
options bttv card=103
</pre>

I haven't had any problems testing with a single input but with each input added, the image gets brighter and more washed out. At 4 monitors, the image is no longer viewable with the default monitor brightness and contrast. The current theory is that providing a live connection to each input will resolve the problem and is supported by the following statement from Grandtec

<blockquote>
Q. All of the cameras are just white screens. Why?
 
A. The card attempts to automatically color-balance all of the cameras at once. If a camera port is listed as active (9 and 16 port) or if a preview window is open (4 port) for a port that does not physically have a camera connected, then it tries to balance with a camera that is not there. The result is a white screen for all cameras. To resolve this, close or de-list as active any ports without cameras connected.
</blockquote>

== GrandTec Grand X-Guard 16P (GXG-1600) ==

Needs the same configurations changes as the 9P card above.

== Sources ==

[http://www.zoneminder.com/forums/viewtopic.php?p=4536&sid=071efc96ee14a2370e5d4f159aa2a685 davide post]

[http://www.zoneminder.com/forums/viewtopic.php?t=3285 Another davide post]

Beginner hardware

2014-07-06T17:47:55Z

Gkmac: Undo SPAM revision 6284 by Kristof (talk)

==Option 1==

The best, first advice is to check that your camera is compatible with zoneminder's motion JPEG (MJPEG).

You should read the [[Documentation]]. The developers spent and continue to spend a great deal of time writing it... you should spend at least a little time reading it. Specifically, read the part about shared memory.

'''Recommended IP cameras'''

[[Axis]] brand cameras are a good choice, but expensive.

[[BSIT]] are really cheap but also not the greatest quality.

Camera quality varies greatly, both in actual image quality and in operational reliability. Remember that you often "get what you pay for." Cameras from high volume manufacturers may be subject to software/hardware compromises that lower cost at the risk of breaking functionality and/or compatibility with standards.

Avoid cameras that require 1.24(aka: mpeg video) because it make things harder for beginners.

==Option 2==

The best beginners hardware and setup is to use an old unused system, anything from late Pentium 3 or Athlon XP generation of cpus will be more than enough for a setup capable of running 2 or 3 cameras depending on configuration.

You will need one of the cheap pci cctv capture cards from Ebay that use the bt878 chip, if you search for pci cctv on ebay then most of the cheap cards that show up will be a card of this type, see the [[Pico2000]] section of the Zoneminder wiki for a few photos of these cards and a little more technical information.
For capture cards with tw6800 chips you have to compile the driver. Have a look at [[KesCom PG104]] for instructions.

You can alternatively buy them and better boards from the retailers in the [[shop]] section of this webpage.

You will need to configure the capture card as described in the [[Pico2000]] wiki

Next source some standard analogue cameras from the retailers listed on this page or any other source you like.

Install Zoneminder using the [[CentOS]] guide contained in the wiki or any other distro guide you are happy with, I personally started with the CentOS guide and it has worked well for me.

Configure and then you're running!!!.

This is of course a beginners system and so can be expanded and improved on once you are happy, my aim in this design is to build a Zoneminder system as cheaply and basic as possible, I have made a lots of setups that are still operating on the above basis.

MobileDevices

2014-07-06T17:47:35Z

Gkmac: Undo SPAM revision 6285 by Kristof (talk)

Hardware Compatibility List

2014-07-05T09:55:51Z

Gkmac: Undo SPAM revision 6259 by Kristof (talk)

WinFast TV2000 XP

2014-07-05T09:55:34Z

Gkmac: Undo SPAM revision 6260 by Kristof (talk)

This card uses a bt878 chipset and the bttv kernel module and is probably one of the more common capture cards found in a home PC/DVR. It is quite generic but comes in 2 flavours: "ATX version" and "Low profile version"

There are 4 inputs:
# '''Television''' (Coaxial cable) This is where you can tune to a TV channel frequency
# '''Composite1''' (RCA lead)
# '''SVideo''' (MiniDIN connector)
# '''Composite3''' (RCA lead) This is the FM tuner for radio

'''Note:''' You should have a connector cable to connect the Composite1 and SVideo cables into a single 6-pin MiniDIN port on the card. The cable for the Low profile version also includes the Left/Right Audio inputs, connecting to a 9-pin MiniDIN port on the card.

There is also an input for the Infrared sensor which plugs into a headphone jack. This is probably not useful for ZoneMinder but may be used with Linux InfraRed Control (LIRC) if you want to capture from TV occasionally.

== dmesg ==
<pre>
Linux video capture interface: v2.00
bttv: driver version 0.9.16 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
GSI 23 sharing vector 0xE9 and IRQ 23
ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 23
bttv0: Bt878 (rev 17) at 0000:01:07.0, irq: 23, latency: 32, mmio: 0xe5100000
bttv0: detected: Leadtek WinFast TV 2000 [card=34], PCI subsystem ID is 107d:6606
bttv0: using: Leadtek WinFast 2000/ WinFast 2000 XP [card=34,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00bff706 [init]
bttv0: using tuner=5
bttv0: i2c: checking for MSP34xx @ 0x80... not found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
bttv0: i2c: checking for TDA9887 @ 0x86... not found
tuner 5-0061: chip found @ 0xc2 (bt878 #0 [sw])
tuner 5-0061: type set to 5 (Philips PAL_BG (FI1216 and compatibles))
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: registered device radio0
bttv0: PLL: 28636363 => 35468950 .. ok
input: bttv IR (card=34) as /class/input/input7
bttv-input: bttv IR (card=34) detected at pci-0000:01:07.0/ir0
</pre>

== lspci ==
<pre>
helot# lspci | grep Bt878
01:07.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
01:07.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
</pre>

== xawtv -hwscan ==
<pre>
helot# xawtv -hwscan
This is xawtv-3.95, running on Linux/x86_64 (2.6.18-ck1)
looking for available devices

/dev/video0: OK [ -device /dev/video0 ]
type : v4l2
name : BT878 video (Leadtek WinFast 20
flags: overlay capture tuner
</pre>

When you run <tt>xawtv</tt>, you may need to fiddle with some of the options. In my case, I set the ''''input'''' to '''Composite1''' and ''''capture'''' to '''grabdisplay'''. Once you have a picture, you can adjust the colour, contrast, brightness etc. ZoneMinder will recognise these settings when you set up a Monitor for this input (you may need to leave xawtv running).

== zmu -d <device> -q -v ==
<pre>
helot# zmu -d /dev/video0 -q -v
Video Capabilities
Name: BT878 video (Leadtek WinFast 20
Type: 171
Can capture
Can tune
Overlay onto frame buffer
Can clip
Scalable
Video Channels: 4
Audio Channels: 1
Maximum Width: 924
Maximum Height: 576
Minimum Width: 48
Minimum Height: 32
Window Attributes
X Offset: 0
Y Offset: 0
Width: 384
Height: 288
Picture Attributes
Palette: 5 - 32bit RGB
Colour Depth: 32
Brightness: 27086
Hue: 22280
Colour :47185
Contrast: 25340
Whiteness: 0
Channel 0 Attributes
Name: Television
Channel: 0
Flags: 3
Channel has a tuner
Channel has audio
Type: 1 - TV
Format: 0 - PAL
Channel 1 Attributes
Name: Composite1
Channel: 1
Flags: 2
Channel has audio
Type: 2 - Camera
Format: 0 - PAL
Channel 2 Attributes
Name: S-Video
Channel: 2
Flags: 2
Channel has audio
Type: 2 - Camera
Format: 0 - PAL
Channel 3 Attributes
Name: Composite3
Channel: 3
Flags: 2
Channel has audio
Type: 2 - Camera
Format: 0 - PAL
</pre>

== Configuring a Monitor ==
In the ZoneMinder Console (main page), click '''Add New Monitor'''. Click the '''Source''' tab. Verify the settings match what you saw with <tt>xawtv</tt>:
; Device Path : <tt>/dev/video0</tt> (or <tt>/dev/v4l/video0</tt>)
; Device Channel : <tt>1</tt> (Composite1)
; Device Format : <tt>PAL</tt> (NTSC in America)
; Capture Palette : <tt>RGB24</tt>
; Capture Width (pixels) : <tt>384</tt>
; Capture Height (pixels) : <tt>288</tt>
; Orientation : <tt>Normal</tt>

When you click ''Save'', your new Monitor's ''Source'' column should be coloured '''''Orange or Green'''''. If it is Red, you probably need to adjust the Width/Height of the captured image.
----
'''For more info, see the [http://www.linuxtv.org/v4lwiki/index.php/Leadtek_WinFast_2000 Video4Linux Wiki]'''

Synectics E100

2014-07-05T09:55:21Z

Gkmac: Undo SPAM revision 6261 by Kristof (talk)

Zms-inetd

2014-07-05T09:55:05Z

Gkmac: Undo SPAM revision 6262 by Kristof (talk)

Bt878 4chip 8inputs

2014-07-05T09:54:53Z

Gkmac: Undo SPAM revision 6263 by Kristof (talk)

== Noname with 4 bt878 chips and 8 inputs ==

* tip: also check [[Pico2000]] related card info;

When using all channels you'll get around 5 fps.
Warning it takes a long time to boot using this card. Maybe settings are bad. But it is working OK.

== Configuration ==

''/etc/modprobe.conf''
<pre>
options bttv card=0,0,0,0 tuner=4,4,4,4
</pre>

If your driver is compiled into the kernel, add the following to be passed onto the kernel from LILO or GRUB.
<pre>
bttv.card=0,0,0,0 bttv.tuner=4,4,4,4
</pre>

* A list of card types and tuner types can be found in the Linux kernel sources under Documentation
<pre>
http://linuxtv.org/hg/v4l-dvb/file/tip/linux/Documentation/video4linux
</pre>

== Photos ==

[[Image:Bt878_4chip_8inputs_1.jpg|200px]]
[[Image:Bt878_4chip_8inputs_2.jpg|200px]]

LinkDelight CCTV H.264 4CH DVR Card

2014-07-05T09:54:35Z

Gkmac: Undo SPAM revision 6264 by Kristof (talk)

Grandtec Grand X Guard

2014-07-05T09:54:22Z

Gkmac: Undo SPAM revision 6265 by Kristof (talk)

Beginner hardware

2014-07-05T09:53:56Z

Gkmac: Undo SPAM revision 6266 by Kristof (talk)

MobileDevices

2014-07-05T09:53:43Z

Gkmac: Undo SPAM revision 6267 by Kristof (talk)

Hardware Compatibility List

2014-06-19T19:59:53Z

Gkmac: Undo SPAM revision 6208 by Kristof (talk)

WinFast TV2000 XP

2014-06-17T10:02:03Z

Gkmac: Undo SPAM revision 6206 by Kristof (talk)

UDP Technology NCP3200v2

2014-06-11T17:31:34Z

Gkmac: Cleanup path-socket table.

Hardware Compatibility List

2014-06-11T09:21:06Z

Gkmac: Undo SPAM revision 6203 by Kristof (talk)

Hardware Compatibility List

2014-06-03T18:51:38Z

Gkmac: SPAM removal

MobileDevices

2014-06-03T18:44:46Z

Gkmac: SPAM - Undo revision 5748 by Kristof (talk)

WinFast TV2000 XP

2014-06-03T18:42:54Z

Gkmac: SPAM - Undo revision 5743 by Kristof (talk)

Synectics E100

2014-06-03T18:41:26Z

Gkmac: Spam removal

UDP Technology NCP3200v2

2014-05-25T19:58:12Z

Gkmac: Major re-jig.

Hardware Compatibility List

2014-05-12T11:01:40Z

Gkmac: Added UDP Technology NCP3200v2

Zoneminder will work with almost any capture card that is supported by the linux kernel. You may find additional details about supported hardware in the part of the forums. Also if you find something in the forums that is missing from the wiki ADD IT.

== Capture Cards ==

[[Anykeeper]]

[[Avermedia]]

[[Camsecure PCI Express video capture]]

[[Digiflower]]

[[Geovision GV250 - bt878a chip]]

[[Grandtec Grand X Guard]]

[[Hauppauge]]

[[Ituner Spectra 8]]

[[Kodicom 4400r]]

[[Kodicom 8800]]

[[Tungson TE-8008]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[LinkDelight CCTV H.264 4CH DVR Card]]

[[Linux Media Labs LMLBT44]]

[[Osprey 100]]

[[Provideo PV- series (Bluecherry)]]
[[ Bluecherry - BC-H16480A]]
[[TView 95/99]]

[[UDP Technology NCP3200v2]]

[[Videocards with Philips saa7134 chipset]]

[[WinFast TV2000 XP]]

[[Rapid OS]]

[[KesCom PG104]]

== bt8x8 Cards ==
A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] -4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - This card is supplied with D-sub to 8 BNC connector and uses the bt878 chip for each input allowing full frame rates and quality. See [[Kodicom 8800]] for more information.

Geovision GV250 bt878a single chip 4 inputs - This capture Card is supplied with 4 video inputs but with NO audio channel

'''Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.'''

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== Network Cameras ==
For Network Cams to work they need to be able to stream MJPEG without the requirement of activex controls. If you see the requirement for the camera calls for IE then there is a good chance it may not work. The other option is to grab JPEG images if the camera supports that option which will work but at a lower frame rate.

Any network camera that allows access to single JPEG image grabs or '''some but not all''' multi-part JPEG feeds.

'''Full Compatibility '''

* [[7Links]](TM Trade Mark)

* [[A-mtk]]

* [[Abus]] some

* [[Airlink 101]] some

* [[AirLive AirCam OD325HD]]

* [[Amovision AM-Q630M]]

* [[Anran VGB101-IP]]

* [[Apexis]] (APM-J011-WS, APM-J012-WS, possibly others)

* [[ArecontVision]] (AV3130M, probably other too)

* [[Astak Mole]] Some

* [[Axis]] All

* [[Brickcom]] These have been tested

* [[B-QTECH]] H.264 Camera

* [[BSTI]] Some

* [[Cisco]] some

* [[D-Link]] Most

* [[Foscam]] (FI8908W, FI8904W, possibly others)

* [[Gadspot]] Most

* [[Generic]] Only tested one

* [[Geovision]] (GV-FE420, possibly others)

* [[Grandstream]] Grandstream (GXV-3672-FHD & GXV-3672-FHD-36 tested)

* [[hootoo]] Some

* [[Iguard]] IP390E

* [[Instar]] (IN-2905, possibly others)

* [[Level One]] some

* [[Linksys]] WVC-210 / WVC2300 / PVC2300 / WVC54GC

* [[Loftek]] Sentinel PTZ

* [[Maygion]] (IP-603, IP-604, possibly others)

* [[Messoa]] (NCR870, probably others)

* [[Rimax]] Some

* [[Rovio]]

* [[Sony]] Most

* [[TP-LINK]] Some

* [[Trendnet]] Most

* [[Wanscam]] FR4020A2 (Foscam clone)

* [[x-vision]] Xvision cameras by y3k

* [[Y-Cam]] (Sharx Ip) Most

* [[Zavio]] Some

* [[Zecumate]] JPT3815W

* Remote systems, themselves running zoneminder, can be accessed as cameras using the Remote Path of '''/cgi-bin/nph-zms?mode=single&monitor=1&scale=100&maxfps=5&buffer=1000''' - where the monitor number is the correct camera on the remote system.

'''Single Jpeg Only'''

* [[Airlink 101]] some

* [[JVC]] some

* [[Panasonic]] some

* [[PLANET]] some

*[[Toshiba]] some

* [[Veo Observer IP NetCam]] most

*[[Vivotek]] All

'''Mpeg(ver1.24.0 and up)'''

*[[ABS_MegaCam]]

* [[Axis]] All

* [[ ACTi]] All

*[[Vivotek]] Most

*[[Logitech 700 series]] some

*[[Ubiqiti]] some

'''Compatible with modifications'''

*[[Aviosys]] some

* [[Mobotix]] all

*[[Edimax]] some

* [[Conceptronic]] some

'''Compatible with problems'''

* [[Compro]] IP70. MPEG4 only, some reliability issues and general poor firmware quality.

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.

* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* OvisLink AirLive WL-5400CAM

Useful link: Flash's IP Camera Database, with Zoneminder compatibility guide: http://digdilem.org/cameras

== Network Digitizers ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source.

* [[Synectics E100]] encoder
*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

With the yoics Aviosys 9100 firmware at http://www.yoics.com/?p=28, ZoneMinder can directly access all four ports via /usr/yoicsX.jpg as the remote host path, where X is 0 - 3.

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3, LIVE! Cam OPTIA PRO (V4L2, Chan 0, PAL, YUYV)

*''Most'' UVCvideo cameras, including: [[Logitech QuickCam Express]], QuickCam Pro 3000, [[QuickCam Pro 4000]], QuickCam Communicate STX/Deluxe, [[Logitech Webcam Pro 9000]], and [[Webcam C250]]

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

*Confirmed basic functionality with Microsoft Lifecam VX 5000 using UVC Streaming method

Note that most USB cameras that can use Video4Linux/V4L2, and so can be used by ZoneMinder. Some have older chipsets and can be hard to find new.

Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links:
* [http://www.smcc.demon.nl/webcam/ Old Maintainer]
* [http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the [http://www.zoneminder.com/forums/viewforum.php?f=10 HCL]

== Plug Computers ==
Guruplug Server Plus -> How to install Zoneminder

UDP Technology NCP3200v2

2014-05-12T10:25:16Z

Gkmac: Very sketchy summary at the moment. More details will be added soon.

The UDP Technology NCP3200v2 card is a 16 channel video capture card.

Manufacturers website: http://www.udptechnology.com/products/PC/NCP3200V2.html

== Linux usage ==

The card has very partial Linux "support" using the bttv driver. In <tt>/etc/modprobe.d/bttv.conf</tt> the driver needs to be told to use the Geovision GV-800 master and slave cards, but unlike the GV-800 the "master" card needs to be the last 2 numbers.
options bttv card=158,158,158,158,158,158,157,157
In this configuration, 4 of the 16 inputs are spread across the /dev/video inputs. Changing channels on the inputs will have no effect.
{| border="1" cellspacing="0" align="center"
|-
! Path
! Socket
|-
| /dev/video0|| 4
|-
| /dev/video1|| 4
|-
| /dev/video2|| 3
|-
| /dev/video3|| 3
|-
| /dev/video4|| 2
|-
| /dev/video5|| 2
|-
| /dev/video6|| 1
|-
| /dev/video7|| 1

|}

[[Image:Ncp3200v2front.jpg|600px|NCP3200v2 capture card - front view]]

File:Ncp3200v2front.jpg

2014-05-12T09:42:17Z

Gkmac: UDP Technology NCP3200v2 capture card - front view

UDP Technology NCP3200v2 capture card - front view

Pico2000

2014-02-25T19:29:23Z

Gkmac: Undo revision 5609 by Andrewq (talk) remove spam link

== Introduction ==

PICO2000 is a cheap DVR card that works well with ZoneMinder.

=== Name origination ===

The name "PICO2000," though often used, is technically not correct. PICO2000 is the name of proprietary software that was bundled with this class of cards.

PICO2000 is available under many different brand names such as '''Star Imavision Video Capture''', '''Brooktree 848''', '''Brooktree 878'''. They are generally stated as '''PICO2000 compatible'''.

=== Specifications ===

PICO2000 is a quad camera input PCI card. The card uses a single Conexant 878A chip. In addition, some models have 1 audio input jack; it has not been tested with ZoneMinder.

* Compression: MPEG4
* Display Resolution: 352 x 240 (NTSC)
* Screen Display: 1/4/7/10/13/16 multi-view or full screen
* Multiple cards allowed as per your PCI slot allocation
* Minimum PC capability: Pentium III 800 MHz or equivalent
* 30 FPS (degrades as the channels are utilized; expect ~2 FPS with all four channels capturing)

=== Purchase information ===

A PICO2000 costs about US$5.00 in China with free shipping.

For the United States, ebay may be the best place to purchase a PICO2000. As of January of 2010, they are $30 each (including shipping from China). An ebay search for "PICO CCTV" will return results.

== Linux driver ==

Linux kernels after 2.6.2x appear to have the driver for this card bundled in. Further info can be found at [http://linux.bytesex.org/v4l2/bttv.html http://linux.bytesex.org/v4l2/bttv.html].

=== Linux configurations and experiments ===

In <tt>/etc/modprobe.conf</tt>

For one card:
options bttv card=77 tuner=4 radio=0 triton1=0 vsfx=0 autoload=0
For two cards:
options bttv card=77,77 tuner=4,4 radio=0,0 triton1=0 vsfx=0 autoload=0
And so on.

Also, if during bootup your system hangs for 5 minutes or more at "Setting clock (utc)":
options i2c-algo-bit bit_test=1
options bttv card=77 tuner=4 radio=0 triton1=0 vsfx=0 autoload=0
The order of the lines is important.

In Ubuntu 12.04 server, <tt>/etc/modprobe.conf</tt> is gone, so you need to create a config file in <tt>/etc/modprobe.d/</tt>:
* call it bttv.conf (the name doesn't really matter), and it contains:

alias char-major-81-0 bttv
options bttv card=77 pll=1

On an AMD 6-core running zm 1.25 on Centos 6 I got this error a couple times
a second in /var/log/messages -- kernel: bttv0: PLL can sleep. The remedy was
to remove the options from a file in modprobe.d and put it in /etc/rc.d/rc.local as

modprobe bttv card=77,77 tuner=4,4 radio=0,0 triton1=0 vsfx=0 autoload=0

== ZoneMinder configuration ==

Settings under source >> source >> general...

The following settings depend on your camera. Check your camera's specification sheet (try the suggested starting values in brackets):

* Device format [NTSC, PAL]
* Capture pallet [GREY]
* Dimensions [X=320, Y=240]

When you have multiple cameras sharing one Pico card, you may have issues where:

* An image from one camera shows up on more than one input
* Blank images on certain inputs
* Mixed images between inputs.

The reported solution for these problems has varied. You may want to try each of the following options one at a time. Remember to restart ZoneMinder after each change.

* Disable V4L_MULTI_BUFFER (found in options >> config)
* Change CAPTURES_PER_FRAME to a value such as 2 or 4 (found in options >> config)
* Use Video For Linux version 1 for each input (found in source >> source >> capture method)
* In ZoneMinder 1.25, I had to use V4L2 to get it to work

== ZoneMinder configuration 2.0 ==
This is working for me. Might not work for others.
'''This card is very 50/50 when getting it to work. Each system is different!'''

I live in UK so for me I use PAL.
PAL is 768x576
NTCS should be 640x480 (NOT TESTED).

My settings are just like the other ones but like so.

In the ZoneMinder Console, Add/edit a camera to this.

'''Source'''
{| {{table}}
|-
| Device Path|| /dev/video0
|-
| Capture Method|| Video for Linux Version 2
|-
| Device Channel||X
|-
| Device Format|| PAL
|-
| Capture Palette|| YUYV (Tested most of them, half work, half working ones are B/W or wrong color).
|-
| Capture Width (pixels)||768
|-
| Capture Height (pixels) ||576
|-
|
|}
X = what input you are using. I have a image on the bottom of this page showing what inputs are what.
(NTSC should be 640x480)

'''In your /etc/modprobe.d/bbtv.conf'''

{| {{table}}
| alias char-major-81-0 bttv
|-
| options bttv gbuffers=32 card=77 tuner=4 radio=0 coring=1 full_luma_range=1 chroma_agc=1 combfilter=1 autoload=0 triton1=0 vsfx=0
|-
|
|}

Expect about 7-15FPS, 10 average at this resolution.
I have added a photo of a night garden shot. More to come.
http://www.zoneminder.com/forums/viewtopic.php?f=29&t=20692&p=78737#p78737
TBH, This capture card is a waste of time and money unless if you are happy with 1-2FPS 4 channel or 1 channel 10FPS.

Test with config 2.0
Night garden http://img163.imageshack.us/img163/6170/capturexwm.png

Card input numbers. http://img803.imageshack.us/img803/8941/inputsfw.png

== Chip history ==

The Conexant Fusion 878A is the newer version of the Brooktree Bt878A. The Brooktree Bt878A is the successor to the Bt848.

Video capture software supporting Bt878A that is not designed for CCTV will likely only allow you to access one camera port at a time.

[http://wiki.robotz.com/index.php/Pico_Install_Instructions_4_Port_CCTV_DVR_Card#Conexant_Fusion_878A http://wiki.robotz.com/images/d/da/Conexantfusion878A.png]

== Photos ==
[[Image:4ch DVR card.jpg|220px|Pico2000 photo 3]]
[[Image:Pico2000_1.jpg|200px|Pico2000 photo 1]]
[[Image:Pico2000_2.jpg|200px|Pico2000 photo 2]]