IMB barcodes not found- but handheld scanner says it's OK

Aspose.BarCode Product Family
1

Hey guys. I’ve run into a problem where the barcode recognition is not detecting these barcodes, although they appear to be quite clean and well formatted. The RecognitionDemo for the older 3.x version does not see these at all. I will attach .JPG’s of some of these and the appropriate values.


barcode_1.jpg = 00,260,100866,000028934,33525713445
barcode_2.jpg = 00,260,100866,000029032,33525713445
barcode_3.jpg = 00,260,100866,000028995,33525713445
barcode_4.jpg = 00,260,100866,000028977,33525713445
barcode_5.jpg = 00,260,100866,000028971,33525713445
barcode_6.jpg = 00,260,100866,000028934,33525713445

However the RecognitionDemo does not find these. Is there a setting or configuration that will work with these? I have not tried this with the Aspose 4.x code as (for my implementation at least) there is a significant performance penalty over the 3.x level Aspose.barcode.dll

Thanks for any help you can provide!!
–workingjoe–

2

Hi,

Thank you for inquiry.

I checked the images with the toolkit provided with v4.2 and it failed to recognize after setting all postal or just OneCode. It seems to be an issue with the toolkit demo, we will look into it (Issue ID: 29999).

But, when I use BarCodeReader class in VS with dll from bin/3.5 folder, it reads all these barcodes.

List filenames = new List();
filenames.Add(@“barcode_1.JPG”);
filenames.Add(@“barcode_2.jpg”);
filenames.Add(@“barcode_3.jpg”);
filenames.Add(@“barcode_4.jpg”);
filenames.Add(@“barcode_5.jpg”);
filenames.Add(@“barcode_6.jpg”);

foreach (string filename in filenames)
{
Console.WriteLine("Trying to read from " + filename + “…”);
BarCodeReader reader = new BarCodeReader(filename, BarCodeReadType.OneCode);
while (reader.Read() == true)
{
Console.WriteLine("Recognized from " + filename + ": Codetext: " + reader.GetCodeText() +
" Symbology: " + reader.GetReadType().ToString());
}
reader.Close();
}

3

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

This message was posted using Notification2Forum from Downloads module by aspose.notifier.