Color space of TYPE_CMYK

Hi,
I tried to create a color space of type CMYK as follows:
ColorSpace cmykCS = ColorSpace.getInstance(ColorSpace.TYPE_CMYK);But i got "Unknown color space" error message.
Exception in thread "main" java.lang.IllegalArgumentException: Unknown color spaceIt seems like we can only create colorspace of type CS_CIEXYZ, CS_GRAY, CS_LINEAR_RGB, CS_PYCC or CS_sRGB.
Then what is the use of TYPE_CMYK constant?
But it is known that one can use some formulas to convert between RGB and CMYK colorspace.
But is it really possible to create the ColorSpace instance of type CMYK?
any thoughts!!!!

Usually an embedded file is the same color space as the AI file.
Only when you open a PDF generated elsewhere this might also be something like multichannel.

Similar Messages

Can you show slideshow within Lightroom 4.4 in Adobe RGB color space?

Can you show slideshow within Lightroom 4.4 (not export out from LR) in Adobe RGB color space provided that you are using a wide gamut monitor which is capable and hardware calibrated & profiled to show such color space?
If this is possible, what is required to do so in Windows 8 and i7-4770 & HD Graphics 4600 platform or does LR take care of it automatically?
This is very basic question, however, I could not find a clear answer/info from LR documentation, so wish that someone can advice.

Those settings are probably stored in a plist somewhere in ~/Library/Preferences. If you can locate the appropriate file, you should be able to copy it to all the network user folders.

Image in PDF error - Expected end of color space

Hi friends,
I am displaying a PDF file in an webdynpro application. The contents are coming from the output of a RFC. The pdf file contains an image. While I am running the Webdynpro application the image is not coming. An error popup <b>"Expected end of color space"</b> is generated. But the texts of pdf file is coming properly.
Please help.
With regards,
Sekhar

Hi Sekar
We are facing the same issue. Have you managed to resolve this issue ?
Please advise
Regards
Vivek

Asking the Bridge Team: Bridge "working color space" setting when one does not have the Suite?

Common sense tells me there is really no such thing as a
"working color space" in Bridge, because
Bridge is not an image editor, just a browser
Therefore, this may turn out to be a purely academic question; but that doesn't keep my curiosity from forcing me to ask it anyway. ;)
Is there a way to set the Bridge
"color settings" when one does not have the suite?
The only Adobe program I keep up to date is Photoshop, so I've never had the suite. My version of Photoshop is 11 (CS4) and I run updated
(not upgraded) versions of Adobe Acrobat 7.x, Illustrator 10.x and InDesign 2.x. Consequently, the Synchronize color settings command is not available to me.
It seems to me that Bridge is behaving like a proper color-managed browser (e.g. Firefox with color management enabled), in that it displays tagged image files correctly and assumes sRGB for untagged image files. This normally works fine.
But what if I wanted Bridge to assume my
Photoshop color working space for untagged images
so that it behaves the same as Photoshop? I'm just curious, as I deal with a minuscule, practically negligible amount of untagged files.
My reason for bringing it up now is that I don't recall this being explicitly mentioned in forum replies when users inquire about color settings in Bridge. A recent post regarding Version Cue in the Photoshop Macintosh forum got me thinking about this. Just wanting to make sure that I'm right in my assumption that
there is really no such thing as a
"working color space" in Bridge, because Bridge is not an image editor, just a browser.
Thanks in advance.

Hi Ramón,
Thanks for sharing the outcome of your tests. However, I may have found a bug/exception to Bridge's colour management policy!
It appears that CMYK EPS photoshop files are not colour managed in Adobe Bridge, even if they contain an embedded ICC profile.
I've tried every combination in the EPS 'Save As' dialogue box, so it doesn't seem to be an issue with file encoding. Also, Bridge doesn't rely on the low-res preview that is held within the EPS itself.
My guess is that Bridge is previewing the CMYK EPS with a Bridge-generated RGB image, but it's being displayed as monitor RGB (assigned) rather than colour managed (converted to monitor RGB). For most users the difference will be barely perceptible, but the problem became very noticeable when using Bridge to preview Newsprint CMYK images on a wide-gamut monitor (images that should have appeared muted really leapt off the screen!).
How do I report this to the Colour Police at Adobe?!?

Lightroom's 4 color "spaces"

I’m working on designing an advanced photography course. This course makes use of Lightroom and Photoshop in the photographic workflow.
I’m learning and researching myself as I go along, and I feel I have reached a ceiling on what I can work out from the sources at my disposal thus far.
So I am turning here for help.
I am trying to clarify how tones and colours are affected from the actual scene through to the printed page. This might seem like overkill to some. However, there is a lot of misunderstanding and confusion, not to mention heated discussions amongst photographers about these issues. I’m experimenting with metering and colour / tone targets and my calculations are only meaningful if I understand how tones and colours are affected at every stage of the workflow.
Here’s how I understand it:
There are 4 (sort of) Colour “spaces” in Develop where a real-time dynamic preview of an image is rendered
1.       The “viewing space” (ProPhotoRGB Chromaticity co-ordinates, sRGB gamma)
2.       The “computational space” (ProPhotoRGB chromaticity co-ordinates, linear gamma – “MelissaRGB”)
(Martin Evening’s Lightroom 3 book published by Adobe press - Appendix B, section on color space page 628-632)
Below that, things get a little fuzzy. According to Jeff Schewe (Real World Camera RAW for CS5, page 32) there is a sort of
3.            “Native Camera Space” and of course there is the
4.            RAW data in the file on disk.
So to generate the dynamically rendered preview, the image goes through the four “layers” as follows (from bottom to top). This is almost certainly flawed, but one has to start somewhere when trying to work things out :-)
1. The RAW file is read from disk. Colorimetric interpretation is performed using a camera profile (e.g. Adobe Standard for whatever camera it is you are using). This process puts the image data into “Native camera space” (“Plotted” onto CIE XYZ with D50 white point)
2. In “Native camera space, the scene white balance (as selected by user, guessed by Lightroom or reported by camera) as well as additional camera calibration panel matrix tweaks “informs” the colorimetric conversion into Lightroom’s “computational space” e.g. Melissa RGB. The colorimetric definition of camera RGB primaries and white is re-DEFINED. The demosaicing as well as chromatic aberration corrections are performed in “native camera space”
3. Almost all image processing calculations occur computationally in the “MelissaRGB Lightroom computational space”
4. What is displayed on the screen, however, has an sRGB tone curve applied. This represents the “viewing” space. The histogram is generated from this and the RGB colour percentage readouts are generated from this as well. In addition, some slider controls from user input are weighted back through the tone curve into the computational space below.
Could someone from Adobe kindly help me to clarify the steps? Eric are you reading this? :-)
Thanks in advance

Sandy - Thanks for the link. The spreadsheets you posted on your site is quite helpful.
Jao – I think what you said goes to the heart of what I am trying to achieve here: “Photograph a grey target at the exact same exposure with the exact same lighting but with different cameras and you'll end up with different values in the raw files” Which is why I encourage photographers to experiment with their cameras in order to understand exactly how the camera will respond in the heat of a real shoot. Set up a scene; take a picture, open in Lightroom. What is clipped and why? Use a reflective spot meter. Repeat. Use a hand held incident meter. Repeat. How much can you reliably recover? Are you happy with what your meter considers the mid-point (and what you set your exposure for on the camera) or do you need to compensate? Just how much latitude do you have between what your camera histogram shows as a blown out highlight and what Lightroom shows as a blown out highlight. This relates to tone. I could go on with more examples, but by now, I am (hopefully) making more sense.
I’m merely trying to clarify that which is already public in order to form a coherent mental picture. And by mental picture I do not mean an accurate representation of the minutiae and maths involved. Think of a subway map. It represents a bird’s eye view of a transportation system in a logical fashion, yet it bears almost no resemblance to the cartographical reality of the physical topography. I really don’t care where the tunnels go, how they were dug, how they are maintained or where they twist and turn. What I AM looking for is a logical (not physical) map. This map tells me where the different lines begin and end, and where I can change from one line to the other. The most important quality of the map as a whole is that it provides context. You can tell, at a glance, how different lines interact with each other and even how it links to other entities such as bus stations or public landmarks.
As many have rightfully pointed out, I should not have to care about the maths/secret sauce/internal calculations. And I don’t. In addition, I am a very happy Lightroom user and I am very comfortable using it. I know what a user needs to know to get his picture from A to B. There is no shortage of information on how to accomplish that.
It might help if I illustrate what I am trying to do below:
Please excuse the low resolution, the maximum height allowed for upload is 600 pixels. The picture below goes on the bottom left of the "layer" picture above.
Even though there are certainly many mistakes in my diagram, this is a helpful visualisation. I derived this diagram from publicly available information. As the subway map, this is a logical (not physical) representation that provides context in a visual form. With a little help from people like Eric I am sure I can correct and expand it. The net result is an enhanced understanding of Lightroom and ACR and where it fits into the photographic process, both in terms of tone and colour.
I am not posting the entire chart here since I am not even certain that a 4 “layered” representation is an appropriate logical representation. I posted the spine of the chart with the 4 “layers” and one part that elaborates on the colorimetric interpretation between the two bottom layers. Comments and corrections are welcomed. And I am convinced that this can be accomplished without divulging anything confidential.

Rendering Chroma 4:2:2 with color space 0-255

Hello Everyone.
Just as a warning I'm fairly new to video editing, so I will probably not say this right. I have a screen recording that I used FRAPS to collect, and then I packaged it into an .AVI container w/ a lararith codec , and a 24bit RGB color scheme in video dub. I have then opened and edited that video in Premiere Pro and want to export it. The problem that I'm having is screen recording has a LOT of color between 0-16 and 235-255, so any broadcast color space I use makes the video look awful. I was wondering if anyone knows how I can render out with a 0-255 color space and a decent chroma subsampling (my guess is 4:2:2).
Thank you everyone for your help.

No, you are asking the right question, and I understand your problem. I just can't recreate it.
I just took a really wild Quicktime video I downloaded from Videoblocks.com that isn't anywhere close to being broadcast safe, and I exported it to a Windows Media file.
The first picture is a screenshot from the video. (it is a set of lower thirds in one video - I am just supposed to use one at a time of course.
The second picture is the Reference monitor from frame 12;24
I exported the sequence to a Windows Media file and then imported it, putting it right on top of the other video on the sequence so I could make sure to be on the exact same frame. The third picture is the reference monitor from the WMV file on the sequence. As you can see, there is not much difference. Some, but you have to look closely.
So, my question to you, since I do not use FRAPS, is what are your sequence setting? Did you just drop a clip on the New button to create a new sequence with the exact right settings? And, are you making the mistake of using the renders to help you export?
The problem is that I don't understand your source material. I guess I could download FRAPS from somewhere and give it a try? I am just a bit busy with other things today.

Open in external editor -- original color space workaround

I was frustrated--like other's whose posts I've read--by the fact that when opening files (tiff, jpeg, psd) in an external editor they are all converted to the Adobe 1998 rgb space.
I am working around this comfortably and by using some Automator actions that I got from Ben Long's Complete Digital Photography site: http://www.completedigitalphotography.com/?p=414#more-414
In my Pictures folder I have an Auto Processing subfolder with Photoshop droplets and lots of 'hot folders' tied to Applescript folder actions. I made two new folders: OPEN in Photoshop & IMPORT to Aperture
The Open in Photoshop folder has attached from Automator the following actions from the default Finder suite: Open Finder Items and Move to Trash.
The Open action is self explanitory, the next step of moving the recently opened file to the trash guarantees that I can't save to the source file. This forces Photoshop to do a Save As even if I hit command + S. The Save As prompts me for a location and I choose the Import to Aperture folder.
The IMPORT to Aperture folder has attached the Import Photos action from Ben Long's Aperture suite. By selecting the Delete the Source Images After Importing Them option and the Show Action When Run option I get a prompt asking what project to add the new files to and the old files are deleted from my hot folder after the import.
This isn't a perfect round trip solution because I still end up with two copies of the image in Aperture--even if I was just opening the source image to tweak an adjustment layer. I might create an Applescript that would prompt the user and delete the precvious copy of the image if desired.
Like many of you I was feeling blue yesterday about rumors of changes in the Aperture team at Adobe. Blue not because I beleive Aperture's going away, instead because I expect if this rumor is true that we will see some delays in the short term while the new team gets up to speed.
While I am waiting for that to happen I intend to use this discussion site to find creative workarounds for Aperture's current limitations and share them as widely as possible. Many of you are already doing the same.
Thanks!

Yes you could do that.
I was part of the alpha/beta test group for Adobe CS2. Most of my work was with scripting and automation, especially for Bridge. I did have a very good dialog with Bruce Fraser, Seth Resnick and other testers whose opinions are as good as fact in my book.
The consensus was that most digital cameras--certainly the pro models--had a color gamut substantially larger than Adobe RGB (1998). Note that ACR give the option of developing an image into sRGB, Adobe RGB, Color Match RGB, or Pro Photo RGB; 8-bit or 16-bit. That's the way I want it in Aperture.
If you use the perceptial rendering intent (this is almost certainly what Aperture is using as its undisclosed default setting) then you will compress the wider gamut of the camera into the smaller Adobe RGB (1998) gamut. If in Photoshop you used the Convert to profile command and choose the perceptial rendering you would probably expand the color gamut back out a little bit. Why bother? Aperture really should have options for open in external editor like the very good export version settings.
I have in my Aperture library a bunch of 16-bit grayscale scans and some CYMK files that seem to be working fine with the workflow above and Automator actions. (Lab files won't import.) I wouldn't want to go through the convert to Adobe RGB (1998) and reconvert to proper space with these files. My workflow is letting my store these files in Aperture and still edit in native color spaces in Photoshop with minimal effort for a round trip. I like it.
P.S. I said in my original post that it would be easy to write an Applscript to delete the orignial file in Aperture when reimporting a slightly modified Photoshop version. It may be possible but its not easy in the current version which only has a bare skeleton of Applescript functionality.

ACR 4.1 Color space(s)

Windows XP Bridge CS3
ACR 3.7 and previous used to give the option to convert to various colour spaces (profiles I always get confused here).
I've noticed that my Canon raw files show up in bridge as "colour mode RGB"
If I edit in ACR4.1 and save; they show up as "colour mode RGB and colour profile Adobe RGB" which is the color space of the camera (20D).
Files that I have previosly edited in lightroom (ACR 4) show up as "pro photo RGB"
I have my colour space in photoshop set to pro photo RGB so lightroom edited files open without a mismatch whereas files edited in ACR4.1 in bridge produce a colour space mismatch.
Am I missing something? or has the behavior of ACR changed in this respect since the comming of version 4?

It sounds like you have Camera Raw set to Adobe RGB. You can change that to Pro Photo RGB.
Along the bottom of the Camera Raw dialog box there should be a link that lists the color space, bit depth, file size, and resolution. Click on that change the Space from Adobe RGB to ProPhoto RGB.

The availability of color space in RAW, TIFF and JPEG files

This is useful if your new to DSLR photography.
This is Nikon response on my question in the discussion: View photo metadata
I'm assuming that you know that Adobe RGB shows about 50% and sRGB 35% of CIELAB color space.
In a DSLR camera like the Nikon D800 you can select a color space (Adobe RGB or sRGB) in the shooting menu.
In Adobe Lightroom 4.3 the RAW metadata shows no color space info. Therefore I asked why not?
In the (Dutch) Nikon D800 manual on page 84 (about RAW) and 274 (about color space) and Nikon FAQ website there is no descripton about the color space availability/behavior in RAW, JPEG and TIFF files.
In the book "Mastering the Nikon D800 by Darrel Young" on page 125 - 126 is written: "If you shoot in RAW format a lot, you may want to consider using Adobe RGB....."
All experts on this forum answered: color space does not apply/affect the RAW data file or RAW files have no color space.
The respone of Nikon Europe Support (Robert Vermeulen) was: In Nikon D800 NEF RAW files both color spaces (Adobe RGB and sRGB) are always physically available. In JPEG and TIFF files only the in the shooting menu selected color space is physically available. So the forum experts gave the correct answer!
Of course you can convert afterwards a JPEG or TIFF file with sRGB color space to Adobe RGB but you don't get more colors.
When you install the Microsoft Camera Codec Pack or FastPictureViewer Codec Pack they only show color space metadata for JPEG and TIFF files and nothing for RAW because color space "doesn't exist". I thought the codec packs removed the color space metadata for my RAW files.
Adobe Lightroom also can not show color space for RAW files because that "doesn't exist".

Van-Paul wrote:
The respone of Nikon Europe Support (Robert Vermeulen) was: In Nikon D800 NEF RAW files both color spaces (Adobe RGB and sRGB) are physically available. In JPEG and TIFF files only the in the shooting menu selected color space is physically available.
I still think this is an evasive answer that doesn't really pinpoint the exact chain of events that take place. They are:
1. The raw file contains the naked data captured by the sensor. This is just a very dark grayscale image.
2. In the raw converter it is encoded into a working color space to process the information. In Lightroom this is known as "Melissa RGB", or linear gamma Prophoto. It is also demosaiced to bring back the color information.
3. From Lightroom it can be exported to one of the familiar color spaces like sRGB or Adobe RGB. This is, in principle at least, a normal profile conversion.
These three steps are what the camera does to produce a jpeg. So the basic steps are the same, the camera is just doing it automatically (and usually butchering the image in the process...).
This Darrell Young is, I'm sure, an excellent photographer, but in this he is seriously confused and just propagating a common myth. Anyway, thanks for bringing up this discussion, hope you didn't object too much to the tone of the answers... Our only concern here was to get this right and with no room for misunderstanding.

Color Space Management & Final Color Output-not WYSIWYG?

I have constantly had problems with getting final output color to match what i am seeing on my monitors when color correcting. This has been a continual problem mainly with R3d footage and going to Prores...but for the sake of this discussion here is my prime example:
Start a new project in PrPro and clor from PrPro adding effects, 3 way color, 3rd party effects like Finesse and Colorista...then output the project to Tiff for master then convert from Tiff sequence to Prorest; H264 or anything else....But, when i output a prores file, and then open the prores file on its own--not brining it back into Premier...i notice a shift in colors....completely desaturated etc...this happens whehter i choose for gamma as "auto" or "none" when choosing codec settings for prores. I've had this continual problem for many years and the ONLY way i have found it to work is by using Apple's Color and then going to Prores....seems apple hardware and software work well together...but this cannot be an isolated incident with me only...AND coloring a project on your desktop and putting all that work into it and seeing it DIFFERENT at the end of the day is more than a let down...
...so maybe a discussion on properly setting a project for color work is in order...I came across another forum members website reToolednet and he had some great info on setting up the sequence timeline and video preview area that is great info...but even when i do that i cannot get a perfect match at the end of the output....Exapmples below all done in PrPro and then output to Prores 4444.
I've found info on Adobe site that does not seem current about setting project settings and color space, but no place in PrPro do i find that setting...is this only AE? OR...can we even do a proper color job within PrPr? or should that be done elsewhere?
Id like to go through the proper steps of setting workspace and color schemes for say a Prores output since that is likely 75% to 90% of everyone's deliverables in the tv realm....
Snapsot of Tiff sequence WITHIN PrPro (colored)
Final Output from PrPro to Prores--snap from actual QT prores file--(Desaturated)
When i began this project i had my sequence settings to R3d 1080p @ 29.97 and video previews to Iframe....
**NOW, i think i would have been better off to change video preview to my final output of Prores 4444...BUT, i tried that and still see a color shift.
**Note, i oriingally colored this on 5.5 with Matrox out to my color corrected monitors....and results on those monitors DO and WILL be diffrent than what you see on your computer screen....my monitors were set to rec709 and RGB at end of the line for viewing....but i see nothing within PrPro on how to set this....however at end of the day i do not get what i see on my preview monitors....

Thanks Jim....yes, i'm covered on all cc monitors and quite used ot viewing output on color calibrated...as well viewing both on the same platform/monitor....The BIG question is PrPr being able to do color work---and my question is why would it have all the color effects if it did not? But i agree with you....first place to start is can you do proper color work on PrPr AT ALL? no problem to do a quick web video...but can you properly color a for television product---I seem to think NO....i could not get colors in end to match....i can view out on PrPr view my I/O box (Matrox MXO2) and see great colors that i colored the project on to my FSI color corrected monitor....but then when i view the ProRes file back (not on PrPro)...but on it's own with its own codec engine...this is where things go awry and stray from colors i originally put on the images...
But this is a PARAMOUNT subject as Pr is offering coloring....i hate to bring this in, but in FCP i can get accurate colors on my Matrox and same when rendered out to Prores file....Again, i think Apple plays well with apple.....but as you say, there are a great number of varialbes involved in the preferences etc...within PrPr...seems to me AE may be better just by reading about it...but why not both?

Color problem with ProPhoto RGB color space

Hi, everyone,
I have wery special problem I think. I use MacBook pro 15" with retina display, adobe Photoshop CC and when I export RAW (from Nikon D7000) from Lightroom 5 to Photoshop with settings: 16 bit TIF, color space: ProPhoto RGB I have a problem with displaying the correct colors. As you can see in this picture:
My problem are some "green" artefacts in absolutely black and white picture. I tried myself to solve this problem and found the following facts: when I convert picture into Adobe RGB or sRGB color space is everything OK - without green artefacts.
But here is one important fact: I have calibrated monitor by datacolor spyder4elite and problem with ProPhoto RGB incorrect color displaying is only when the color calibration configuration is loaded. When I change my display calibration to standard apple color LCD profile than is everything OK.
But using uncalibrated monitor and also Adobe RGB color space are no right solutions for me.
My question is why I have problem with displaying ProPhoto RGB color space in photoshop under calibrated monitor profile and can anybody help me please?
Thanks for answers.

That's a classic example of the basic problem with 16 bit color. There is no solution that I know of.

How can I convert to NTSC color space?

I'm developing graphics for a Roku application which requires that colors be broadcast safe in the SDTV NTSC color space. For instance, I cannot have true white or true black colors. They are not allowed.
There is an RGB color space available. When I create a new document in CS6, I can select that profile as the color space. However, I am still able to paste in images that have pure white in them. When I save the document for web & devices, it still saves with the pure white.
I'm positive I've done this conversion in the past before, but I cannot get it working in CS6. I've tried going to Edit -> Assign Profile and Edit -> Convert to Profile, but in both cases the colors I am dealing with still end up pure white.
How can this be done?

Hi,
See if Filter>Video>NTSC Colors makes any difference.

Color Space on Thumbnail Image Variants

Hi all-
I'm loading some CMYK images into my repository (5.5 SP05) and trying to use the default thumbnail variant in a web application. For some reason, even though the color space of the thumbnail is set to RGB, it doesn't get converted when the thumbnail is created. This results in a .jpg that is CMYK (and isn't understood by a browser).
If I create a custom variant as .jpg and of the RGB color space, it works fine after generation. Is this a bug? Or is there a way to force the generation of thumbnails? I was trying to not have too many variants in my repository because I was worried about bloating it. Perhaps this shouldn't be a concern, but it still seems as if the thumbnail should get converted to RGB according to the settings in the Console. Any thoughts?
Thanks
Tim

Tim,
Sounds like this may be a bug. Since the Thumbnails are set to RGB, and cannot be changed, it seems as though they should be generated in RGB color space.
One thing to try. Go into the images table, right click on an image in the records window, and select Generate Thumbnail. I believe it will actually regenerate the thumbnail. Maybe this will regenerate with the RGB color space. That's my only idea. Other than that you really don't have much control over the thumbnails.
Regards,
Tim

PDF in CMYK color space?

I'm working on the most recent version of Pages from iWork 2008 running on the most recent version of Leopard, and I have to create a PDF in the CMYK color space for publication, but I do not have Acrobat Distiller.
Is it possible to create a CMYK PDF with ColorSync filters? I have tried using the "Generate PDF-X/3" filter, with "Generic CMYK" as the target profile and transparency flattening, but the printer still says that my PDF is in the RGB color space. If not, is there any other way to create a CMYK PDF from Pages or to convert a RGB PDF or PostScript file to CMYK using ColorSync Utility? Are there any alternatives without purchasing Adobe Acrobat? What about if I first convert images to the CMYK color space before importing them to Pages?
I have seen similar questions posted elsewhere, but I can't find a straight answer anywhere.

1. Obtain the ICC profile from the printer for his output device.
Correct. Either the shop printing condition or an ISO 12647 printing condition to which the shop can configure and calibrate the printing condition it is selling you. If the latter, you can get default ICC printer profiles for standard printing conditions at www.eci.org.
2. Create a filter in ColorSync Utility for generating PDF/X-3 documents with the ICC profile as the output intent (besides flattening the transparency and applying an appropriate resolution).
Correct.
3. Print to PDF in Pages.
Incorrect.
Your PDF/X-3 filter will become available in the system dialog for File > Print > Save as PDF. In saving as PDF you pick your PDF/X-3 filter as the template for the save process.
4. Use ColorSync Utility to modify the resulting PDF with the filter I created in ColorSync Utility.
(or 3-4. Print directly to PDF through the filter from Pages)
Your second step to combine 3 and 4 is correct, your first step 4 to save to disk and then postprocess in the ColorSync utility is incorrect.
5. Send this PDF/X-3 to the printer.
Correct.
It seems that no hard conversion from RGB to CMYK should be necessary if I take these steps, is that correct?
Correct.
If I send the printer a PDF in the RGB color space, should it cause problems for him to convert the PDF himself to the color space of his output device?
No.
You create three channel RGB images in the RGB colourant data model (it's just a model, it is not a colour space which a size and a shape of the gamut).
You save your colourants to disk in TIFF or PDF format with the ICC profile for the capture colour space (e.g. the ICC profile for your specific scanner with a Kodak EktaChrome IT8) or correction colour space (e.g. Joseph Holmes' RGB working space for EktaChrome). This ICC profile is the _colour space_ that you can view in the ColorSync Utility as a specific size and shape of gamut. The colour space determines what colours the colourants in your TIFF or PDF image should reproduce on different colour devices.
You now have a pagination with photographic objects in three component RGB, and you know what colours those colourants are supposed to reproduce. You then include the production profile for the printing condition. Your source profiles must match to this destination profile in the matching session, so all your photographs get converted to the SAME ink limit, the SAME graybalance and so forth. This unifies the inking behaviour and the colour formation for your printing.
If you imagine that in your pagination you place photographs which are manually converted into four component CMYK using a different ink limit, a different graybalance and so forth then you have not unified your inking behavour and colour formation for the printing process. This is IDIOTIC because the only way to correct in this case is to change the calibration of the individual inking zones on the offset press - increasing or decreasing the cyan, magenta, yellow or black for that zone.
It used to be that lithography on the press was the only way to work. This was in the days of EPS and EPS DCS, and before that in the days of photographic printing masters pasted together manually piece by piece to make the printing planes. Nobody in their right mind works that way today.
/hh

PDF ERROR! ICC Based color space contains/ alternate key

Can somebody help me?
When I put in Rip (Agfa Apogee X) a pdf I receive the follow error: ICC Based color space contains/ alternate key.
I don t know where is the problem? There Is a problem with pdf? or it is a problem in my Rip? how can I solve this?

That's pretty odd, because (techncnically) an ICCBased color space must contain an Alternate key, so why complain about it? It certainly seems specific to your RIP, so I would check with Agfa what it means and whether it is a check you can turn off, or if an update is available.

Color space of TYPE_CMYK

Similar Messages

Maybe you are looking for