Yeah I just tested with Seeebeks lang file, and got slightly lower accuracy than the default lang, but that is with my preprocessing
cowboy: I've been playing around with that for hours actually. I detect the rows of text with my own code, then cut them up into pieces. This is at 1920x1080.
Scaling the text up (normally good for OCR) seems to drop my accuracy to below 30%, and I'm not quite sure why.
I also believe I have the font that they use (taken from another thing they made), but training tesseract on it using jTesBoxEditor has been rather disappointing so far.
I'd love to be able to work together with everyone currently trying to find an OCR solution, it's just funny that seeebek is using python, I'm using .net, and you're using straight up bash lol
cowboy: I've been playing around with that for hours actually. I detect the rows of text with my own code, then cut them up into pieces. This is at 1920x1080.
Scaling the text up (normally good for OCR) seems to drop my accuracy to below 30%, and I'm not quite sure why.
I also believe I have the font that they use (taken from another thing they made), but training tesseract on it using jTesBoxEditor has been rather disappointing so far.
I'd love to be able to work together with everyone currently trying to find an OCR solution, it's just funny that seeebek is using python, I'm using .net, and you're using straight up bash lol
Last edited: