Not able to Read Whole Barcode Length


#1

Hi ,

We are using Aspose.Barcode version 18.7 for reading barcode. But we found that it is not reading whole length of barcode.

Please find the attached image for the sample. Barcode on the image is ‘BAR010885156’ . But while reading it is ‘BAR01’.
Since the latest version of Aspose.Barcode is 19.6 . So, we have tried with this also but still issue exists . Is there any other change that we need to implement in our application ?
Please suggest.
20190614904478.zip (28.7 KB)


#2

@52000537,
We were able to observe the issue but we need to look into it more. We have logged the issue in our database for investigation and for a fix. Once, we will have some news for you, we will update you in this topic.

This issue has been logged as

BARCODENET-37235 - Whole Barcode Length is not read

#3

Thank You @ahsaniqbalsidiqui .

Can you please let us know when we can expect fix for this issue ?
Since It is affecting our production, we need to get this on priority. If possible , please look into this on priority.


#4

@52000537,
This issue is logged too recently and may take time to be analyzed and resolved as other tasks are already there in the queue. You may please be patient until this issue is analyzed in detail and feedback is ready to share.


#5

Hi @ahsaniqbalsidiqui

Is there any update regarding this issue ?
Please let us know your findings .


#6

@52000537,
I am afraid that after an initial investigation, this issue seems to be more complex and requires more deliberation at our end. It may take time and is postponed for the time being. Due to this reason, no ETA can be provided immediately. You may wait until we are back with some feedback.

Sorry for the inconvenience caused in this regard.


#7

Thank You @ahsaniqbalsidiqui for your response.

This is a production issue which needs a quick resolution. So Is it possible to get any workaround until the issue is fixed ?

Also can you let us know if the issue would be fixed with priority if we use paid support option.


#8

The problem exists in fully wiped bar in the one barcode segment, you can see this in 37235_cut_marked.png. For the Nbase barcodes (Code128 set) with checksum the problem was partially solved by pickup algorithm which builds recognition versions and checks them by checksum. Main problem here that Code39 doesn’t have any checksum (only in special cases).

In this way, we could set your issue on the fist place if paid support is ordered. But the probability of successful solution is not more then 40% (no checksum, we have to use other parameters to select correct version).

37235_cut.png (1.4 KB)
37235_cut_edited.png (1.4 KB)
37235_cut_marked.png (1.8 KB)


#9

Thank You @alexander.gavriluk for looking on this.

Can you please let us know if there are any workarounds for resolving this issue so that we can try to incorporate it on our side ?
Also if there are any suggestions about barcode quality or font that will improve the barcode recognition then we will inform to our customers until fix is provided by Aspose.


#10

Workaround could be only in increasing barcode quality. You can use one, or at least 300 dpi barcode resolution (original image has 200dpi), this prevents barcode segments gluing in most cases. Or you could use grayscale (not monochrome) barcode images. Our binarization algorithms are much better and allow to split even mostly glued barcodes if there any difference in brightness between bars.

There is no workaround to recognize original image (the white bar fully wiped) we could provide only fix in future Aspose Barcode versions.


#11

However you can provide us great help if you add more images with the same issues. This allows to implement more accurate solution.


#12

Hi ,

I have attached few more Images having same Issue.
Looking for your further response for any solution of this issue .

Images.zip (78.8 KB)


#13

@52000537,
Thank you for providing sample files. We will look into these and get back to you soon to share our feedback.


#14

Thank you. This would help. I think the investigation of this issue will be started in 08-09.2019. Currently we have more urgent issues.