Color Space for uploading

I shoot Camera Raw, in Adobe 1998 RGB color space, then upload to iPhoto 08 and make some adjustments via editing in iPhoto. If I then send the JPEG photos to email or to Phanfare.com photo sharing site, should I be converting to sRGB color space first? Or, does iPhoto convert the color space?

For printing using the Apple print service you should use sRGB - if you are happy with the display colors then no need to change the profile for e-mail and displaying only
LN

Similar Messages

How to select color space for PDF export in Aperture 3

If you're exporting a book layout as a PDF for printing by a third-party album company, you may need to specify sRGB as the color space for images in the PDF. That's OK if your book is composed of JPEGs that are already in the sRGB color space. But, if your images are RAW, Aperture will export them into PDF using the Adobe RGB color space by default. Sending aRGB images to an sRGB printer will result in flat, unsaturated colors, as I learned the hard way. Apple tech support was unable to tell me how to handle this, but I stumbled on the answer myself. Select the book in the Library pane. Select File > Print Book. In the resulting printer dialogue window, pull down the Color Profile menu (default: No Profile Selected) and select sRGB or whatever target color space you desire. Then, click the PDF button and select Save as PDF. Presto! Your PDF images will now be in the appropriate color space.

Hi again, here some updates.
the issue is still there.
From Aperture, I tried to export to PDF the single images, and they look good (no posterization).
Furthermore, I created a photo book from iPhoto with the same pictures, and exported it to PDF. It also looks fine.
Also opening/exporting to PDF from photoshop does not show any problem.
The problem occurs only if I try to print the book from Aperture (option "print book" -> "save as PDF"), or if I make a book preview before placing the order (I suppose it's the same action).
Is anybody aware of what exactly Aperture does in these particular cases?
Please consider that:
1. my monitor (iMac 24") is hardware calibrated
2. the source pictures are in RAW (so no color profile on them) and (just a couple) in TIFF (16bit, Adobe RGB). I also tried reimporting in the album jpg converted versions, with no better results.
3. OS and Aperture are updated to the latest versions.
This problem is blocking me from placing the order...
Someone could give some help here?
thanks in advance
marco

Is LAB the "native color space" for ID?

Is it correct to say that LAB is the "native color space" for InDesign? That colors specified in RGB that need to be translated into CMYK will go through LAB along the way, and vice versa?

No, LAB is not the native color space of InDesign. InDesign does not have a native color space.
However, all color conversions between color spaces is done via ACE, the Adobe Color Engine, a component of Adobe's Core Technology, using ICC color management techniques. All conversions between color spaces are made first to a connection color space and then to the target color space. LAB is pretty much what that connection color space is.
- Dov

Correct export color space for wide gamut monitors.

Running a photography studio I have 4 typical scenarios of how clients or end users will see my photo work. I create and edit the photos using LR 3 on a HP 2475w (wide gamut) monitor. I'm aware that there are color shifts, but trying to figure out which export color space to use to be most consistent.
A) Wide Gamut monitor using color managed software or browser such as Firefox.
B) Wide Gamut monitor NOT using color managed software such as IE 8.
C) Standard monitor using color managed software or browser such as Firefox.
D) Standard monitor NOT using color managed software such as IE 8.
A) gives the best results and that's what I run myself. No matter the color space that I export (sRGB, aRGB, or my custom calibrated ICC) the images appear to be correct 100%
B) gives mixed results...the hosting site for my photos seems to oversaturate a bit when I view the photos in their preview size which is what my clients see, when I view the original photo in full resolution (this feature disabled for my clients to avoid them downloading full rez copies of images), then the images appears a bit dull (70%). When I try this same scenario using aRGB export, it looks better (90-95%). When I export it using my monitor profile then the photo is spot on 100% however my monitor profile shows the photo incorrectly when viewing it using the standard Windows Vista photo viewer, it appears lighter and less saturated which I guess I expect since it's not color managed.
C) On a standard monitor the photos all look the same regardless of color space export so long as I use a color managed browser such as Firefox.
D) This gives pretty much the same breakdown of results as scenario B above. At the moment, it appears that when I use my custom ICC profile which is the calibration of my monitor...I get the best web results.
However my custom ICC profile gives me the worst local results within my windows viewer and when my clients load the photos on their machines, no doubt they will look just as bad on theirs regardless of which monitor they use. So aRGB seems to be the best choice for output. Anyone else do this? It's significantly better when viewing in IE on both Wide Gamut and Standard LCD's when compared to sRGB.
I would guess that my typical client has a laptop with Windows and they will both view the photos locally and upload them on the web, so it needs to look as close to what it looks like when I'm processing it in LR and Photoshop as possible. I know that a lot of people ask questions about their photos being off because they don't understand that there's a shift between WG and non-WG monitors, but I get that there's a difference...question is which color space export has worked best for others.

I am saying that since images on the internet are with extremely few
exceptions targeted towards sRGB. It is extremely common for those images to
not contain ICC profiles even if they really are sRGB. If they do not
contain ICC profiles in the default mode in Firefox, Firefox (as well as
Safari btw, another color managed browser), will not convert to the monitor
profile but will send the image straight to the monitor. This means that on
a wide gamut display, the colors will look oversaturated. You've no doubt
seen this on your display, but perhaps you've gotten used to it. If you
enable the "1" color management mode, Firefox will translate every image to
the monitor profile. This will make the colors on your display more
realistic and more predictable (since your monitor's very specific
properties no longer interfere and the image's colors are displayed as they
really are) for many sites including many photographic ones. This is most
important on a wide gamut display and not that big of a deal on a standard
monitor, which usually is closer to sRGB.
It seems you are suggesting that for a wide-gamut display it is better to
try using your own monitor's calibration profile on everything out there,
assuming on images posted with a wider gamat it will get you more color
range while there would be nothing lost for images posted in sRGB.
Indeed. The point of color management is to make the specific
characteristics of your monitor not a factor anymore and to make sure that
you see the correct color as described in the working space (almost always
sRGB on the web). This only breaks down when the color to be displayed is
outside of the monitor's gamut. In that case the color will typically get
clipped to the monitor's gamut. The other way around, if your original is in
sRGB and your monitor is closer to adobeRGB, the file's color space is
limiting. For your monitor, you want to make the system (Firefox in this
case) assume that untagged files are in sRGB as that is what the entire
world works in and translate those to the monitor profile. When you
encounter adobeRGB or wider files (extremely rare but does happen), it will
do the right thing and translate from that color space to the monitor
profile.
Wide gamut displays are great but you have to know what you are doing. For
almost everybody, even photographers a standard gamut monitor is often a
better choice. One thing is that you should not use unmanaged browsers on
wide gamut displays as your colors will be completely out of whack even on
calibrated monitors. This limits you to Firefox and Safari. Firefox has the
secret option to enable color management for every image. Safari doesn't
have this. There is one remaining problem, which is flash content on
websites. Flash does not color manage by default and a lot of flash content
will look very garish on your wide gamut display. This includes a lot of
photographer's websites.

Color space for picture to use in FCP or DVDSP ???

I'm using 720x480 TIFF file from Photoshop to import in FCP, should I use Adobe RGB 1998 for the color space ? What about DVDSP ? The same ?
Merci,
Jean

720x480 is important. DPI doesn't matter.
Patrick

Converting color space for web

i shoot all my photos in adobe rgb. i would like to convert them for use on the web. i have read that they should be in sRGB color space. in photoshop i convert to sRGb color space but they still look the same as they did with adobe rgb, muddy and desaturated. can anyone help? i am getting extremely frustrated! thanks

Probably you're using a web browser that assumes monitor RGB for untagged images, and the gamut of your monitor is smaller than sRGB. So when monitor RGB is assumed, your images look desaturated.
You can get a wider gamut display. You can use a browser like Firefox with color management enabled, which assumes sRGB for untagged images. Or you can tag all your images with the sRGB profile (at a cost of 3.5k per image). In PS, you can assign your display profile after you've converted to sRGB to simulate what your browser is doing (or proof setup > monitor RGB).
In general though, don't sweat it too much. All the images you've ever viewed on the web that were prepared for sRGB have been muddy and desaturated as you're now experiencing, and it's never bothered you before. Have faith in your users' capacity for ignoring these details...
http://www.gballard.net/psd/saveforwebshift.html

ICC working color space for the System?

(I posted this in another area but I did not get any replies, so I'm trying here)
Hey, any color management pros out there...
What is the ICC color space of the OS itself? Is it the calibrated monitor profile I'm using?
For example, let's say I'm working in an app. that doesn't use any color management. By default is that color space the app is using by default the ICC profile of the calibrated monitor profile?
I'm specifically wondering in regards to rendering in 3d applications, such as, Lightwave, Strata3d, etc. These apps. don't save ICC profiles with the final rendered files. Are these files essentially in the Monitor space then? This is my guess, and has proven to be so in my tests, but I want to hear what other people think/know...
thanks!
Jeff

What is the ICC color space of the OS itself? Is it
the calibrated monitor profile I'm using?
As Ned said, the OS doesn't have an ICC profile. Profiles describe the properties of image input or output devices. They tell which colour an output device will display when sent a certain RGB value, or which RGB value an input device will return when it sees a certain colour.
Colour space and profile are basically synonymous, a colour space is the range of colours a device can produce or see, as described by its ICC profile.
For example, let's say I'm working in an app. that
doesn't use any color management. By default is that
color space the app is using by default the ICC
profile of the calibrated monitor profile?
No, if the app doesn't use colour management it is oblivious to colour profiles. It will simply throw the RGB values at the output device as they are.
I'm specifically wondering in regards to rendering in
3d applications, such as, Lightwave, Strata3d, etc.
Don't know these two, so can't comment.
These apps. don't save ICC profiles with the final
rendered files. Are these files essentially in the
Monitor space then?
Strictly speaking, no. You will get whatever the monitor or printer make of the RGB values. However, most apps produce/expect RGB values that look reasonably correct on sRGB monitors, for historical reasons. Hence, even on systems without colour management (or when using apps that aren't CM aware) you can calibrate your monitor to mimick sRGB behaviour (using the on-screen menu) and get reasonable results. Most good CRT monitors come pretty close to sRGB out of the box.
Cheers
Steffen.

Need seperation color space for identified font (text)

I want to write it into a Seperation color space If i found a font for the text specified in the PDF.
I got the font name for the text element using PDETextGetFont() function but i want to write those text element into different plane other than CMYK.
Is there any functions to write those text element into different color space?
Thanks!!

Please use the Acrobat SDK forum to reach the specialists who might help.

Separation color space for specific fonts

I Want to write a text (having special font) into a separation color space where my output device supports.
I was able to get the font name for the text using PDETextGetFont() function but i want to write those txet element into different plane (basically the separation color space which i have created) other than CMYK.
Is there any specific functions in PDFEdit_Layer to achieve that?
I tried with some of the functions like PDEColorSpaceCeate() -- for separation but i am unable to achieve my result.
Thanks for your help

You must first understand colour spaces in detail and how they are used and their affect on the PDF. The API does not help you with these things. Once you understand colour spaces, you can easily use the API to create colours in any of the 11 colour space families (well, in 10 of them, patterns are not easy). You can use DeviceN or Separation, but what makes them not too easy is that you need to understand (a) the purpose of tint transforms (b) the internal structure of PDF function dictionaries (c) how to create a function dictionary to implement the desired tint transforms.
You will not find examples of most things, but continued return to the documentation (both plug-in API and 32000-1) should usually yield results.
As you will see in 32000-1, there is no central list of spot colorants used in a PDF. The list of colorants simply comes from the colour spaces used throughout all pages, form XObjects, patterns and type 3 fonts, and you can freely add more colours. However, it is very bad practice to add new spot colorants with different properties, so a good implementation will start with an analysis of the whole file to discover if the colorant is used, and how it is defined.

Color Space for iBook Printers and Photo Printers?

Has anyone figured out what the Color Spaces are for the iBook Printers and the Photo printers they use when you order prints through iPhoto? is it sRGB IEC61966 or something else? I want to clean up some shots in Photoshop before sending...
Thanks!

Yes, I set all profiles to the sRGB except the monitor. I calibrated my monitor thru the system preferences as the whites seemed too yellow with the sRGB for my viewing tastes.
I don't do a whole lot of printing. More into creating iDVD projects but I have Photoshop set for sRGB. There are a number of sites on color management which may give you some more insight.
http://www.shootsmarter.com/infocenter/wc007.html
http://www.gballard.net/psd.html
http://www.gballard.net/psd/honormyembeddedprofile.html
http://www.apple.com/pro/color/

Color Space for external editing

I know I can set LightRoom Preferences to open an image in Photoshop, but it seems my only choices are ProPhoto RGB, Adobe RGB or sRGB as working spaces. I'd like to set it up to use BetaRGB as my standard editing space. I know I could open in ProPhoto and convert to Beta RGB, but that is an extra step each and every time I edit an image. I would prefer to go straight from LR to Beta RGB in Photoshop.
Is there any way to do this or am I stuck with one of the big three? If I can change it, how?
Thanks,
Lou Dina

Thanks...that'll work, though I'd prefer if Adobe allowed the use of any profile for external editing to retain the features you mentioned.
I just created an Export preset, with Beta RGB, full sized PSD, save to same folder, add to catalog and open in Photoshop after the export is complete. That'll work.
Thanks,
Lou

Can i provide a space for uploading a photo in my application form?

I need to insert a photo in my application form. Please tell me if there is any way for doing this. Thanks in advance

Harry,
Rik is on the right track. Here is a sample insert trigger: Would need to substitute you sequence ORDERS_SEQ with my sequence las_log_seq, how you define or use timestamps is up to you.
DROP TRIGGER LASDEV.BINS1_LAS_LOG_TBL;
CREATE OR REPLACE TRIGGER LASDEV."BINS1_LAS_LOG_TBL"
   BEFORE INSERT
   ON las_log_tbl
   FOR EACH ROW
BEGIN
   -- Description: Insert log_seq, creation_dt, creation_id,
   --              lst_updt_dt and lst_updt_id.
   -- Maintenance:
   -- Date        Actor          Action
   -- ====        =====          ======
   -- 07-Sep-2010 J. Wells       Create.
   :new.creation_id := nvl( v( 'app_user' ), user );
   :new.creation_dt := SYSDATE;
   :new.lst_updt_dt := :new.creation_dt;
   :new.lst_updt_id := :new.creation_id;
    SELECT las_log_seq.NEXTVAL
      INTO :new.las_log_seq
      FROM DUAL;
END bins1_las_log_tbl;
/Heff

How to find the Color Space name for a PDEElement

Hi
I am trying to find out the color space for each PDEElement in my PDF file. While doing this,
I put some debug statements ( cout stmts ) that print the color_space as integer values. I gave this list
after the code. I belive the color spaces should be something like CMYK, DeviceRGB,DeviceGray..etc.
How can I know the actual color space name coresponding to these numbers printed in Debug statements.
Kindly please help me..
void   ProcessElementDetails(PDEElement element)
                PDEGraphicState gfx_state;
                ASInt32 pdeType = PDEObjectGetType(reinterpret_cast<PDEObject>(element));
    ofstream outfile("E:\\temp\\test.txt",ios::app);
    outfile<<"ProcessElementDetails\n";
    if ( pdeType == kPDEText )
      outfile<<"PDE Text type\n";
      PDEText pde_text = (PDEText) element;
      ASInt32 num_run,i;
          num_run = PDETextGetNumRuns(pde_text);
      outfile<<"Number of Runs for PDEText :"<<num_run<<"\n";
      for (i = 0; i < num_run; i++)
        PDETextGetGState(pde_text,kPDETextRun,i,&gfx_state, sizeof (PDEGraphicState));
        ASAtom color_space = PDEColorSpaceGetName(gfx_state.fillColorSpec.space);
        outfile<<"Color Space :"<<color_space<<"\n";
    if (pdeType == kPDEImage )
      outfile<<"PDE Image type\n";
      PDEElementGetGState(element,&gfx_state,sizeof (PDEGraphicState));
      ASAtom color_space = PDEColorSpaceGetName(gfx_state.fillColorSpec.space);
      outfile<<"Color Space :"<<color_space<<"\n";
    if (pdeType == kPDEContainer)
      outfile<<"PDE Container type\n";
                        PDEContent content = PDEContainerGetContent(reinterpret_cast<PDEContainer>(element));
                        ASInt32 numElem = PDEContentGetNumElems(content);
                        for (ASInt32 i = 0; i < numElem; i++)
                             element = PDEContentGetElem(content, i);
                             ProcessElementDetails(element);
Debug statements with color numbers:
====================================
ProcessElementDetails
PDE Image type
Color Space :700
ProcessElementDetails
PDE Text type
Number of Runs for PDEText :63
Color Space :388
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :388
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :388
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
ProcessElementDetails
ProcessElementDetails
PDE Text type
Number of Runs for PDEText :38
Color Space :389
Color Space :700
Color Space :390
Color Space :388
Color Space :390
Color Space :388
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :390
Color Space :389
Color Space :700
Color Space :700
Color Space :700
Color Space :700
Color Space :700
Color Space :700
Color Space :700
Color Space :700
SeparateColorPlates
PDF file exists
Number of Pages:1
Number of Elements:5

As you may have noticed, the "numbers" you see are actually of type ASAtom -
which is a type declared in the SDK to represent reused strings. You have to
read the relevant documentation to learn how to use the SDK - there is no
way around it. The Acrobat SDK is very powerful, but also a lot more
complicated than most people expect when they start to work with it. Take
your time to learn how to use it.
In this particular case, you need to call this function to convert the
ASAtom to a string:
const char* ASAtomGetString<http://livedocs.adobe.com/acrobat_sdk/10/Acrobat10_HTMLHelp/API_References/Acrobat_API_Ref erence/AS_Layer/ASAtom.html#ASAtomGetString135%28%29>
(ASAtom<http://livedocs.adobe.com/acrobat_sdk/10/Acrobat10_HTMLHelp/API_References/Acrobat_API_Ref erence/AS_Layer/ASAtom.html#ASAtom>atm)
(from
http://livedocs.adobe.com/acrobat_sdk/10/Acrobat10_HTMLHelp/API_References/Acrobat_API_Ref erence/AS_Layer/ASAtom.html
Karl Heinz Kremer
PDF Acrobatics Without a Net
[email protected]
http://www.khkonsulting.com

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.

IPhoto color space

What color space does iPhoto use to import digital photos from a digital camera, if the camera does not embed its own profiles? I read that iPhoto uses Colorsync default settings, but even though I set the RGB space to Adobe RGB1998, the photos seem to be embedded with sRGB IEC61966-2.1 profile when opened in Photoshop CS. There are no preferences settings in iPhoto for choice of color space for importing.
Any help is appreciated.

Joe:
Welcome to the Apple Discussions. I'll try to answer those that I can.
Linescreen - not familiar with that term but read a while ago that 150 lpi printers were used. Don't know if that's related or not. Also there seems to be a difference (for large book at least) between those printed at the West coast site and those from the East coast site. The west coast books were reported better.
Print resolution - large books are printed at 150 dpi. However, you can change the dpi resolution of the pdf file that gets created for uploading and printing as follows:
Method to increase the print resolution for books:
1 - download and run Pref Setter.
2 - open the iPhoto preference file from within Pref Setter.
3 - locate the Keys titled BookTargetMediumImageDPI, BookTargetSmallImageDPI and BookTargetImageDPI.
4 - change their current values to 300.
5 - save and quit Pref Setter.
Colorspace - I've used sRGB but don't know if that's the optimal one. My results have been OK in my mind.
Files accepted - all those you've listed are acceptable. Tiff file shouldn't have alpha layers as iPhoto doesn't play well with them.
Dot gain - don't know what that is.
For sharpening of those I've sharpened I used Photoshop's Unsharp Mask filter.

Color Space for uploading

Similar Messages

Maybe you are looking for