You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CaptureVisionRouter module is defined in the namespace `Dynamsoft.CVR`. It consists of the classes `CaptureVisionRouterModule`, `CaptureVisionRouter`, `CapturedResultReceiver`, `IntermediateResultReceiver`, `IntermediateResultManager` and a few interfaces and enumerations.
Copy file name to clipboardExpand all lines: programming/javascript/api-reference/capture-vision-router/interfaces/simplified-capture-vision-settings.md
Represents the minimum time interval (in milliseconds) that must elapse before the next image capture operation can be initiated. Setting a larger value for this property will introduce a delay between image captures, while setting a smaller value allows for more frequent captures. It can be used to reduce the computational frequency, which can effectively lower energy consumption.
99
+
Defines the minimum time interval in milliseconds that controls the time gap between consecutive image captures. It's a crucial parameter for managing the balance between capture frequency and computational load. Here's how it works:
100
+
101
+
1.**Adjustable Time Interval**: The value of `minImageCaptureInterval` dictates the minimum duration that should pass before another image capture can occur. A higher value means less frequent captures, leading to reduced computational demands and energy usage. Conversely, a lower value allows for more rapid image capturing.
102
+
103
+
2.**Special Values and Their Functions**:
104
+
105
+
* -1: Setting this value indicates that the image source should wait until the `CaptureVisionRouter` object has completely processed the current image before capturing the next one. This ensures there's a processing break between two successive images.
106
+
* 0 (Default Setting): This value signifies that the image source should prepare the next image for capture immediately. As soon as the `CaptureVisionRouter` finishes processing an image, it can straightaway start with the next, ensuring no delay in processing.
`templateName`(optional): The name of the template to use for capturing. If not specified, the default template (`EnumPresetTemplate.PT_DEFAULT`) will be used.
329
+
`templateName`: specifies a "CaptureVisionTemplate" to use. If not specified, "Default" is used. There are two types of CaptureVisionTemplates: the [built-in ones](./built-in-templates.md) which come with the SDK and the custom ones that get initialized when the user calls [initSettings](./settings.md#initsettings). Please be aware that the [built-in CaptureVisionTemplates](./built-in-templates.md)will be overwritten should the user calls [initSettings](./settings.md#initsettings) and pass his own settings.
|[setInput()](#setinput)| Sets up an image source to provide images for continuous processing. |
17
+
|[getInput()](#getinput)| Returns the image source object. |
18
18
|[addImageSourceStateListener()](#addimagesourcestatelistener)| Adds an `ImageSourceStateListener` object that listens to state changes of the image source. |
19
19
|[removeImageSourceStateListener()](#removeimagesourcestatelistener)| Removes the specified `ImageSourceStateListener` object. |
20
20
|[addResultReceiver()](#addresultreceiver)| Adds a `CapturedResultReceiver` object as the receiver of captured results. |
21
21
|[removeResultReceiver()](#removeresultreceiver)| Removes the specified `CapturedResultReceiver` object. |
22
22
|[addResultFilter()](#addresultfilter)| Adds a `CapturedResultFilter` object to filter non-essential results. |
23
23
|[removeResultFilter()](#removeresultfilter)| Removes the specified `CapturedResultFilter` object. |
24
-
|[startCapturing()](#startcapturing)| Starts to process images consecutively. |
25
-
|[stopCapturing()](#stopcapturing)| Stops the consecutive process. |
24
+
|[startCapturing()](#startcapturing)| Starts to process images consecutively. |
25
+
|[stopCapturing()](#stopcapturing)| Stops the consecutive process. |
26
26
27
27
<!--
28
28
| [addCaptureStateListener()](#addcapturestatelistener) | Adds a CaptureStateListener object to listen to the state changes of the capture process. |
`templateName`(optional): The name of the template to use for capturing. If not specified, the default template will be used.
333
+
`templateName`: specifies a "CaptureVisionTemplate" to use. If not specified, "Default" is used. There are two types of CaptureVisionTemplates: the [built-in ones](./built-in-templates.md) which come with the SDK and the custom ones that get initialized when the user calls [initSettings](./settings.md#initsettings). Please be aware that the [built-in CaptureVisionTemplates](./built-in-templates.md)will be overwritten should the user calls [initSettings](./settings.md#initsettings) and pass his own settings.
`imageOrFile`: specifies the image or file to be processed. It can be the image itself in the form of `DSImageData`, the path of the image/file or the file itself in the form of `blob`, `HTMLImageElement` or `HTMLCanvasElement`.
31
31
32
-
`templateName`: specifies a [CaptureVisionTemplate]({{site.parameterFile}}capture-vision-template.html) to use. If not specified, the default one is used.
32
+
`templateName`: specifies a "CaptureVisionTemplate" to use. If not specified, "Default" is used. There are two types of CaptureVisionTemplates: the [built-in ones](./built-in-templates.md) which come with the SDK and the custom ones that get initialized when the user calls [initSettings](./settings.md#initsettings). Please be aware that the [built-in CaptureVisionTemplates](./built-in-templates.md) will be overwritten should the user calls [initSettings](./settings.md#initsettings) and pass his own settings.
0 commit comments