Provides support for the one shot "fire and forget" approach to OCR suitable for unattended recognition.
You can access the instance of the IOcrAutoRecognizeManager used by an IOcrEngine through the IOcrEngine.AutoRecognizeManager property.
The members of this interface will let you create a document from an image file on disk with optional progress and status monitors.
You can use the Run methods to convert in one line of code an image on disk to a final document with any of the document formats supported by this IOcrEngine.
You can also create jobs using the CreateJob method and then run them synchronously through RunJob or asynchronously through RunJobAsync.
The IOcrAutoRecognizeManager interface also has the following options to use with the Run, RunJob and RunJobAsync methods:
Member | Description |
---|---|
PreprocessPageCommands | Holds an array of OcrAutoPreprocessPageCommand items to control what auto-preprocess operation to perform on each page document prior to recognition. |
JobErrorMode | Ability to resume on none critical errors. For example, if a source document has a page that could not be recognized. The offending page will be added to the final document as a graphics images and recognition will continue to the next page. |
JobStarted, JobProgress, JobOperation and JobCompleted events | Events to track when both synchronous and asynchronous jobs has started, being run and completed. |
AbortAllJobs | Aborts all running and pending jobs. |
EnableTrace | Output debug messages to the standard .NET trace listeners. |
MaximumPagesBeforeLtd |
Important: not used by the LEADTOOLS Advantage OCR engine. Add support for converting a document with unlimited number of pages if the engine does not support it. An OCR recognition operation on a document that contains a large amount of pages (10 and more) might result in an out of memory error. All of the LEADTOOLS OCR engines supports saving the intermediate recognition results to a temporary LTD file (DocumentFormat.LTD). The result of subsequent pages will be appended to this temporary file. When all the pages of the document have been recognized, the engine will convert the temporary LTD file to the desired output format. The LEADTOOLS Advantage OCR engine handles this operation internally by using a file-based document and does not load more than one page in memory at a time and will not use the value of MaximumPagesBeforeLtd. For the other engines, the MaximumPagesBeforeLtd property defines the maximum number of pages processed as a whole. For example, if the original document has 20 pages and the value of this property is 8, the engine will recognize the first 8 pages and saves the result to a temporary file, recognizes the second 8 pages and append the results, and finally, recognize the last 4 pages and convert the temporary document into the final format. |
MaximumThreadsPerJob |
Maximum number of threads to use per job. You can instruct IOcrAutoRecognizeManager to use all available machine CPUs/cores when recognizing a document. This will greatly reduce the time required to finish the OCR operation. The LEADTOOLS Advantage OCR engine uses the system thread pool and does not require a set number of threads. A value of 1 will disable threading and any other value will be treated as "use multi-threading". |
Some OCR engine types support creating multi-threaded documents by creating one IOcrEngine and multiple IOcrDocument or IOcrAutoRecognizeJob each in its own dedicated threads. For more information, refer to Multi-Threading with LEADTOOLS OCR.
This example will convert TIF files in a source folder to PDF in a destination folder
For an example on how to run multiple jobs simultaneously in multiple threads with synchronization and aborting support, refer to RunJob.
Products |
Support |
Feedback: IOcrAutoRecognizeManager Interface - Leadtools.Forms.Ocr |
Introduction |
Help Version 19.0.2017.6.6
|