OK, if you like to edit digital photos, then before you go any further, go to /www.irfanview.com/ and download IrfanView. I use it almost daily.
A book I'll soon review contains mostly photos. In the past, I've used scanned photos in the blog, and I did a lot of work on them for viewing on the computer. My scanner has a "descreen" option, but I found I could use a few steps in IrfanView and get a better result. The following procedure is to completely descreen an image scanned from a halftone print. The example image is a 2-tone Sepia-toned reproduction of an old photo, but the method is the same for monotone or full color.
Halftone on glossy pages such as a magazine or photo-oriented book has from one to four (sometimes seven) hexagonal dot patterns with a pitch of 120 to 180 dots per inch; 150 dpi is most common at present. Halftone on newspaper pages and other non-shiny paper has a pitch of 80 to 120 dpi; 100 dpi is most common. There is a whole discipline of picking the angles for the different screens so they won't produce unsightly Moiré patterns (interference banding). So it makes no sense to try for a final image with more than 100 or 150 dots per inch.


Of course, the "proper" way to descreen such an image is to use Fourier series filtering. It doesn't simply remove all frequencies higher than, say, 80 dpi; it removes the specific frequencies that pertain to the screen patterns, leaving some extra photo detail visible. It is thus better than both the descreen routine in my scanner and this procedure, but for most purposes our process will be sufficient. Those with the extra energy can get Fourier analysis software...it doesn't come cheap or easy.


For many purposes you can reduce this image to ¼ size so it is displayed at 150 dpi (or 50% larger than "life" on a 100 dpi monitor and 2x on a 75 dpi older monitor). In IrfanView, Ctrl+R (Menu Image/Resize) selects Resize where you can single-click a half-size reduction or enter any percent (use 25% for quarter size). Also, I use the slowest resize filter for best results; there are several in a panel on the Resize dialog.
However, I like a little better final results with no halftone remaining, so I blur twice more. Once at this size and once at an intermediate size.


Some day I'll take the time to run a few pix through this process, then do it again skipping this blur step, to see how it impacts the final image.
A test image that I took using the scanner's Descreen option looked rather good at the outset (the scanner delivered a 300 dpi image). I blurred it once, reduced by half for 150 dpi, and it looked as good as a result from this process. However, to Descreen, the scanner scans in a peculiar version of 1200 dpi, capturing each color separately, so it takes much longer than an "ordinary" 600 dpi scan. I guess I prefer to be "doing something" for the same amount of time, such as fiddling with IrfanView! So, I do more steps.



I encourage you to experiment. I had a little theory to drive me; I knew in a general way what the Blur operation does, for example. It may be that starting with a 300 dpi scan and using fewer Blur steps, perhaps at a % different from 99, will work as well. I am usually in production mode, so I must consciously block out time to experiment or I don't do any.



I can see no hint of halftone patterns, not even the Moiré patterning. However, the edges are no longer as sharp as before.
We will be shrinking this image further, to get it to final dimensions and resolution. Remember, our goal is to display at 150 dpi, and this is still at 300 dpi.



Many times, you can stop right here. At the risk of resurrecting some sign of the screens, I like to do a final sharpening step. Most of the time, I like the result better.



There you have it. Start at 600 dpi, then Blur, Blur, reduce by half, Blur, reduce by half again (to ¼ size), Sharpen, and you're done. It really doesn't take long!
Although I have scanning software which will descreen, I find that by using the "shortcut" method (In Irfanview, Start at 600 dpi, then Blur, Blur, reduce by half, Blur, reduce by half again (to ¼ size), Sharpen) the descreening is carried out much more quickly and with no need for experimentation with the level of descreening.
ReplyDeleteI will continue to use this method in future.
Thank you for posting this. I was in the process of writing a book for a publisher who wanted photos descreened. My scanner didn't have the option. Using your instructions, I was able to descreen several valuable photos and get them in the book.
ReplyDeleteone time I had scanning software that would just do this by checking a box... why the heck don't these scanner people wise up? just bought an HPO officejet and no descreen....... WHY! HP WHY!>?
ReplyDeleteAbsolutely brilliant - thank you.
ReplyDeleteThis method is perfect for some of the older pictures in my collection. Thanks.
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteworks perfect, well done! as a subscript of another script of mine, i made this to call in case of images (some variables are needed in my environment, adjust accordingly):
ReplyDeleteEcho Off
SetLocal EnableDelayedExpansion
Set Path=%path%;C:\Program Files\IrfanView;C:\Program Files\IrfanView\Plugins
Cd /d src
Start "" i_view64 !Cd!\folder.tif /effect=(1,99) /effect=(1,99) /resize=(50p,50p) /effect=(1,99) /resize=(50p,50p) /sharpen=21 /jpgq=100 /convert=!Cd!\folder.jpg
GIMP is free image manipulation software. There is a free descreen plugin that lets you do the Fourier transform approach.
ReplyDelete