Version 3.5 (R2010a) Image Acquisition Toolbox Software :: Image Acquisition Toolbox Release Notes (Image Acquisition Toolbox )

Learn more about Image Acquisition Toolbox

Version 3.5 (R2010a) Image Acquisition Toolbox Software

This table summarizes what's new in Version 3.5 (R2010a):

New Features and Changes	Version Compatibility Considerations	Fixed Bugs and Known Problems	Related Documentation at Web Site
Yes Details below	Yes Summary	Bug Reports Includes fixes	Printable Release Notes: PDF Current product documentation

New Features and Changes

Version Compatibility Considerations

Fixed Bugs and Known Problems

Session Log in the Image Acquisition Tool

The new session log dynamically records every action you perform in the Image Acquisition Tool. The corresponding command-line functionality for actions on a videoinput object or videosource object is reflected in the log. The title displays the name of the device, as shown in the Hardware Browser.

You can save the contents of the session log to a MATLAB code file or copy it to another source. For more information, see Saving and Copying the Session Log.

Additional Export Location in the Image Acquisition Tool

You can now export data to an .avi file after it has been acquired. Previously you could export data to a MAT-file, the MATLAB Workspace, or a tool in the Image Processing Toolbox™ (Image Tool, Image File, or Movie Player). Now you can also export to an .avi file and set .avi file options, such as compression, on the export.

For more information, see Exporting Data.

Support for Additional DCAM Trigger Modes

You can now use all trigger modes and all trigger inputs supported by DCAM cameras, as of R2010a. Previous toolbox releases supported only trigger mode 0. Support for the additional trigger modes and inputs will not affect any existing code you may be using.

For information on the additional trigger modes, including use of parameters, see Setting DCAM-Specific Trigger Modes.

Disk Logging on Windows Vista 64-bit Platforms

When using Windows Vista™ 64-bit platforms, if you used disk logging to an .avi file, you could see a crash if there was no colormap set. With other versions of Windows^®, you could see corrupted data.

Compatibility Considerations

Now if you use disk logging to an .avi file without setting a colormap, you will get a warning and a default grayscale colormap will be set in order to avoid this problem.

`WhiteReference` Property Ignored for Matrox Devices

In previous versions of the Matrox^® adaptor, the properties WhiteReference, BlackReference, and InputGain could all be used. Starting in R2010a, the WhiteReference property will be ignored.

This applies to the following devices:

Matrox Helios XA
Matrox Odyssey XA
Matrox Solios XA

Compatibility Considerations

The first phase of deprecating this property is that the WhiteReference property will be ignored. You should use the BlackReference property and the InputGain property. You will receive a warning if you use the WhiteReference property and it will be ignored. The warning specifies that you can use BlackReference property and the InputGain property together.

The second phase of the deprecation, in a future release, is that you will receive a error. The third stage, in a future release, will be removal of the property.