DIY Book Scanner

Daniel Reetz, the founder of the DIY Book Scanner community, has recently started making videos of prototyping and shop tips. If you are tinkering with a book scanner (or any other project) in your home shop, these tips will come in handy. https://www.youtube.com/channel/UCn0gq8 ... g_8K1nfInQ

These are the same build errors I reported above. See Tulon's response - it looks like they should be easy to fix and that we can hope for that soon. Waiting a few days for a real fix is likely better than applying my duct-tape style patch that probably will gum things up and cause unnecessary headaches.

1. It happens if you manually split the image in 2 pages.
In order to crash the program, load the image and then go straight to the splitting menu, and select the double page.

2. Another error is the out of memory issue (i use the 64 bit version on 6 GB RAM, without swap file).
In order to crash the program: run the Fix Orientation option, the jump to the Output option and run it.
The CPU stays at 26%, but the RAM usage went through the roof: 3300 MB.

I could not reproduce the crash or the out-of-memory situation so far. Do you have OpenGL / OpenCL enabled? Does it still crash with those disabled?

The out-of-memory situation on 64-bit systems is usually caused by Qt's limitation of 2GB per image that's in place even in 64bit builds. Your image is huge (18000x18000 px), yet it doesn't break the 2GB limit, even with 2x resolution enhancement factor. However, if the image in question was color rather than grayscale, it would have broken that limit.

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.