Well, the ease of use is the main goal of ST. For deskewing I actually use the same algorithm from leptonica as Rob does. I don't use leptonica itself for various reasons though. The main reason would be its lack of thread-safety, which I need, as I do processing in a background thread. Basically I just reimplemented everything I needed from leptonica.edembowski wrote:What I've found so far is that your program has a very well structured workflow to it, and deals very well with correcting and deskewing pages.
In earlier versions, content area detection used to have the opposite problem. It would interpret various kinds of garbage as content. Now it became much smarter, and it can handle very hard cases, like binarized images with lots of noise. Unfortunately, it's now too eager to classify stuff as garbage, with page numbers often being the victims. If a page number is too far from the rest of content, it's almost for certain it will be classified as garbage. To deal with that, we need to improve the rudimentary text detector that I have, to be able to trust it more. Any computer vision experts here? Anyway, I would like to see a page or two where it fails. It can fail for several reasons, and it's always good to know why it fails for different people.edembowski wrote:The only area that I'm seeing problems with is the detection of the text area. I find that often it does not select the full text area and needs manual adjustment.
edembowski wrote:Thanks for such a great app.
Good output quality is due to 3 things:edembowski wrote:Once I correct that, it seems to output exceptional quality images ready for OCR.
Tulon wrote:I am actually surprised you've managed to build it on a Mac. Is Qt in darwinports the native one, or the X11 one? If it's the former, I would expect you to hit problems with my direct calls to XRender, which is probably not available on Mac. If it's the latter, well - that kind of configuration is completely untested, but it may work I suppose. BTW, I call XRender directly because Qt/X11 doesn't accelerate drawing of transformed pixmaps, which produces very poor performance.
...Anyway, I would like to see a page or two where it fails. It can fail for several reasons, and it's always good to know why it fails for different people.
So here's a problem I'm having with saving the output: This may be because I'm on a Mac, but the saved image is not usable. On screen there are no problems. Can I send you one of these as well?edembowski wrote:... It produces quite nice results though.
In the Russian community we just upload stuff to rapidshare.com or a similar service, and then post a link to it in the forum. Posting a couple of pages should be fine from the legal point of view, so that seems to be the best solution, and others would be able to make comments on those pages as well.Tulon wrote:One image I'm is a little dark, and it's one of the ones that it has a problems with. It's too big to attach, can I email it to you?
PPC or Intel Mac? If it's PPC, I might have got endianness wrong when saving to TIFF. Libtiff is very poorly designed, so you are almost guaranteed to getendianness wrong if you don't test it on all platforms. Fortunately I have an old PPC iBook around, so it's not going to be hard to fix. You may still send me an output image to take a look though.edembowski wrote:So here's a problem I'm having with saving the output: This may be because I'm on a Mac, but the saved image is not usable. On screen there are no problems. Can I send you one of these as well?
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - not found.
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found.
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found.
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - found
-- Looking for QT_MAC_USE_COCOA
-- Looking for QT_MAC_USE_COCOA - not found.
Users browsing this forum: Google [Bot] and 1 guest