API_HARDTIMEOUT_ERR can occur when ImageGear has taken too long to process your document. This tends to happen when the OCR process is spending too much time on things it thinks are characters (very common in bitonal documents), such as, scan artifacts in damaged documents, visual marks (e.g, the distortion of a camera picture of a computer monitor), or other marks that the recognition engine would waste time on because it thinks they’re letters. See the bottom of this page for an example.
For scanned bitonal documents, running a
Despeckle operation on the page can help reduce the amount of noise obstructing the OCR process.
ImGearRasterPage igRasterPage = p.Rasterize(1, 300, 300);
ImGearRasterProcessing.Despeckle(igRasterPage, 3, 3);
Also, if converting documents to bitonal is part of the document process, ImageGear .NET has reducing methods that may make for a less damaged document, such as our
Reduce method with configurable parameters. Alternately, the color document could be OCR’d instead with likely better results.
In the past, some users have found some success adjusting some of the time-based parameters in the recognition engine.
ImGearRecTradeoff and DecompMethod can be modified to trade-off accuracy for speed during the actual OCR process, and Locate can be used to identify existing text before recognition.