1.15 DirectShow interface
75
if
( SUCCEEDED( hr ) )
{
const
int
max_prop = 500;
MVProperty props[max_prop];
unsigned int
propCnt = ScanAllProperties( gcap.pVSC, props, max_prop );
// if successful we get a list something like this otherwise propCnt = 0
//...
//props[0x40]
{propertyName="ImagingSubsystem/Setting/Base/Camera/AutoExposeControl" value={s=
"Off" } ...
//props[0x41]
{propertyName="ImagingSubsystem/Setting/Base/Camera/AutoGainControl" value={s= "Off"
} ...
//props[0x42]
{propertyName="ImagingSubsystem/Setting/Base/Camera/BinningMode" value={s=
"Off" }
...
//props[0x43]
{propertyName="ImagingSubsystem/Setting/Base/Camera/ExposeMode" value={s= "Standard"
} ...
//props[0x44]
{propertyName="ImagingSubsystem/Setting/Base/Camera/Expose_us" value={i=0xea60 } ...
//props[0x45]
{propertyName="ImagingSubsystem/Setting/Base/Camera/FlashMode" value={s= "Off" } ...
//props[0x46]
{propertyName="ImagingSubsystem/Setting/Base/Camera/FrameDelay_us" value={i=0x0 }
...
//props[0x47]
{propertyName="ImagingSubsystem/Setting/Base/Camera/Gain_dB" value={ f=0.0 } ...
//...
// it is strongly recommended to work only with the propertyNames and not with the index from the
list.
// The driver for our cameras and grabber will always return same propertyNames.
MVProperty*
gain_prop = GetProperty( props, propCnt,
"ImagingSubsystem/Setting/Base/Camera/Gain_dB"
);
_WRITE_FLOAT_PROPERTY( ks_prop, gain_prop, gain );
MVProperty*
bayer_prop = GetProperty( props, propCnt,
"ImagingSubsystem/Setting/Base/ImageProcessing/ColorProcessing"
);
// The property ColorProcessing is from type stringArray. Please have a look to the stringArray for
the different strings.
_WRITE_STRING_PROPERTY( ks_prop, bayer_prop, bBayerOFF ?
"Raw"
:
"Auto"
);
// delete the stringarray
_DELETE_POINTER_ARRAY( props, propCnt );
ks_prop->Release();
}
// ...
}
1.15.2
Logging
The DirectShow_acquire logging procedure is equal to the logging of the MATRIX VISION products which uses
mvIMPACT Acquire. The log output itself is based on
XML
.
If you want more information about the logging please have a look at the
Logging
chapter of the respective
"mv
←
-
IMPACT Acquire API"
manual or read on how to configure the log-output using
mvDeviceConfigure
in the
"mv
←
-
IMPACT Acquire GUI Applications"
manual.
1.15.3
Setting up devices for DirectShow usage
In order to be able to access a device through the mvIMPACT Acquire driver stack from an application through
DirectShow a registration procedure is needed. This can either be done using mvDeviceConfigure or by a command
line tool that is part of the Windows operating system.
Note
Please be sure to register the MV device for DirectShow with a matching version of
mvDeviceConfigure
.
I.e. if you have installed the 32-bit version of the VLC Media Player, Virtual Dub, etc., you have to
register devices with the 32-bit version of mvDeviceConfigure (
"C:\Program Files\MATRIX VISION\mv
←
-
IMPACT Acquire\bin"
, the 64-bit version resides in
"C:\Program Files\MATRIX VISION\mvIMPACT Ac-
quire\bin\x64"
)!
MATRIX VISION GmbH
Содержание MATRIX VISION mvBlueFOX Series
Страница 1: ...mvBlueFOX Technical Manual English Version 3 02...
Страница 2: ......
Страница 8: ......
Страница 19: ...1 6 Important Information 11 MATRIX VISION GmbH...
Страница 20: ...12 MATRIX VISION GmbH...
Страница 21: ...1 6 Important Information 13 1 6 3 Legal notice 1 6 3 1 For customers in the U S A Class B MATRIX VISION GmbH...
Страница 238: ...230 MATRIX VISION GmbH...