This tool does not exist. In an earlier stage of the development of Streams 5 we were intending to add a defragmentation feature to the Video Library Tools program that is part of Streams 5. Earlier editions of the Streams 5 User Guide included instructions on where to find this tool and the Video Library Tools may have even included a defragmentation button which did nothing, but as Streams 5 entered the late Beta stage we revised our strategy for dealing with the recovery of space used by unwanted scenes in the Video Library file. The Video Library Archive tool fills the role that was originally intended to be filled by the Video Library Defragmentation tool. The Archive tool generates a new Video Library File containing the Movies and Scenes that the user specifies, allowing unwanted data to be deleted as the new Video Library is kept and the original discarded.

No, Streams 5 SDK functions are vastly different from Video Savant SDK applications. Porting an SDK application from any verson of Video Savant to Streams 5 is much different than porting a Video Savant 3.0 SDK application to Video Savant 4.0. Streams 5 SDK applications are closer to Video Savant Processing Libraries in structure than they are to Video Savant SDK applications.

Every camera has different features and different ways to access those features. As a result it is impossible to build an interface that will work with every camera and frame grabber combination. Camera control features have been implemented through many device drivers for Video Savant and Streams but are always done on a case by case basis. Please contact IO Industries Technical Support for assistance with this type of problem.

Video Savant 4 was originally designed to record from a single camera. The Pro version added "stream filters", which allowed the user to record an additional data stream such as GPS, or IRIG-B. This is a frame-based program, meaning that all devices recording will acquire data at the same point in time, which is aligned on a frame number (or buffer number). Streams 5 was designed to record from multiple cameras and multiple acquisition devices. This is a time-based program, meaning that all devices recording will acquire data continuously at the respective rate of each device. Each sample of information is time-stamped so that all devices are correlated through time. Streams introduces "timing filters", which allow the user to choose a time base (GPS, IRIG-B, system time) For a feature comparison see this link: VS4 vs ST5

Internet Explorer's default settings use Passive FTP Transfers, but our FTP Site does not support this. To access our FTP Site from Internet Explorer, go to the Tools menu, select Internet Options. On the Advanced Tab, locate the setting "Use Passive FTP (For Firewall and DSL modem compatibility)" and un-check it. You may have to restart Internet Explorer before this change takes effect.

The CL160 works best with Seagate Cheetah or Hitachi Ultrastar SCSI drives. Both 68pin and 80pin drives are supported, the latter requires a SCSI backplane. You can expect a throughput of 35MB/s per drive with 10,000RPM, and 45MB/s per drive with 15,000RPM.

The CL160 works best with Seagate Cheetah or Hitachi Ultrastar SCSI drives. Both 68pin and 80pin drives are supported, the latter requires a SCSI backplane. You can expect a throughput of 35MB/s per drive with 10,000RPM, and 45MB/s per drive with 15,000RPM

Frame size refers to the size of a raw camera frame. Keep in mind that the CLFC uses "perfect" bit-packing, so a 10-bit 1024x1024 image is only 1,310,720 bytes. The frame size may range from a few kilobytes to tens of megabytes, however disk-write operations are optimized for roughly 3.5 MB. To ensure maximum record bandwidth, camera frames are either merged or split so that the optimal size write can be performed. A single disk write operation is called a "sequence". Consider two cases. Case 1: A camera has a 1.25 MB frame, split across 4 channels. The size per channel is 327680 bytes. Therefore, 11 frames will be combined into each sequence. Case 2: A camera has a 16 MB frame, recording to 1 channel. The frame will be split into 5 3.5 MB frames (the last being only partially used). When a frame is split into multiple sequences, we call this "fragmented" or "multi" writes. Many DVR Express operations must be aligned to sequence boundaries. In the fragmented case, this does not restrict the user. In the traditional case however, this has several implications. The number of frames recorded must always be a multiple of the sequence size. Since a write does not occur until 11 frames have been acquired, no frames are reported as "recorded" until all 11 have been acquired. All pre-trigger boundaries must also be aligned to sequence boundaries. The CLFC administrator option "Max Disk Write Size" sets the ideal size of a disk-write. Users may change this option to tweak the sequence size used but keep in mind that the disk bandwidth may be reduced also. Users may also force a sequence size by specifying "WRITESIZEBLOCKS" in their camera files.

The DVR Express maintains a log of system activity. It is almost always the first piece of information that technical support will require. You may locate the CLFC log in [DVR Express Install Path]\ClfcLog.txt. If the default install path was used, the file will be in c:\Program Files\IO Industries\DVR Express\CLFC\ClfcLog.txt. Also found in the same directories, it may be useful to send the files "FileTable_Verification_Results.txt" and "ClfcInfo.txt". Always be ready to provide a history describing all significant steps up to and including the suspected issue. Provide all of the above in an email to your support contact (support@ioindustries.com by default). Following these steps will help ensure a prompt and efficient solution to most problems.

The Software Protection Key is a piece of hardware that attaches to your computer through either a Parallel Port or USB Port and acts as a software package's copy protection. You must have the key attached to your computer when you start the software to enable the software's full features. The key is also checked for at key times during a program's execution and many operations will abort if a key is absent that was present when the software was started. You require one Software Protection Key for each computer that will run the software.

Both versions of Video Savant can be run in Demo mode without a software key to allow you to evaluate the features of the software before you purchase. When in Demo mode you can capture images to system memory and execute each processing library once, but you cannot save images or run Video Savant SDK applications. Streams 5 can be started in Viewer mode without a software protection key. In Viewer mode you can do anything except create devices, create scenes, create movies, import files or acquire data in any way (live, snap or record). Operations that you can do include but are not limited to export scenes, archive scenes, playback, run SDK applications and run Python Scripts.

There are a number of reasons that Video Savant might fail to detect the Software Protection Key. The most common is that the Sentinel System Driver has not been installed. The Sentinel System Driver is a kernel mode windows driver that is provided by the company that manufactures the Software Protection Key. This driver must be installed for Video Savant to be able to detect the Software Protection Key. This problem can also occur when the Sentinel System Driver is not correctly configured to detect a Parallel Port Software Protection Key.

There are a number of reasons that Streams might fail to detect the Software Protection Key. The most common is that the Sentinel System Driver has not been installed. The Sentinel System Driver is a kernel mode windows driver that is provided by the company that manufactures the Software Protection Key. This driver must be installed for Streams to be able to detect the Software Protection Key. This problem can also occur when the Sentinel System Driver is not correctly configured to detect a Parallel Port Software Protection Key.

The Sentinel System Driver is included on the CDs included with all IO Industries software products. You can install the Sentinel System Driver from any Video Savant 3.0, Video Savant 4.0 or Streams 5 CD that you have received from IO Industries inc. Future products from IO Industries will also likely include the Sentinel System Driver. IO Industries Products before Video Savant 3.0 may include an older version of the Sentinel System Driver that does not support the newer Software Protection Keys used for Video Savant 4.0 and Streams 5. You can also download the latest version of the Sentinel System Driver from http://www.setupmykey.com. The download is called the "Sentinel Protection Installer".

SafeNet provides an extremely useful utility known as the Sentinel SuperPro Medic. This can be downloaded from http://www.setupmykey.com and can be used to check if the key is detected by the Sentinel System Driver. If the SuperPro Medic fails to detect the key then Video Savant and Streams will not be able to detect the key either.

Use a program called SetupSysDriver.exe. This program is located in the "C:\Program Files\Common Files\SafeNet Sentinel\Sentinel System Driver" directory in the version of the Sentinel System Driver that was current at the time that this FAQ was written, although this file has been known to move around. Run this program and click "Configure Driver". The configuration window that appears will contain one or more lines describing settings used to access the key. the Parallel Port settings should have Physical Address 0x378, Port Type ECP, Bus Number 0, Address Space I/O and Use: Yes. This line is sometimes left out during installation of the Sentinel System Driver and sometimes must be added manually for applications to be able to see a Parallel Port Software Protection Key. The Physical Address 0x378 is the default address for LPT1. If you have the key attached to a parallel port at a different address (such as through an add-in card) or if your motherboard has a different address for LPT1 then you will need to change this entry to contain the correct address. The Ports section on the Windows Device Manager contains information on the address of each Parallel port in the system. The device manager can be found on the Hardware tab of the System icon in the Windows Control Panel.

Sometimes accidents happen, espeically when computers are being moved around. Sometimes the keys get smashed against a wall while being taken out of an aircraft or crushed in an elevator door. When this happens you must contact IO Industries and we will arrange an RMA to have the shattered remains of your Software Protection Key returned to us. Once it has arrived at our office we will issue you a new Software Protection Key for a small replacement fee. Do not contact SafeNet, they cannot provide you with a key that will work with Video Savant or Streams. We recommend that you always remove Software Protection Keys from the computer when moving the system around as these keys are fragile. If you suspect that your Software Protection Key has sustained damage to its electronics please contact our technical support department, we will help you check to see if the key is still working and arrange to have it returned if necessary. Never return any item to IO Industries without an RMA.

No. Each IO Industries product has a different key. If you wish to upgrade from one IO Industries product to another you must contact our Sales Department to purchase an upgrade. When an upgrade is purchased we require the key from the old product to be returned before the key for the new product is issued.

Video Savant 3.0 and Video Savant 4.0 are two different programs and while their SDKs functions are similar, each program has it's own version of vssdkvc.lib that is specific to the version of Video Savant that it is built for and there are differences in the header files. When porting an SDK application from Video Savant 3.0 to Video Savant 4.0 you must rebuild it with the Video Savant 4.0 header files and libraries. Some function prototypes may have changed, some functions will have been renamed and some functions may have been removed if they are no longer appropriate for Video Savant 4.0. When you rebuild your Video Savant 3.0 SDK application with the Video Savant 4.0 SDK it is recommended that you look up the Video Savant 4.0 documentation for each Video Savant SDK function that you use in your application.

Video Savant 3.0 Stream Filters are not the same as Video Savant 4.0 Stream Filters. While many of the functions that you define have the same names and parameters, the calling conventions are different. When porting a Stream Filter from Video Savant 3.0 to Video Savant 4.0 you must update the definition of every Stream Filter function from the Video Savant 3.0 definition to the Video Savant 4.0 definition. In all cases this includes adding the PASCAL keyword to the function definition, but many other functions have changed. You should look in the Video Savant SDK Guide for the updated definition of each function that you define in your Stream Filter.

The Video Savant 3.0 SDK includes a library to build SDK applications with Borland C++ Version 5.01, but not Borland C++ Builder. Borland C++ Builder is not related to the older Borland C++ and libraries built with Borland C++ cannot be linked to Borland C++ Builder applications. The library file "vssdkbc.lib" is for Borland C++, not for Borland C++ Builder. If you need to build a Borland C++ Builder application for Video Savant 3.0 contact IO Industries to obtain the library file vssdkbcb.lib. The Video Savant SDK Library vssdkbcb.lib exists for Video Savant 4.0 as well, but the Borland C++ library vssdkbc.lib does not.

Video Savant SDK allows developers to access the native functionality of Video Savant. Consult DEVGUIDE.pdf for the SDK's documentation. General Control calls may be made directly to the DVR Express driver allow SDK developers to call functions not supported by the SDK, however the format of these calls is complicated and generally undocumented. The DVR Express libraries (clfc_sfgenctrl and cl160_sfgenctrl) provide developer-friendly routines to access features not supported by the Video Savant SDK alone. These features are primarily hardware-specific functions such as signal management, and multi-camera support which is added exclusively by the driver. Consult CL160_sfgenctrl.pdf or CLFC SFGenCtrl Library.pdf for documentation. Most of the functions accessible through the libraries are implemented by making general control calls directly to the driver.