@sergiuds that sounds like something we could put into the docs. i'm guessing useful for people using cameras in landscape mode? doesn't seem too useful for portrait mode
@stefanocali has significantly improved the new code32 reader and that was just merged .. very glad to get some progress on adding some real useful things
:-D :-D :-D
well, weirdly, the node bundle is increasing in size but the browser bundles have dropped 1.3MB and 54K since my last change.. and I think there's more to be gained
i've noticed an amazing improvement in speed of my application that uses quagga loading, since upgrading from 1.2.2 to 1.2.5 .. 1.2.6 should have as much of a gain there
we're about 33k larger than the bundle size from when we forked, and I don't expect to make a 1.x tree any less than that... however i do have some inklings for a 2.x tree someday that will eliminate a LOT of code from the main bundle, and offload it to separate pieces, so you're not saddled with having all the code for all the options you never use.
hi there. my best advice is make sure you're using the best resolution you can, make sure you're not using a wide-angle camera lens, and make sure there's as much empty-space around the barcodes as possible... you can use something like the original repo's demonstration to try to adjust your quagga settings for the best results for your use case .. (i do hope to have time to get that demo up from my repo somewhere, or something similar, but haven't had time to even touch quagga in quite a while)
@zadof i would check to see if there are multiple camera devices showing up, and if there are, try a different one. A lot of modern phones have separate logical devices for different camera attributes (namely wide-angle lens, being very common), and it's really difficult to read a barcode with a wide-angle lens.
like on my LG G6, enumerateDevices shows there are 2 rear cameras and a front camera, the default rear is near impossible to use, have to force select the second one
i know i've got an ios user on my application that says the scanner works great, we're scanning UPC/EAN codes with it
so, there are two things i do know about iOS wrt quagga, one is that the newest version of iOS if you use a "max 100" aspect ratio constraint, it'll actually give you a 100 aspect ratio image, which is just a black screen. no idea how/why it does that. Also, some combinations of iOS hardware/software will refuse to do certain camera resolutions that are commonly possible other devices, like 640x480
unfortunately, there is no focus control available to the HTML media apis right now
yeaa.. small barcodes, you can try to tune the settings for, adjusting the patchsize and such, or using locate: false, with an area parameter in the config
I'm not aware of anything. There is a singleChannel parameter i believe it's called, that forces it to only use a single channel of the image for data.. i've just .. not really had too many problems, using just a single setting, with common UPC/EAN codes.. so i haven't explored too much
i do only have a handful of users for my application, but this is what i use
inputStream: {
type: 'LiveStream',
constraints: {
width: 640,
height: 480,
...(cameraId && { deviceId: cameraId }),
...(!cameraId && { facingMode: 'environment' }),
},
target: scannerRef.current,
},
locator: {
patchSize: 'medium',
halfSample: true,
},
numOfWorkers: 0,
decoder: {
// readers: ['qr-code-reader'],
readers: ['upc_reader', 'ean_reader'],
},
locate: true,
}, (err) => {
those codes you mention work fine
i get the impression that code128 is quite well tested (as opposed to code32, which is new to the lib, and a few others that don't see much use at all that were put in by the original author).. however, you're right that code128 can be quite small, i used it in a business not long ago, because it was able to reproduce a lot of information in a short space. but i never had need to read it with quagga so i never tried
i know the readme, and i have said "try higher resolution so the image comes out better", but something to also try is lower resolution so that the barcode isn't so small. might help? not sure
and if you can get away with setting a locate area, and turning off auto-locate, then you're eliminating a large chunk of the work that makes things break sometimes
128 works, but if it's small enough and the image get a little blurry, it wont work
I don't think you have an automatic way to pick the "good" camera
@zadof Yeah I guess I can make a camera picker and alert users that ultrawide camera might not work for them. And yeah I agree, I can't think of a method to pick "good" camera as well.
What really bothers me is that every single other app(instagram, snapchat, myfitnesspal and etc.) They always seem to open "good" rear camera never ultrawide and never telephoto.
Is it different with native apps?