Store 
| Products & Services | Solutions | Academia | Support | User Community | Company |
 |
Download Product Updates | | |  |
Get Pricing | | | |
Trial Software |
| Documentation → Image Acquisition Toolbox |
| Products & Services | Solutions | Academia | Support | User Community | Company |
|
Download Product Updates | | | |
Get Pricing | | | |
Trial Software |
| Documentation → Image Acquisition Toolbox |
| Contents | Index |
| Learn more about Image Acquisition Toolbox |
This table summarizes what's new in Version 1.6 (R14+):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
| Yes Details below | No | Yes Details below | No |
New features and changes introduced in this version are:
The Image Acquisition Toolbox software now includes a Simulink block library, called the Image Acquisition Block Library. The block library contains one block: the Video Input block. You can use this block to bring live video data into a simulation.
To open the Image Acquisition Block Library, enter
imaqlib
at the MATLAB prompt. MATLAB displays the contents of the block library in a separate window:
The DCAM adaptor now supports properties that let you specify the value of a property as an absolute value, if the device supports that capability for a particular feature.
As defined by the IIDC DCAM specification, the values specified for properties can be interpreted as either relative or absolute. Relative values only have meaning in relation to a device-specific reference point. For example, if you set the shutter speed property to 4000, this value might be interpreted as 4000 seconds for one device, but 4000 milliseconds for another device. Previously, the DCAM adaptor device-specific properties only supported relative values.
To provide more precise control, the IIDC DCAM specification also defines absolute values, where the units are specified as part of the definition. For example, the DCAM specification defines the units for shutter speed property as seconds. So, if you specify a value of 0.10032 for this property, any DCAM device that supports absolute values would interpret the value as 100.32 milliseconds. To find out the units used with a feature that supports absolute values, see Appendix B of the IIDC 1394-based DCAM specification or check the documentation that came with your device.
To support both absolute and relative values, the DCAM adaptor now provides additional device-specific properties. If a device supports absolute values for a particular feature, the DCAM adaptor creates a property, using the same feature name as the relative property but with the word "Absolute" appended to it. For example, if a device supports both relative and absolute values for shutter speed, the DCAM adaptor creates properties named Shutter and ShutterAbsolute.
When it creates an absolute value property, the DCAM adaptor also creates a property to control the type of value the device uses. This property has the same name as the feature with the word "Control" appended to it. For example, if the DCAM adaptor created the ShutterAbsolute property, it also creates a ShutterControl property.
If you set either the relative or absolute properties, the corresponding mode property is set to 'manual'. For example, if you set the ShutterAbsolute property, the value of the ShutterMode property changes to 'manual'. Setting the control property has no effect on the mode property.
Because of a number of enhancements to the way that the toolbox handles video frames, you might notice increased performance in the following areas:
Faster acquisition with the getdata, peekdata, and getsnapshot functions.
Previewing should consume less CPU overhead.
Frame handling during acquisition should be faster.
Note The actual performance improvement achieved depends on factors such as video format, resolution, and CPU speed. |
This release includes the following major bug fix:
For long acquisitions, the metadata information reported from getdata was sometimes incorrect. This included reporting the wrong values for the AbsTime and FrameNumber fields of the getdata metadata structure. This has been fixed.
The following are some changes from previous releases:
The FieldStart property for the Coreco PC-Vision device has been removed. To specify which field the device uses as the first field for an interlaced video signal, use the StartingField property.
The way the toolbox determines the default value of device-specific properties for Matrox devices has changed. In some cases, the initial value of the property at object creation time (and the default value returned by the propinfo function) might be different than what was returned in previous releases. To ensure that properties that are important to your application have the value you expect, you should explicitly set them. Do not depend on the default value.
See the issues described in Known Software and Documentation Issues for Version 1.8.
 | Version 1.7 (R14SP1) Image Acquisition Toolbox Software | Version 1.5 (R14) Image Acquisition Toolbox Software |  |
Includes the most popular MATLAB recorded presentations with Q&A sessions led by MATLAB experts.
| © 1984-2009- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
