You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have the following, apparently good, image:
It should be a i25 code, but:
mcon@cinderella:~/Work/OkCash/Stampante_marche/zbar$ zbarimg/zbarimg -d ../mark2.jpg
scanned 0 barcode symbols from 1 images in 0.01 seconds
WARNING: barcode data was not detected in some image(s)
Things to check:
- is the barcode type supported? Currently supported symbologies are:
. EAN/UPC (EAN-13, EAN-8, EAN-2, EAN-5, UPC-A, UPC-E, ISBN-10, ISBN-13)
. DataBar, DataBar Expanded
. Code 128
. Code 93
. Code 39
. Codabar
. Interleaved 2 of 5
. QR code
. SQ code
- is the barcode large enough in the image?
- is the barcode mostly in focus?
- is there sufficient contrast/illumination?
- If the symbol is split in several barcodes, are they combined in one image?
- Did you enable the barcode type?
some EAN/UPC codes are disabled by default. To enable all, use:
$ zbarimg -S*.enable <files>
Please also notice that some variants take precedence over others.
Due to that, if you want, for example, ISBN-10, you should do:
$ zbarimg -Sisbn10.enable <files>
I tried both Debian standard package and self-built from git master with identical results.
I am not a barcode expert and thus I cannot divine what's going wrong.
I see similar questions are generally ignored in this forum, if I'm trespassing somehow
please redirect me to a "proper place".
Many Thanks in Advance
The text was updated successfully, but these errors were encountered:
I have the following, apparently good, image:
It should be a i25 code, but:
I tried both Debian standard package and self-built from git master with identical results.
I am not a barcode expert and thus I cannot divine what's going wrong.
I see similar questions are generally ignored in this forum, if I'm trespassing somehow
please redirect me to a "proper place".
Many Thanks in Advance
The text was updated successfully, but these errors were encountered: