
Prerequisites
18
Siemens Building Technologies
Fire Safety & Security Products
01.2008
7 Prerequisites
7.1 Hardware
requirements
SISTORE MX integrates a video compression board (or frame grabber) that
features up to 16 (MX 3204) / 32 (MX 3232 - 3208) video inputs, depending on the
model.
SISTORE MX 3204
SISTORE MX 3208 - 3232
4 video inputs
8, 16, 32 video inputs
The video data is stored on local hard disks. Saving on optical CD-R/CD-RW odrr
DVD-R/DVD-RW drives is possible directly from SISTORE MX (see Section
17.16.2: Burning image sequences to CD/DVD).
7.2
Resolution and file format
The files stored by SISTORE MX have the extension .AVI or .k26. The resolution of
the stored images is (by using normal resolution) 352 x 288 pixel and (by using
high resolution) 704 x 288 pixel.
NOTE:
From version 2.35 on, SISTORE MX saves all files as *.k26 files instead of *.avi files. The SISTORE
player makes no difference between these two file types. The *.k26 files can however not be
reproduced using other movie player models (data protection of the SISTORE MX video files).
The user should therefore always copy the file „SISTOREPlayer.exe“ from the Windows directory (e.g.
\Windows) to the target data medium (disk, CD-R/CD-RW, DVD-R/DVD-RW or network drive) using
the Windows explorer. This ensures that the exported files can be reproduced using the SISTORE
player. Alternatively, since Version 2.45, the data can be stored without data protection as *.avi files
which can be played with standard movie player. For detailed information about data protection see
Section 17: Playback.
7.3 Conversion
As of version 2.35, SISTORE MX automatically converts the configurations of the
preceding version to the current version. Nevertheless, we would like to emphasize
that you should check your configuration without fail after an update.
NOTE:
A conversion of older versions (earlier than version 2.35) is not possible. It is also not possible to take
over settings for event-triggered recordings and scenarios from the preceding versions (earlier than
version 2.55). These are deleted during the conversion.