About Lr Develop Module

Develop Module has two very tiny square spots to click turn on/off panel. It takes a little concentrating to hit the right spot. Could those toggle buttons change a bit? Just simply one spot toggle on/off. It would be easier to use.
-pete-

Try putting the Develop module into "Solo" mode (right-click on one of the panels - "Basic", "Detail", what have you - and select "Solo Mode" from the menu) - this automatically closes open panels as you open a new one, saving you from the trouble of closing them yourself.

Similar Messages

Doesn't launch after 5.5 update "Develop module is disabled"

Im REALLY HATING my LR 5.5 experience... first it wouldnt launch AT ALL... then that got fixed, worked for A DAY. Re-launched it, and now I get this BS about the "Develop Module Being Disabled"...
Have tried all 3 "work-arounds" suggested in the forums, none work. About to get a pirated version that ACTUALLY WORKS.
I REALLY need to work and this isnt helping AT ALL!
Please help?

Even though you purchased a license for Lightroom, you have installed the creative cloud installation of Lightroom. It cannot be activated with your serial number. It would have to be activated with your Adobe ID and password. You will have to remove that installation and then install from one of these two links:
Adobe - Lightroom : For Windows : Adobe Photoshop Lightroom 5.7.1
Adobe - Lightroom : For Macintosh : Adobe Photoshop Lightroom 5.7.1

I upgraded to Lightroom 5 about 2yrs ago,bit now my system is asking me to renew my membership to activate the develop module in Lightroom5. The upgrade was already paid for though.

I upgraded to lightroom5 about 2yrs ago, but now my system prompts me to renew my membership to activate my develop module as the develop module has been de-activated

If it asks for an activation to activate the develop, it must be a CC version installed. If you use a CC version you have to pay you for your selected plan like monthly or annually.
If you should have the stand-alone version because you don't have/want a CC plan, then you probably have installed the wrong version - the CC instead of the stand-alone.
Download the stand-alone version from here: Win, Mac

Since updating to LR5.5 it crashes about every 5-10 images while working in the development module. Computer is PC Windows 7 Home Premium. I have been using this computer for several years with zero problems. Is this related to the updating? What is the f

Since updating to LR5.5 it crashes about every 5-10 images while working in the development module. Computer is PC Windows 7 Home Premium. I have been using this computer for several years with zero problems. Is this related to the updating? What is the fix?

Do you get an error message? If so, what does it say?
Do you get a Blue Screen?
Does something else happen?

In the develop module, sliders jump about when clicked

In the develop module, sliders jump about when I try to click on them.
This happens after I re-size the window by dragging to the left in order to make the sliders longer. Any ideas on How to stop the sliders from misbehaving?

I am seeing the same problem. Closing and re-opening LR reduces the problem, but there is still a slight (~0.05) change in the value when the slider is clicked on. More disturbing, resizing the right panel brings the problem back, with very large jumps. For example, my Exposure value changed +5 units when I clicked on the slider after widening the panel.
LR 5.7 from CC
27" (late 2012) iMac running Yosemite
Problem happens with either Apple Magic Mouse or Wacom Intuos tablet (with the latest driver, 6.3.10w2)
Edit: Deleting the Preferences file did not solve the problem.

I am running LR 4.4 on a iMac with OS X (Yosemite). Everything works in the develop module but when i get to the print module, clicl on print and the apple print dialogue box opens, and I click onn print there, the app closes. It has now happened about

I am running LR 4.4 on a iMac with OS X (Yosemite). Everything works in the develop module but when i get to the print module, clicl on print and the apple print dialogue box opens, and I click onn print there, the app closes. It has now happened about a dozen times. I have downloaded LR 4.4 from the internet but the problem continues.

Very Important, how much Free Space is on your Hard Drive first of all? Click on the Macintosh HD on the Desktop, then do a Get Info on it.
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.
Do they launch OK while in Safe Mode?

How can I quickly configure & save different views in Develop module?

Is there a method to quicky switch custom views (including my favourite selections for Panels, Toolbars, Window's Bars, and Info Overlay)?
In the "Develop" module, I would like to switch quickly from (1) seeing all panels, etc. to (2) seeing only my image and the right-side panel. There must be a better procedure than what I do now (please don't laugh). I use about six keystrokes as shown below:
(a) turn off top, left-side, and bottom Panels by clicking each individually,
(b) press the "t" key to turn off the Toolbar,
(c) press the "f" key to turn off Window's two top bars and one bottom bar, and
(d) press the [Ctrl-i] key combo to turn off the Info Overlay.
At other times in the "Develop" module, I use about six keystrokes to turn all these hidden objects back on!
I am using "Lightroom 2.5" with Windows Vista Home Premium.
Thanks in advance for your help.

Thank you, johnbeardy, for your suggestion of "Solo Mode". Checking "Help" for "Solo", I discovered the Windows\Screen Mode menu for the 1st time -- it helps. While right-clicking the panels, I also found "Sync with Opposite Panel" which allows me to turn both the top and bottom panels On or Off with only one click. (the LR book that I use doesn't cover these items).
However, I have not yet benefited form "Solo Mode". I turned it On for both left and right panels, but it doesn't appear to make any difference, even after I closed and re-opened LR. Is there something else I need to set to make "Solo" work? Is it applicable for only the left and right panels?

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.

Third party plug-ins for develop module

It's been a while since this has been brought up, so I thought I'd restate this request in the current context.
One of the major things that's missing from the Lightroom ecosystem is a way for third parties to produce plug-ins/extensions for the develop module. The advantages would be numerous:
1) Ability to add exotic features that may not appeal to a large audience (although in combination all these features would), such as negative inversion, alternate tone curves, color correction and replacement tools.
2) Third-party versions of features that users have been clamoring for: color space clipping, lens/perspective correction, multi-parameter noise reduction.
3) Community buzz (if approached more openly than the Photoshop SDK)
As for the implementation, maybe it's a good idea to let developers use a combination of Lua and PixelBender (2.0)? The combination would allow for platform-independent code that is still fast. Also, the plug-ins should get to choose from (at least) two entry points: (1) after demosaicing but before color mixing (B&W) & tone curve, and (2) at the end of the pipeline.
Here's hoping for the SDK appearance in LR3!
Simon

There have been numerous requests for third party plugin (or some way to extend the Develop module) over the years. I agree it is a critical item that needs to be addressed ASAP. Hopefully in LR3.
What I find most interesting about this particular request is that Simon has pointed out that Adobe already have the technology (Pixel Bender) and just need to apply it. Its already in Photoshop CS4 and Flash 10, and is used for non-destructive editing in those apps. So I'd be extremely disappointed if it doesn't make it into the next major release of their workflow/non-destructive editing tool. You'd have to be an optimist to expect it anytime before LR3.
The only real question remaining is will Pixel Bender, as it currently stands, meet the full needs of the LR plugin developer community? e.g. Could Noise Ninja or Nik plugins be ported to Pixel Bender? My guess is "not yet". Then Adobe need to figure out how much to change LR, how much to change Pixel Bender, and indeed how big a first step they take when adding Develop module extensibility to LR3. Lets hope it is enough for developers of the most popular plugins to invest the time and effort to develop LR specific versions of their products.
My 2c worth.
Matt

Unreasonably Slow Develop Module LR 4.3/5.3

I was running LR 4.3 (updated version) on an iMac with OSX Mavericks w/ only 4GB of RAM but that hasn't been a problem in the past, 350GB of free space on the desktop hard drive, and 200 GB of space on the external drive where the images and catalog are located. Working on a wedding with RAW files, CR2 (Canon 5D Mk II) and NEFs (D700) (about 700 images total). Develop module takes 60+ seconds (up to several minutes) to load each image with the "loading" window, then an additional 60+ seconds for the image to load completely from a pixellated preview. This also happened on my Macbook Pro wth 16GB of RAM. Tried to auto-sync develop settings (Basic exposure settings, lens profile corrections) for ~45 photos and it took over 3 hours on the MBP. Haven't been running any other programs, ran a cleanup on the desktop to clear unnecessary files. Cleared the RAW cache, increased the size of the RAW cache, optimized the catalog, rendered the 1:1 previews (took many hours), and even created a new catalog with the images on the desktop. When all of this didn't work, I upgraded to LR5.3 and I'm still having slow (not quite as slow as before, but still infuriatingly slow) reaction times from Develop. I've wasted so many hours and I can't pinpoint where the problem is coming from.
Also receive an error message that "another program is using ____ Catalog" for several other catalogs. Could that be related to this?
Is my only option to get a new computer? This iMac (21.5") supposedly doesn't support any additional RAM...or so I've heard.

myhrmar wrote:
I just had a chat with the adobe support team and they say Lightroom is working perfectly, because the changes show up in Bridge and LR. And the people from ACDSee say that the lightroom edits are Adobe specific.
Correct. That's proprietary processing with the LR engine which has yet to be done (rendered and exported). The preview in those Adobe app's understand this and show you the edits but ACDC can't. You have to render an iteration as a TIFF or similar with the edits applied for another app to 'see' that. ACDC has not access to those preivews so it doesn't show you what will be applied upon export.

Rendering issue in Develop Module

Slow rendering has been discussed in many threads, but can anyone explain what is going on with this specific issue I am having?
If I am working in the Develop Module and I render two raw files at 1:1, after the initial rendering delay I can generally toggle between the two and they are rendered almost instantaneously. I assume this is because some info has been stored in the ACR Cache and Lightroom can quickly display them. Now if I render a 3rd raw file at 1:1 and try to toggle between 3 images, one of them always needs 10 seconds or so to load/render. What is happening here? I thought the purpose of the ACR Cache was to allow for fast rendering of previously rendered images. I currently have my ACR Cache set to 10GB and I have recently purged it, so I am nowhere near the limit. Other system/software specs as follows:
LR 5.2
NEF files from Nikon D7100 (approx 30MB)
iMac 27-inch 2560x1440
OS 10.8.5
Processor: 3.06 GHz Intel Core 2 Duo
RAM: 16GB
Video Card: ATI Radeon HD 4670 (256MB)
Storage: 1TB SATA 7200rpm, 25% full

LanceBenedict wrote:
Thanks for the explanation on the RAM caching. If I am understanding you correctly on the ACR Cache, it sounds like it is essentially useless once you have applied some editing to the image because you need to wait on those edits to be rendered.
No, I wouldn't agree that it's useless. When you load an image into Develop you'll be presented first with a brief view of your Library preview, which should quickly be replaced with the ACR Cache "scene-referred" preview that will have any existsing edits applied before you see it. That should all happen quite quickly, and when that preview is loaded the sliders will be activated. When that happens you can start work, even though the full file is being rendered in background, and there is no need to wait until the "Loading" indicator goes out (as I said earlier, you can turn that off if you prefer).
So the benefit of the ACR Cache entry is that it allows you to start work in Develop whilst the original file is still being fully converted.
Note that although we are talking specifically about the ACR Cache entry, the same holds true for DNG Fast Load Data and/or Smart Previews. Which one of those 3 is initially used depends on what exists at the time of loading, and what file type is being used. But the same principle applies to all three.
In terms of reducing the rendering time, that's a more problematical issue as there are various factors in the pipeline which come into play, any one (or more) of which may be sub-optimal. These factors include:
1. Size of the files being loaded. It should go without saying that 36mp files from a Nikon 800 are going to take quite a bit longer that the 10mp files from say a Canon 40D.
2. Location of the files and speed of the interface, i.e. expect image files on a USB2 connected hard drive spinning at 5400rpm to be a lot slower to load than if they were on a 7200rpm drive internally connected on a 6gb/s Sata hub.
3. Once the data has been read, how fast is the CPU.....rendering a raw file will be quite a CPU-intensive task, so the faster the processor the better.
4. User expectation.....one man's "painfully slow" could be another's "quite acceptable".
With that in mind, I have no idea if what you are experiencing is "typical" or too slow. Putting it into context, all my original files are on a fast internal drive on a 3gb/s connection, I have an i7-930 quad-core processor (now over 3 years old, so not leading edge by any means), 12gb of RAM. Full loading times in Develop are now about 3 seconds per image when using 22mp files from a Canon 5D3.
Looking at the things you've tried, purging the ACR Cache and increasing its size would have no effect unless:
a) There was a problem with the existing cache, and
b) You regenerated new cache entries
Discarding old previews and rebuilding would have had no effect on Develop loading times, nor would downsizing the dimensions of the develop window.
Increasing system RAM should certainly be beneficial to other areas of Lightroom, I'm just not sure it would have a specific benefit to image loading into Develop. That might be dependant upon what else was running in the system at the time.

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.

Library Module view of Photo different than Develop Module Version

I'm sooooo frustrated. I'v worked on a .NEF file using Topaz Lab's Adjust4, then Denoise then Photoshop CS5, each time it saves an new version of my file in Lightroom, I have about 6 of them.
Problem....when I scroll through pictures in develop, the pictures look perfect (noise reduction, excellent colors and contrast, the way I expect it to look after my adjustments), then about 1-2 seconds later it changes to a noisy, less contrasty and less colorful version).
If I switch to Library mode the pictures looks good again. If I export, though, it exports the Develop module version that doesn't look good. The whole thing is very hit and miss, sometimes Library looks good, then other times it looks like Develop. If I zoom to 1:1, then both version look bad permanently.
I just want to export and use the Library version of the file. Also, I cannot recreate the look using any combination of Lightroom adjustment, which strongly suggests that the Library version I am viewing is the result of my Plug-in and Photoshop work.
I've read that the initial view may be the JPG version of the shot, but I don't think so, it looks way better than the other JPG's that came out of the camera at the same event.
Help

Its possible the thumbnail is viewing the edited version that was created via the camera. Lets say you made a change in the camera such as sepia for example. When you first load the image into LR it will be displayed as sepia, but a few seconds later, it will remove those changes giving you the raw image.
In the develope module it ignores the camera changes and you must recreate the changes in the develop module. When you are done, its a good idea to save the file (ctrl-s on windows) which saves the changes to the sidecar file, should you need to see the changes in Bridge for example.

Lightroom 2.3 crashes in Development module

I am having a brand new problem with LR 2.2 & 2.3 with my Dell 730x 64bit 6GB Ram. I am running VIsta Home Premium 64 bit.   I have been running LR 2 since it came out with no trouble - until a few days ago.
I also have a Sony Monitor as the #1 Monitor on the Nvidea GeForce 9800 GT using the Generic PnP Monitor driver from Microsft - 6.0.6001.1800 dated 6/21/2006.
I have a second monitor which I use for Lightroom: - Dell 2007FP Monitor with Nvidia GeForce 9800 GT Video card with all settings at defaults. The driver is NVIDIA v 7.15.11.7744 dated 7/17/2008. This was the original driver and has been performing well for months
This has worked splendidly since I bought this high end PC in Feb, 2009.
. In the last few days, however LR crashes any time I try to use the Develop module on the Dell monitor. I get "Adobe Photoshop Lightshop 64 bit has stopped working" when I try to crop or use other tools at the top of the Develop list. The lower tools like exposure changes the histrogram, but not the image. This also happens when I switch the driver on the Dell to the Generic PnP Monitor driver. This happens for NEF and JPG files.
When I run Lightroom on the smaller Sony screen, the photos don't display - only gray rectangles for photos. However, in the Develop menu, when I try to crop a gray rectangle, the image appears and the crop works OK. When I finish the crop, the image goes back to a gray rectangle. It does not, however crash the program. This makes Lightroom unusable since photos and thumbnails are not visible. I believe this may have been happening for a longer time, but since it worked fine on the larger Dell screen, I was OK.
All the rest of the LR modules seem to to work. .
Here's a list of things I've tried with no success - they all resulted in the Develop Module crashing LR.
The problem started a few days ago, so I went ahead installed the update to go from Service Pack 1 to Service Pack 2. There was no diffrence.
I have re-booted with only MS services - no others and no startup using msconfig - same problem
I have deleted the preferences file and created a new one - no luck
I have imported new files - same sympton
I have loaded other catalogs - same sympton
I have uninstalled 2.3 re- installed ver 2.2 - no luck
I have uninstalled 2.3 and installed the 32 bit version of LR - same sympton
I have run chkdsk on my drive - no problems, no difference
I have removed the Develop Presets, External Editor Presets, Modules lrplugins, Local adjustment Presents from AppData\Roaming|Adobe\Lightroom directory - no problem
I have tried to use system restore several times - to dates prior to recent windows updates, but system restore won't work???
Photoshop CS4 64 and 32 bit work fine, but it doesn't have the speed of editing NEF files that LR does when it works.
Any other ideas on what to try? I have completely changed my workflow to do 80%+ Lightroom and loved it. The thought of returning to Photoshop is devestating!

FIXED!!
Thanks for the suggestions from those who replied. I spent 90 minutes last night with the Dell support team who provided me with a previously unaccessable new driver for my NVIdia GeForce 9800 CT - this one was version 7.15.11.8130 dated 12/30/2008. They also provided me with the new NVidia Display Control Panel.   This program is in windows/system32/ and runs with the file name: nvsvc.exe.
Two suggestions were to turn off this program. It was not running, and typically has not been running over the past few months. I started it to see if it made a difference. It did not. Then I turned off and it still didn't change any LR problems. My guess is that there are some options that can mess stuff up, but I only had the defaults set.
Another suggestion from KDWAVES: Gray rectangles when using the Sony monitor is a sympton of a corrupt color profile. If you use color calibration, try re-calibrating the Dell. If you are using the default color profile, try changing it.
My Sony was using some default, so I loaded the Dell Monitor.icc color profile created by my color calibration hardware/software (Eye One Match v3) and appied to the Sony. It worked and the gray images were displayed properly. Also all the Develop modules worked fine. I was a little disappointed, since the Sony is a smaller moniter and I bought the larger Dell Monitor specifically to be the color calibrated large monitor for photo editing. So I moved lightroom to the Dell Monintor .....    AND IT WORKED GREAT!!   Thanks much KDWAVES!
I had only calibrated the one monitor since both monitors were run by the NVidia video card and it seemed to only run one color profile at a time. I didn't bother to calibrate the Sony, but just adjusted the color controls manually to make the screen look like the Dell. Now that both monitors have the same color calibration file, everything seems fine.
I've listed all the details for the next person who gets this surprise. I still can't figure why it ran OK for the last few months, on the Dell monitor.
I can't thank you guys enough for helping. Maybe the next victim won't take the five days it took me to unravel this one.
This is my first Vista machine and I bought theVista 64bit version and the Intel Core i7: quad & hyperthread processers for the Adobe 64bit software. When I'm not chasing bugs like this one, the machine and the Adobe software run REALLY FAST. I have been able to double my photo coverage since the Lightroom RAW file import / export / render / edit and everything goes about as fast I can click the keyboard - unlike any of the Adobe stuff has behaved on my prior PC's. I have even switched my sports photos to LR exclusively since it's so fast,
P.S. CR Henderson's advice on a new Nvidia driver dated May 6th 2009 is great idea. I will be hunting for that next. I have not had any Photoshop CS4 problems in either 32bit or 64bit versions (except not many plugins run in the 64 bit version). But I didn't buy this PC until I confirmed that my NVidia GeForce 9800 CT video card was on Adobe's approved list.

Having problem with develop module

When I take a pic from library to develop module, I get the "loading" message but then it doesn't go off (and doesn't load); this is a new problem; hasn't happened before; I don't know if recent loading of 2.6 version caused a problem. Thanks for any insight.

Is there anyone that can help? This is frustrating to say the least. The edits are taking effect, but only showing on the filmstrip. If I go back to library the edits are there, and will then show in develop when I take it back again. This makes it just about impossible to apply anything like cloning, or minute edits, because I can't see them when they happen!!

About Lr Develop Module

Similar Messages

Maybe you are looking for