RE: [ECI-EN] Why be scared by device independent color? (Martin Bailey)

Hello, Hope everyone had a good vacation. Martin Bailey wrote: be same standard using If we finally do get some sort of intelligent best image conversion method engine, then I am sure this would have to change. The simple fact that the PDF/X standard specifies that a certain RI has to be used shows that this is a real problem area - different RIs can give very different and very poor results. If a technology evolves which can solve this, then this would become a non-issue and the 4 choices could even disappear from the user-interface altogether (at least in basic mode). This is presently one of the main stumbling blocks in automated workflows. only simpler Not really. What often happens in discussions about CMYK or RGB workflows is that it is usually supposed that if you mention CMYK somewhere, then this means that you are going into this space from the start. With the exception maybe of legacy scanners, many workflows are actually mixed, and the conversion from RGB to CMYK may happen anywhere along the chain. Maybe the following example could explain better. An editorial which captures digitally has RGB input. The images are then optimized, retouched, etc. in RGB and left there. Page layout also is done with the RGB images, although there might be some CMYK images as well which could come from other sources. Once the layout is done, the PDF can be created, and this PDF, usually X-3, then is ready to go anywhere. As the usual final destination is a web offset press, the PDF is then given to iQueue and converted to CMYK for proofing and sent along with the proof to the print shop. If, in the future, the RGB chain could be extended to the print shop, or in the case of the PDF going somewhere other than to web offset, then it is a simple decision of not sending it to the iQueue queue. X-3, I think, gives greater flexibility in this respect. My understanding of the original part of the thread was that it referred to the whole workflow, but in particular to the part of data exchange between prepress and press, for example, where PDF comes into play. At this part of the chain, I do not see any overwhelming benefits of maintaining RGB data, and at the same time there are many disadvantages, and hence the reason I maintain (IMO) that it should be CMYK for this stage of the process. is alternate get concerns a press. print. I am not really sure I followed you here. I don't understand the need for the document to have device independent color to proof spot colors correctly. A good proofing software will have its database of the necessary (CMYK, CcMmYKk, etc.) values to give the closest reproduction possible of the spot color whose name it picks out during processing. Could you explain bit more what you mean here? Regards. Darrian Young