-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zbarimg fail to decode large QR code created by qrencode #66
Comments
I was able to reproduce this issue with $ yes | dd bs=1 count=3000 | qrencode -S -v 32 -o 66.png
$ zbarimg --version
0.23
$ zbarimg -Sdisable -Sqr.enable 66-01.png 66-02.png 2>&1 | grep WARNING
WARNING: barcode data was not detected in some image(s)
$ zbar/zbarimg/zbarimg -Sdisable -Sqr.enable 66-01.png 66-02.png 2>&1 | grep WARNING
WARNING: barcode data was not detected in some image(s) |
possibly related: #65 |
I noticed this problem recently when attempting to split a large block of data into multiple QR codes to solve this issue. My workaround was to split the data myself and run It would be nice if zbarimg could decode these, and even better if it could somehow report the structured append metadata (sequence indicator and parity data). |
looking forward to seeing support for structured append in zbar! |
@jose1711 how do you generate an |
@jose1711 You have to set DEBUG_SVG and recompile... |
What is the status of this issue? Is there any chance to recover a QR code that is created with qrencode? It is very large. |
Maybe try to upgrade zbarimg=0.23, It seem to be a similar issue that Polyconseil/zbarlight#33. |
Do you mean you did not see the problem with zbarimg version 0.23, in contradiction to the message in #66 (comment) ? I hope the recipe to reproduce it is simple enough for anyone to test. |
This issue is originally reported to https://bugs.debian.org/719013 .
I just tested this with zbar version 0.22, and sure enough, the problem still exist:
I expected zbar to handle QR codes generated by qrencode.
The text was updated successfully, but these errors were encountered: