Skip to content
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

Scanning is too sensitive #21

Closed
renerisha opened this issue May 12, 2015 · 7 comments
Closed

Scanning is too sensitive #21

renerisha opened this issue May 12, 2015 · 7 comments
Labels

Comments

@renerisha
Copy link

I'm getting barcodes from walking around with the scanner opened on android, it seems that asphalt and my carpet result in whatever pattern. The carpet has the following design (if it helps you):
carpet

Asphalt is resulting in a barcode like: 0142722651309245
The carpet returns: 0159932124100211

@jjbridges
Copy link

That's "the man" sending you subliminal messages. :)

@tjwoon
Copy link
Owner

tjwoon commented Jun 16, 2015

This is interesting 😆
Will have to check if the upstream ZBar project has a known issue on this.
Thanks!

@nickgerman
Copy link
Contributor

@tjwoon I am noticing this as well on newer devices, not so much older ones. I wonder if its to do with the X_DENSITY and Y_DENSITY. Just lowered the density to 1 and am now getting less barcodes in the wild, my guess would be the higher megapixel cameras are causing this to be sensitive.

@binoculars88
Copy link

@nickgerman thanks for this. Was getting some false scans too. This fix seems to work.

@dcousens
Copy link
Contributor

@binoculars88 / @nickgerman can you elaborate on how you resolved this?
Is it something we could add as a parameter?

@nrcrabbe
Copy link

@dcousens

Lines 147, 148 of android/ZBarScannerActivity.java

scanner.setConfig(0, Config.X_DENSITY, 3);
scanner.setConfig(0, Config.Y_DENSITY, 3);

Change the values 3 to 1. Fixes the false scans and I haven't had any negative issues after the change. Would be great to have these either changed to 1 (if there are no unintended consequences), or at least have it parameterised.

Cheers

@dcousens
Copy link
Contributor

Thanks @nrcrabbe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants