Closed scarrick68 closed 1 year ago
Thank you for filing an issue! Please be patient. :-)
oooh i guess i left in some debug messages in the last release, and forgot to mention it in README, thanks for pointing that out.
You can try adding willReadFrequently: true to the inputStream and locator objects in Quagga.init(). Please let me know if that makes any sort of improvement, measureable or just by feel. In my tests, I wasn't able to measure any change, but that was using automated testing on my rather powerful desktop, which zips through tests incredibly fast. I also don't notice any obvious change on my Motorola G Stylus, which is a reasonably fast phone made in the last couple of years.
It would be nice to know if someone who's experiencing an issue with speed that they notice to begin with can comment on it. As far as I can tell it's just a warning from the browser that doesn't mean a lot.
closing as willReadFrequently should be working fine
Hey, I have bunch of console warnings and I'm wondering if I can get rid of them and maybe get some better performance based on what the console is telling me.
Warnings: "InputStreamBrowser createLiveStream" "InputStreamBrowser createVideoStream" "initCanvas getCanvasAndContext" "frame_grabber_browser: willReadFrequently= undefined canvas= " "Invalid asm.js: Unexpected token" "initCanvas willReadFrequently false" "Canvas2D: Multiple readback operations using getImageData are faster with the willReadFrequently attribute set to true."
Seems like I need to set willReadFrequently but I don't know and it's not in the docs.
Here's the snippet I'm working with: