Is OMR license is different from OCR license?

Aspose.OCR Product Family
1

Hi support team


We have got the temporary license for OCR and tried to apply it in our omr reader code. But it throws exception as below com.aspose.omr.AsposeLicenseException: The license is not valid for this product.

Is the omr license is different from ocr license. Please help
2

Hi,


Thank you for contacting Aspose support.

Both components from Aspose.OCR API package use the same license therefore you should not be experiencing the said problem. Please try the same case with Aspose.OCR for Java 2.0.0, in case you are using any older revision of the API. If the problem persists or you’r using the v2.0.0 then please send us the license file via an email. Please use the Contact button on the post window to send an email to babar.raza, and attach your license file to the email. Once you have sent the license file, please post here with a confirmation.

Note: DO NOT attach the license file in the public forum, instead use the method as suggested above.
3

Dear Support

I have sent license file as email with subject Aspose OCR license file from varnatech

4

Hi,


Thank you for sharing your license file for our investigation.

We are able to observe the said problem while using the latest version of Aspose.OMR API 2.0.0 and your license. Your license file works well with Aspose.OCR but throws AsposeLicenseException when set with Aspose.OMR API. We need to further investigate the matter to isolate the problem cause therefore we have logged the problem in our bug tracking system under the ticket OCR-33911. Please spare us little time to properly evaluate the scenario on our end. In the meanwhile, we will keep you posted with updates in this regard.
5

Hi Support Team

Can we have an update on this. We have a evaluation tomorrow and we cannot show the demo with 2 or three questions . We need to show it with atleast 50-100 questions so please help . We need to purchase once this evaluation is done.

Thanks
Varna
6

Hi Varna,


I am afraid, the ticket logged earlier as OCR-33911 is currently pending for analysis, and is in the queue with other priority tasks. The investigation will take some time then we can move forward to fix the problem with upcoming release of Aspose.OCR for Java API (if applicable).

That being said, I have performed a few tests by requesting temporary licenses from the sales department. I have noticed that Aspose.Total for Java license can be set for Aspose.OMR for Java component without any issue. I would suggest you to request another temporary license, this time select the Aspose.Total for Java from the available product list.

We are sorry for the inconvenience caused to you.

7

Hi

Thanks for the update, will apply for a temp license again, aspose.total this time.

Are there any timelines for the upcoming release of Aspose.OCR for Java API, in case this issue is scheduled in it? This will allow us to plan for some workaround until then, if possible.

Thanks
Krish
8

Hi Krish,


The next release of Aspose.OCR for Java isn’t scheduled yet. Allow me some time to work with the product team to bring you an estimated schedule for the next release.
9

Hi Krish,


This is to inform you that the next release of Aspose.OCR for Java is scheduled for the last quarter of February 2015. Moreover, the ticket attached to this thread is scheduled for the next revision of Aspose.OCR for Java.
10

Hi

Thanks for the update. Is applet exception (<a href="https://forum.aspose.com/t/1605) also handled in this release ?.Please let us know

Thanks
Varna
11

Hi Varna,


Yes, the ticket OCR-33912 is also scheduled for the upcoming release of Aspose.OCR for Java 2.2.0. I have left a note on the corresponding thread for future reference.
12

The issues you have found earlier (filed as OCR-33911) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
13

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