Inadvertently saving in unwanted color space.

In ACR (5.3) the color space to be used when saving an image in set in Workflow options. Since I change this setting to see how much is clipped in various spaces (aRGB, sRGB), I sometimes forget to re-set it to the space I actually want to use before actually saving the image or opening in PS (as a smart obj). Of course, I can return to ACR, change the workflow setting and re-save. I am concerned that some image information is being lost when this is done. These are drum scanned images originally in Ektaspace. For example, I inadvertently save as sRGB (I assume it convert?). If it does these types of conversions, I would expect that image information would be lost and not recoverable. I'm hoping that someone can confirm my suspicion or educate me. Thanks.

Paul,
Yes, if you open your
raw image into Photoshop in a smaller color space, such as sRGB, you will lose color range in the Photoshop image,
but your raw image file remains untouched. You can always discard the file you opened in Photoshop and go back to your raw space and open a new copy.
ACR always opens a copy of the raw file. It treats all raw files as read-only files. Even the adjustments you make in ACR do not affect the raw data, they are all kept in metadata and are not applied to the pixels until you open the copy in Photoshop.
>Of course, I can return to ACR, change the workflow setting and re-save. I am concerned that some image information is being lost when this is done.
Absolutely not, just see above.
>These are drum scanned images originally in Ektaspace.
Ah, so they are
not raw images at all. Nevertheless, what I wrote above still applies to your images, presumably saved as TIFFs. Any and all adjustments you make in ACR are still kept in metadata only.
Keep in mind, however, that TIFFs do not give you anywhere near the latitude and flexibility that raw images afford. But you know that, of course.

Similar Messages

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

CoordinateMapper is not working properly when converting Depth into Camera then into Color Space

Hello everyone,
I am trying to map depth point to color space in the defined portion of the depth frame data in my Kinect v2. I am using CoordinateMapper for conversion between various spaces.
Below is the snippet of the code-
private void KinectMultiSourceFrameArrived(object sender, MultiSourceFrameArrivedEventArgs e)
var reference = e.FrameReference.AcquireFrame();
ColorFrame ColorFrame = reference.ColorFrameReference.AcquireFrame();
DepthFrame DepthFrame = reference.DepthFrameReference.AcquireFrame();
if (ColorFrame != null && DepthFrame != null)//Do not proceed, if any frame is expired
ColorFrame.CopyConvertedFrameDataToArray(ColorFramePixels, ColorImageFormat.Bgra);
Image<Bgra, byte> ColorFrameImage = GetBgraImageFromBytes(colorFrameWidth, colorFrameHeight, colorFramePixels);
DepthFrame.CopyFrameDataToArray(DepthFrameData);
CoordinateMapper.MapColorFrameToDepthSpace(DepthFrameData, DepthSpacePoints);
for (int index = 0; index < DepthFrameData.Length; index++)
ushort depth = DepthFrameData[index];// Get the depth for current pixel
if (depth > depthMinReliableDistance && depth < depthMaxReliableDistance)//Ignore outside points
CameraSpacePoint point = CoordinateMapper.MapDepthPointToCameraSpace(DepthSpacePoints[i], depth);
//Some processing on CameraSpacePoint are cropped while putting the code here
ColorSpacePoint colorSpacePoint = CoordinateMapper.MapCameraPointToColorSpace(point);
DrawMarkInImage(ColorFrameImage, colorSpacePoint);
ColorImgBox.Image = ColorFrameImage;// See the image
if (ColorFrame != null) ColorFrame.Dispose();
if (DepthFrame != null) DepthFrame.Dispose();
//Convert the bytes into image using EmguCV
Image<Bgra, byte> GetBgraImageFromBytes(int Width, int Height, byte[] Pixels)
Image<Bgra, byte> Image = new Image<Bgra, byte>(Width, Height);
Image.Bytes = Pixels;
return Image
//Draw circle (Just for debugging purpose)
void DrawMarkInImage(Image<Bgra, byte> ColorFrameImage, ColorSpacePoint ColorSpacePoint)
Point CircleCenter = new Point((int)ColorSpacePoint.X, (int)ColorSpacePoint.Y)
ColorFrameImage.Draw(new CircleF(CircleCenter, 2), new Bgra(0, 255, 255, 255), 1);
However, when I tried to converting the depth directly to color space, it works well. But since I am doing processing over CameraSpacePoint, I need to make above working.
Somebody please tell me where is the error and how to resolve it.

Hi Carmine,
I apologize for this confusion. I am trying to process only a defined portion in the depth frame, which resides between MinReliableDistance and MaxReliableDistance. For the testing purpose, I kept my Kinect v2 in the table facing towards the floor at the
height of 1 meter from the floor. Some objects are kept in the floor. Based on the depth information, I just want to mark their top face.
I tried following two methods-
Method1: First compare the depth and ignore the undesired depth points. Then find out CameraSpacePoint of this depth point. Do the processing, whatever is needed. Now convert this CameraSpacePoint into ColorSpacePoint and draw a mark on this point in the
color image. Below is the code snippet-
CoordinateMapper.MapColorFrameToDepthSpace(DepthFrameData, DepthSpacePoints);
for (int DepthIndex = 0; DepthIndex < DepthFrameData.Length; ++DepthIndex)
ushort Depth = DepthFrameData[depthIndex];// Get the depth for current pixel
if (Depth > depthMinReliableDistance && Depth < depthMaxReliableDistance)
CameraSpacePoint CameraSpacePoint = CoordinateMapper.MapDepthPointToCameraSpace(DepthSpacePoints[depthIndex], Depth);
//some of the code is removed while putting it here
ColorSpacePoint ColorSpacePoint = CoordinateMapper.MapCameraPointToColorSpace(CameraSpacePoint);
if ((ColorSpacePoint.X >= 0) && (ColorSpacePoint.X < ColorFrameWidth) && (ColorSpacePoint.Y >= 0) && (ColorSpacePoint.Y < ColorFrameHeight))
DrawMarkInImage(ColorFrameImage, ColorSpacePoint);
DisplayImage(ColorFrameImage);
MinReliableDistance is 676mm whereas MaxReliableDistance is 850mm. (Just for this setup)
The above code doesn't work. It is unable to find out the objects standing in the floor. Please see attached image and notice the yellow marks are not in correct locations.
Method 2: Just to check the setup, I tried this method but I can't go with this method further (Since I need the points in CameraSpace. In this method, I first check for valid depth point. Then corresponding color pixel is picked up from the ColorFramePixels
using ColorSpacePoint. Below is the snippet-
CoordinateMapper.MapDepthFrameToColorSpace(DepthFrameData, ColorSpacePoints);
Array.Clear(DisplayPixels, 0, DisplayPixels.Length); //Clear pixels to black
for (int DepthIndex = 0; DepthIndex < DepthFrameData.Length; ++DepthIndex)
ushort Depth = DepthFrameData[depthIndex];// Get the depth for current pixel
if (Depth > depthMinReliableDistance && Depth < depthMaxReliableDistance)
ColorSpacePoint Point = ColorSpacePoints[depthIndex];
int ColorX = (int)Math.Floor(Point.X + 0.5);
int ColorY = (int)Math.Floor(Point.Y + 0.5);
if ((ColorX >= 0) && (ColorX < ColorFrameWidth) && (ColorY >= 0) && (ColorY < ColorFrameHeight))
int ColorImageIndex = ((colorFrameWidth * ColorY) + ColorX) * BytesPerPixel;
int DepthPixel = DepthIndex * BytesPerPixel;
DisplayPixels[DepthPixel] = ColorFramePixels[ColorImageIndex];
DisplayPixels[DepthPixel + 1] = ColorFramePixels[ColorImageIndex + 1];
DisplayPixels[DepthPixel + 2] = ColorFramePixels[ColorImageIndex + 2];
DisplayPixels[DepthPixel + 3] = 255;
Image<Bgra, byte> DepthFrameImage = GetBgraImageFromBytes(DepthFrameWidth, DepthFrameHeight, DisplayPixels);
DisplayImage(DepthFrameImage);
Please see the attached output image. You can notice the internal pixels are picked from color fame and outside pixels are black as expected.
Output image of method 1. Notice the yellow marks are not in proper place. They should lie on the top face of objects
Output image of method 2. Notice the unwanted area and top face of the standing object are black (as expected)-
Hope is clears your doubt.

Change Aperture previews color space from Adobe98 to sRgb

Hi,
I'd like to change the default color space for the jpg previews that Aperture generates from the masters of my library.
I now have all my jpegs saved as Adobe98 but it's important for me to have them saved as sRGB because when third party apps and devices go to read them, they can't reproduce the right colors if they find the wrong color profile.
Thanks in advance for your help!

I don't know how many different ways to say that you cannot change the color space for previews. The files themselves have specific image data that corresponds to a specific color profile that is Adobe 1998 you cannot change the way Aperture generates these. Changing your system has nothing to do with it.
As for work-flow - If you need this to work and it doesn't then it never has so I really don't see how it is changing your work-flow that never existed?
RB
Ps. External devices like projectors work fine as long as your presentation software respects the source profile and has an output device profile - what kind of "device" are you using?
Message was edited by: rwboyer

Color Space Issue with Wide-Gamut monitor

Since getting my new (and carefully calibrated) LaCie 324 monitor, I have noticed that RAW (and maybe other) images exported from Lightroom as
sRGB jpegs look washed out and slightly green when viewed outside of Lightroom (IE8, Firefox, ACDSee, windows 7 viewer). It seems not to matter whether the external application horors embedded color space profiles or not, since the unmanaged ones assume sRGB.
When I bring one of these jpegs into PhotoShop it still looks bad, and not what I see in Lightroom. However, if I Assign the Adobe RGB profile to the image, it immediately looks like the Lightroom version. And if I then Convert that image to sRGB and save it, it looks fine everywhere, even on an uncalibrated standard Dell TN LCD display.
Any ideas what I might be seeing here. A friend with the same monitor has the same problem, which is what is leading me to suspect the monitor.
The first image here is converted from Lightroom with sRGB color space. The second was first assigned the Adobe RGB color profile and then converted and saved out again as a jpeg.
Converted Only

I downloaded and ran the program. My version number appears to be 2.1 if I read the numbers right.
I am still at a loss as to why my sRGB jpegs only look right if I assign the wrong profile to them.
Here are the settings in Windows 7 for color management. The highlighted profile is the one just created for my monitor. Display 2 is my main display. Note the "viewing conditions" setting on the advanced tab. Do you think the rendering intent might be at fault here? In Lightroom, should I use Perceptual over Relative or vice versa?

Color space question for photoshop cs on mac os10

I'm sure this has been beaten to death here before. I've been dealing with color space issues for months now, and I'm about at my wits end.
I realize that I should be saving in sRGB in order to get the same looking photo on the web that I get in photoshop. I go image-mode- convert to profile- destination space- profile: srgb profile. I've tried saving for web. I check "ICC" when I do that. When I just save an image as a jpeg (from a tiff), I check the box that says, "embed color profile." Still, my images look washed out on my website (which I made with iweb)- which I'm trying to put my images in a new web interface (flash palette) and my images STILL look washed out. The weird thing is, I NEVER have this issue when I upload images to photobucket or to the photography forum that I frequent.
What the heck am I doing wrong??
Thanks,
Hope

>> images are still a bit washed out with a warmish/ yellow cast to them, particularly, my black and white images
Here is a simple test to help evaluate if the monitor profile is reasonably good:
Open a RGB file in Photoshop (flatten if not already flattened).
Press M key> Drag a selection> Com+Shift+U (Desaturate).
Com+Z (to toggle back and forth).
If the unsaturated selection looks neutral you've got a reasonably fair monitor profile.
If selection has color casts (not neutral) -- you have a bad monitor profile
+++++
Here is a simple test to help evaluate if a bad monitor profile is whacking out your Photoshop color:
Monitors/Displays (control panel)> Color> highlight AppleRGB or sRGB (don't run Calibrate), quit and reboot.
If the Photoshop colors are back under control, then the problem was most surely a bad monitor profile go back into Monitors/Displays> Color and Calibrate a good profile highlight (load) sRGB, or preferably, the monitor's OEM profile as a starting point.
If you are using a puck, it is likely defective; or your monitor hardware is the culprit...search it on Google by model number

Photoshop not seeing export color space setting in Lightroom 4

MY LR or PS programs are not acting as expected.
When my Lightroom 4 is set to export to Photoshop in either the sRGB color space or the AdobeRGB color space, and Photoshop is set for the sRGB space, Photoshop gives a color mismatch error in both cases, saying the image is an AdobeRGB embedded image. However, if the color space in PS is set for AdobeRGB, even if the export setting in Lightroom is sRGB, there is no mismatch error.
Apparently, PS sees every image as embedded with AdobeRGB.
I have a Sony NEX6 camera. I have taken pictures in the camera sRGB color space and the AdobeRGB space, which I used for this test. Since I shoot in RAW, this should not matter, so I don’t think it is the issue, and, in fact, I get the same result no matter which color space the camera is in.
If LR export and PS color space are the same, why should there be a mismatch, and why is PS not seeing the sRGB space? Might there be a setting in Lightroom or Photoshop that I am missing?

howdego wrote:
I am, however, trying to decide on the right color space to use, which is how I noticed this problem. I rarely make prints of my photos. I make bluray movies using Proshow Producer. I recently got a new monitor and Samsung LED HDTV, and found that my photo videos did not display right and I am trying to find out why. I found the normal viewing settings of the TV have too much color and sharpness, so I established another group of settings for photos, which helped. However, I am still not satisfied.
These are two separate but related issues.
1) It's almost impossible to get accurate Color and Luminance level rendering inside LR if you don't use a hardware monitor calibrator to adjust your computer monitor.
2) LCD TV's use settings to "enhance" color, brightness, and contrast that is usually very, very inacuuarte. But this is what most non-photography people seem to like so TV manufacturers crank up the "default settings." I also have an older 52" Samsung TV (LN-T5265F) that I've manually adjusted for more accurate color. Try using the 'Movie' mode, which is the most accurate mode and turn the Backlight setting down. Here are the settings I use with my Samsung TV. I assume your Samsung TV's controls are similar:
Setup Screens
HDMI 1 (Cable Box) & Coax (Cable)
HDMI 2 (Panasonic Blu-Ray Player)
PICTURE - 1
Movie
Standard
Dynamic
Movie
Standard
Dynamic
Contrast
82
82
82
82
82
82
Brightness
43
45
45
43
45
45
Sharpness
25
25
35
15
15
25
Color
42
45
45
44
45
45
Tint
77 R
77 R
84 R
77 R
77 R
84 R
Backlight
5
6
7
5
5
6
PICTURE - 2
Color Tone
Normal
Normal
Normal
Normal
Normal
Normal
Detailed Settings
Black Adjust
Off
NA
NA
Off
NA
NA
Dynamic Contrast
Low
NA
NA
Low
NA
NA
Gamma
-1
NA
NA
-1
NA
NA
Color Space
Auto
NA
NA
Auto
NA
NA
White Balance
R-Offset
13
NA
NA
13
NA
NA
G-Offset
15
NA
NA
15
NA
NA
B-Offset
17
NA
NA
17
NA
NA
R-Gain
15
NA
NA
15
NA
NA
G-Gain
12
NA
NA
12
NA
NA
B-Gain
17
NA
NA
17
NA
NA
My Color Control
Pink
15
NA
NA
15
NA
NA
Green
15
NA
NA
15
NA
NA
Blue
15
NA
NA
15
NA
NA
White
15
NA
NA
15
NA
NA
Edge Ehnacement
On
NA
NA
On
NA
NA
xvYCC
Off
NA
NA
Off
NA
NA
Digital NR
Low
Low
Low
Low
Low
Low
Active Color
Off(NA)
Off(NA)
Off
Off(NA)
Off(NA)
Off
Dnie
Off(NA)
Off
Off
Off(NA)
Off
Off
SETUP - Screen 2
Energy Saving
Off
Off
Off
Off
Off
Off
SETUP - Screen 3
HDMI Black Level
Low
Low
Low
Low
Low
Low
Film Mode
Off(NA)
Off(NA)
Off(NA)
Off(NA)
Off(NA)
Off(NA)
howdego wrote:
So it occurred to me that some colors might be wrong, or too saturated, because I am not seeing them on my monitor as they will appear on the HDTV. I am thinking that since sRGB is my final color space, I would try to do everything in the sRGB space, including setting my monitor to sRGB (I have a Dell 2413 which supports adobeRGB too). I was inn the process of trying this when I found the issue at hand. Might you have any thoughts about this color space choice
If you have a wide-gamut monitor you are better off using it in Adobe RGB mode with a monitor calibrator. But then the monitor will not look correct in non-color managed applications:
http://www.gballard.net/photoshop/srgb_wide_gamut.html
You can circumvent this issue by using your monitor in sRGB mode, but I'd still suggest you use a hardware monitor calibrator. Either way it is imortatnt that you have a proper monitor profile assigned in Windows or OS X Color Management. The monitor manufacturer provides these, but they don't always work well with LR for numerous reasons.
To insure the best image quality you should do all of your editing in PS using 16 bit TIFF with ProPhoto RGB profile format until you are ready to Export. For use with ProShow you can use TIFFs or JPEGs, but use sRGB color profile to avoid any color management issue. JPEGs are fine and a LR Quality higher than 80 (10 in PS) is a waste of disk space for slideshow images.
In short you've got a lot of "variables" between the uncalibrated monitor and out-of-the-box non-adjusted TV. The former requires a good hardware calibrator aad the latter a good "eye" to adjust it.

How to set PS for the most reliable image previews and how to make sure the color spaces are the same across plateforms

I've been having an ongoing problem with some of my images changing color/luminance values after merging or flattening an image. This seems to most often happen if I use one of the filters (like crosshatch or notepaper, not sharpen or blur). I can make a copy using command/option/shift + E which most often will look exactly like what's on screen.
Some people have suggested that it's to do with resolution, PS showing me a low resolution image but I don't think so because the histogram changes -- sometimes in a big way, but most often those spikes in the luminance levels are shaved off. Also, when I have the image open at 100% and effect a merge/flatten, the color changes.
I'd like to know if there's a way to have PS show me one for one what I'm working on while I'm working on it, or if there is a way to control the color profiles when I'm saving. My best guess at this point is that there is a color profile mismatch going on somewhere. I just don't know where to look for it.
Typically I work in 16 bit, so my color space is set to ProPhoto RGB; my camera is set to the Adobe color space;
color management policies are set to preserve color profiles;
conversion options --> intent is set to relative colorimetric.

But it is calibrated. I use Xrite 1 and update it every month (on the first).
The colors can be really off. Here's an example.
https://flic.kr/p/r6A1Zd (what I want) https://flic.kr/p/qc5QTD (not what I want)
Also, I can't see how the bit depth will have any effect since the change in color happens in PS when I merge or flatten. It's 8 bit through the editing and 8 bit when I flatten it.
Have you any suggestions on what I can do on the computer side?

"Unsupported Color Space" error trying to open b/w PDF in PS

This glitch has occured periodically in every version of PS I've ever used. I'm sick of getting it. Let me emphasize" I'm working with a b/w all-text image scanned into a PDF using the "text" setting on my scanner. In past attempts with Adobe tech support to get this fixed, it ends up having something to do with a glitch in PS programming, which gets fixed after an hour and a half of being treated like an airhead by the support tech and finally going into the secret settings area of PS and fixing it.

I did some tests on that image (Color Space: Indexed Device Gray) in Acrobat Pro.
If you want to open it in PhotoShop you could convert the whole PDF to RGB.
There is a Single Fix Up in the Preflight section of Acrobat Pro for this.
See screen shot of Acrobat Pro 9 here (in X or XI this feature is also available):
After using that fix up and saving the PDF to a new name, the TouchUp Object tool can use PhotoShop to open the image as an Indexed 8Bit Channel image in PhotoShop.
You can now convert to Grayscale in PhotoShop if you want…
Uwe
Message was edited by: Laubender (some typos)

Watermark, color space, and transparency problem

I'm having a problem with inserting a watermark image into my pdfs.
I created the watermark image in Photoshop. It is 8-bit gray with a transparent background. I saved it as a pdf (pdf 1.4 to allow transparency).
The main pdfs (to be watermarked) are created through a seperate process (they are scans of old book pages). The pdfs are produced from 8-bit gray tiff images, but I cannot determine what color space the these pdfs are.
To the problem: in Acrobat 9, when I insert the watermark above, all of the blacks on the page shift to grey, as if the opacity was shifted lower. The opacity is set to 100%, so this should not be a problem! The watermark does have a transparent background, though.
Since this seems to be a color space conflict, if I save the watermark PDF in CYMK or RGB, it does not cause the tonal shift (blacks remain true), but the watermark now has an opaque background. I need it to be transparent, as the background of the files to be watermarked are not tonally consistent (old discolored paper).
I guess these are my questions:
(1) Is there any way to determine the color space of a PDF? File->Properties does not list color space.
(2) Why does the watermark PDF, saved in CYMK or RGB, not allow a transparent background? Is this an Acrobat issue or color space?
(3) Does anyone have an idea on how to solve this? :)
Thanks a bunch.

First, I have 2 questions: 1) How do the color and watermark background look when you have Advanced > Print Production > Output Preview open? 2) What version of Acrobat are you working in?
The most common reason that people see an almost "washed out" appearance (or looking as though additional opacity is applied) is due to a bug in Acrobat 8. This was fixed in the 8.1 dot release. One way to determine if this is what you are running into is to view the file with the Output Preview dialog open. If it views correctly then, make sure you have the update installed.
I don't work with watermarks, but understanding the general concept of watermarks it seems like a reasonable guess that they would use overprinting. I'm wonder if this is what is affecting the display of them (non-transparent background) since Acrobat needs Overprint Preview ON to accurately display objects with overprint flags . As with above, turning on Output Preview will help you deduce if that's what is happening since Output Preview automatically enables Overprint Preview (which is off by default).
BTW, Preflight will let you know what color spaces are in PDF file. Run any Profile. In the results panel, drop down the "Overview" section. There you will find a color spaces section listing the color spaces of the document.

Which color space to save still images for FCP?

When saving still images as TIFF files to be brought into FCP, what color space should the files be saved in? The Adobe color space or SRGB, or other?
Thanks.

sRGB/JPEG is the best because all the color information is encoded in the actual image when you create a JPEG, as JPEGs don't carry color space information with them, like .PSD and .TIFF do.
As for sRGB, that is as close as there is to a universal color space for monitors, and you are least likely to find a surprise when you check across many monitors. The tradeoff is a reduced color gamut if you display on a well calibrated broad gamut monitor.
The gamma matters all the way through, if you want what you see in Photoshop to match what you see on a calibrated display monitor. The newest Photoshop, and Lightroom, use a native gamma of 2.2, which matches all video displays (not computer displays). If you generate JPEGs from them, they will have a gamma of 2.2. You then need to import them into FCP with a gamma of 2.2 for the interpretation. If you go directly to DVD from there, all is fine. If you go to a Quicktime movie, you need to know what the codec you plan to use will do. ProRes maintains the existing gamma, H.264 lightens up to 1.8, as does animation. I haven't characterized the others.

Color space conversion problem when importing JPEG's

Hi,
I'm currently playing with the trial version of LR. While importing JPEG's with different color spaces (sRGB and Adobe RGB) to LR I've noticed a strange effect: There is a small but noticable difference in color, depending if the JPEG was previously saved in AdobeRGB, or sRGB. All the images I've tested so far should not contain critical colors that exceed normal sRGB. When opened in CS2 both versions of a JPEG, AdobeRGB and sRGB, typically look perceptually identical, no matter if I leave the sRGB image to sRGB, or convert it to the working space (AdobeRGB). Also my color-managed image viewer behaves as it should. So I don't think it's a matter of the different color spaces.
Looking at the imported images in LR I would say that the AdobeRGB image is correctly converted while the sRGB image suffers from a slight reddish cast, most noticable in skin tones. The effect is not as strong as if I would load the sRGB image into CS2 and skip color conversion to my working space (AdobeRGB).
The sRGB versions of the JPEG's were obtained from the AdobeRGB JPEG's using CS2 for conversion.
Anyone else here experienced a similar problem? Is this a bug in the xRGB-to-ProPhotoRGB conversion of LR, or a feature?
/Steffen

Hi Uli,
thanks for pointing me to your thread. I followed the discussion with great interest. Actually, I think the effect I am describing here is of different nature and a LOT stronger, at least for the type of images I've tested.
I did some more experiments yesterday with interesting results:
1) When I export a processed RAW from LR to JPEG or PSD, no matter what Color Space (I tested AdobeRGB, sRGB and ProphotoRGB), and re-import those JPEG/PSD's to LR, they look absolutely identical to the RAW I started with. Also, at first glance, they look similar when opened in CS2, but only because I tested with color images. I can indeed see small differences when testing with B/W, as you described in your "Color management bug" thread.
2) When I change the color space of an PSD or JPEG inside CS2 (I used the default setting 'relative colorimetric') and save it to JPEG and then import this JPEG to LR, colors are far off. The strength of this mostly reddish color cast depends on the color space of the imported JPEG, strongest for Prophoto, less strong for Adobe and sRGB. Interestingly, when I convert the color space inside CS2 and save the result to PSD, it will display correctly when imported in LR. Another interesting side effect: the thumbnails of LR-exported JPEG's in the "Open" dialogs of CS2 and LR (I guess those are not color-managed) show the typical color-flatness for the Adobe and even more the ProPhoto version. For the CS2-converted JPEG's, all thumbnails look just a colorful as the thumbnail of the sRGB version.
3) Such an image which doesn't display correctly in LR will keep its color cast when exported again to a JPEG (not sure about PSD). So something goes wrong with the color conversion during the import of such CS2-converted images.
My explanation so far is that CS2 uses a slightly different way of coding the colorspace information in the metadata of JPEG's which somehow prevents LR to recognise the color space correctly.
Can you confirm this behaviour?
Steffen

Photoshop 7.0 - Problem Retaining Original Color Space After Export

I just registered for this forum & would appreciate your input.
I convert Canon RAW files to jpgs & always embed the sRGB color profile & color space in the converted files.. Once I open & edit one of these files in Photoshop 7.0 & save it, the color space is changed to Abobe RGB. I have tried many changes via Edit > Color Settings, but still the same results. I thought that the settings preset "Web Graphics sRGB Color Space" would do the trick - but it doesn't.
If I go to Image > Mode > Convert to Profile & select sRGB for both source space and destination space for an opened jpg file, the sRGB color space is embedded in the saved file - even after reopening in PS, editing, and re-saving. Must I do this for each jpg I edit?
Please educate me how to set PS so all exported files either retain the sRGB color space or have PS embed the sRGB color space upon export.
Thank you.

This is of course, an issue of permissions so there may be no solution.
Absolutely not. Don't jump to false premature conclusions. As Noel said, it solely depends on detecting a previous install/ verifying the install media. Since the latter is out of the question, the first would be way to go, the point being that it merely looks for the respective registry keys in HKEY_Local_Machine\Software\Adobe. Lucky for you, back then nobody cared to encrypt such stuff so it could be hacked in manually. Off hand I'm just not aware of the specific structure for the keys, though, but a little digging might turn up that info. In fact it would be almost identical to the ones for PS 7, which might already linger there just lacking the proper vlaues...
Mylenium

Color spaces not sticking...?

What's Confusing: I have a layered file, the color space assigned to it is sRGB. I save a png file via Save For Web, tick the option to convert export to sRGB. All looks good in the save for web 2-up preview. But when I open the new png file, it's color profile is set to Adobe RGB, and the color space looks off—not like it did in the SFW preview.
Details: My default color space is Adobe RGB. Sync'd across all CS5 apps. I have the option ticked to warn me on profile mismatches when opening a file. So far so good.
So it seems like my Working Space color (Adobe RGB) is overriding SFW settings as well as my document color space settings
Same thing happens when saving as a jpg.
Any thoughts?

To erase, delete or reset Save For Web & Devices SFW preferences:
Open a small .jpg in Photoshop (to ungray the File menu).
Mac: Press and hold Option+Command keys, while File> Save For Web Devices (you will get a prompt confirming you want to erase all Save for Web preferences).
Windows PC: Press and hold Control+Alt keys, while File> Save For Web Devices (you will get a prompt confirming you want to erase all Save for Web preferences).
that should configure SFW default settings to CONVERT your Photoshop Source Space to sRGB and strip the ICC profile by default
How to reset Photoshop's preferences using special key combinations (most Adobe apps use this method of keystrokes):
First Quit Photoshop.
Mac: Press and hold Command+Option+Shift keys, while opening Photoshop (you will get a prompt confirming you want to delete the Adobe Photoshop settings folder).
Windows PC: Press and hold Alt+Control+Shift keys, while opening Photoshop (you will get a prompt confirming you want to delete the Adobe Photoshop settings folder).

Save PNG as gray color space

Hi all,
I've searched high and low for a good answer to this, but no luck so far:
I have an AI file that I wish to save as a mask for an app.
The image has to be:
Format:               PNG
Color space:        Gray
Alpha Channel:    No
I have set the following for my AI file: Document raster effect settings: Colormode: Grayscale
I have changed Edit -> Edit colors -> Convert to grayscale (but the "Convert to grayscale" text is not grayed out the next time I look in the menu, problem?)
I then save the file for Web and Devices as a PNG-24 or PNG-8 (Grayscale, no dither) but no matter how I save it the file info still says that the "Color Space" of the file is RGB. I can't get it to save the file with Color Space: Gray.
I am doing somthing wrong, but what?
Any help would be greatly appreciated!!
Kind regards,
Smulan

Thanks for your answer Larry!
I was afraid of that... I tried everything.
However, I still have a PNG file on my Mac that has "Color Space: Grey" when I look att it in file information.
Incorrect file with RGB:
Correct file with Gray (not created by me):
Sorry about the Swedish . "Färgrymd" is "Color Space"
So there is some information stored in the correct file that I seem to be unable to save using AI. Maybe I need to use some other program... The files I created with Grey scale and saved are useless when creating the mask unfortunately.
Kind regards,
Åsa

Inadvertently saving in unwanted color space.

Similar Messages

Maybe you are looking for