I want to know. Why Barcode Read Fail

Aspose.BarCode Product Family
1

Hi.

I use Aspose Barcode to Read Multiple Barcode

Test Purpose is improvement of Barcode Recognition
Same Camera, Same Barcode, Same Delay…
Repeat Capture Image ,Read Barcode and Check Barcode Text
Look What I attached Zip File(Read Fail / Read Ok Image)
It is Same Barcode, but one is Read Failed and another is Read Success
I used my phone app(manatee works barcode scanner- cognex coporation)
to Read Barcode From Two Image and Read Success All…

I use VB net and VS 2010 to develop Program
and Aspose Barcode Version is 7.2.0.0
I use BarcodeReader.Read() to read Barcode

I have a Question about Read Barcode
Why one Image Read Fail and Another Read Success?
What is Different of two image?



2
Hi,

Thank you for your inquiry and sharing samples.

This is to update you that we have investigated the issue at our end. We have used the following code snippet. We are unable to notice the said issue. It is recognizing the barcode successful.

CODE:
Aspose.BarCode.BarCodeRecognition.BarCodeReader objBReader =
new Aspose.BarCode.BarCodeRecognition.BarCodeReader(@"barcode_ReadFail.bmp");
objBReader.RecognitionMode = Aspose.BarCode.BarCodeRecognition.RecognitionMode.ManualHints;
int counter = 0;
while (objBReader.Read())
{
counter++;
Console.WriteLine(" -- Symbol:" + objBReader.GetCodeType() + " Code :" + objBReader.GetCodeText());
}
objBReader.Close();

Console.WriteLine(counter.ToString());


Output:

Symbol:DataMatrix Code :YDEDATA913

3

Hi

Thank for Fast your reply. It is very helpful for me

I recheck my code, and I didn’t use RecognitionMode…

It means I used Only MaxPerformance Option.

So I add that Option to my code, and Retest.

But still Read Fail Image existed…

So I reattached Some Image.

In Zip File…there are two folder. AppReadFail / AppReadOk

AppReadOk means Aspose Read Fail but my phone App Read Success…

Please test AppReadOk Folder Image and let me know what should I do

to read barcode…

I will wait your reply… Thank you for reading

4
Hi,

Thank you for writing us back and sharing samples.

This is to update you that we have investigated the issue at our end. Initial investigation shows that the issue persists. The issue has been logged into our system with ID BARCODENET-36493. Our product team will further look into it and provide feedback. We will update you with the feedback in this thread.

5

Hi,

Any Update or news for this Issue?

I wait for Reply…


Thank you for Reading…


6
Hi,

Thank you for your inquiry.

This is to update you that our product team is working on this issue. We have asked them to provide feedback. We will share it with you as soon as we have any feedback on this issue.

7

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

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