Hi Asad,
Thank you for sharing your template for investigation.
I have thoroughly checked your samples against the template. Please note, one of the samples namely
Document+(33).png cannot be used for OMR scanning because the markers are not filled, instead the markers are circled. Such markers are not to be considered as filled/marked, and therefore cannot be recognized even with lowest
FillThreshold possible. All other samples can be processed easily by setting the low FillThreshold such as some value below than 0.5. However, you must keep a note that with such a low FillThreshold, even a partially filled marker will be considered as filled. Also if the marker has exceeded its boundaries and seeped to the neighboring marker then the second marker will also be recognized as filled. So caution is advised while setting too low FillThreshold.
Hi Asad,
With the release of Aspose.OCR for .NET 2.4.0, we have merged the Aspose.OCR & Aspose.OMR namespaces in one assembly. However, this change should not effect your existing application because all the classes relevant to OMR features are still present under the Aspose.OMR namespace.
Please provide the details of the problems you have faced during the compilation of you project so we could investigate the matter on our end.
Hi Babur,
Simply install new setup and remove the reference of OMR.dll from your project then build the solution. It will not build itself and will demand for OMR dll. Please check.
Regards,
Asad Naeem
Hi Asad,
You need to reference only Aspose.OCR.dll in your project to get rid of all build errors. Please note, no other changes are required, however, if you find any issues, please provide the snapshot/error details for further investigation.
The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.