Color Space Problems w/ Files?

I use Lightroom 2.5 to manage my photos. There are several things I don't understand regarding embedded color spaces in files.
When I export a file from LR to Photoshop CS4 as a TIF in the Adobe RGB color space the file shows as "Uncalibrated" in the EXIF & XMP metadata.
Using PS CS4, if I save a JPG file from the above Adobe RGB TIF file, and then use the edit -> convert to profile function, with Destination Space -> Adobe RGB selected, toggling the preview check box shows a color shift in the image. If I convert an image to the same color space why is there a color shift?
Is the color profile stored in the EXIF or XMP metadata?
Jack

I can provide some general information on the topic, though I do not use Lightroom so thers may jump in.
Information about color space is contained within the tiff file proper. That is, in a tag (the T in TIFF) and if I am correct it is tag 262 (PhotometricInterpretation). I do not know if LR also puts this info into the metadata.
When you convert a file to jpg you invoke the YCbCr color space and convert your source data into it. That is, the "compression" process also involves a color space change if you did not start out with YCbCr. This could account for the color shift you are seeing.
Paulo

Similar Messages

The Organizer does not support the color space in the file

I just purchased and installed PSE 8 as an upgrade to PSE 6. My catalog correctly shows all of my existing images. However, when I try to import photos into the Organizer, I get a message that nothing was imported. The reason given is that "The Organizer does not support the color space in the file." This happens with photos taken on my iPhone as well as those from my Canon PowerShot A1100 IS. Any suggestions?
Here is my system information:
Elements Organizer 8.0.0.0
Core Version: 8.0 (20090905.r.605812)
Language Version: 8.0 (20090905.r.605812)
Current Catalog:
Catalog Name: My Catalog
Catalog Location: C:/Documents and Settings/All Users/Application Data/Adobe/Elements Organizer/Catalogs/My Catalog
Catalog Size: 83.9MB
Catalog Cache Size: 459.8MB
System:
Operating System Name: XP
Operating System Version: 5.1 Service Pack 3
System Architecture: AMD CPU Family:15 Model:11 Stepping:1 with MMX, SSE Integer, SSE FP
Built-in Memory: 2GB
Free Memory: 829MB
Important Drivers / Plug-ins / Libraries:
Microsoft DirectX Version: 9.0
Apple QuickTime Version: 7.65
Adobe Reader Version: 9.2
Adobe Acrobat Version: Not installed
CD and DVD drives:
J: (SONY DVD BUS: 3 ID: 3 Firmware: RW)

It turns out that this problem went away after the program crashed. Everything seems to be working well now.

Color space of embedded files

Is there a way to determine the color space of a file that is embedded in Illustrator?

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.

Color space problem/confusion

I posted the following message to another thread, but at the recommendation of a member I am starting a new thread here. For a couple of answers see the thread below.
http://forums.adobe.com/message/3298911#3298911
I will provide much more information hoping an Adobe support person will chime in. This is extremely odd.
System: HP, AMD, Windows 7 64-Bit, Nvidia 9100, all updates to Windows, latest Nvidia 9100 driver
Display: Samsung 226CW, Windows settings 32-bit color, correct resolution,
Calibration: Done with ColorMunki, D65 target, done after monitor has been on for more than 30 minutes
Personal: (I am adding this information with some hesitation, please excuse it if it sounds like I'm bragging; I am not). I have multiple posts on my blog, have made many presentations on color managed workflow and am very comfortable with the settings in Photoshop and Lightroom. Please take this only as a baseline information, I am not bragging. In fact, I am begging for information!
Problem:
Any, I mean ANY, original JPEG image in sRGB space coming out of the camera with no adjustments, any PSD file in sRGB space, any TIFF file in sRGB space look significantly paler in Lightroom and in Photoshop CS5 than they look in other Windows based image viewers like FastStone or XnView. This should not need these applications to be color space aware, but the situation is the same with or without their color managment turned on or off. I have done the following:
1. Totally uninstalled Lightroom 3 and reinstalled it
2. Recreated a brand new Lightroom catalog/library and reimported all the images, converting all the RAW files to DNG (just in case!)
3. Recalibrated the display
When I view a file, any file and I will use for the sake of simplicity a JPEG file in sRGB color space, in Lightroom it looks pale. Since the file is in sRGB color space, I have verified this, the rendering in Lightroom should be the same as rendering in anything else. But it is not. I took my monitor and connected it to this system with the same odd behavior of rendering in Lightroom being much paler than outside. It appears as if I am viewing an image in Adobe RGB in a windows viewer that is not color managed.
I further tried the following:
1. I copied various versions of one file, all in sRGB color space. One PSD and two JPEG files from the folders of the above system and copied them to my system, Intel, Windows 7 64-bit, display calibrated and profiled with ColorMunki to the same standards as the problem system above.
2. Imported them to Lightroom on my system
3. The rendering in Lightroom is identical to rendering outside Lightroom for all the files and all are same as the rendering in FastStone on the problem system. Outside rendering was done using FastStone as on the problem system.
My deduction is that something on the problem system outlined in the opening of the message is interfering with the Adobe rendering engine and I have no idea what it could be. I WILL GREATLY APPRECIATE if an Adobe engineer could chime in and steer me in the right direction. I am willing to try other things but I have run out of ideas despite the fact that I have reduced much of the problem to the lowest common denominator of sRGB and JPEG against a PSD in sRGB.
Waiting anxiously of your help.
Cemal

Also, I know enough to calibrate a monitor when it is connected to a new computer. That said, even without calibration the behavior should have changed to display all the images in question the same but perhaps with somewhat off colors. Am I right? I am not arguing the point, I am rhetorically raising the question. If the 226CW is wide gamut and 244T is not, when I connect 244T on the same computer the wide gamut issue should be eliminated, should it not? I am not talking at this point about the "correct" color, but the same color in or out of Lightroom.
Unfortunately when you connect another monitor to a computer and don't calibrate or manually change it, Windows will not change the monitor profile. Macs will autodetect and change the profile but this innovation has not reached windows yet. The behavior you observe is caused by managed apps using the monitor profile and unmanaged apps not. If the monitor profile is not changed, the behavior doesn't change.
BTW, for a "cheap" software to be color space aware it does not need a quantum leap in technology I believe. It simply needs to know how to read the ICC profile and the LUT, is that correct?
It's extremely simple to program color management into apps. Standard API libraries have been available in Windows for over a decade. The reason why this hasn't happened is related to the fact that Microsoft hasn't made IE color managed and the software makers do not want to confuse folks when images look different in their program vs IE. Considering that this still is the biggest issue people wrongly complain about in every color managed application (just check Photoshop fora) that is maybe not that strange.

Lightroom Color Space Problem.

Hello,
I am processing my photos in Lightrrom. The histogram in Lightroom looks ok without any clipping, but when i export them to AdobeRGB or sRGB (for web) the photos have clipped shadows or highlights or both. I belive that the problem is that the histogram in lightroom reflect the data of the photo in ProPhoto RGB, and when you export to a narrow color space the clipping happens.
Is there any way to fix this? I will always have clipping if i export to AdobeRGB or sRGB? What do you do to not have this problem?
Beside of the clipping problem. The diferece between the histogram in the develop module in Lightroom and the histogram of the exported photo in AdobeRGB or sRGB makes that you don't know what the exported photo will look like, is like working blind. I don't know about you guys, but for me the is a big problem. Well, maybe if you work all in ProPhoto RGB this is a little issue.
I would appreciate a lot any help or comment that you could give me.
Thanks, :)
Marcelo.

Another thing I sometimes do is to save the development settings (save metadata in metadata menu) to file in LR, and then open the RAW in Camera RAW. In camera RAW the histogram reflects the color space you set, so you can optimize the development settings there. Then I close Camera Raw, which updates the xmp file (or the stuff written into the dng) and in LR do read metadata from file, which will apply the changed settings. This does the trick typically.

Color space problems

Somewhere the colors seem to get messed up. Viewing in LR and Photoshop the skin tones look pink but when viewing in windows photo gallery on computer or typepad site the skin tones are grey. I have LR and Photoshop set to ProPhoto rgb 16 bit resolution 240, monitor calibrated with spyder 3 and exporting file setting is procolor rgb. Does anyone know what's wrong? Where are my settings getting messed up. It really is messing with my editing b/c I keep trying to put more pink in b/c I know it'll print and web view more grey than I see it in LR/cs3. Very frustrating. At this point I'm afraid to edit any photos b/c nothing is what it seems.
thx for any advice.

>and exporting file setting is procolor rgb. Does anyone know what's wrong?
Yes. You're using prophotoRGB. The other apps you mention are not color managed and thus do not understand the prophotoRGB profile. You need to use the sRGB color space and even then will you see small differences if your screen is correctly calibrated and profiled. Non-managed apps (internet explorer and such) always lie to you color wise, even if you calibrate your screen. Read this excellent (but long) article on this: http://regex.info/blog/photo-tech/color-spaces-page1 If your images are meant for web viewing, ALWAYS use sRGB.
Also consider using a managed browser. Safari is one and Firefox (
using the secret setting) is another. Flash galleries will not be color managed even in those programs however.

Color Space Problem

Ok so I'm having a huge problem with when I go from lightroom to photoshop to edit it is changing the color space on my photos and is causing me a lot of headache and my photos to look muddy and the colors to be off. I know this because the photos I started editing in lightroom and switched over say that they were for some reason save in Pro photo RbG and then the photos I pulled up directly from camera raw to photoshop save in srbg. I would love to know what setting in lightroom I need to change to make this not happen anymore! Thank you!

Also, I know enough to calibrate a monitor when it is connected to a new computer. That said, even without calibration the behavior should have changed to display all the images in question the same but perhaps with somewhat off colors. Am I right? I am not arguing the point, I am rhetorically raising the question. If the 226CW is wide gamut and 244T is not, when I connect 244T on the same computer the wide gamut issue should be eliminated, should it not? I am not talking at this point about the "correct" color, but the same color in or out of Lightroom.
Unfortunately when you connect another monitor to a computer and don't calibrate or manually change it, Windows will not change the monitor profile. Macs will autodetect and change the profile but this innovation has not reached windows yet. The behavior you observe is caused by managed apps using the monitor profile and unmanaged apps not. If the monitor profile is not changed, the behavior doesn't change.
BTW, for a "cheap" software to be color space aware it does not need a quantum leap in technology I believe. It simply needs to know how to read the ICC profile and the LUT, is that correct?
It's extremely simple to program color management into apps. Standard API libraries have been available in Windows for over a decade. The reason why this hasn't happened is related to the fact that Microsoft hasn't made IE color managed and the software makers do not want to confuse folks when images look different in their program vs IE. Considering that this still is the biggest issue people wrongly complain about in every color managed application (just check Photoshop fora) that is maybe not that strange.

Assigning color space to dng files

I use pe5. I can't assign a color space to my dng files. I have to convert them to jpg or tiff before I print them.
In LR, can I assign color spaces directly to the dng file and thus can I print from the dng file?
Andy

-->The RAW file when printed from LR is in the Pro Photo space<br /><br />Well kind of <g><br /><br />http://www.ppmag.com/reviews/200701_rodneycm.pdf<br /><br />When using Draft mode, they are sRGB from the thumbnails.

DeviceN color space problem

I'm trying to create a DeviceN color space, all is fine but when I set the PDEContent to the page I get segfault
can someone try to help me ?
        CosDoc cosDoc= PDDocGetCosDoc( pdDoc );
        CosObj clrspc = CosNewArray(cosDoc,true,4);
        CosArrayPut(clrspc,0,CosNewNameFromString(cosDoc,false,"DeviceN"));
        CosObj names=CosNewArray(cosDoc,false,6);
//adding colors name
        CosArrayPut(names,0,CosNewNameFromString(cosDoc,false,"Cyan"));
        CosArrayPut(names,1,CosNewNameFromString(cosDoc,false,"Magenta"));
        CosArrayPut(names,2,CosNewNameFromString(cosDoc,false,"Yellow"));
        CosArrayPut(names,3,CosNewNameFromString(cosDoc,false,"Black"));
        CosArrayPut(names,4,CosNewNameFromString(cosDoc,false,"Spot1"));
        CosArrayPut(names,5,CosNewNameFromString(cosDoc,false,"Spot2"));
        CosArrayPut(clrspc,1,names);
        CosArrayPut(clrspc,2,CosNewNameFromString(cosDoc,false,"DeviceCMYK"));
        CosObj domain=CosNewArray(cosDoc,false,12);
        CosArrayPut(domain,0,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,1,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,2,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,3,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,4,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,5,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,6,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,7,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,8,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,9,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,10,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,11,CosNewFloat(cosDoc,false,1.0));
        CosObj range=CosNewArray(cosDoc,false,8);
        CosArrayPut(range,0,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,1,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(range,2,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,3,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(range,4,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,5,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(range,6,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,7,CosNewFloat(cosDoc,false,1.0));
        CosObj cosFuncDict = CosNewDict(cosDoc,false,4);
        CosDictPut(cosFuncDict,ASAtomFromString("FunctionType"), CosNewInteger(cosDoc, false, 4));
        CosDictPut( cosFuncDict, ASAtomFromString("Domain"),domain );
        CosDictPut( cosFuncDict, ASAtomFromString("Range"), range );
        char* psFunc="{0.3 0.4 0.5 0.1}";
        ASInt32 iSize = strlen(psFunc);
        CosDictPut( cosFuncDict, ASAtomFromString("Length"),CosNewInteger(cosDoc, true, iSize ) );
        ASStm objNewStream = ASMemStmRdOpen( psFunc, iSize);
        CosObj psFuncStreamObj = CosNewStream( cosDoc, true, objNewStream, 0, false, cosFuncDict, CosNewNull(), -1 );
        ASStmClose(objNewStream);
        CosArrayPut( clrspc, 3, psFuncStreamObj );
        PDEColorSpace pdeColorSpace = PDEColorSpaceCreateFromCosObj( &clrspc );
        ASFixed notused = fixedZero;
        ASFixed basex = FloatToASFixed(0);
        ASFixed basey = FloatToASFixed(0);
        ASFixed maxx = FloatToASFixed(200);
        ASFixed maxy = FloatToASFixed(200);
        PDEPath pdePath = PDEPathCreate();
        PDEPathAddSegment(pdePath, kPDEMoveTo, basex, basey, notused, notused, notused, notused);
        PDEPathAddSegment(pdePath, kPDELineTo, basex, maxy, notused, notused, notused, notused);
        PDEPathAddSegment(pdePath, kPDELineTo, maxx, maxy, notused, notused, notused, notused);
        PDEPathAddSegment(pdePath, kPDELineTo, maxx, basey, notused, notused, notused, notused);
        PDEPathAddSegment(pdePath, kPDEClosePath, notused, notused, notused, notused, notused, notused);
        PDEPathSetPaintOp(pdePath, kPDEFill|kPDEStroke);
        PDEGraphicState gState;
        memset(&gState, 0, sizeof(PDEGraphicState));
        /* graphic state initialization */
        gState.strokeColorSpec.space = pdeColorSpace;
        gState.fillColorSpec.space = pdeColorSpace;
        gState.miterLimit = fixedTen;
        gState.flatness = fixedOne;
        gState.lineWidth = fixedZero;
        /* setting colors */
        gState.strokeColorSpec.value.color[0] = FloatToASFixed(1);
        gState.strokeColorSpec.value.color[1] = FloatToASFixed(1);
        gState.strokeColorSpec.value.color[2] = FloatToASFixed(1);
        gState.strokeColorSpec.value.color[3] = FloatToASFixed(1);
        gState.strokeColorSpec.value.color[4] = FloatToASFixed(1);
        gState.strokeColorSpec.value.color[5] = FloatToASFixed(1);
        gState.fillColorSpec.value.color[0] = FloatToASFixed(1);
        gState.fillColorSpec.value.color[1] = FloatToASFixed(1);
        gState.fillColorSpec.value.color[2] = FloatToASFixed(1);
        gState.fillColorSpec.value.color[3] = FloatToASFixed(1);
        gState.fillColorSpec.value.color[4] = FloatToASFixed(1);
        gState.fillColorSpec.value.color[5] = FloatToASFixed(1);
        /* add color to swatch */
        PDEElementSetGState ((PDEElement)pdePath, &gState, sizeof(gState));
        /* adding swatch to main container */
        PDEContentAddElem(pdeContent, kPDEAfterLast, (PDEElement) pdePath);
        PDPageSetPDEContent(pdPage, NULL);

Now I tried to do that differently (always without success) with PDE Layer,
I create my function as usual
CosObj domain=CosNewArray(cosDoc,false,12);
        CosArrayPut(domain,0,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,1,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,2,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,3,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,4,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,5,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,6,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,7,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,8,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,9,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,10,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,11,CosNewFloat(cosDoc,false,1.0));
        CosObj range=CosNewArray(cosDoc,false,8);
        CosArrayPut(range,0,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,1,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(range,2,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,3,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(range,4,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,5,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(range,6,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,7,CosNewFloat(cosDoc,false,1.0));
        CosObj cosFuncDict = CosNewDict(cosDoc,false,4);
        CosDictPut(cosFuncDict,ASAtomFromString("FunctionType"), CosNewInteger(cosDoc, false, 4));
        CosDictPut( cosFuncDict, ASAtomFromString("Domain"),domain );
        CosDictPut( cosFuncDict, ASAtomFromString("Range"), range );
        char* psFunc="{0.1 0.1 0.9 0.1}";
        ASInt32 iSize = strlen(psFunc);
        CosDictPut( cosFuncDict, ASAtomFromString("Length"),CosNewInteger(cosDoc, true, iSize ) );
        ASStm objNewStream = ASMemStmRdOpen( psFunc, iSize);
        CosObj psFuncStreamObj = CosNewStream( cosDoc, true, objNewStream, 0, false, cosFuncDict, CosNewNull(), -1 );
        ASStmClose(objNewStream);
then I create my colorspace
        PDEDeviceNColorData data;
        data.size = sizeof(data);
        data.names=calloc(1,sizeof(ASAtom));
        //~ data.names[0]=ASAtomFromString("Cyan");
        //~ data.names[1]=ASAtomFromString("Magenta");
        //~ data.names[2]=ASAtomFromString("Yellow");
        //~ data.names[3]=ASAtomFromString("Black");
        //~ data.names[4]=ASAtomFromString("Orange");
        //~ data.names[5]=ASAtomFromString("Green");
        data.nNames=0;
        data.alt=PDEColorSpaceCreateFromName(ASAtomFromString("DeviceCMYK"));
        data.tintTransform=psFuncStreamObj;
        PDEColorSpaceStruct spcstruct;
        spcstruct.devn=&data;
        PDEColorSpace pdeColorSpace=PDEColorSpaceCreate(ASAtomFromString("DeviceN"),&spcstruct);
If I create a pdf document like this all work fine and my DeviceN colorspace is well defined:
     11 0 obj
      [/DeviceN[]/DeviceCMYK 12 0 R]
      endobj
      12 0 obj
      <</Domain[0.0 1.0 0.0 1.0 0.0 1.0 0.0 1.0 0.0 1.0 0.0 1.0]/FunctionType 4/Length 17/Range[0.0 1.0 0.0 1.0 0.0 1.0 0.0 1.0]>>stream
      {0.1 0.1 0.9 0.1}
      endstream
     endobj
Now when I try to add one colorant (Orange or Cyan for example), my application crash, and I don't know why either ...
Can somebody say me what I miss ?
Regards,
William

Color spaces problem

Hi guys, i try to make a program that would let me choose a color, then modify some images i need using the color i choose. so i have an image, 12x12 pixels, casted to a BufferedImage. I loop through each pixel (counters x and y), executing:
mybufferedimage.setRGB(x,y,mycolor.getRGB());
sadly, the image i gat is not at all a square of my specified color, instead it is some other color (i noticed a similarity between my color's brightness and the colour that got on the image, but i'm not sure it has any relevance). I'm thinking this may be due to differences in Color Spaces (hence the title of this topic) but i am not sure.
so my question is this:
I have myColor and myBufferedImage. How do i set some (any) pixel(s) in myBufferedImage to be of the same color as myColor? And please explain (if you can) why my variant doesn't work.
thanks.

Teodor.Sandu wrote:
Hi guys, i try to make a program that would let me choose a color, then modify some images i need using the color i choose. so i have an image, 12x12 pixels, casted to a BufferedImage. Where does this image come from? What does calling getType() on the BufferedImage return?
I loop through each pixel (counters x and y), executing:
mybufferedimage.setRGB(x,y,mycolor.getRGB());How is 'myColor' created?
Post an SSCCE:
http://www.physci.org/codes/sscce.html
Jim S.

Trailing spaces problem during file content conversion

I have developed a proxy to file scenario.And am using file content conversion for creating the file. The file is to be a fixed length file.
File Structure
<Header>
<Item>
<Item Trailer>
<File Trailer>
Each tab in the file has the last character mapped to spaces.
Eg: Header00000001 2006011700000000020060<blank   space>
Item00000001        2006011700000000020060<blank   space>
The problem is that during file content conversion. XI does not preserve trailing spaces at the end of the line i.e.if a particular line in the file ends with space. It terminates the line at the last non-space character (in this case at 060).
However we are required to maintain these trailing spaces at the end of each line.
I have tried preserve white space in data type that does not work.
I know that xslt mapping may solve the problem but I am looking for a workaround with my current graphical mapping.
Looking for suggestions !!
Thanks,
Rashida

Hi,
I have the problem quite opposite to this where we are getting the trailing spaces at end of each record which should not come.
File structure is
<Record>
- <Data>
<Content>11/09/2007@210@ZACSL007@GBB-56436@PS01@29@1044@19@646@0</Content>
</Data>
</Record>
............. n records
<Header>
<File_Name>UK01</File_Name>
</Header>
Record structure in communication channel used is
Header, Data
Data.fieldFixedLengths     1024
Data.addHeaderLine     0
Header.addHeaderLine     0
Header.fieldFixedLengths     0
Header.fixedLengthTooShortHandling     Cut
Data.fixedLengthTooShortHandling     Cut
Header.endSeparator     '0'
Actually if the length of record is less than 1024, rest of the length is being filled with spaces which should not occur.
Many advanced thanks.
Jitender

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 in file?

has anyone seen this error message, 'Organizer does not support color space in the file'? Pls help

Elements does RGB, sRGB, Adobe RGB, index, grayscale. It doesn't do CMYK, LAB, etc.

Color space/profile name

I have some pictures that don't show a thumbnail in iPhoto. The info dialog for them says the Color Space is "Gray" and the Profile name is "Gr?skala - gamma 2,2". If I double-click on of these the enlarged image seems somewhat faded. The picture looks fine if I just view it directly in Preview, or ColorSync Utility. It seems most pictures have a Color Space of RGB, how to I change the Color Space of these files to RGB?

Justin:
Download the Automator application "Embed sRGB Profile" from Toad's Cellar and unzip it. Then locate the original files for those problem images and drop them on it. Next launch iPhoto with the Command+Option keys depressed and follow the instructions to rebuild the library and select the first three options. This should get those images compatible with iPhoto.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

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

Color Space Problems w/ Files?

Similar Messages

Maybe you are looking for