DualStream Imaging

At this time, the iNSIGHT 20 and iNSIGHT 30 support the dual stream.

Test the Boolean property, HardwareConfig.DualStreamCapable. You can do this at any time after the scanner is detected, for example at the ScannerFound or ScannerSearchComplete events. You can also test the boolean property just prior to scanning or within an event handler.

Yes. You can capture color-dropped grayscale (or color-dropped bi-tone) images from the primary channel and either full color (or non-dropped bi-tone) images from the dual stream.

Yes, but only if you are writing to a TIFF file. The TIFF file format supports multiple images in the same file.

Yes. The same is true for images on the primary channel as well.

Yes. If you are absolutely new to ScanToolsLink SDK, start with the QuickStart Desktop sample which shows you how to detect and configure your scanner.

Follow this with the QuickStart Imaging sample, which shows how to capture a grayscale image on the primary channel.

Then look at the QuickStart DualStream sample, which illustrates how to confirm that your scanner can do dual stream, configure the dual stream mode for true color, and finally capture a color image. These samples are written in Vb.Net and available for the Visual Studio 2010 environment.

Yes. There are only a few new object model elements exclusive to dual stream. Apart from setting up the dual stream mode, capturing images on the dual stream is no different than what you do for the primary channel. Compare the code in the QuickStart Imaging and QuickStart DualStream samples.

The earliest is SheetAcquired, the latest is SheetComplete. You can also capture images at the ScanError event. In any case, you should test ClipHelper.TopImageExists and ClipHelper.BottomImageExists to confirm that an image is available.

Dual stream images already have the form background at capture time. As a result, ClipHelper.CombineWithForm is irrelevant for dual stream, and the same applies to Clip.CombineWithForm.

Yes. The scanning API supports the COM IStream interface. In .Net, the unmanaged IStream interface is defined in the namespace System.Runtime. InteropServices.ComTypes and the roughly equivalent managed code Stream interface is defined in the namespace System.IO.

To make IStream work with Stream:

1. Create a StreamWrapper class that inherits IStream. Its constructor accepts the Stream to be wrapped.
2. Implement the methods of the IStream interface by delegating to similar methods of the wrapped Stream object. When invoking a ScanTools Plus Link method such as ClipHelper.WriteClipToStream, pass a StreamWrapper instance.

Likewise, to consume an IStream returned by a ScanTools Plus Link method such as ClipHelper.GetClipAsStream , create an IStreamWrapper class that inherits Stream. Its constructor takes an IStream as the argument. Implement methods of the Stream interface by making suitable calls to the wrapped IStream. The QuickStart StreamIO sample illustrates how to accomplish the preceding suggestions.

At this time, while we have comprehensive JavaScript support for OMR, we have not exposed the imaging subset of the ScanTools Plus Link API to JavaScript support. If you wish to scan and upload images to a web service, you should write a standard Windows program.