dpc wrote:Wow, what a hassle. If it were me, I would try to find out what was the cause of this (CHDK bug/setting or switch bounce) rather than work on an efficient way to determine and reshoot the missing pages and eliminate the duplicates. Have you tried triggering the camera by hand instead of using your remote switch to see if you end up with a similar problem? You may need to add a debounce circuit to your switch.
If you knew the general area where the page numbers were located within each page's image, you could write a program that saved just that clipped area for each page into a separate image, ran that through OCR, then use another program to parse the numerical text output and look for missing/duplicate page numbers. I thought about doing something like this to detect missed/duplicate pages for an automated page turning scanner I was designing, but you shouldn't have to worry about this if you're turning the pages by hand (I would hope).
<<I would try to find out what was the cause of this (CHDK bug/setting or switch bounce)>><< rather than work on an efficient way to determine and reshoot the missing pages and eliminate the duplicate>>
I think I probably need to do both! Process and Procedure Cont...
I didn't like the idea of two separate types of paper Work lists as described above. But the steps involved seemed the right approach. So after further thoughts and a bit of playing about I came up with an application to cut the paper out of the loop (well mostly). This is to be known as "Book Mapper".
The idea is to use this to speed up getting a good set of images on the SD card prior to copying them to HD for post-processing in Homer etc. You firstly set the directory of the source image files (which will be on the SD card). You also enter key attributes for the book to create an overview "map":
The "Intro pages" are just page number counts of all the stuff prior to the first numbered page, similarly for the "Ending pages". You then enter the last numbered page.
It then populates the "Map" list in this:
The logically created "Book Map" and Source files are shown in the top two list boxes. You can scroll through the images and identify i) Any for duplicates or duff ones for deletion (and "Add to Deletes"). If a match is made between image file and book map page, then Click on the "Match" button. These two operations create entries in the lower two lists (Matched Map/Images and Deletion list) and remove the entries from the upper work lists.
1) The "Delete All" will batch delete all the files in the Deletion list.
2) The "Work list" option will create a list of any pages remaining in the "Map" list (which can be printed off, taken to the scanner for the next cycle etc)...
I haven't used it for real yet and there's tons of stuff left to do (Undelete, Save book map, Load Saved book map, Edit individual book map entries (to add some description or such for pages with no page number) etc etc)....
If anyone has any thoughts on other useful functions, please chime in....Book 2 Continued.....
This week I struggled with the 386 odd page book whose images I took last weekend. I ran into troubles in Scan Tailor. Basically, it kept bombing. Frequently on page one or two! The images themselves were at the same resolution and settings, but this book was much bigger. In the end I guess it was just really needing to get more experience with ST. I set the first two pages (in colour) to "Mixed" type, I used the arrange by increasing width and height to crop all the largest images (I was suspicious that some were too "wide") and finally I set the output to 300 dpi and not 600. It then ran through to completion. The book is fine, no duff pages, and less than 9Mb in size.
DPC is quite right that I need to do a lot more work with CHDK and the remote and I think I'll add a second light (see above) to the lighting rig..... but the next step is to bash on with Book3 using the program above and note whether it helps or not.