Compare X/Y in Develop module

I would like to be able to do an X/Y compare in the develop module. I often attempt to color-match digital files and with images scanned from negatives and being limited to X/Y compare in Library doesn't really do me any good since there are no color correction modules outside of white balance.

This has been requested a lot and it's usually called "2-up" compare mode in Develop. RSP had 4-up compare mode so I'd encourage the team to make available the largest number they can in the available memory.

Similar Messages

  • Develop module & library module aren't matching

    When I am editing, my photos look how I want them to in the develop module, but when I switch over to the library they look different. Some photos it doesn't apply the clarity, highlights, noise reduction, or sharpening. I haven't had this problem up until a month or two ago. It used to be the same between the two modules and I no problems editing. Now it's a pain to edit because I have to switch to the Library to see what the image is really looking like, go back to develop to try and change it, but cant end up getting it to look how I want. Images look the same zoomed in, but not in normal view. I am on Windows, Lightroom 3.6. I have tried reupdating the software, downloading an older version. also updated my video driver, and nothing helped. trying to avoid reinstalling all of lightroom because I do not want to lose any previewly modified images.
    first one is the view from develop. you can tell its a lot more noisey.
    second picture is from the library. it's a lot more smooth.
    so basically my images aren't being shown correctly. I have looked through a lot of discussions on here and no one seems to have an answer...please help me! editing should be fun, not frustrating.

    Rivosyke wrote:
    Thanks for the response. This appears to be more the issue with image that is exported is using the algorithm for the library module as opposed to the changes made using the develop module. The histograms are different when switching between the two modules (Library/Develop) for the same image.
    Camera: D7100
    Image Type: RAW
    ISO: 3200
    Bingo! You're using an ISO 3200 image with fairly high sharpening settings, which is going to increase noise in the image. If you view the image at 1:1 in the Develop module the noise should very visible. The Develop module and Library module 1:1 previews should both show the noise and look very close to each other. The reason why less than 1:1 Zoom previews (i.e. Fit, Fill, 1:4) and histograms look different is explained in my reply #29 under this heading MORE THAN YOU PROBABLY NEED TO KNOW (For Techno Geeks & Nerds Only). The Export module uses the same Bicubic algorithm as the Library module, which is why the Library module's preview is more accurate than the Develop module. Virtually all image editors (not just LR) use the same Bicubic resizing algorithms and will produce the same discrepancy when compared to LR's Develop module preview.
    Fortunately there is a very easy solution to this issue. Unfortunately many people prefer to complain, say it is a LR "bug," and don't listen further to suggestions on "fixing" the issue. If you fall into the latter camp don't bother reading further! Sorry if this sounds crass and cynical, but I can only provide advice. Whether you believe me and try it is your decision! It works for me using five different camera models with both raw and JPEG image files.
    High ISO and/or High Sharpening Preview Discrepancy Fix
    1) Set Develop module to 1:1 Zoom View.
    2) a. Adjust Sharpening panel settings for desired look.
        b. With noisy images it's best to keep the Detail setting no higher than 35.
        c. Try using the Masking slider to reduce noise in even toned areas.
    3) Increase Detail panel Color setting until the color noise is barely visible.
    4) If there is still some residual color noise try increasing the Color detail setting to ~80.
    4) Increase the Detail panel Luminance setting until noise is barely visible or gone.
    5) If the image has lost significant sharpness try increasing the Luminance Detail setting to ~80.
    6) If necessary go back to steps # 2-5 and make small adjustments to the Sharpening and NR settings.
    Now compare the Develop and Library previews at Fit view or better yet at 1:8, 1:4, or 1:3. They should look very close to each other with the Develop preview very slightly sharper. Full-size and reduced size Exports should look very close to what you see in the Develop module. When Resizing images don't forget to add Export Output Sharpening. When images are Resized the Output Sharpening setting has more influence on image sharpness than the LR Develop Sharpening settings. For most images the Screen Standard setting should produce crisp images. If you want more try the High setting. I generally find the Screen Low setting produces the most natural look. YMMV dependent on lens performance, camera shake, focus issues, or simply poor lighting (cloudy, foggy, etc.).

  • Images in library module aren't as sharp compared to develop module.

    For some reason images in the library module aren’t as sharp compared to the develop module. If I’m in develop images are nice and sharp but as soon as I select the library you can see the image quality drop and image becomes less blurry!
    I’ve had a look on here and other people have this issue and I’ve tried the various fixes suggested with no success at all.

    It sounds like the library module is using a lower quality preview. If you are using minimal or embedded previews, they could look different than what you saw in the Develop module. Do other changes you make seem to be in the preview, just lower quality? Like if you applied a heavy vingette, do you see the that in the preview? If you don't, that could mean LR isn't updating the previews it uses in the Library module and you might want to look and purging your cache. If you do, try rendering a 1:1 preview for the image and see if the preview looks better.
    Another thing to check is to make sure your standard preview size is appropriate for the size of your monitor. If you've got a huge monitor but have a small preview size, you'll notice a difference.
    Choose Edit >  Catalog Settings (Windows) or Lightroom > Catalog Settings (Mac OS), and then select File Handling.
    For Standard Preview Size, choose the amount that is closest to the longest edge of your screen resolution, but not shorter than it. For example, if your screen resolution is 1920 x 1200 pixels, choose Standard Preview Size > 2048 Pixels.
    For Preview Quality, choose Low or Medium, which equates to the low- or mid-range of the quality scale for JPEG files.

  • Photos in Develop module look different when switching to library module

    Hello everyone this is my first post on adobe.  I ran into a problem today for the first time using lightroom 5.  I recently purchased lightroom 5 about 2 weeks ago and have been in love using it.  I have ran into 0 problems until today.  I uploaded some new photos and was going through them under the develop module editing the photos and what not.  When I am done editing I usually go to the library module and export them.
    Today I tried to do that exact thing and ran into this issue:  the colors in the photo are changing ever so slightly when I switch to the library module and are not exporting exactly as I edited them in the develop module. 
    I have tried changing the contrast/clarity to see if it would remain when switching and it does.  But for some reason the yellow on the flower in the picture becomes less vibrant when seen/exported from library module.  It is very frustrating because I spend alot of time editing the photo in a develop module and every transfers but the colors it seems.  It becomes more dull and less vibrant.
    It is not the photo itself.  I think it is something wrong with my lightroom?  I uninstalled and reinstalled and the same issue keeps happening.

    Just to clarify. When you compare the exported image to the original inside LR do they look the same when viewed together in the Library module, and how about when both are viewed in the Develop module? Are you using a wide gamut monitor and do you also use a hardware monitor calibrator? All of these things affect how images looks in LR and some are fixable, but others are not as Web Weaver posted.
    There is also another issue that can cause the Library module view and exported images to look different than they do in the Develop module:
    http://feedback.photoshop.com/photoshop_family/topics/afm8rbh6tnc31
    The solution is to view the image at 1:1 (100%) view size. You can also use more conservative Sharpening settings (i.e. lower) and more aggressive Luminance Noise Reduction settings (i.e. higher), which will significantly decrease the view difference.

  • Prority applying filters in Develope module

    LR is one of the best tools for those who wnat quick ranking, metadata editing for copyright, sorting and processing LARGE quantities of files...
    Among those photographers wedding, event and sport shooters are those who really need to fastly sort thigns outm they are most interested in using LR.
    also, the same photographers work in the most critical lightning environments, very often we shoot in very bad lightning at very high ISO settings.
    for us noise is a real pain.
    as we all know, advanced processing of a very noisy raw material exponentially increase noise levels in the final product.
    for this reason, inside PS, our workflow include NR filters among the first operations we do...
    this way, working on a cleaner background, the noise is kept under a relative control.
    often, at the end of our workflow we again trim the nise as a final touch...
    back to lightroom, few questons and requests are born from this imediate reality we confront each day:
    1. LR offers NO control regarding order develope adjustments are applied... this is sometimes good, other times a real pain...
    2. there is no information regarding WHICH is the order those filtes are applied when developing RAW files... NONE.
    we could guess the order they appear in XML files and inside develope module is the order they are considered when RAW information is processed?
    that mean noise is indeed among the last filters applied, correct me if i am wrong.
    3. how we could maximize our results? just make minimum adjustments in LR, go to PS, where we can control the order of applying filters, process and export from there???
    not exactly compatible with our need for speed and easy processing large quantities of files that make us choose LR, isn't it?
    not to mention RAW data offers much more "hidden" info we can bring to life thru processing compared to exported PS files, even 16 bit tiffs are not as "good" on this regard...this is the reason we shoot raw, to benefit from this better latitude of information raw's offers ....
    4. now the requests themselves:
    a} please allow us to choosethe order of applying these filters...maybe not all, not all are that critical, but things like NR we should be able to put among the first filters applied.
    if Adobe already thought about this and NR is among the first on that list, please let us know. we NEED to know , we need that info, we need control.
    b} please allow us to double the filter alteration.
    as i said, we often apply a NR fiter at the beggining of the workflow and then again, another NR with softer settings at the end of the workflow, sometimes just before the final sharpening.
    such flexibility and customization availability would really help us, especially those who really need lightroom and do not have the time to bring every picture in PS and tweak it...
    imagine shooting 1000 pictures in one session with a delivery deadline of 24 hours...LR is great help, have a lot of great features and we really apreciate the wayit works, even this elastic way of applying filters inside develope module...
    BUT it would be a much better tool with more flexibility available.
    Thanks Adobe, i also compelted an official request form regarding this subject.
    maybe someone who really knows how things work inside developing engine could bring some light in this regard, how things really work right now,even this info could be very helpfull.
    regards ,Liviu

    first i need to KNOW officially how thigns work, if ucan offer me a proof i'd gladly accept that.
    second, as i said, adobe might have think about that, is a request area and i have theright to request what I think is usefull to me.
    i ask for more CONTROL, what is wrong about that?
    i also request for 2 alteration using the same filter, NR in this case, once at the beggining and one at the eng of the developing process, i am also entitled to ask for such a thing, right?
    qith all due respect, if u do not have similar needs please allow me to ask , understand and not suppose adobe thought of everything and there is no better way, ok?
    here is a quote from a XMP file, i PRESUME the order if operation inside that file is the one processes are piped, am i wrong again?
    5.3
       As Shot
       4900
       -2
       -0.57
       15
       +79
       -7
       +33
       25
       39
       18
       0
       0
       0
       0
       0
       0
       0
       0
       0
       0
       17
       -21
       29
       +10
       0
       0
       0
       0
       0
       0
       0
       0
       0
       0
       0
       0
       0
       0
       0
       0
       0
       +60
       0
       -24
       0
       +19
       0
       -24
       0
       0
       0
       0
       0
       0
       0
       0
       0
       0
       25
       50
       75
    +1.0
       25
    0
       0
       False
       Medium Contrast
         0, 0
         32, 22
         64, 56
         128, 128
         192, 196
         255, 255
       ACR 3.3
       8E1722706FEF96E97D62F657E50DF272
       True
       False
    so ,as u see i spaced the noise reduction fucntions in order to make them more visible, i can;t use colors to underline what i consider important, ok?
    SO, as u can see here, WB, exposure, contrast, SHARPNESS, brightness, SHADDOWS are ALL listed BEFORE noise reduction...
    later on the end of the list there is ANOTHER sharpening listed, so double fiter IS ALREADY applied, thus possible, right???
    again, ALL fiters applied BEFORE NR influences noise levels, all increse noise, more or less....
    WB influences exposure, try to go 50000 and see where hystogram goes to the right...
    exposure also increase noise in shaddow areas.
    contrast increse noise.
    brightness also influence noise.
    Shaddows are working exactly on most noisiest levels, the shades...
    sharpness before NR??? indeed, is "well thought"...
    so, Lee jay, seems i am not that wrong after all, isn't it???
    i really hope that order inside XMP to mean nothing but i really doubt is meaningless ...
    and again, even if a were wrong, i am entitled to ask explanations as i pay for this product. I also am entitled to ask for what i consider improvements, if Adobe decide to implement or not is another discussion...
    a little "friendlier" tone in your replies would also be apreciated, thank you in advance. i hope u do not work for Adobe ;)
    so, i am waiting for documented proofs related to my questions, thank you Adobe.

  • Lightroom 4.1 Develop Module Preview Problems

    Hi All,
    I have been using LR4 and now 4.1 since beta and subsequently the first release and now 4.1RC. I too have been irritated by the lack of responsivness compared to LR3.6 but in 4.1 it does seem to have improved. BUT the problem I am seeing is that the preview image in develop module chnages to a lower res and muddier looking version as I drag most of the various adjustment sliders, once the slider is realeased the image refreshed to a better resolution version. This happens in all panels from Basic to Detail and even Effects.  It is almost as if Adobe are increasing the apparent speed by applying the adjustment to a low res embedded file first and then to the full RAW data in the background.  On detailed images it is more irritating that the slow develop module in LR4.0 as it makes adjustments impossible to preview until the slider has been deslected.  The same occurs if you select the slider setting digits and advance using the cursors.  Very frustrating indeed.  I will be going back to LR4.0 and fingers crossed that this is resolved when LR4.1 is reeased in full.
    My PC is fairly good, Win 7 64bit with Quad Intel 9550 cpu (2.83Ghz) with 8Gb ram, GTX-260. I have the same problem at work with a dual cpu (8 cores total) Zeon 5365 (3.0Ghz) and 12Gb Ram & Quadro FX4600. The problem does not seem to manifest in the second display preview but this is laggy and obviously not any use for setting local adjustments.
    Anyone else had a similar issue to this? I cant find any reference to it on the web or these forums.
    BGhibby

    I have exactly same symptoms as Dave Mayfield.
    Except I moved images to sub-folders and renamed them, from within Lightroom.
    After it locked up, it did not show sub-folders in Library and all the images have question marks on them. If I show it where the file is in Explorer, it does not show any changes.
    I Imported one folder and it could see the images in the folder.
    Some were without any changes.
    Some were the final edited configuration, but not change history shows in Develop. It is if it kept an Exported fersion.
    HELP!
    Jack Lane

  • Library and Develop Module Photos Appear Different

    I am using Lightroom 4.4   Dell Ultrasharp monitor is calibrated.  I own and have been referring to Scott Kelby's Lightroom4 book for digital photographers.  I recently took some photos of my daughters prom.  She had on a beautiful reddish orange dress.  I notice that the dress appears very red in the develop module, however, appears a bit more orange in the library module.  The change is very noticeable between the modules.  The dress also appears similar to the library module view (a bit more orange) when viewed on the web via Flickr utilizing Chrome, Firefox, or IPad.  It also appears the same when exported to a JPEG file.
    I have done some experimenting and have determined that this color change effect appears to be very noticeable utilizing the Adobe Standard Camera Calibration Profile.  It does not happen (at least to a noticeable extent) with the others such as Camera Standard where the dress appears a bit more orange in both the library and develop module.  I do, however, like the appearance of the Adobe Standard profile better and this happens to be the default profile as well.
    I have also noticed that the dress looks more orange when Soft Proofing is enabled.  The change happens immediately when the check box is enabled.  Checking the box makes the photo appear similar to the Library module view.  Enabling Soft Proofing does make noticeable that there is Destination Gamut Warning which mainly involves the dress which is the point of interest, however, there is no warning with the Monitor Gamut Warning.  I am intending to place the photos on the web at this time via Flickr.  I will be printing several later so will be worrying about the printer gamut at that time.  But for now, I would like to get the photos on the web looking as intended.
    Having the photos look so different in the Library and Develop Modules is very frustrating.  I am hoping that there is a simple setting or fix for this problem that I am experiencing.  Your assistance will be greatly appreciated.  Thank you.
    -Mark

    Hi Victoria. Thanks for your reply. Re the saturation of the yellows, an example of a photo which shows the behaviour is that of a sunflower shot in direct sunlight. So a typical bright yellow. The raw files are from a D7000, so I have several "camera" profiles to choose from in LR4, in addition to the default Adobe Standard. None of the camera profiles show a difference between Library & Develop. Also, the Adobe Standard profile only shows the described behaviour when yellows are present. I can find plenty of examples where the photos are identical between the two modules when there are no yellows in the shot. I doubt this is a monitor profiling problem, given that it affects just the Adobe Standard profile, however I will try re-profiling. My U2412M display is not wide gamut. I posted here because the issue I am seeing sounds very similar to the original poster's. We're both using Dell Ultrasharp displays, although that could be a coincidence. I'll see if I can get some screen grabs from my Mac and upload here later today. I'm on my Windows 7 laptop at the moment.
    R
    Update:
    I have a pair of screen grab JPEGs from the Mac which I'm happy to share, however the upload here in the forum is limited in size. Any suggestions how I can best share the full size JPEGs?
    Re-profiling hasn't changed anything. I'm pretty sure my profile is good. Ambient natural lighting, monitor warmed up, etc. Native white point used as always. The difference between profiled and unprofiled is very subtle. The U2412M appears to be pretty accurate at factory settings.
    If I turn soft proofing on in Develop I see the less saturated image which matches Library. Turning it off again and the differences return.
    LR4 on my Windows 7 laptop doesn't have the same problem. The screen on that is calibrated with the same Spyder3, however the laptop's screen is of a mediocre quality compared to the U2412M.
    Found another thread where the poster is having the same problems with yellows, this time in LR5.
    http://forums.adobe.com/thread/1265004

  • Do we need a Library and Develop Module?

    Do we really need a Library and Develop module? There's lots of dissatisfaction with Lightroom speed and one of the problem areas is when switching from Library, when in standard preview or 1:1, to Develop and the 'loading' message appears or as on my mac the dreaded spinning beach ball goes crazy. Even with all the previews created it's still slow.
    So, if we have a standard preview or 1:1 loaded why can't we automatically be ready to apply any adjustments and save an extra step to another module? The quick develop in the library seems unnecessary and I've never used it. That leaves the metadata and keywording panels requiring a new location, but again these are not something I need to refer to on a regular basis.
    Anyone else any similar thoughts?

    > ...but I'm pretty darn sure there won't be any back-stepping to REMOVE or substantially alter LR's basic premise...pretty sure Develop will always be about dealing with a single image adjustment (and applying that adjustment to other images if you wish).
    And I'm okay with this premise, but it needs additional functionality, such as the ability to apply relative adjustments. It already has this via the keyboard shortcuts while hovering. It just needs a UI adjustment (I once did a mockup of this, and I think it works) and the ability for autosync to recognize them as relative adjustments to the other images.
    It also needs additional views. Grid, survey and compare would be nice, but you're only adjusting a single image's RAW data rendering at a time - the others are shown as previews and adjustments to them are rendered that way (like Library does).
    The issue is, many people like me end up switching modules far too often. I generally go back and forth between Library and Develop hundreds of times per day. That's way too many times to be suffering the module-switching penalty. I'd prefer to select the images I'm working on in Library, and never see that module again until I'm done working on them. For now, grid and survey are too often needed, and so are relative adjustments.
    Develop already has most of the needed functionality. Relative adjustments are already available to one image, a grid is available but only at 1 row (film strip supplied by Library) and a quick-render (the image in the upper left) is available as well. This just needs to be expanded and adjusted so that going back and forth to Library isn't as necessary as it is now. Ideally, you'd import in Library, to your metadata stuff there or in other related modules, choose the image group you want to work on using filters/folders/collections/find, then go to Develop and work on them until you are done.

  • LR5: Moving develop module sliders blurs the image for a moment

    I'm evaluating Lightroom 5 during the 30 day trial and it's all cool except for this one big annoyance that I noticed immediately when trying to work on an image in Develop module. As stated in the title, moving any slider (exposure, highlights, noise reduction, etc.) causes the image to go very blurry for the duration of the slider movement. It goes immediately back to being sharp as soon as I stop moving the slider. This is super annoying, feels as though my eyes are going bad.
    What's interesting is that the problem doesn't show up when I'm adjusting the Tone Curve directly, but it will get triggered if I'll expand and use the sliders underneath. So looks like a bug that only applies to sliders.
    This doesn't happen at all in Lightroom 4.4, which I still have installed and can compare side-by-side.
    As for the hardware, I'm using the 2013 Macbook Air with 1.3 GHz i5 CPU and 8 GB of RAM. The OS X version is 10.8.4 with all latest upgrades installed.
    I've already tried optimizing the catalog, giving it more space (currently at 3 GB) and purging it. I'm not using Smart Previews, although I've turned them on for a moment to see if the problem persists with them on - it does. I've also re-rendered the 1:1 preview for the specific image I've been trying it on. Btw, the file is a NEF from Nikon D300 and I'm using the 2012 process (as was the case with LR4). Not sure what else might be relevant here.

    If this is indeed intentional, is there any way to turn it off? I would much rather it had taken a bit longer to update the photo, than to have the image switch to this "pixel doubled" version.
    Also, this doesn't happen at all in LR 4.4 on the same machine. However, if it indeed isn't a bug, this probably means LR5 requires more resources to process a photo than 4.4. This would be somewhat disappointing, given that LR5 was supposed to be faster than its predecessor.

  • Preview Panel Appears Brighter than Loupe View In Develop Module

    Settings and Hardware:
    - Macintosh 15" Power Book G4
    - Lightroom Version 2.1
    - Attached Apple Cinema Display
    - Mac OSX 10.4.11
    When viewing Lightroom on the PowerBook monitor all is well and the Preview Pane shows the same brightness value. Yet when the Lightroom interface is brought over to the Cinema Display the Preview pane in the Develop Module is significantly brighter than the main image in the Loupe View.
    Any help with getting the value of the Preview Pane to the same brightness value of the Loupe view would be of help. Or if there is a simple explanation as to why this happens, that would also be appreciated.
    Cheers,
    Jarrod.

    Monitors should be calibrated at around 120 cd/m2. This is usualy around 2/3 brightness for Cinema displays and around 4 to 5 clicks back from maximum on a mac book Pro. If you don't, you'll think all your prints are far too dark.
    >being a different luminance than the loupe view image on the same monitor
    huh? I thought you were comparing between monitors?
    Lightroom might not realize that you moved the entire interface to a different monitor and use the wrong profile or it forgets to use the different profile for the preview. This is very common even in managed apps. Lightroom does have a nice dual monitor interface now that uses the correct profiles for both monitors, but I don't think it likes the main window being dragged over.

  • LR 2.7 bug: Tone Curve is ignored in Develop module during loading

    I have found a problem that occurs after upgrading from 2.6 to 2.7. It probably wasn't existent before, but now I am not sure.
    What happens is this: After making a Tone Curve changes to a series of photograps, I stayed in the Develop module and looked at the next/previous photos and this happens during every change:
    1) current photo is displayed
    2) I click on another photo
    3) The new photo is displayed and "Loading..." message appears
    4) [After about 0.5 sec.] The new photo darkens (more precisely: Same view as without the Tone Curve adjusments)
    5) [After another 1 sec.] The new pohto lightens up again (Tone Curve is applied correctly) and "Loading..." message disappears
    This prevents from comparing brigness of photographs directly in the Develop module In the Library module, this problem doesn't happen.

    Hi Dan,
    OK, so now I'm confused... I have removed the profiles for the monitors (one for each) and now use the manufacturer supplied one and haven't been able to get a crash since yesterday when I did the change. I'm not 100% confident the bug has gone, but it's passed my "it should happen by now" criteria. I'm wondering if the size of the .icc profiles could have an influence. When I calibrate my monitors, I always do a full calibration which stores the data as a full LUT iccview.de lists it as:
    Description Tag:
    Monitor_2_17-03-2011
    ICC-Tag: BToA1 (Colorimetric)
    Calculation: LUT with 35937 grid points
    Header:
    size = 690296 bytes
    CMM = 'APPL'
    Version = 2.4.0
    Device Class = Display
    Color Space = RGB
    Conn. Space = XYZ
    Date, Time = 17 Mar 2011, 15:50:32
    Platform = Microsoft
    Flags = Not Embedded Profile, Use anywhere
    Dev. Mnfctr. = 0x0
    Dev. Model = 0x0
    Dev. Attrbts = Reflective, Glossy
    Rndrng Intnt = Perceptual
    Illuminant = 0, 1, 0 [Lab 100, 0, -0]
    Creator = 'LOGO'
    Total volume of gamut is 885574 cubic colorspace units
    The profile I have moved to and which seems to be working is a much smaller matrix profile. iccview.de says:
    Description Tag:
    DELL U2410 Color Profile,D6500
    ICC-Tag: XYZ Matrix
    Calculation: 3x3 Matrix
    Header:
    size = 6756 bytes
    CMM = 'ADBE'
    Version = 2.0.0
    Device Class = Display
    Color Space = RGB
    Conn. Space = XYZ
    Date, Time = 1 Mar 2010, 14:15:19
    Platform = Microsoft
    Flags = Not Embedded Profile, Use anywhere
    Dev. Mnfctr. = 'DELL'
    Dev. Model = 0x534654
    Dev. Attrbts = Reflective, Glossy
    Rndrng Intnt = Perceptual
    Illuminant = 0, 1, 0 [Lab 100, 0, -0]
    Creator = 'DELL'
    Total volume of gamut is 1401609 cubic colorspace units
    So, assuming I get no more crashes, how do you want to debug this further? Do you want my icc profiles?

  • How do I view two "different" images in the Develop module so I can match exposure ?

    Seems like a dumb question, but for the life of me cannot figure this out ?
    Thx

    I am not aware of any view mode in the Developer module that is similar to the Library module's Compare View mode. If the images you are trying to adjust were taken at the same time under similar lighting, you can select the settings of the image you adjusted and copy them to the other images. Select the image whose setting you want to copy and then click on the Copy button found in the bottom left side panel. This will display the Copy Settings panel. Insure the setting you want to copy are checked and any you don't want to copy are unchecked. Click the Copy button. Next, select one or more images you want to copy the setting to and click on the Paste button (bottom of left panel). The selected setting will be applied to the selected images. You can also perform a similar function when in the Library module but this time, look for the Synch Settings button found at the bottom of the right hand panel. Button names are changed but the dialog is essentially the same. Photos can be selected either in grid view or the film strip.

  • Lightroom 3.0 Develop Issue: Can't Access Develop Module

    Hello.  Need to tap you guys' expertise!
    Went into develop module on my Lightroom 3.0 run on Windows Vista.  Did some editing with the color, closed the color I was working with, opened and used a new color, went to erase and the pic disappeared!  Screen faded.  I closed the program, re-entered my LR and this message showed up on a wide empty screen:
    ?:0:attempt to compare number with string
    I exited the message box and went into my Library.  Then, after finding pics, hit the develop module tab, would not come up.  Same message appeared.  I can access everything else in my LR but the develop module.  I have tried to reboot the computer and re-access LR, not successful as message still appears.  Tried closing and re-opening LR, but the same thing happens.  Not sure what happened as this never happened to me before.
    Can anyone offer any insight as to what may have happened and what I can do to fix this problem?  I am pulling my hair out as I have pics to finish and cannot make any changes on any of them!  Ugh!  HELP!!!!!     Grrrrrr...........

    Just wanted to point out that re-installing Lightroom hardly ever solves a problem.
    Updating to the latest version usually will do.
    Should the preference file deletion not solve the issue, try to create a new catalog and just import the images you need to get ready urgently.
    Better to start over with them than not getting anything done.
    You can always import from this partial catalog afterwards, when you  will have restored the rest.
    This should address catalog corruption.
    For same root cause you could also try your last backup(s) of catalog.
    User presets could be the culprit, as well (move them hiding from LR).
    Worst case: LR is an early detection means for damaged RAM...
    I wish you a speedy solution,
    Cornelia

  • Can you only increase expose by 2 stops in the develop module?

    Can you only increase expose by 2 stops in the develop module? IT seems you can make photos really bright in the Library module compare to the develop module.

    My develop module goes –5 to +5 steps on the exposure slider

  • Problems losing quality when going from develop module to library module ??  anyone have a fix

    Problems losing quality when going to library module from develop module.  Sharpness and color quality decrease

    This is normal. There will be a difference as you are comparing Library Previews with the image in Develop which accesses the original file, although the difference is usually slight. Real results need to be judged from exporting after selecting the output sharpening e.g. for glossy paper, if printing or screen sharpening for web images or emailing.
    The idea with sharpening is to apply capture sharpening so that the image in Develop looks just sharp but not over sharp. Lightroom then uses the correct algorithm for output sharpening based upon image size and quality settings etc.

Maybe you are looking for

  • Can use airplay on other devices if I have my iphone docked in one

    Hi Can anyone offer any advice? I'm looking to buy several airplay enabled devices to stream itunes around the house and understand that I can only play the same song out of all devices, but can anyone tell me that if they all have docking stations w

  • New computer, uploaded music, but some is missing in iTunes

    I uploaded my music from a series of USB drives and I can see all of my music in my iTunes library, BUT when I open iTunes, some of it is missing. I've run the 'Organize Library' and it still doesn't appear in the iTunes music screen. When I search f

  • Non-grouped contacts?

    Is there any way I can tell which Contacts have not been assigned to a group? (I've tried figuring out how to set up a Smart Group to do this, but haven't figured it out.)

  • Adobe pro X and Spanish install

    As part of features for Acrobat Pro X, it says you can install Eglish, French, Gernan. and Spnish. But when it comes to installation there is no Spanish install, it only installs English, French, and Gernan? does any one knows how to fix it? or how t

  • Cardanality In adobe forms

    Hello SDN,                I have a simple User form, with one text Field.How can i make this field Optional or mandatory in terms of cardanality. What is the default in Adobe forms. Regards, Anirban.