Ellie Kennard wrote: > Thanks for the reply. Yes, I built the profile as a RGB profile. I > was wondering if I should have built it as a CMYK one?
Probably not. (if what you have is accurate you're allright <G>. > But your reply > has made me think that a RGB is right in most situations I encounter. > > The printer does have a RIP, and can process either CMYK or RGB > files. If you have the correct tools you may hit the target better with a CMYK profile and a lot of RIP linearisation, but it's hard to tell without being there. > When I configure the port that is receiving files, I specify > CMYK or RGB input, and then specify the colorspace for RGB files. Basically the assumed source profile. > The > files that I work on are RGB, and sent through as such. I need the > RGB gamut, which I understand is greater. Though how that can work > like that, when it is CMYK inks being used to print, is beyond me! It's not the inks, it's the driver. What really makes the difference is the kind of target file that's sent to the RIP. The resulting profile however doesn't really differ. Both profile use LAB as a reference so you are able to convert it to almost anything else. Think about it, how could you make a softproof of a CMYK profile on an RGB screen? > > If a customer gives me a CMYK file to print, which I will send > through as I receive it, should I then make a CMYK profile for soft- > proofing? No need. Your printer profile describes your printer, regardless of the driver type. If it is accurate it's accurate for both RGB AND CMYK... Best Regards Thomas Holm / Pixl ApS - Photographer & Colour Management Expert - Adobe Certified Training Provider in Photoshop� - Imacon Authorized Scanner Training Facility - Remote Profiling Service (Output ICC profiles) - Seminars speaker and tutor on CM and Digital Imaging etc. - Home Page: www.pixl.dk � Email: th[AT]pixl.dk -- =============================================================== GO TO http://www.prodig.org for ~ GUIDELINES ~ un/SUBSCRIBING ~ ITEMS for SALE
