Make Tess a part of your project (you can use only needed source files), or compile it as a DLL and use the API. That way you can call it as frequently as you like, without much overhead. Not sure about the DLL way - is it viable now? I've implemented projects that use Tess in real time, with no memory hogging (as an answer to other forum thread), using select parts of it, though.
Warm regards, Dmitri Silaev www.CustomOCR.com On Wed, Oct 17, 2012 at 5:37 PM, Attila Somogyi <bmfneum...@gmail.com> wrote: > Hello! > > My application processes images in a very small interval, about 1 sec. This > means that the tesseract exe executes in every second then it quits, then my > app processes the hOCR output. > Is there another way to communicate with tesseract? I'm looking for > something like this: tesseract exe wont quit after processing and when > required it processes again( sending a message maybe?). > > > -- > You received this message because you are subscribed to the Google > Groups "tesseract-ocr" group. > To post to this group, send email to tesseract-ocr@googlegroups.com > To unsubscribe from this group, send email to > tesseract-ocr+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/tesseract-ocr?hl=en -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To post to this group, send email to tesseract-ocr@googlegroups.com To unsubscribe from this group, send email to tesseract-ocr+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/tesseract-ocr?hl=en
