We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

OCR Fails after 12 minutes on 2 page TIF


Running a test with your OCR Engine using a TIF file that has been part of our test suite for 9 years. (I can provide other TIF files that fail, but those take even longer.)

Given the attached code and TIF file (2 pages, 300 dpi, 1 bpp), the OCR engine churns for just about 12 minutes and then throws an exception. (see below)

At the moment, we have returned to MODI.OCR (deprecated by Microsoft, but still available). It does this files in well under a minute - about 20 seconds.

Is there a problem with our code, or do we just need to wait for your OCR engine to be more mature?

The exception info:
Aspose.OCR.OcrException: Alphabet of english language doesn't contains symbol:
at ‼.☺.GetClassName(Char ch)
at ¶.♫.↕(☼[] fuzzyWord)
at ¶.♫.☺( ocrResult)
at ¶.♣.‼(‼ bitmap, ♦ fontCollection, § blob)
at ¶.♣.↕(‼ bitmap, ♦ fontCollection, § blob)
at ¶.♣.‼(‼ pBitmap)
at ¶.♣.↕()
at ¶.♣.↕(‼ bitmap)
at Aspose.OCR.OcrEngine.↕()
at Aspose.OCR.OcrEngine.Process()
at AsposeOCRProblem.Module1.Main()

Hi there,

Sorry for the delayed response. While testing the scenario, I’ve manged to reproduce the issue and logged issue as OCR-33451 for further investigation and resolution. We’ll keep you updated about the issue progress via this forum thread.

Moreover, currently Aspose.OCR capabilities are not up to mark. Our development team is working hard to improve the performance and capabilities of the product. For the purpose some new algorithms are under testing for improvement of supported fonts recognition accuracy and performance.

Sorry for the inconvenience faced.

Best Regards,

Hi Stan,

Just to bring in your knowledge that we have closed the ticket logged earlier as OCR-33491. Reason being, we were unable to reproduce the said problem with latest release at that moment. If you are still interested in Aspose.OCR APIs, we would request you to please try the latest revision of Aspose.OCR for .NET 2.0.0.

The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.