EDIT: Fixed a few typos and made some corrections.
Created this as Sourceforge ticket also, but wanted to open it up for wider discussion. See ticked link below.
Usecase:
When scanning multiple pages e.g. of a book or a magazine pages, in most cases the Cropping is usually needed to be done by similar in size. Currently, user has to adjust the size manually for each scanned page separately. If you have say 50+ pages to scan, this (altering the croping size) can be pretty time consuming process.
Proposal:
Ability to save (into NAPS2 profiles/scanning sesssion) pre-defined Crop-sizes ("frames")to be selected and then placed (location and size could still be adjusted) as "Cropping frame" for scanned pages.
Implementation:
Just as a poor mock-up, the "Crop" dialog could have two separate buttons (1 & 2); see linked image. Button (1) as "Save Crop" to save adjusted crop size and "dropdown menu" (2) as "Select Crop" to select (and then place/adjust) previously saved Crop" frames". These saved frames could either be available for all profiles OR just per scan.
Benefit:
This would gratly enhance the UX and speed-upediting (cropping) process for multi-page scans.
Anyone else would like to have such feature implemented to speed-up multi-page scans page cropping? Was the description above clear or should I make a better, quick mock-up? :)
//timo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Definately a major missing feature, but I'd like the tool to autocrop to at least the sheet that is on the scanner and better yet autodetect on that paper significant information when deciding where to autocrop. If not automatic and least a manual option.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The autocopping is (I guess ;) ) very challenging on books (which I scan the most). Therefore I had proposed this 'Crop Frames' thing - let's see if Ben picks it up for implementation. It would be rather non-technical compared to implementing algorithms/autocrop stuff. But let's see!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
EDIT: Fixed a few typos and made some corrections.
Created this as Sourceforge ticket also, but wanted to open it up for wider discussion. See ticked link below.
Usecase:
When scanning multiple pages e.g. of a book or a magazine pages, in most cases the Cropping is usually needed to be done by similar in size. Currently, user has to adjust the size manually for each scanned page separately. If you have say 50+ pages to scan, this (altering the croping size) can be pretty time consuming process.
Proposal:
Ability to save (into NAPS2 profiles/scanning sesssion) pre-defined Crop-sizes ("frames")to be selected and then placed (location and size could still be adjusted) as "Cropping frame" for scanned pages.
Implementation:
Just as a poor mock-up, the "Crop" dialog could have two separate buttons (1 & 2); see linked image. Button (1) as "Save Crop" to save adjusted crop size and "dropdown menu" (2) as "Select Crop" to select (and then place/adjust) previously saved Crop" frames". These saved frames could either be available for all profiles OR just per scan.
Benefit:
This would gratly enhance the UX and speed-upediting (cropping) process for multi-page scans.
Ticket link:
https://sourceforge.net/p/naps2/tickets/446/
Image:
https://1drv.ms/u/s!AuMivHwSi2p1isF_f1nDnrZqKHa3xQ
Last edit: Timo 2018-05-28
Hi.
Anyone else would like to have such feature implemented to speed-up multi-page scans page cropping? Was the description above clear or should I make a better, quick mock-up? :)
//timo
Definately a major missing feature, but I'd like the tool to autocrop to at least the sheet that is on the scanner and better yet autodetect on that paper significant information when deciding where to autocrop. If not automatic and least a manual option.
The autocopping is (I guess ;) ) very challenging on books (which I scan the most). Therefore I had proposed this 'Crop Frames' thing - let's see if Ben picks it up for implementation. It would be rather non-technical compared to implementing algorithms/autocrop stuff. But let's see!