Develop Module: Inaccurate Preview in Detail

So the develop module is producing a different rendering than the library module is in regard to sharpening and noise reduction.  In develop the image is extremely blurry where in loupe view it seems to be previewed correctly. So I tested by bringing the image into PS (cmd+E) but processing the DNG in LR.  I then quit PS, leaving an untouched PSD that should be identical to the DNG. In Loupe view the DNG is close to identical, though still a little softer. In develop, the DNG is obviously more blurry than the PSD.  So I pulled my preview file, forcing LR to re-render the previews and the images were the same as before.
PSD in Develop:
DNG in Develop:
PSD in Loupe:
DNG in Loupe:
This issue is making it really dificult to perform sharpening and noise reduction.

There are two issues. One there is a bug with the rendering in Develop in LR 3. After you move a slider, the develop view will lose all sharpness only to regain it after zooming in and out to 1:1. See this thread: http://forums.adobe.com/message/2898311#2898311
No solution for this yet. The Develop view is supposed to now be able to give you a preview of what the image should look like after proper output sharpening, but it doesn't really do that correctly yet.
The second issue is that you should NEVER try to optimize sharpening (and noise reduction) in the Fit/Fill zoom views. You should only do this at 1:1. The reason is that the sharpening is supposed to be a capture sharpening meant to deal with loss of sharpness due to the demosaic process and some lens blur, meaning that it works at the pixel level, not at the very low res zoomed out level. Do not attempt to deal with sharpness at the scaled down level. This is done at the export stage and has to be done in different levels depending on the output medium (screen or print). You cannot accurately preview capture sharpening and noise reduction in a zoomed out view. It is just physically impossible due to the low res display.
Lightroom does not show capture sharpening and noise reduction in Develop in anything but the 1:1 (and higher) zoom levels in order to make the program usable. It would be completely glacially slow if it would have to rerender the entire image at 1:1 (otherwise the sharpening has no real effect) including all the settings you apply and scale down for display. Even on the fastest computers that would take a few seconds and be unacceptably slow as a result. In Library you see some effect because the view in Library is rendered from a jpeg preview, not from the original data. This makes it much faster to display, but not as accurate.

Similar Messages

  • Lightroom shows no image in develop module

    I just downloaded the new Lightroom and when in Develop module, I just get a blue screen. When I select before and after in develop, I get picture on L and blue screen on R.

    Hi All,
    This is a GPU related issue. Please update your GPU drivers from the manufacturers website.
    In the mean while, disabling "Use Graphics Processor" (Preferences > Performance), should help load the Develop module.
    For more details, Adobe Photoshop Lightroom Help | Lightroom GPU FAQ
    Similar post, Lightroom CC - blue box in develop module
    ~ Arpit

  • 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

  • Just updated to LR5.4 on my mac and the Detail Panel in the Develop module is missing. How to fix?

    How do you fix the missing Detail panel in the Develop module? I just updated on the Mac to LR 5.4.

    Right-click on any RH panel header in Develop and put a check mark next to the Detail panel

  • 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.

  • Lightroom 3.2 previews of presets not showing in Develope module.

    Hey, any idea why LR 3.2 will not preview the effects of presets when scrolling over them in the Develop module?  This was a fast way to work creatively with previous versions of LR.
    This happens for all presets, including those shipped with LR.  Presets "work" but you cannot see effects unless you apply them first.  Preview is broken.
    Anyone else having this issue or have a fix idea?
    Thanks!

    THEY SURE DO!  WISH I SLEPT MORE...:)
    THX!

  • Lightroom 4 (and 5) Develop Module Preview Problem

    The Develop module in Lightroom 4 (and 30 day trial of 5) is not updating/rendering the preview as I edit RAW image files. It also doesn't show the full size preview unless I zoom in on the image in the Library view first. I do have the latest RAW and the lrdata file is in the same folder as the catalog file. I have the RAW Cache set to 5gb and noticed there is nothing in the RAW Cache folder (doesn't seem to be important for editing anyway. The Navigator window and filmstrip versions do seem to update as I make changes.

    Alright,
    no replies so far! Anyways, here's some more information which is leading me to the conclusion that the bug causing the effect described above is a combination of Apple's SMB implementation of Mavericks and the way Lightroom is actually using SMB network access:
    I did another trial by connecting a USB hard drive to the USB port of my router (Netgear). The connection is quite slow, but moving one of the folders in question (see my 1st post above) to the shared drive connected to the Router made Lightroom on my Windows machine to see the photos again, when I told Lightroom where to find the moved folder!
    Everything was working as expected, on the Windows machine again! Moving the folder back again to the Mac Mini fileshare was causing Lightroom on the PC to get blind again for the pictures trying to sync or import. However, accessing and modifying a photo was possible again, like it was before the trial. So it's only the sync and import function having a problem!
    I also did some trial in re-building ACLs and access rights on the file server with no luck. So there's got to be a functionality in sync and import of Lightroom which is using a certain SMB feature which is not supported by Apple's SMB implementation!
    Any thoughts or hints?
    Thanks!

  • 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.).

  • I use a Mac, new to lightroom, I purchased the software, and now I cannot get into my develop module because it is telling me that I need to renew my membership ?  Lost !!!  lost in a dark cold cave of lightroom someone please help me !!

    I cannot get into my develop module on lightroom, it is telling me to "please renew my membershipto reactivate the develop module"  I do not understand.  I bought the software must I pay a membership as well ?  Also I do not want to use lightroom mobile and it is trying to sync my photos.  I use a MAC

    Did you purchased the Full Perpetual License from Adobe for $149.00?, if so then what has happened is that you probably downloaded the Creative Cloud trial version which has now expired.
    The license key for the perpetual version will not be accepted to activate the CC version.
    Uninstall the existing Lightroom and then download the one available from the link below. The uninstall process will not affect your Catalog, Preferences or personal files but will just remove the application. Install the new download and you license key will be accepted.
    Adobe - Lightroom : For Macintosh : Adobe Photoshop Lightroom 5.6
    If this is not the situation you face then provide some more details.

  • Lightroom crash in Develop module with RAW files with sidecar files from ver 3

    The issue probably has to do with the differences in settings between the two versions but I figured I would document what I am experiencing. 
    I am using the 64 bit version of Windows 7.
    I imported a group of pictures with the XMP sidecar files generated with Lightroom v3.  All the image files, a mixture of Canon Mark 5D II RAW and jpg files from my point & shoot UFO camera, imported without issue picking up all my tagging and GPS settings. When importing you are put into the Library module and from the Library module I could click on any RAW or jpg file, look at the meta data and view full screen.
    I then entered the Develop module with a jpg picture selected and none of my settings made it across. The process was set to 2012.  I was able to try out the new adjustments and all worked very well. 
    I then selected a RAW file while still in the Develop module and all hell broke loose.
    I got a tip window pop up, the film strip went orange, the rest of the app screen then became greyed out and then behind tip pop up a crash window containing this information appeared:
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: lightroom.exe
    Application Version: 4.0.0.1
    Application Timestamp: 4ef2621d
    Fault Module Name: MSVCR100.dll
    Fault Module Version: 10.0.40219.1
    Fault Module Timestamp: 4d5f034a
    Exception Code: c000041d
    Exception Offset: 000000000003c1be
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033
    Additional Information 1: cc7e
    Additional Information 2: cc7e9ac0f4374c9d4c9f2c948a85a235
    Additional Information 3: 41e7
    Additional Information 4: 41e779def86567567ae94271de75e4e9
    There was no other path but to have the app close after that.  Now since Lightroom has left off with the RAW file in the develop module when I restart the app it starts in the develop module with that same RAW image selected and I crash before I can change to a jpg.   I am probably going to have to delete and recreated the data file to use the app again
    After the all this I went back and checked to see how I had the catalog settings in LR 3 set because there were no sidecar files for the jpg images.  I did not have the option to write settings to jpg and tif files but did have write settings to sidecar set.  So I have a bit of a mystery why I have no sidecar files for jpg files when I should have based on the way the settings were.  This probably explains why I had no issues at all with them in LR 4.
    I am going to get LR 4 working again and then import the same batch of pictures without any sidecar files and see if I have any issues.  I will report back soon.
    When I imported the files without the sidecar files I had no issues at all but the RAW images came under older process not the 2012 process. There were no settings without the sidecar files so why would the app not start the images at the most recent process level? I updated then to 2012 and some of the setting sliders changed.  I tried all the adjustment might use with both RAW and jpg files and no issues were observed.
    The new develop module does seem to light darker areas without impacting other lighter areas better.  The brush toll does work better and I see some additional settings were added along with presets.
    As I posted elsewhere, I am disappointed content aware fill and healing were not included.  This is the functionality that would save me from going to Photoshop when I have some undesirable reality in an image.
    I tried out the new geo coding functionality and I really like it as it beats using Google maps on the web (painfully slow these days), dropping latitude / longitude markers, copying and pasting the data from the markers into a Lightroom plug-in and then going through a time consuming three step process.

    Idem for me on Mac:
    No problem to developp a RAW file from a D300 never develop before in LR 3 but when I enter a RAW file develop in LR3 into the develop module of LR4, Lightroom Crash. The report on Mac:
    Process:         Adobe Photoshop Lightroom 4 [412]
    Path:            /Applications/Adobe Photoshop Lightroom 4.app/Contents/MacOS/Adobe Photoshop Lightroom 4
    Identifier:      com.adobe.Lightroom4
    Version:         Adobe Photoshop Lightroom 4.0 Beta [800002] (4.0)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [295]
    Date/Time:       2012-01-13 18:46:19.729 +1100
    OS Version:      Mac OS X 10.6.8 (10K549)
    Report Version:  6
    Interval Since Last Report:          24816 sec
    Crashes Since Last Report:           11
    Per-App Interval Since Last Report:  3225 sec
    Per-App Crashes Since Last Report:   11
    Anonymous UUID:                      B2BF54C2-46B7-4994-A520-D74AD1B91289
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000126c5f000
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   com.adobe.ag.AgImageIO                  0x0000000116f384f4 private_load_AgColorProfile + 386306
    1   com.adobe.ag.AgImageIO                  0x0000000116f2e7e7 private_load_AgColorProfile + 346101
    2   com.adobe.ag.AgImageIO                  0x0000000116f2ccdc private_load_AgColorProfile + 339178
    3   com.adobe.ag.AgImageIO                  0x0000000116f2c5e4 private_load_AgColorProfile + 337394
    4   com.adobe.ag.AgImageIO                  0x0000000116f2cb7c private_load_AgColorProfile + 338826
    5   com.adobe.ag.AgImageIO                  0x000000011702773b private_load_AgColorProfile + 1365833
    6   com.adobe.ag.AgImageIO                  0x0000000117029937 private_load_AgColorProfile + 1374533
    7   com.adobe.ag.AgImageIO                  0x0000000116f3f3eb private_load_AgColorProfile + 414713
    8   com.adobe.ag.AgImageIO                  0x0000000116f3f4cd private_load_AgColorProfile + 414939
    9   com.adobe.ag.AgImageIO                  0x0000000116fb8e70 private_load_AgColorProfile + 913022
    10  com.adobe.ag.AgImageIO                  0x0000000117147175 private_load_AgColorProfile + 2544003
    11  com.adobe.ag.AgImageIO                  0x00000001171482d6 private_load_AgColorProfile + 2548452
    12  com.adobe.ag.AgImageIO                  0x0000000116eb7d71 0x116eae000 + 40305
    13  com.adobe.ag.AgImageIO                  0x0000000116ecc4fc AgDevelopSupport_load + 27921
    14  com.adobe.ag.AgImageIO                  0x0000000116ecc6d5 AgDevelopSupport_load + 28394
    15  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    16  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    17  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    18  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    19  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    20  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    21  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    22  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    23  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    24  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    25  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    26  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    27  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    28  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    29  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    30  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    31  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    32  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    33  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    34  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    35  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    36  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    37  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    38  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    39  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    40  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    41  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    42  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    43  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    44  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    45  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    46  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    47  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    48  com.adobe.ag.ui                         0x000000010009b4a5 AgUI_fontFullNameL + 36981
    49  com.apple.AppKit                        0x00007fff884d5d75 -[NSView _drawRect:clip:] + 3566
    50  com.apple.AppKit                        0x00007fff884d354b -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 2112
    51  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    52  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    53  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    54  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    55  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    56  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    57  com.apple.AppKit                        0x00007fff885f19c4 -[NSNextStepFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 276
    58  com.apple.AppKit                        0x00007fff884cf3de -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2683
    59  com.apple.AppKit                        0x00007fff88448c0e -[NSView displayIfNeeded] + 969
    60  com.apple.AppKit                        0x00007fff883fe5a4 -[NSNextStepFrame displayIfNeeded] + 76
    61  com.apple.AppKit                        0x00007fff88443aba _handleWindowNeedsDisplay + 678
    62  com.apple.CoreFoundation                0x00007fff82f75b07 __CFRunLoopDoObservers + 519
    63  com.apple.CoreFoundation                0x00007fff82f51434 __CFRunLoopRun + 468
    64  com.apple.CoreFoundation                0x00007fff82f50d8f CFRunLoopRunSpecific + 575
    65  com.apple.HIToolbox                     0x00007fff896db7ee RunCurrentEventLoopInMode + 333
    66  com.apple.HIToolbox                     0x00007fff896db5f3 ReceiveNextEventCommon + 310
    67  com.apple.HIToolbox                     0x00007fff896db4ac BlockUntilNextEventMatchingListInMode + 59
    68  com.apple.AppKit                        0x00007fff88418eb2 _DPSNextEvent + 708
    69  com.apple.AppKit                        0x00007fff88418801 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155
    70  com.apple.AppKit                        0x00007fff883de68f -[NSApplication run] + 395
    71  com.apple.AppKit                        0x00007fff883d73b0 NSApplicationMain + 364
    72  com.adobe.Lightroom4                    0x0000000100001c35 main + 1073
    73  com.adobe.Lightroom4                    0x00000001000017fc start + 52
    Thread 1:  Dispatch queue: com.apple.libdispatch-manager
    0   libSystem.B.dylib                       0x00007fff88de9c0a kevent + 10
    1   libSystem.B.dylib                       0x00007fff88debadd _dispatch_mgr_invoke + 154
    2   libSystem.B.dylib                       0x00007fff88deb7b4 _dispatch_queue_invoke + 185
    3   libSystem.B.dylib                       0x00007fff88deb2de _dispatch_worker_thread2 + 252
    4   libSystem.B.dylib                       0x00007fff88deac08 _pthread_wqthread + 353
    5   libSystem.B.dylib                       0x00007fff88deaaa5 start_wqthread + 13
    Thread 2:  Worker Thread Dispatcher
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    9   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    10  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    11  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    12  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    13  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    14  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    15  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    16  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    17  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    18  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    19  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 3:  ace
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   ...ple.CoreServices.CarbonCore          0x00007fff8150dd87 TSWaitOnCondition + 118
    3   ...ple.CoreServices.CarbonCore          0x00007fff8147cff8 TSWaitOnConditionTimedRelative + 177
    4   ...ple.CoreServices.CarbonCore          0x00007fff81476efb MPWaitOnQueue + 215
    5   com.adobe.ag.AgImageIO                  0x00000001170d944f private_load_AgColorProfile + 2094173
    6   com.adobe.ag.AgImageIO                  0x00000001170d9a16 private_load_AgColorProfile + 2095652
    7   ...ple.CoreServices.CarbonCore          0x00007fff8144f0d1 PrivateMPEntryPoint + 63
    8   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    9   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 4:  ace
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   ...ple.CoreServices.CarbonCore          0x00007fff8150dd87 TSWaitOnCondition + 118
    3   ...ple.CoreServices.CarbonCore          0x00007fff8147cff8 TSWaitOnConditionTimedRelative + 177
    4   ...ple.CoreServices.CarbonCore          0x00007fff81476efb MPWaitOnQueue + 215
    5   com.adobe.ag.AgImageIO                  0x00000001170d944f private_load_AgColorProfile + 2094173
    6   com.adobe.ag.AgImageIO                  0x00000001170d9a16 private_load_AgColorProfile + 2095652
    7   ...ple.CoreServices.CarbonCore          0x00007fff8144f0d1 PrivateMPEntryPoint + 63
    8   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    9   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 5:  ace
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   ...ple.CoreServices.CarbonCore          0x00007fff8150dd87 TSWaitOnCondition + 118
    3   ...ple.CoreServices.CarbonCore          0x00007fff8147cff8 TSWaitOnConditionTimedRelative + 177
    4   ...ple.CoreServices.CarbonCore          0x00007fff81476efb MPWaitOnQueue + 215
    5   com.adobe.ag.AgImageIO                  0x00000001170d944f private_load_AgColorProfile + 2094173
    6   com.adobe.ag.AgImageIO                  0x00000001170d9a16 private_load_AgColorProfile + 2095652
    7   ...ple.CoreServices.CarbonCore          0x00007fff8144f0d1 PrivateMPEntryPoint + 63
    8   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    9   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 6:  cr_scratch
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.AgImageIO                  0x0000000116fe717e private_load_AgColorProfile + 1102220
    3   com.adobe.ag.AgImageIO                  0x000000011718f99b private_load_AgColorProfile + 2841001
    4   com.adobe.ag.AgImageIO                  0x0000000116fb7fb9 private_load_AgColorProfile + 909255
    5   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    6   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 7:  AsyncDataServer
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x00000001000415af AgConditionLock_wait + 171
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    9   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    10  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    11  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    12  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    13  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    14  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    15  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    16  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    17  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    18  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    19  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 8:  Queue Processor - AgPhotoAvailability
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 9:  Preview Server
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x00000001000415af AgConditionLock_wait + 171
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    9   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    10  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    11  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    12  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    13  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    14  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    15  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    16  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    17  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    18  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    19  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 10:  Queue Processor - PreviewFileStore
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 11:  Worker Thread
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    9   com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    10  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    11  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    12  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    13  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    14  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    15  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    18  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    19  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    20  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    21  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    22  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    23  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    24  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    25  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 12:  Queue Processor - NegativeQueue
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 13:  Queue Processor - HistogramQueue
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 14:  Queue Processor - RenderQueue_Render
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 15:  Queue Processor - RenderQueue_ReadPreview
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 16:  Queue Processor - RenderQueue_Video
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 17:  Worker Thread
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    9   com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    10  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    11  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    12  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    13  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    14  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    15  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    18  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    19  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    20  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    21  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    22  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    23  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    24  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    25  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 18:
    0   libSystem.B.dylib                       0x00007fff88dd0d7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff88dd13ed mach_msg + 59
    2   com.apple.CoreFoundation                0x00007fff82f51902 __CFRunLoopRun + 1698
    3   com.apple.CoreFoundation                0x00007fff82f50d8f CFRunLoopRunSpecific + 575
    4   com.apple.Foundation                    0x00007fff87ebb14f +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 297
    5   com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    6   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    7   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 19:  com.apple.CFSocket.private
    0   libSystem.B.dylib                       0x00007fff88e14932 select$DARWIN_EXTSN + 10
    1   com.apple.CoreFoundation                0x00007fff82f73468 __CFSocketManager + 824
    2   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    3   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 20:  Worker Thread
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    9   com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    10  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    11  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    12  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    13  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    14  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    15  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    18  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    19  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    20  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    21  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    22  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    23  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    24  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    25  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 21:
    0   libSystem.B.dylib                       0x00007fff88deaa2a __workq_kernreturn + 10
    1   libSystem.B.dylib                       0x00007fff88deae3c _pthread_wqthread + 917
    2   libSystem.B.dylib                       0x00007fff88deaaa5 start_wqthread + 13
    Thread 22:  Queue Processor - renderPixmapWorkerThreadQueue
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.AgImageIO                  0x0000000116fe71de private_load_AgColorProfile + 1102316
    3   com.adobe.ag.AgImageIO                  0x0000000116fb8110 private_load_AgColorProfile + 909598
    4   com.adobe.ag.AgImageIO                  0x0000000116fb8d53 private_load_AgColorProfile + 912737
    5   com.adobe.ag.AgImageIO                  0x0000000117147175 private_load_AgColorProfile + 2544003
    6   com.adobe.ag.AgImageIO                  0x00000001171482d6 private_load_AgColorProfile + 2548452
    7   com.adobe.ag.AgImageIO                  0x0000000116eb7d71 0x116eae000 + 40305
    8   com.adobe.ag.AgImageIO                  0x0000000116ecc4fc AgDevelopSupport_load + 27921
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    11  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    12  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    13  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    14  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    15  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    16  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    17  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    18  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    19  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    20  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    21  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    22  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    23  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    24  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    25  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    26  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    27  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    28  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    29  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    30  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    31  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    32  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    33  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    34  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    35  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    36  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    37  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    38  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    39  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    40  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    41  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    42  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 23:  cr_area_task
    0   com.adobe.ag.AgImageIO      

  • Develop Module is not working after the latest 5.5 update.

    I have uninstalled and installed from the direct link.
    Cleaned up and optimized the catalog, etc.
    Images are visible in the library and develop module, but if I try to start editing - there are no changes visible, unless I go to Library and back to Develop.
    If I click "before/after" the blank screen appears.
    Help! This is a major work issue for me!

    Ok, I'm back!
    - apply develop settings (via preset), if so: is it a custom preset?
    I did apply a special preset (custom), just recently. Right now, uploading images without. Will see if that makes any difference. (Update) - NO difference. 
    - apply metadata
    Copyright and Creator, but has done so for a while
    - apply keywords
    Yes. Always
    - rename files
    No.
    Does Develop misbehave in the same way for all your images, or is it for a subset of the images? (Do you have any jpegs in your catalog? If so, does develop work for them?)
    Do have some JPG, but generally all raw and it misbehaves with them all.
    Have you tried making changes in Develop with the image zoomed in to 1:1? If so, is the behavior still the same?
    Yes. At different zoom levels. Same problem.
    Have you tried removing the *Previews.lrdata package that sits next to the catalog? Would need to do this while Lr is not running. (This will cause the need to regenerate previews, which can impact performance for a while.)
    Mmmmm... I removed a bunch of things last time, maybe it was part of it... Can't find it right now. Where would it be?
    Have you tried purging the Camera Raw cache, in the 'Camera Raw Cache Settings' of the 'File Handling' tab in the preferences?
    Yes. No change.

  • 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.

  • Develop module not displaying photos and tool updates.

    This problem just cropped up on a previously working install - Windows 7, LR 5.6
    The large display of the image in the develop module does not update for any of the actions selected in the develop module.  Pick a tool, make an adjustment - you cannot see the results of your adjustment on the large image.  The image in the filmstrip does display the results of the adjustment.  Selecting the crop tool causes the image to go grey.
    Using the simple tools in the library module - they all work and show the proper results.
    I have uninstalled LR and re-installed.
    I have purged previews.
    I have deleted "Lightroom 5 Preferences.agprefs".
    What next?
    David Hidding

    Further info - Full Screen mode in the Develop Module - it's just black, no image.  FS mode in the Library module works correctly.
    I have tried loading the latest video drivers for my video card, rebooted multiple times, etc.  Frustrated.
    I should also note that this problem started right in the middle of an editing session, everything was fine, and then suddenly, the image stopped updating.
    David Hidding

  • 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.

Maybe you are looking for