VeriLook Surveillance SDK
Face identification for video surveillance
applications
Click
Here
to
download
the
full
VeriLook
Surveillance
SDK
brochure
as
a
.pdf
document
VeriLook Surveillance SDK is intended for developing biometric
software that performs face identification using live video streams
from high-resolution digital surveillance cameras. The SDK is based on
VeriLook facial recognition technology and is
used for passive biometric identification – when
passers-by do not make any efforts to be recognized. List of possible
uses includes law enforcement, security, attendance control, visitor
counting and other commercial applications.
The VeriLook Surveillance SDK allows to create applications for
Microsoft Windows and Linux platforms.
Advantages of VeriLook
- Real time face detection, template extraction and matching
against watchlist database.
- Simultaneous multiple face tracking in live video.
- Automatic operation allows to log and report face appearance,
match and dissapearance events, as well as to enroll new faces from
video stream and add them to watchlist automatically.
- Available as multiplatform SDK that supports multiple programming
languages.
- Reasonable prices, flexible licensing and free customer support.
VeriLook Surveillance Technology and SDK
- VeriLook Surveillance 1.1 SDK contents. The SDK
includes one VeriLook Surveillance component. A Camera Manager
library is included for image capture from cameras. Programming
tutorials are included. Components of the SDK are listed with supported
platforms… Read more
- System requirements. VeriLook-Surveillance-based
software can be run on computers with x86 multi-core processors (at
least 2.66 GHz Core2 Quad processor recommended). Windows
and
Linux platforms are supported. A high-resolution surveillance
camera required to capture face images… Read more
- Technical specifications. VeriLook Surveillance
SDK performs real-time face detection, tracking,
enrollment and matching… Read more
- Download. VeriLook Surveillance brochure, algorithm demo application and
VeriLook Surveillance 30-day SDK Trial
are available for downloading.
Back to top of this page
Contents of VeriLook Surveillance SDK
VeriLook Surveillance 1.1 SDK is based on the VeriLook Surveillance 1.1
technology that is specially designed for integrating biometric facial
recognition into video surveillance systems. Face templates created
with VeriLook Surveillance SDK are fully compatible with VeriLook
3.2/3.3/4.0 SDK and MegaMatcher SDK multi-biometric technology.
VeriLook Surveillance 1.1 SDK includes Camera Manager library for
Microsoft Windows and Linux that allows to perform simultaneous
capture
from multiple cameras.
| Components |
Microsoft Windows
(32 & 64 bit) |
Linux
(32 & 64 bit) |
| • VeriLook Surveillance 1.1 component |
1 license |
| • Camera manager library |
+ |
+ |
| Programming
samples |
| • C++ |
+ |
+ |
| • C# |
+ |
|
| • Visual Basic .NET |
+ |
|
| Programming
tutorials |
| • C |
+ |
+ |
| • C# |
+ |
|
| Documentation |
| • VeriLook Surveillance 1.1 SDK
documentation |
+ |
VeriLook Surveillance Component
The VeriLook Surveillance Component performs real-time detection and
tracking of all near-frontal faces from live video stream. The
component is able to track multiple faces simultaneously and match them
with faces from internal database (i.e. a watch-list of suspects or a
list of company employees). New faces may be automatically enrolled to
the database.
Camera Manager library
Camera Manager library works under Microsoft Windows and Linux and
provides functionality for working with cameras. The library supports a
range of high-resolution digital surveillance cameras and other cameras
that provide DirectShow interface for Windows platform, or Video4Linux
interface for Linux platform.
The list of supported cameras is available below in the System Requirements section.
A video file can be also used as a data source for
VeriLook Surveillance. The input from the file is processed as coming
from a virtual camera, thus the video is processed in real-time.
Back to top of this page
VeriLook Surveillance SDK System Requirements
- At least Intel Core2 CPU with 4 cores
running at 2.66 GHz or equivalent multi-core
processor from other manufacturer
- At least 1 GB of free RAM
- A high-resolution digital camera. The camera
resolution may vary depending on the actual application. The
recommended resolution is about 1 Megapixel, as processing video from
cameras with higher resolution will require more free RAM and more
powerful processor to keep the acceptable frame rate.
These supported cameras are suitable for using with VeriLook
Surveillance 1.1 SDK:
- Axis M1114 camera (Microsoft Windows only)
- Cisco 4500 IP camera (Microsoft Windows and
Linux)
- Mobotix DualNight M12 IP camera (Microsoft
Windows and Linux)
- PiXORD N606 camera (Microsoft Windows and
Linux)
- Prosilica GigE Vision camera (Microsoft
Windows and Linux)
- Any other high-resolution digital camera that is accessible
using:
- DirectShow interface for Microsoft
Windows platform;
- Video4Linux interface for Linux platform.
- Microsoft Windows specific:
- Microsoft Windows 2000/XP/2003/Vista/7
- Microsoft DirectX 9.0 or later
- Microsoft .NET Framework 2.0 or later
- Linux specific:
- Linux (based on glibc 2.5 or newer)
- Video4linux
Back to top of this page
Technical Specifications
All specifications are given for a PC
with Intel Core2 processor (with 4 cores) running at 2.66 GHz and one
camera connected to the PC.
VeriLook Surveillance has certain tolerance to face
posture that assures face detection and tracking:
- head roll (tilt) – ±180 degrees
(configurable);
±15 degrees recommended as it is the
fastest setting which is usually sufficient for most near-frontal face
images.
- head pitch (nod) – ±15 degrees from
frontal position.
- head yaw (bobble) – ±15 degrees from
frontal position.
| VeriLook
Surveillance
1.1 algorithm technical specifications |
| Minimal frame size |
640 x 480 pixels |
| Minimal face size for face recognition |
40 pixels between the eyes |
| Frame rate when tracking up to 3 faces |
More than 10 frames per second |
| Watch-list database matching time |
Less than 1 second* |
| Maximum watch-list database size |
Limited by amount of free RAM |
* up
to 50,000 records in the database; larger database yelds slower
response time.
Back to top of this page