First build with automatic dewarping
Moderator: peterZ
Re: First build with automatic dewarping
The first one is probably hopeless, matt. There are no long lines at all. Those separator lines would do, if they didn't have text so close to them. The second one might be fine, after I finish a better selection method for representative lines.
Scan Tailor experimental doesn't output 96 DPI images. It's just what your software shows when DPI information is missing. Usually what you get is input DPI times the resolution enhancement factor.
Re: First build with automatic dewarping
Thanks for the input. Also, I'm curious about using the top/bottom edges of the page (if available) as cues for dewarping. I know that another image processing program (Snapter) does this; in fact it requires that the top/bottom edges be visible. Would that sort of grid algorithm be helpful/possible in the first example page I posted?
Re: First build with automatic dewarping
I don't want to require that, and neither do I want to invest another few months to come up with an edge tracing algorithm.matt wrote:in fact it requires that the top/bottom edges be visible. Would that sort of grid algorithm be helpful/possible in the first example page I posted?
Scan Tailor experimental doesn't output 96 DPI images. It's just what your software shows when DPI information is missing. Usually what you get is input DPI times the resolution enhancement factor.
Re: First build with automatic dewarping
Report: 1.0 ßeta5 doesn't hang on me anymore.
Great work, Tulon.
Best regards.
Great work, Tulon.
Best regards.
Re: First build with automatic dewarping
Gotcha. In my naiveté I thought edge tracing might be a special case of some more advanced algorithm that was already in use.I don't want to require that, and neither do I want to invest another few months to come up with an edge tracing algorithm.
On another front, I"m noticing that ST (latest from Git) is crashing during batch output processing with auto-dewarping enabled. When this happens the following is displayed at the command line
and a standard Mac crash reporter pops up and offers to send the report to Apple. Will you get this information as well? If not, would you like me to private message or otherwise send the report to you?Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.
Abort trap
Thanks!
Matt
Re: First build with automatic dewarping
Nope.matt wrote:and a standard Mac crash reporter pops up and offers to send the report to Apple. Will you get this information as well?
Yes, PM is the way to go.matt wrote: If not, would you like me to private message or otherwise send the report to you?
Scan Tailor experimental doesn't output 96 DPI images. It's just what your software shows when DPI information is missing. Usually what you get is input DPI times the resolution enhancement factor.
Re: First build with automatic dewarping
Beta6 has arrived: http://depositfiles.com/files/y5en4ust4
I implemented RANSAC for selecting representative lines and made some other improvements. Here are a couple examples where beta6 succeeds where previous versions failed: Unfortunately, it turns out even with good representative lines you can still end up with significant wobbling: I haven't looked into this issue yet.
I implemented RANSAC for selecting representative lines and made some other improvements. Here are a couple examples where beta6 succeeds where previous versions failed: Unfortunately, it turns out even with good representative lines you can still end up with significant wobbling: I haven't looked into this issue yet.
Scan Tailor experimental doesn't output 96 DPI images. It's just what your software shows when DPI information is missing. Usually what you get is input DPI times the resolution enhancement factor.
Re: First build with automatic dewarping
I never cease to be amazed with the work you put into this, Tulon. Thanks once again.
Those 'good' representative lines don't quite seem perfect to my eyes: Is it possible to get ST to calculate all possible representative lines, and then to manually pick two opposed to letting an algorithm do it?
Those 'good' representative lines don't quite seem perfect to my eyes: Is it possible to get ST to calculate all possible representative lines, and then to manually pick two opposed to letting an algorithm do it?
Re: First build with automatic dewarping
Maybe.ahmad wrote:Is it possible to get ST to calculate all possible representative lines, and then to manually pick two opposed to letting an algorithm do it?
Scan Tailor experimental doesn't output 96 DPI images. It's just what your software shows when DPI information is missing. Usually what you get is input DPI times the resolution enhancement factor.
Re: First build with automatic dewarping
I logged in to tell you that I was eagerly and patiently awaiting the automatic dewarping function, just to give you some support, and here it is already! This is great and I will be testing it out somewhere this week. Thanks a lot!