Gary, first, welcome to the group! Hopefully other members here who know your particular equipment better than me will come to your aid, but in the meantime here are some general thoughts to consider: - The Epson driver needs to see an RGB file in order to separate into its inks. If it is not given that, it internally converts a grayscale or CMYK or whetever into RGB. - By scanning a grayscale you may not take full advantage of your scanner. At least two reasons come to mind: (a) not all channels have the same noise; the red may be far better than the blue for example. (b) the gray set up in many scanners is inferior to their RGB color setup, mostly because of software issues. - If memory is not a problem, you may consider scanning in RGB, using a layer of channel mixer to make the best bw conversion, flatten a copy of the layered file (that may also include your other adjustment layers), go profile-to-profile using the specific Epson profile for the paper you will use. Then sent the converted RGB file to print, setting the Epson driver to do no color adjustments. At least it may be worth a try to compare this to your current workflow. - Down the line, if you do a lot of bw printing, you may consider dedicating a printer with a grayscale inkset (piezo, MIS etc) and a CIS (continuous ink supply) that saves money and time messing with carts. The book I like is "Real World Photoshop" by Blattner and Fraser. Good luck! Antonis --- In DigitalBlackandWhiteThePrint@y..., "Gary Benson" <bensonga@g...> wrote: .... > Perhaps a simple question (if there is one in this area!): To get the > best results from my Epson 980 using the OEM inks on Epson heavy > weight matte paper would I be better off scanning RGB and working > with an RGB image in Photoshop or scanning and working with a > grayscale image from beginning to end? ... > > Also, any recommendations for a good book on BW digital printing or > Photoshop techniques? .....
Message
Re: Scanning RGB vs Grayscale
2001-11-11 by Antonis Ricos
Attachments
- No local attachments were found for this message.