Re: Remote Proofing
Re: Remote Proofing
- Subject: Re: Remote Proofing
- From: Steve Upton <email@hidden>
- Date: Mon, 8 Mar 2004 10:22:10 -0800
At 8:32 AM -0600 3/8/04, Rich Apollo wrote:
>
>
Second point. Henrik, you brought up PDF/X-3 and output intents. Okay, again I see a huge lack of information in the market. IF, and that's a might big if, I receive tagged images/files they are incorrectly tagged. Upwards of 90% of the tagged images are CMYK and have a SWOP profile (usually the dreaded SWOP (20%)). Fine and dandy, except that we are a sheet-fed shop. I know immediately that this hasn't been thought through. Nobody has asked for my press profile and the data is tagged for a different production process. The same will happen with PDF/X. The only folks that will benefit in terms of color from PDF/X will be publication printers that receive files from separation houses and resellers of iQueue.
first off, chances are very good that if a file is tagged with a SWOP 20% profile that it was separated with that profile. So you are looking at a problem that is larger than the file just having the "wrong profile" attached. It contains the "wrong" CMYK and actually has the right profile (correctly describing the contents of the file) attached.
I hear you when you say that people could be asking for your profile or at least separating with a sheet-fed profile.
PDF/X-1a has a number of significant benefits that could certainly benefit you the most important might be that the entire file will have been separated to CMYK and if it was correctly made, the SAME CMYK.
>
I don't think much of the output intent idea. It seems counterintuitive to me. I'm the guy controlling the output. I don't understand how someone upstream can do it more effectively. The output intent seems like we're throwing in the towel on RGB workflows.
>
<snip & paste>
>
I just don't think PDF/X is going to help color much. PDF/X-1x will help assure that things are CMYK, but that's about it.
PDF/X-3 is really able to carry the device independent workflow farther along a standardized path than what is typically being done today. If I want to include RGB (or CIE) colors in my compound documents then PDF/X-3 will allow it. The problem lies in how the rendering will be performed to the output device. Am I interested in maintaining the differences between colors or is corporate branding color accuracy more important? Do I want to leave that decision up to the printer? Probably not. No offense to the printer but they don't know what I (or my customers) want from the product. In a way, PDF/X-3 allows me to more accurately specify how I want my printed product manufactured without me having to do all the work (full access to press profiles, separation of all images) and without having to lock my document color down to one device or device type.
I prefer a hybrid approach. One of separating and printing to standards when possible and proofing with actual device profile for the true reality check.
Regards,
Steve
________________________________________________________________________
o Steve Upton CHROMiX www.chromix.com
o (hueman) 866.CHROMiX
o email@hidden 206.985.6837
o ColorGear ColorThink ColorValet ColorSmarts ProfileCentral
________________________________________________________________________
--
_______________________________________________
colorsync-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/colorsync-users
Do not post admin requests to the list. They will be ignored.