Preview in sRGB

In Lightroom, is it possible to preview RAW images in sRGB before
exporting them to that colour space?
Roy

Roy,
there is only one color space that works on the web and that is sRGB. So exporting for the web implies that you export for sRGB. There is no alternative. You cannot get around that people will see different colors than you since the overwhelming majority does not use color managed browsers and there is a large variation in monitors. Since all consumer monitors are designed to approximate sRGB your ONLY bet is to use sRGB and live with the fact that not everybody will see what you see. If you would export to your monitor profile, so that the image will look correct on your computer in IE, it will actually look worse on the majority of browsers. This is the unfortunate reality of the web currently. If you want to read more about this, check out
this long post. It is very unfortunate that in 2007, we still do not have color management in the majority of browsers. Perhaps Firefox 3.0 (which has color management) and the release of Safari for windows will change this.
P.S. I looked at your image and the RGB histogram implies that your entire image is inside the sRGB gamut (safe a tiny blown out area in the sky), so your image is indeed identical to that in Lightroom and should look so if you use color managed apps.

Similar Messages

  • Files no longer default to SRGB after processing

    I still have the ICC profile box checked when ave a Jpeg after processing.
    Noticed that there was a bit of color shift on some images viewed on my web site in firefox----
    checked the color space---unassigned!!  That usually only happened the check box inadvertantly
    was not checked.  Now it doesn't save in sRGB unless I assign a profile under the edit menu--not sure that is a good thing to do
    or not.  Wonder how to restore it so the check-box on saving a Jpeg works again.
    Any help greatly appreciated.
    Mike

    usher999 wrote:
    I'll have to figure out an expand ed color gamut workflow for some prints later.Thanks so much!!!
    You're welcome.  Just watch your histograms to make sure you don't clip color channels when converting directly to sRGB.
    For wide-gamut work I convert to ProPhoto RGB.  For combinational stuff, for example where I need a print and web image, I (try to) remember to do Edit - Convert to Profile before saving as a web preview requiring sRGB.  I created an action that embodies the conversion and "bends" the colors at the gamut edges so that the conversion to sRGB doesn't clip color channels.  Finally, I keep a quick photo viewer (IrfanView) on hand set to do no color management, so I'll be able to see in a quick preview visually if I forgot to convert the image to use the sRGB profile.
    -Noel

  • Lightroom 3 and previews

    Hi Everyone,
    I'm struggling with some issues regarding previews in lightroom.
    1. I've upgraded my catalog from lightroom 2 to 3 without re-rendering the previews. According to Jeff Schewe in the Luminous Landscape lightroom 3 tutorial there would be an advantage to disregard all your old previews and let lightroom 3 re-render everything. Could someone elaborate why this is the case and how the difference will be noticeable? He mentions something about a new rendering technique and use of color space.
    2. I've tested the re-rendering by exporting my entire catalog without previews. Then re-importing it in a new, empty catalog and selecting library -> previews -> render 1:1 previews. What I've noticed is that the standard preview size in the catalog settings influences the total file size the catalog will have on the hard drive. Also when only selecting render 1:1 previews. The lightroom manual says the following about previews:
    Lightroom renders three types of previews: thumbnails, screen resolution images, and 1:1 previews. 1:1 previews
    have the same pixel dimensions as the original photos.
    Does lightroom then render out all three of these previews when selecting render 1:1 previews?
    3. To determine what setting to choose for the standard preview size and quality in the catalog settings I need to know what the standard preview is used for. Is it what you see when selecting fit in loupe mode?
    4. After re-rendering all the 1:1 previews and then choosing to export a certain folder as a catalog lightroom completes the procedure but gives me the warning that it couldn't find certain photo previews. It seems these are the pictures that havn't yet been viewed in loupe mode by me. This contradicts the assumption I made earlier that lightroom would render out all three previews when choosing render 1:1. What exactly is lightroom missing here and what does it render out in loupe mode that it doesn't do when rendering 1:1's?
    Hope this is not too confusing and thanks already for the help.
    Freddy.

    1. ... According to Jeff Schewe in the Luminous Landscape lightroom 3 tutorial there would be an advantage to disregard all your old previews and let lightroom 3 re-render everything. Could someone elaborate why this is the case and how the difference will be noticeable? He mentions something about a new rendering technique and use of color space.
    Lightroom 2 used different color spaces for different preview levels: sRGB for low, Adobe RGB for medium an ProPhoto for high quality and 1:1 previews. Lightroom 3 uses Adobe RGB all the time. Plus, LR2 never applied sharpening and NR to standard previews (only to 1:1), LR3 does sometimes.
    Also, the preview cache contains some databases, apart from the preview files themselves. These are a sort of directory, or index for the entire cache. They might be corrupted or malformed. Rebuilding them is a good thing sometimes.
    I've tested the re-rendering by exporting my entire catalog without previews. Then re-importing it in a new, empty catalog
    You might simply copy the catalog. Same result, but faster.
    What I've noticed is that the standard preview size in the catalog settings influences the total file size the catalog will have on the hard drive. ... Does lightroom then render out all three of these previews when selecting render 1:1 previews?
    Lightroom often builds several levels of previews. Some large images may have not two (standard and 1:1), but 6-7 levels.
    To determine what setting to choose for the standard preview size and quality in the catalog settings I need to know what the standard preview is used for. Is it what you see when selecting fit in loupe mode?
    Yes.
    You must select a size that is egual or larger than you screen width in pixels.
    What exactly is lightroom missing here and what does it render out in loupe mode that it doesn't do when rendering 1:1's?
    I'm afraid, Lightroom sometimes silently fails to render the requested previews. That's why they are "missing".
    I have experienced myself and read many times on the forum, about cases when re-running "Build Previews" just after a previous run has finished, still finds missing previews and builds again. That means that the previous run crashed silently, despite lack of any error messages.

  • Soft Proofing: may not work on my screen

    First of all: Thanks so much for implementing soft proofing! Especially in such an easy way! I was really hoping you'd do it exactly like that.
    Anyway, I've got a wide gamut monitor (Thinkpad W520 laptop screen). And I've got an image with a lot of strongly saturated reds (PowerShot S95, RAW).
    Now, if I switch between Loup View and Develop View, I can see a huge difference in the reds because the Loup preview is sRGB (medium quality). I can also see the same difference when exporting to sRGB vs. exporting to AdobeRGB.
    However, if I engage soft proofing and select sRGB, the image still looks the same. Only the little preview in the upper left changes to what I would expect.
    That's not exactly what I would expect ^^
    On the other hand, if I select a custom profile (AdoramaPix, lustre paper), the whole rig seems to work.
    More information:
    - Windows 7, 64 bit with 64 LR4 beta
    - Whether relative or perceptual doesn't matter
    - Only seems to affect sRGB
    - The image shows very, very clear differences between sRGB and AdobeRGB on my monitor, so it's definitely not a visual problem on my end
    - The histogram changes when switching between sRGB and AdobeRGB in soft proofing mode
    - I really cannot see the slightest change in the image when switching
    I hope you can find a fix or point out what I'm doing wrong because I would really like to use soft proofing for images published on the web, which is of course in sRGB.

    I went on about this a little more scientific by creating an image with three rectangles: red, blue and green.
    All of them are 100%, e.g. (255, 0, 0). Colorspace: ProPhoto RGB.
    Results when exporting the images to AdobeRGB and sRGB, concentrating on the reds:
    - sRGB looks very washed out
    - AdobeRGB looks a bit washed out
    - Original ProPhoto has so much red that it almost drives me nuts
    Now, I would really expect similar results when activiating soft proofing.
    But when selecting either AdobeRGB or sRGB, the reds always drive me nuts.
    There is just no difference at all to the original ProPhoto image!
    Conclusion 1: Dorin, you were right, previews are in AdobeRGB. What I saw in the reds was the difference between ProPhoto and AdobeRGB. Somehow my screen seems to have extreme reds (calibrated recently with an X-Rite ColorMunki Display).
    Conclusion 2: Soft proofing with AdobeRGB and sRGB really DOES NOT WORK!

  • Unreadable jpg from photoshop export

    I have been converting a slew of tiffs (in 48 bit color adobe 98 colorspace) to 24 bit jpegs in srgb color space (as well as rescaling them). The resulting jpegs can be read and used in every photo management program (aperture, preview, photoshop .. even iweb!) but if i drag it to iphoto i get the following error :
    Unreadable Files: 1
    The following file could not be imported. (The import failed.)
    and a list of files..
    I have tried everything from making sure the jpg is in a temp directory to no avail.. interestingly the original tiffs import fine .. the new jpegs do not and (as i said before) the jpegs themselves seem to have no issue being viewed/editted in any other program.
    I have been searching around for answers to no avail .
    I have put a copy of the jpg here :
    http://www.bloosqr.com/tmp/gr01-1-1.jpg
    in fact if i ctrl click the above jpeg i get the same error so i am pretty sure it is a filetype issue rather than a "location" issue.
    this is on a dual G5/ 1.8 ghz mac w/ iphoto 6.05
    i also tried (via the web) importing that file on an intel macbook pro that had not been ever used iphoto before and had the same error.
    The photo is a Adobe Photoshop JPEG file w/ the embedded color profile SRGB IEC61966-2.1 (i.e. the normal adobe sRGB colorspace)
    any help on this matter would be most appreciated!
    dual 1.8 - G5/macbook pro intel   Mac OS X (10.4.8)  
    dual 1.8 - G5/Powerbook G4   Mac OS X (10.4.4)  

    Yes it does work in preview (i.e. i can convert to sRGB profile which can be read) but it does not work inside of photoshop. That is can take a adobe98 tiff file, convert to sRGB (any one), save as jpg w/ the embedded profile. Every other program recognizes the embedded profile (including preview). W/ preview you can "reassign" the profile to another colorspace and resave it and it imports properly. (I am guessing preview's assignment of colorspace is an assignment rather than a conversion?)
    so as an example
    photoshop -> srgb IEC1966 (this is the adobe sRGB space)
    iphoto can't read this file
    preview detects srgb IEC1966 .. i can reassign in preview to "sRGB Profile" (i.e. the one in system). I can not reassign it to srgb IEC1966 as it knows what the old profile is and assumes i haven't done anything when i do this so doesn't resave it. When I resave it it imports fine w/ iphoto.
    i can also
    photoshop -> "srgb profile" directly (this is the colorsync sRGB profile)
    iphoto can't read this file
    preview detects "srgb profile" and i can reassign it to the "srgb IEC1966" profile, save it and it will import properly.
    it seems that my version of iphoto has a bug in reading in the embedded "profile" format that adobe is writing, even though preview can read that file properly (and convert to a format that iphoto can read).
    the other interesting thing is tiff files work fine, its some mixing of jpg and embedded profiles .. one "fix" on apples website is to import you should use png rather than jpgs
    http://docs.info.apple.com/article.html?artnum=304487
    I can't tell what is going on really but there are obviously some issues w/ colorspace and jpgs and iphoto..
    in any case thanks again for your help, perhaps i should submit this as a bug report somewhere on apples site, but i can't imagine they don't know about it already.
    dual 1.8 - G5/Powerbook G4   Mac OS X (10.4.4)  

  • Working in Linear color space confusion

    When comping in Nuke we usually use Rec. 709 footage and comp in Linear color space. We can then preview in sRGB or Rec. 709 or whatever othe color space to check what it will look like.
    In after effects how do we achieve the same?
    You would think that:
    1/ Interpret footage as Rec 709. No problem here.
    2/ Set Project to Linear colorspace. But this is were the weird stuff happens. Since you have to select a color space other than linear and THEN tick linear compositing. That is the same as saying that you want composite in two different colorspaces at the same time? Thats is confusing so what is the right way of working here to composite in Linear cool space to get after effect to act the way Nuke does?
    3/ Then Simulate Output  -> Rec 709
    Thank you in advance.

    Actually, it seems AE doesn't really do it correctly without specifying color space and clicking "linearize working space" as you can see here (These two images is just a 3D render where I've added the diffuse, reflection, refraction and indirect passes together.): http://i1052.photobucket.com/albums/s443/lostparanoia/AE_LWF_error.jpg
    Also, the somewhat correct image is not 100% correct either because of (I assume) the color space adjustments that after effects applies.
    Another issue when working in sRGB 2.1 (linear) space is that I can no longer get the correct colors for my solids.
    Lets say I need to color pick some company's brand color to use as a background in my comp. When I color pick it, it will be in the completely wrong gamma, but I can't figure out any way to correct it so that it becomes the correct colour. I've tried applying a Color profile converter, and I've tried a inverse 2.2 gamma (0.455). Nothing seems to work. It's just a completely different colour.
    So my question is, is there still no way of using a proper linear compositing workflow in AE? And how do you work with solids and the colour picker in sRGB (linear)?

  • Colors off in Preview when viewing JPG's with sRGB profiles

    I have a 30" Dell monitor and my display preferences are set to use the calibrated profile for it. When I view JPGs images in any color managed application such as Preview the colors are horribly off. They are kind of dull, unsaturated, pale. JPG's that don't have sRGB profiles show up fine.
    I can fix the problem in photoshop by opening the image and then doing a save for web which strips the profile information off of the jpg.
    If I use sRGB as my monitor's profile colors are consistent across all applications but the problem is the colors are really bad. Extremely over contrasty and very dark.
    What's going on with my color profiles?

    Hi topmodelphotography ..
    If you're keen about running the right profiles - please don't mess up the way you do. The sRGB profile that you're using is showing a narrower color space (value 0-16 of blacks are out). The sRGB profile is mainly used for consumer monitors in the cheap end where contrast conditions are worse that expensive and professional displays to present contents in a similar way across manufacturers. If you should use any predefined color profile, please use Adobe (1998) profiling.
    best practive is calibrating your monitor with a good calibrator and use these profiles.
    In System Preferences you should set up the calibrated profile and the same goes for all Adobe apps under Color Settings.
    Useful reading concerning Color Profiles:
    http://kb.adobe.com/selfservice/viewContent.do?externalId=321382&sliceId=1
    Your issue with Preview is most likely due to erroneous setup in System Settings. otherwise try and disable Dithering in Preview.
    And don't use Save for Web if you intend to keep at least a minor part of your colors in your images. Use TIFF's where possible (without 'upgrading' images from compressed formats such as JPEG's, GIF's, etc.)
    useful reading about Image compression:
    http://en.wikipedia.org/wiki/Image_compression
    Hope this answers some of you questions.

  • 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

  • LR2: export jpg sRGB vs. print to jpeg sRGB - Same colors in MS explorer preview?

    Hello !
    Im using LR2 and do have problems understanding why "printing" to jpeg and exporting to jpeg give different results (colorwise) in the following case:
    The first picture was exported using "jpeg" file format and "sRGB" color space.
    The second picture was "printed" to jpeg using "sRGB" profile and rendering intend etiher "perceptual" or "relative" (doesn't matter).
    I was just wondering, why in explorer preview(MS Windows XP sp3 with a calibrated monitor) colors of both pictures look different. The "printed" jpeg does have less red in it.
    shouldn't the look the same in this case?
    Did I miss something here?
    Any hints appreciated.
    Thank you very much
    Sokrates

    Hello,
    thanks for pointing me to the related threads.
    Indeed the results of the LR2 functions "print to jpeg" and "slideshow to jpeg" are dependent of the current monitor profile being used.
    Here are my expamples:
    http://www.tiga-online.de/downloads/comparison.jpg
    if you have a closer look, it becomes more obvious:
    upper left picture:
    http://www.tiga-online.de/downloads/P5248984_print_sRGB_with_sRGB_monitor_profile.jpg
    upper right picture (which shows different color):
    http://www.tiga-online.de/downloads/P5248984_print_sRGB_with_sypder_profile.jpg
    lower left picture:
    http://www.tiga-online.de/downloads/P5248984_export_sRGB_with_sypder_profile.jpg
    lower right picture:
    http://www.tiga-online.de/downloads/P5248984_export_sRGB_with_sRGB_monitor_profile.jpg
    Thanks again
    Sokrates

  • Bridge CC - Content Panel looks different than Preview

    Problem - Images in the Content panel look dull and desaturated. The view of the same image in the Preview Panel, as well as Photoshop CC, looks fine (ie, like I expect from working with these images in CS6). This applies to NEF, JPEG and PSD files. In the attached screenshot, note the distinct lack of red in the skin tones in the Content Panel compared to Preview. Blues look a little dull as well. This is a PSD file. This image is tagged sRGB, verified in the Metadata panel as well as in Photoshop CC.
    I have read similar threads here (where all of Bridge was dull and desaturated), but I don't see anything that mentions the two panels in Bridge displaying images differently.
    Background - 10 years as a pro photographer, and I know what I'm doing around a Mac and color management. I finally "upgraded" from CS6 to CC when I got my new Mac.
    System -
    Retina iMac w/Yosemite. Second monitor - HP LP2475w (Bridge sits on the HP monitor)
    Both monitors have profiles generated with an i1 Display and the i1 Profiler application.
    Both monitors are using their correct profiles
    Steps Already taken (condensed)
    1. Purge cache (multiple times throughout the process).
    2. Check color cache and cache permissions.
    3. Reinstall Bridge at the behest of Adobe support, even though this was a new install.
    4. Check that "Always high quality" thumbnails is checked in Bridge (this seems to have no effect either way).
    5. Check color settings - NA GP2 in Bridge. Interestingly, the same behavior is exhibited no matter what I select here.
    6. Drag Bridge to the iMac display - everything now looks good. Drag back - now BOTH Content and Preview are desaturated. Will stay like this until Bridge is restarted.
    7. Recalibrate the HP (Bridge) monitor. No change in behavior.
    8. Verify no sidecar xmp for this image, to rule out ACR in the problem.
    9. Open Output module to verify that the content panel looks the same way there (it does).
    10. Investigate ~user/Library/Caches/Adobe/Bridge CC/Cache/ folders. Wow, the preview for this particular image in /1024/xxxx LOOKS CORRECT (like it does in the Preview panel). So Bridge IS generating high quality previews correctly.
    Thoughts -
    1. This seems unlikely to be a monitor profile issue. Bridge itself is displaying the same PSD two different ways. A bad profile would make everything on that monitor look wrong, wouldn't it?
    2. Some of my images sit on an external drive, but the screenshot here is from the internal mac drive, to try and rule that out.
    3. It's not some strange issue with the HP monitor not displaying color evenly across it's surface - if it were, than the screenshot would not show the difference between the panels. I also moved the Bridge window around the display to further verify that color is the same across the whole panel.
    4. Maybe Bridge ignores the profile for the content panel - but in the case of no profile, it assumes sRGB (or does it?) which is exactly what this image is. I have tried this with Adobe RGB images and the same behavior is exhibited.
    5. Previews are being generated correctly, but do not seem to be what is read off disc to display in the Content Panel.
    Any thoughts would be appreciated. My gut feeling is that for some reason, Bridge is not showing me the saved high quality preview in the Content panel. But why?

    Is your file tagged?  I.e. does it have the proper color profile embedded?
    Is your monitor accurately calibrated and profiled?
    What are your preferences in Bridge re previews and profiles?

  • Preview options in the "save for web" dialog

    According to the reference, the previews in the "save for web" dialog are there only for showing how the image can be seen on various platforms with different gamma values.
    But, if we open a non-sRGB image (ProPhoto for example) by the "save for web" option, the preview options (other than the "use document profile) in the "save for web" dialog assign sRGB color space to the image even when the "convert to sRGB" option is unchecked ... this causes unrealistic, dull previews for the image.
    What is the reason behind that PS assigns sRGB to the image previews if we uncheck "convert to sRGB" option?

    Basically, how animation works with GIF and Save for Web in PSE is that each layer in your document is a frame of animation. So you see one layer, then the next, and so on. You should not see the contents of the last frame/layer when looking at the current/next frame of the animation.
    Could you post a screen shot of your layers panel and give us a link to the GIF that is coming out of Save for Web?

  • I am unable to get same preview image colors in Bridge and Lightroom

    I am unable to get same file preview in Bridge and Lightroom. The Lightroom preview image (in both the Library and Develop) is more de-saturated. But the exported/saved jpegs match. If I try to match the Lightroom preview image to the Bridge preview image, the resulting Lightroom  export colors are off. I have tried this with images with no changes and with changes and the result is the same. I have Lightroom 5.6 and CR 8.6. I am using the latest version of Bridge.
    I contacted Adobe support and followed all instructions to try to fix but the problem remains. This comment was made after several solutions were tried, including updating Lightroom. :
    Adobe: there would be little difference in case of preview of Bridge CC and Lightroom 5. However, after exporting it would be same. Both use different technology at the background and work in a different way. The preview which you see in lightroom is not the actual image but incase of Bridge you see the actual image ( original ). That's the reason there is a color variation between previews.
    Me: But how can I then use the Lightroom preview to get accurate colors when processing a RAW file? If I do adjustments to the RAW file in Lightroom it looks different when exported. That doesn't seem to make sense when Lightroom is designed for photograhy
    Adobe: Please check in develop module of lightroom.
    Me: Nothing changes in the develop mode. The image looks the same as in the preview/Library mode.
    This screenshot shows the unmodified images in Develop (Lightroom) and ACR (Bridge). The color differences are significant.
    Lightroom exported jpeg file, unmodified from preview image in Develop (which looks like Bridge preview image not the Lightroom preview)
    Bridge saved jpeg file, unmodified from preview image in ACR
    Any suggestions on what I need to do to Lightroom to make it show accurate colors. If not, I don't see any point in using it to process files.
    Thanks, Marie

    Bridge is just a browser. It displays according to the embedded color profile but assumes sRGB for all untagged images.
    In Lightroom library previews use Adobe RGB and in Develop the working space is Pro Photo RGB.
    The real question is why use both Bridge and Lightroom. Stick to one, not both.

  • I am having some huge problems with my colorspace settings. Every time I upload my raw files from my Canon 5D mark II or 6D the pics are perfect in color. That includes the back of my camera, the pic viewer on my macbook pro, and previews. They even look

    I am having some huge problems with my colorspace settings. Every time I upload my raw files from my Canon 5D mark II or 6D the pics are perfect in color. That includes the back of my camera, the pic viewer on my macbook pro, and previews. They even look normal when I first open them in photoshop. I will edit, save, and then realize once i've sent it to myself to test the color is WAY off. This only happens in photoshop. I've read some forums and have tried different things, but it seems to be making it worse. PLEASE HELP! Even viewing the saved image on the mac's pic viewer is way off once i've edited in photoshop. I am having to adjust all my colors by emailing myself to test. Its just getting ridiculous.

    Check the color space in camera raw, the options are in the link at the bottom of the dialog box. Then when saving make sure you save it to the srgb color space when sending to others. Not all programs understand color space and or will default to srgb. That won't necessarily mean it will be accurate, but it will put it in the ballpark. Using save for web will use the srgb color space.

  • Why doesn't LR let us use embedded/standard previews (at least optionally)?

    I bought LR but cannot commit to using it mainly because it is too slow importing and browsing previews but also because LR's previews are worse than the embedded previews in RAW images or JPGs as displayed by other standard programs like Photo Mechanic, Breeze Browser or ADCSee.
    I shoot Canon RAW (then convert the CR2s to DNG) and occasionally JPG (1DMkII) but I get hundreds of images from friends and family, mostly JPG, taken with many different cameras. The vast majority of these pictures look terrific in PM, BB or ACDSee, etc but they look significantly worse in LR. LR renders its own previews from RAW files instead of using the excellent embedded preview that's already there and LR also somehow changes the JPG preview so that it looks bland and off color in comparison to the same image viewed in PM, ACDC or BB on the same computer. I assume LR's color management or color space is what changes the previews (and thumbs) so they look different (bad) in LR than they look in other standard programs.
    Why can't we at least have the option of using embedded previews in LR and display them normally like PM, BB and ACDC. Then LR would be fast (like PM, BB and ACDC) importing and displaying previews and we would not have to fiddle with exposure or color adjustments to get decent previews. Yes, I can get LR to just about match (sometimes exceed) the image quality of other programs but only with massive fiddling with individual images (the camera calibration controls are not sufficient by themselves) and that is a massive pain in the butt.
    I, of course, have read many posts about color management. But I refuse to buy expensive color calibration tools and go through that expense and aggravation just to accommodate LR. My pictures already look great in PM, BB, ACDSee and web browsers and on other non-color managed computers. I think LR should be able to be operated in a standard manner so it is consistent with other standard software. The fact is that the vast majority of all amateur photographers, even pretty serious folks, do not hassle with color management because standard software displays very nice images already.
    Another point. Some folks like to use Canon or Nikon or other RAW converters instead of Adobe's (for all or some images). If they develop their RAWS in DPP or Capture NX, etc, then import the images into LR, LR renders its own previews which disregard the work done in the 3rd party converter. This is pretty annoying and virtually prevents such folks from using LR. Other programs that use the embedded previews display the adjustments made in 3rd party RAW converters very nicely.
    Regards
    Bill Wood

    Thanks for the replies. Sorry I could not respond sooner.
    Nobody addressed my question. Why is there no option in LR to use embedded previews in RAW files and why is there no option to display JPG previews in a standard color space, presumably sRGB, like other standard software - Photo Mechanic, Breeze Browser, ACDSee, etc, etc?
    LR's insistence on rendering previews from RAW files makes the program too slow and it forces users to diddle with settings to get previews that look normal - meaning match what 99% of the rest of the world sees on normal non-color managed computer screens. Folks who want rendered previews and non-standard color space (ProPhoto) and all the rest of us who just want standard previews by default should both be accommodated. Just give us the option to choose.
    I just downloaded IDImager, a competing database type DAM program, for a trial. It does give users the option to use embedded previews for fast import and display or it will render previews from RAW if you choose that option. So it can be done and an embedded preview choice makes the program much faster and easier for most people to use.
    Just a few comments about the replies:
    Lee Jay said LR doesn't use embedded previews because:
    "Correct...that's because it's a RAW converter and must display what you'd get from a RAW conversion."
    Well, with respect, I cannot agree. First, LR is not just a RAW converter, its much more. If it was that limited, I never would have bought it and neither would anybody else. I already have ACR in Photoshop. Second, it is not mandatory that LR render previews from RAWs. It could optionally use embedded previews if that option was offered. Why do some folks lobby for lack of flexibility? I bet even you naysayers would use embedded previews sometimes, like when you want speed to show pictures to your family, friends and don't need to fester over image adjustments.
    Lee Jay also said regarding the difference between my JPG previews in LR vs. other standard software:
    "That is likely the fault of your monitor profile, which LR uses and the other programs (probably) don't. It could also be caused by you having "automatically apply auto tone" set, or by applying a preset on import."
    No, it LR's fault, period. Every other program I have ever used displays my pictures just fine (Photo Mechanic, Breeze Browser, ADCSee, etc, etc, even Windows free Picture and Fax Viewer works fine. Yes, I can diddle with LR's settings and get nice previews but I don't want to diddle with every image. And it ain't my monitor profile - I can delete it or change it and the issue remains. LR makes different previews from standard software because it renders previews from RAW data and uses a non-standard color space. Camera calibration (or presets) is not a reasonable solution for everybody. I have several cameras, my kids have many different cameras, friends have different cameras and I get images from all these people - so I have a ton of very different images in different lighting and I am not about to setup numerous different calibrations or presets to see previews in LR when I get excellent previews from other standard software that uses embedded previews and produces great previews with no work whatsoever. All I am suggesting is the option to use embedded previews and a standard color space. Again I must ask why do some folks argue for lack of flexibility?
    John McWilliams said about LR's power:
    "The neat thing is you can make the image look just about anyway you want without loss of quality."
    I could not agree more - LR is a good program! But, I don't want to diddle with every image. Most of them are fine, in fact, terrific right out of the camera. I just want to see them faster and I want them to match what other people see on standard non-color managed computers. If PM, BB, ACDSee and others can do it, so can LR.
    David Edwards said:
    "The images that I want to see in the Library section are RAW images with all the adjustments I have made to them and certainly not the embedded JPGs. If I wanted to see those I would have shot JPG."
    This is fine and no doubt makes perfect sense for David's workflow. But, why advocate against an option to use embedded previews for those who would find that useful? I too shoot only RAW with my DSLR cameras because I want the best images and the ability to use all of LR's (or DPPs) conversion powers when appropriate. But, as I said above, the vast majority of my embedded previews are good enough right out of the camera as viewed in PM, BB or ACDSee so I don't need to make any adjustments. :) Only LR creates a problem my rendering less than desirable previews by default. I also want to note that embedded previews do, in fact, display all changes made in LR and I cannot tell any difference in quality on screen between embedded previews and rendered previews when I adjust the LR version to match the default embedded preview and compare them side-by-side in LR and PM, for example.
    David also asked:
    "Do you need a RAW converter or an application to display images?"
    Both. Preferably in the same program. LR is supposed to be an all-in-one solution. It certainly will be when it gets more mature, I hope. I am a amateur so my main need is to see my pictures. I like them and enjoy them but LR is too slow importing and displaying thumbs and previews in Library mode and its previews usually need adjustment. So right now I am forced to use PM, BB or ACDSee all of which are way faster importing and browsing images and they use embedded previews that are fine, even excellent, by default.
    I think Adobe is missing out on a significant number of potential users because LR does not provide the options I am requesting. I am certainly not the only person who wants faster importing and browsing and previews that look good by default. And, as I mentioned before, folks who use other RAW converters are also excluded since they cannot see the changes they make before importing images into LR because LR will not display embedded previews.
    Regards
    Bill Wood

  • RAW output to an adobe rgb and srgb look identical in bridge but different in PS on wide gamut monitor.

    Photoshop CS6.  Wide gamut HP LP2475w monitor.  Spider 3 Elite calibrated.  Working space adobe rgb.  When outputting a raw to Adobe RGB jpg it looks a bit whacked with color blotches/jumps in PS.  The sRGB of it does not.  BUT......in bridge they look identical.  The adobe rgb jpg almost acts like viewing an image in a non-color aware browser on a wide gamut monitor.  Like bridge shows it right but photoshop is showing it whacked out.  I can't tell what is lying to me and if there is even a problem with the image.  Here is a half second 2 frame gif alternating between the two from a screen cap.  http://www.extremeinstability.com/hmm.gif  Abrupt blotchy color changes with the adobe rgb when viewed in photoshop.  And again, when you look at the two images in bridge they don't show that, they look identical.
    Thanks,
    Mike

    I guess I now learned that Bridge only generates srgb previews.  So I see them the same in there I guess.  Looks like it comes down to the adobe space and jpg.  Oddly enough an 8 bit adobe tiff covers it fine without breaking up.  Can see the 3 on this gif.  http://www.extremeinstability.com/3.gif 

Maybe you are looking for