![Matrix Vision mvHYPERION-32R16 Technical Manual Download Page 75](http://html1.mh-extra.com/html/matrix-vision/mvhyperion-32r16/mvhyperion-32r16_technical-manual_1741405075.webp)
9.1
wxPropView
71
Figure 27: wxPropView - Call refresh
9.1.2.4
Working with camera descriptions
Certain capture device (e.g. frame grabber) can process data from a wide range of imaging devices (e.g. cameras).
However, in order to interpret the incoming data from an imaging device correctly, the capture device needs to be
given a certain amount of information about the structure of the video signal.
The
"mvIMPACT Acquire"
interface addresses this necessity by the introduction of so called
"camera descrip-
tions"
. A
"camera description"
is a certain set of parameters that should enable the capture device to cope with
the incoming image data to reconstruct a correct image from the imaging device in the memory of the host system.
For instance, this information may contain information whether the image is transmitted as a whole or if it's transmit-
ted as individual blocks (e.g. when dealing with interlaced cameras) that need to be reconstructed in a certain way
to form the complete image.
Each capture device will support different sets of parameters. For example some capture devices will only be able to
capture image data from standard video source such as a
PAL
or
NTSC
compliant camera, while others might only
be capable to acquire data from digital image source such as
CameraLink®
compliant cameras. To reflect these
device specific capabilities
"camera descriptions"
have been grouped into different base classes. See e.g.
mv
←
-
IMPACT::acquire::CameraDescriptionStandard
to find out how the basic structure of these objects look. Which
basic
"camera description"
classes are supported by an individual device can be seen directly after the device
has been initialised by looking in the
"camera description"
list. By default this list will contain one description for
each supported basic family:
MATRIX VISION GmbH