Hi! So, I am running tesseract4 on clean, 1-bit images of rasterized text (not printed and scanned). I'm getting very accurate output, as expected, but tesseract is taking about 1 second to process a single page on a core i7 cpu, and that seems a lot longer than I'd have expected.
I've been trying to enable debug output so that I can see what's taking the most time, to see if there is anything that I could get away with turning off to speed it up (since I don't need to account for e.g. dirt on the lens), but thus far I'm feeling pretty stupid. So: A) is there any straightforward way to get more information on what tesseract is actually doing? (I've built with --enable-debug and it doesn't seem to have changed the output on the command line) B) are there any control parameters you folks would suggest setting to speed up image processing/turn off unnecessary work, given the inputs I've described? Many thanks, PTR -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tesseract-ocr. To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-ocr/893cf5f7-8f64-428e-b1fe-5e6214215059%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
