Role of Competencies in Performance & Development module... Impact?

Hi every one,
I have got a tricky question from my client.
My client doesnu2019t want to implement "Competencies", but asked us to provide OM, PA, Training & Event, Personnel Development and Talent Management systems.
I understand that without Competencies "we cannot score individual's qualifications, we cannot run profile matchup against ee's job or desired job, we cannot do query trainings based on qualifications gap, we cannot derive what are the qualifications required to perform a job".
But, I am bit confused with a question- What would be the other direct and indirect impact when the Competencies are not implemented in scope of the project (OM, PA, Training & Event, Personnel Development and Talent Management areas).
I will be very thankful if any one can share their knowledge / experiences here.
Many Thanks
Raj
Edited by: Raj Nammi on Apr 20, 2010 12:02 PM
Edited by: Raj Nammi on Apr 20, 2010 1:10 PM

Well, it sounds to me that these parameters are self explaining, but let me give a try anyway.
Changing: You can use this parameter to import some data into your functionmodule, change it and send it back to the caller. This way you don't need an import and export parameter.
Tables: In the early days, you could only transfer tabular data into a function module using the TABLES parameter. So instead of transferring (import and/or export) one record, you can now pass several records to the function module.
BTW: You could als use the F1 help for this, search on help.sap.com, or search SCN first, before even thinking about posting a standard question like this.

Similar Messages

  • Ever noticed that Auto Tone performs slightly different adjustments when applied during import as opposed to when applied in the Develop module? I've just run some experiments using LR 5.7.1 Camera Raw 8.7.1 using Canon CR2 images. 3 out of 4 test images

    Original Images after applying Auto tone in the develop module
    Image
    14BD3911.CR2
    14BD3912.CR2
    14BD3913.CR2
    14BD3914.CR2
    Exposure captured
    Under
    Over
    Slightly over
    Under
    WB Temp (as shot)
    2300
    2300
    6650
    6650
    WB Tint (as shot)
    +7
    +7
    +6
    +6
    Tone Exposure (auto)
    +2.9
    +0.5
    +0.5
    +1.9
    Contrast (auto)
    +4
    -3
    -17
    +6
    Highlights (auto)
    -48
    -45
    -11
    -10
    Shadows (auto)
    +48
    +45
    +11
    +10
    Whites (auto)
    0
    0
    +23
    +29
    Blacks (auto)
    -7
    -6
    -14
    -6
    Images imported with LR General Preset Auto Tone
    Image
    14BD3911-2.CR2
    14BD3912-2.CR2
    14BD3913-2.CR2
    14BD3914-2.CR2
    Exposure captured
    Under
    Over
    Slightly over
    Under
    WB Temp (as shot)
    2300
    2300
    6650
    6650
    WB Tint (as shot)
    +7
    +7
    +6
    +6
    Tone Exposure (auto)
    +2.9
    +0.5
    +0.5
    +1.9
    Contrast (auto)
    +4
    -2
    -17
    +6
    Highlights (auto)
    -48
    -45
    -12
    -10
    Shadows (auto)
    +48
    +45
    +12
    +10
    Whites (auto)
    0
    0
    +22
    +29
    Blacks (auto)
    -7
    -3
    -12
    -3

    I received two email replies (BriPhoto & Rob Cole) to my above post, which are now missing here. I only mentioned Auto WB because of this statement in your PDF posted here Shared Cat:
    "Apply auto WB and Auto tone to an unmodified photo and note the changes.
    Apply auto WB and tone to another photo with very different exposure and tone and note changes to confirm that changes are different and do depend on the content of the photo being operated on (assumption)."
    You are now saying:
    "However, in this case we are talking about the SAME raw file, imported from the camera's CF card twice. One is imported with no preset, then the Auto Tone preset applied, the other is imported with the Auto Tone preset set in the import module. Both files have the SAME WB setting (As Shot) and the same Temp and Tint, as you would expect. The only differences (in LR) are in the tonal values."
    I repeated Import of the two copies of your 14BD3913 CR2 file (14BD3913.CR2, 14BD3913-2.CR2) following the above procedure. The Tone values are identical for both using LR5.7 on my Windows 7 SP1 system. I cannot duplicate your issue as outlined above.
    Is this the Auto Tone preset you are using on Import?
    Two other things you can try:
    1) Reset your LR Preferences file:
    http://members.lightroomqueen.com/Knowledgebase/Article/View/1148/198/how-do-i-delete-the- lightroom-preferences-file
    2) If that doesn't correct the issue I would try uninstalling LR5.7.1, delete the LR Preferences file, and then reinstall LR5.7.1 using a fresh download.

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

  • 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      

  • Crash in develop module RAW files with sidecar files from Lightroom 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.

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

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

  • Lightroom 2.2 Develop Module Lockup Problems

    I have a Windows XP SP2 system with the following specs:
    AMD 64 X2 4400+ processor
    2GB of Ram
    Nvidia 6600GT Graphics (128mB ram)
    NView shut off
    3D settings: performance
    Norton Internet Security 2009 with Lightroom, cache and image file types excluded from scans
    The problem that I am experiencing is as follows:
    When I am editing an image in the develop module, the Lightroom application will randomly freeze. When the application freezes, the title bar of the Lightroom application window will revert to the blue bar that is the default for the active window within Windows and the cursor symbol will switch to the hourglass and the Lightroom will be completely unresponsive. Sometimes, the problem will clear itself in 30 60 seconds time and the program will become operational again. But, on other occasions it will remain completely locked up and will require a forced shutdown and restart of Lightroom using Control-Alt-Delete.
    This problem started with Lightroom 2.0 but occurred infrequently. With Lightroom 2.1 and 2.2, the lockups occur much more often. Also, I have had one instance where the computer completely locked and I had to do a forced shutdown of the entire computer with the power button. When I attempted to restart Lightroom, it complained about not being able to read the database and shut itself down. I started the application again and it came up but appeared to have reverted to an older database backup as I lost all of the edits that I had made during this working session.
    I havent been able to determine any specific task that triggers the lock up but I am using the develop module and am doing tasks like selecting another image on the filmstrip, making an adjustment or selecting another tab in the develop pane.
    I have updated my nVidia driver to the latest released version as I thought that this might help but I didnt see any changes following the update.
    This problem never occurred with Lightroom versions 1.x and my system is very stable otherwise. I treated the temporary lockups as an annoyance but having the database not be readable after the forced shut down of the computer is extremely concerning to me.
    I love the idea of Lightroom and plan to stay with it but I need help in resolving this issues. Thanks in advance for your suggestions.
    Dave Mayfield

    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

  • Develop module in Lightroom CC not working

    I've just installed Lightroom CC& used it to create a panorama and a HDR, both of which were successful. I then tried to edit them in the Develop module but was rewarded with a blue screen where the image should be; I then found that this happened to all the images I tried to edit.
    I then imported the panorama and HDR to Lightroom 5.7, and tried to edit them - successfully. So it works in Lightroom 5.7, but not in CC - does anybody know what's happening?

    Hi there,
    this solution worked for me with LTCC - win8/64bit
    once turned off the graphics card acceleration in Preferences->performance
    closd application
    opened back application > solved!
    thank you

  • In Adobe Lightroom, the Develop module is saying "Develop module disabled. Please renew your membership to reactivate the Develop module". I bought this product at full price several months ago.

    The Develop module is saying "Develop module disabled. Please renew your membership to reactivate the Develop module". I bought the product at full price several months ago and have had no problems using it until, so I am not sure what it is asking of me. I only had it on one other computer before I added it to this second computer, and I understand we get 3 copies. There should not be any issues. I need an answer ASAP.. actually pretty shocked that there is no immediate customer service that I can contact for a problem like this.

    If the develop module is disabled then you have downloaded and installed Lightroom from the creative cloud. It cannot be licensed with a serial number. It requires a creative cloud subscription, and is activated and kept active with your Adobe ID and password. That version will not work on your computer and will have to be uninstalled. Then you can 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
    This will have no impact on your catalog or your images. After you install from the right website you will be able to continue where you left off.

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

  • LR3 Fix for Crash when using Develop Module

    Adobe tech provided the following fix for my system which crashed when switching to the Develop module.
    This is the  response I received from Adobe Tech.  
    Recreating the preferences file corrected the problem.
    Their help was right-on and appreciated.
    Ed
    * to Customer**
    06/11/201018:11:12
    Hi Ed,
    Thank you for getting back to us. I appreciate your promptness in
    responding to our email.
    The information provided was really helpful in understanding the issue.
    In order to resolve this issue I would request you to perform the below
    mentioned steps in order to resolve this issue:
    * Remove Lightroom beta from your system as you have the the full
    purchase version Adobe Lightroom 3.0 (Because there may be conflicts
    between the Beta Version and original product)
    * Try to create new Catalog with some new images and check if you are
    facing the same issue with Develop module.
    * Check if other functions are working fine like Slideshow, Print, Web.
    If the problem still exist after removing the Lightroom beta version
    from your PC, then perform the below mentioned troubleshooting steps:
    * Re-create the Photoshop Lightroom preferences file.
    Re-create the Photoshop Lightroom 3.0 and 1.x preferences files to
    eliminate problems that a damaged preferences file might cause. If you
    do not delete your 1.x preferences as well as your 3.0 preferences,
    other issues may occur.
    To re-create the Photoshop Lightroom preferences file:
    1. Quit Photoshop Lightroom.
    1. Rename the Lightroom 3 Preferences.agprefs file (for example, to
    Lightroom 3 Preferencesagprefs.old) and the Lightroom Prefere
    nces.agprefs file (for example, to Lightroom Preferences.old) in the
    Documents and Settings/[Username ]/Application
    Data/Adobe/Lightroom/Preferences folder.
    1. Start Photoshop Lightroom. Photoshop Lightroom creates a new
    preferences file.
    If the problem continues, the preferences file isn't the cause. To
    restore custom settings, delete the new preferences file and restore the
    original name of the previous preferences file.
    * Also Send us the Image size and format on which your are working in
    Lightroom hence resulting in this issue.
    This should resolve your issue. If it does, please let us know, however
    in case it does not; please revert with any new information that you
    might want to add which will help us in resolving your issue.
    You can also try referring to our knowledge base and User to User forums
    by clicking on the following links:
    Knowledgebase: http://www.adobe.com/cfusion/search/index.cfm
    U2U Forums: www.forums.adobe.com

    Creating a new catalogue and importing the images does not resolve the problem.
    The problem is only occuring on a few images from a particular collection.
    Creating a virtual copy also will not edit in photoshop.
    Creating a virtual copy and reseting the develop settings will allow the ctrl-e command to work.
    However, manually re-applying the develop settings once again stops the ctrl-e command working.

  • LightRoom 2.3 Hangs Randomly in Develope Module

    I'm running Windows XP with patching up to date. At random intervals in the Develop module when I click on something, nothing happens. The next time I click on something I get an hour glass that never goes away. Hard disk activity starts and then subsides after a few minutes, but the window cannot be closed without rebooting. System will not shutdown as LightRoom is not killable at that point. I usually have to reboot the system at that point using the power button to turn it off and then let it start up again. The file system is left in a clean state as the first few dozen times I performed a chkdsk after it and didn't get any errors.
    Has occurred with JPG files from my 20D and 50D Canon cameras.

    Same issue
    Win8 x64, quad amd, hd5850, 2x 1T hdds + 60gig scratch + 160gig os,

  • Camera Calibration Profiles do not show in Develop Module LR5 / Windows 7

    I have selected three specific camera profiles (Nikon D300, Nikon D700 and Canon G12) and placed them into:
    c:\Users\{me}\AppData\Roaming\Adobe\CameraRaw\CameraProfiles\{Nikon D800}
    I restarted Lightroom 5 and viewed a RAW photo (not jpg or tif).
    But my Nikon D800 or the other two camera profiles do not show up in the Develop Module Camera Calibration drop down menu, nor in the Presets drop down in the Navigator panel.
    What am I doing wrong?

    DdeGannes wrote:
    It is possible to have third party software providers create profiles for your camera that simulate other camera profiles. I have had that done for my Olympus E520 and E300 cameras so that I have dozens of option available.
    Yes (to a degree). You can build your own custom DNG camera profiles, that's a good first start. Then you could edit them using the free DNG Profile Editor from Adobe. I'd start with custom profiles for each camera and see if that produces an acceptable match among them.
    This may help too:
    In this 30 minute video, we’ll look into the creation and use of DNG camera profiles in three raw converters. The video covers:
    What are DNG camera profiles, how do they differ from ICC camera profiles.
    Misconceptions about DNG camera profiles.
    Just when, and why do you need to build custom DNG camera profiles?
    How to build custom DNG camera profiles using the X-rite Passport software.
    The role of various illuminants on camera sensors and DNG camera profiles.
    Dual Illuminant DNG camera profiles.
    Examples of usage of DNG camera profiles in Lightroom, ACR, and Iridient Developer.
    Low Rez (YouTube):
    http://youtu.be/_fikTm8XIt4
    High Rez (download):
    http://www.digitaldog.net/files/DNG%20Camera%20profile%20video.mov

  • Lightroom 5.4 64-bit crashes when switching to develop module (and during random other functions)

    This seems to be a new issue that has developed over the past few days. I have been using Lightroom for multiple years without too many issues. Within the last 90 days I have upgraded to Lightroom 5. Today, upon loading up Lightroom (either 3.6 or 5.2) they both crash upon switching over to the develop module. I have upgraded 5.2 to 5.4, uninstalled 3.6, restarted my computer; still crashes with error message: "Adobe Photoshop Lightroom 64-bit has stopped working - A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." Which upon clicking "Close Program" it simply closes the program. Any ideas as to why this is happening and a possible fix? This is greatly impacting workflow. Following is a copy of my System info from Lightroom.
    Lightroom version: 5.4 [955652]
    Operating system: Windows 8.1 Home Premium Edition
    Version: 6.3 [9600]
    Application architecture: x64
    System architecture: x64
    Logical processor count: 8
    Processor speed: 2.3 GHz
    Built-in memory: 7944.2 MB
    Real memory available to Lightroom: 7944.2 MB
    Real memory used by Lightroom: 298.6 MB (3.7%)
    Virtual memory used by Lightroom: 268.0 MB
    Memory cache size: 103.5 MB
    Maximum thread count used by Camera Raw: 4
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    Displays: 1) 1920x1080
    Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 5.4
    Library Path: C:\Users\Joshuah\Pictures\Lightroom\Lightroom 5 Catalog.lrcat
    Settings Folder: C:\Users\Joshuah\AppData\Roaming\Adobe\Lightroom
    Installed Plugins:
    1) Behance
    2) Canon Tether Plugin
    3) Facebook
    4) Flickr
    5) Leica Tether Plugin
    6) Nikon Tether Plugin
    Config.lua flags: None
    Adapter #1: Vendor : 8086
        Device : 416
        Subsystem : fa721179
        Revision : 6
        Video Memory : 0
    Adapter #2: Vendor : 1414
        Device : 8c
        Subsystem : 0
        Revision : 0
        Video Memory : 0
    AudioDeviceIOBlockSize: 1024
    AudioDeviceName: Speakers (Conexant SmartAudio HD)
    AudioDeviceNumberOfChannels: 2
    AudioDeviceSampleRate: 44100
    Build: Uninitialized
    CardID: 1046
    Direct2DEnabled: false
    GPUDevice: D3D
    MaxTexture2DSize: 8192
    OGLEnabled: true
    Renderer: Intel(R) HD Graphics 4600
    ShaderModel: 11.1
    Vendor: Intel
    VendorID: 32902
    Version: 8086:0416:fa721179:0006

    I have had this same issue now. I have been away from my pc for a week or so and now i cannot use the Develop button
    Lightroom version: 5.4 [955652]
    Operating system: Windows 7 Business Edition
    Version: 6.1 [7601]
    Application architecture: x64
    System architecture: x64
    Logical processor count: 8
    Processor speed: 3.5 GHz
    Built-in memory: 32651.3 MB
    Real memory available to Lightroom: 32651.3 MB
    Real memory used by Lightroom: 366.3 MB (1.1%)
    Virtual memory used by Lightroom: 328.1 MB
    Memory cache size: 205.9 MB
    Maximum thread count used by Camera Raw: 4
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    Displays: 1) 1920x1080, 2) 1920x1080, 3) 1920x1080
    Seeming this seems to have stopped around the 21st of May and its now the 9th of June, does this mean we just do nothing about it and hope and pray that one day Adobe, who are very quick to take our money every month, can resolve this ? Has there been a fix noted for this yet ?

Maybe you are looking for