Develop module sliders in LR 4.4
Develop module sliders changed to grey from their previous colors and gradients. Any way to change back?
Yes, I just upgraded to OSX Mavericks this morning. It's not really a huge deal, but it does slow down my workflow a little.
Similar Messages
-
In the develop module, sliders jump about when clicked
In the develop module, sliders jump about when I try to click on them.
This happens after I re-size the window by dragging to the left in order to make the sliders longer. Any ideas on How to stop the sliders from misbehaving?I am seeing the same problem. Closing and re-opening LR reduces the problem, but there is still a slight (~0.05) change in the value when the slider is clicked on. More disturbing, resizing the right panel brings the problem back, with very large jumps. For example, my Exposure value changed +5 units when I clicked on the slider after widening the panel.
LR 5.7 from CC
27" (late 2012) iMac running Yosemite
Problem happens with either Apple Magic Mouse or Wacom Intuos tablet (with the latest driver, 6.3.10w2)
Edit: Deleting the Preferences file did not solve the problem. -
Develop module sliders for overall exposure, contrast, saturation etc. are gone.
The Develop module used to have sliders for overall exposure, contrast, saturation as well as highlights, whites, blacks, shadows, vibrance, clarity etc. Now these functions are only to be found in Library Quick Develop as left/right buttons. I miss the sliders in Develop. There are similar sliders there, but only relating to specific colors, not the overall image. How do I get the sliders back?
Right-click (Ctrl-click on Mac) on any panel group tab e.g Detail, Lens Correction etc and make sure all are checked (see image below).
-
LR5: Moving develop module sliders blurs the image for a moment
I'm evaluating Lightroom 5 during the 30 day trial and it's all cool except for this one big annoyance that I noticed immediately when trying to work on an image in Develop module. As stated in the title, moving any slider (exposure, highlights, noise reduction, etc.) causes the image to go very blurry for the duration of the slider movement. It goes immediately back to being sharp as soon as I stop moving the slider. This is super annoying, feels as though my eyes are going bad.
What's interesting is that the problem doesn't show up when I'm adjusting the Tone Curve directly, but it will get triggered if I'll expand and use the sliders underneath. So looks like a bug that only applies to sliders.
This doesn't happen at all in Lightroom 4.4, which I still have installed and can compare side-by-side.
As for the hardware, I'm using the 2013 Macbook Air with 1.3 GHz i5 CPU and 8 GB of RAM. The OS X version is 10.8.4 with all latest upgrades installed.
I've already tried optimizing the catalog, giving it more space (currently at 3 GB) and purging it. I'm not using Smart Previews, although I've turned them on for a moment to see if the problem persists with them on - it does. I've also re-rendered the 1:1 preview for the specific image I've been trying it on. Btw, the file is a NEF from Nikon D300 and I'm using the 2012 process (as was the case with LR4). Not sure what else might be relevant here.If this is indeed intentional, is there any way to turn it off? I would much rather it had taken a bit longer to update the photo, than to have the image switch to this "pixel doubled" version.
Also, this doesn't happen at all in LR 4.4 on the same machine. However, if it indeed isn't a bug, this probably means LR5 requires more resources to process a photo than 4.4. This would be somewhat disappointing, given that LR5 was supposed to be faster than its predecessor. -
Screen Flicker When Using Slide Bars in Develop Module
Image below shows 6 core usage during edit of an image using LR 4.2RC. Image import was running in the background. This only occurs when I use the develop module sliders (it doesn't matter which slider).
At this point, I think I will have to go back to LR 3.x. Lightroom 4 is so unstable that I cannot get it to work. I constantly get not responding messages and screen flickering in the develop module.
I have done everything I can find and nothing seems to work. It is either an incompatibility with the AMD video drivers (best guess) or there is something seriously wrong with the code (second guess), however LR 3.2 does not have this issue.
Lightroom version: 4.2 RC [844780]
Operating system: Windows 7 Home Premium Edition
Version: 6.1 [7601]
Application architecture: x64
System architecture: x64
Physical processor count: 6
Processor speed: 2.8 GHz
Built-in memory: 16381.5 MB
Real memory available to Lightroom: 16381.5 MB
Real memory used by Lightroom: 603.5 MB (3.6%)
Virtual memory used by Lightroom: 621.6 MB
Memory cache size: 191.8 MB
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080, 2) 1280x1024 -
Why can't I see the changes in my image when I move the sliders in LR's Develop Module
When I use the quick develop tools in the LR 5.3 Library module, I see the changes in the selected image. When I switch to the Develop Module, when I move the sliders for the different tools, nothing happens to my image. When I go back to the Library module, I see the changes, but not in the Develop Module. Why is this happening? I have a PC running Windows 7. I have 30 gigs of space on my C drive. I recently updated my LR to 5.3 and subscribed to CC. I uninstalled the LR program and reinstalled it from the cloud. Same problem.
Hello lakota85usa, the [http://kb.mozillazine.org/Profile_folder_-_Firefox#Mac profile folder is hidden Mac OS X 10.7 and above], not in your version(10.6.8), see if the "Showing hidden files and folders on Mac OS X" in the next link is helpful: http://kb.mozillazine.org/Show_hidden_files_and_folders#Mac_OS_X
thank you -
Help with the sliders in develop module
In the develop module I no longer see the sliders for exposure, contrast, etc. can someone help me?
Those sliders are located in the Basic panel. And for some reason what is happening to you has been happening to several others. While in the Develop module, right-click on one of the other section headings (tone curve, detail, etc.) and make sure there is a checkmark in all the sections that you want to display. My suspicion is that the Basic panel checkmark is missing.
-
Have downloaded Lightroom 5 to iMac (Mavericks OS10.9.3). No Basic sliders in Develope module?
Why do I not find Basic slider section in the Develope Module of a trial version of Lightroom 5?
Michel,
Right-click (or ctrl-click on Mac) on any header on the right side of the develop module and choose Basic from the context menu. (Or 'Show All').
Hal -
Link histogram to exposer sliders in develop module
I am in the develop module of light room 5, all of a sudden the actions stopped working. To adjust exposer I have to slide the histogram, not the slider. I am not sure how I did this?
The option for Blacks and whites is also missing now?
-
Develop Module Advancements in Lightroom 4 | What's New in Lightroom 4 | Adobe TV
Learn how to create the highest quality photographs by taking advantage of new and improved global and local adjustments in the Lightroom 4 Develop module.
http://adobe.ly/x7mwOKload an image and open the tone curve panel (you already did this probably). at the lower right of the canvas you'll see a button with "!" on it. click the button to convert to "2012 process". wait. when it is done if you *still* don't see the channel dropdown click the "edit tone curve" button to hide the sliders and *then* you should see the channel dropdown.
I found this totally mystifying, but once I found it (luck) I get it...new features, new entries in the database or some other magic. anyway the video sure didn't give me a hint.
this will be my 5th try posting an answer to your question, hopefully this time it will work, no thanks to support, 5 times resetting the password, etc etc. -
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. -
How do I show the Develop Module settings when I open up an image I've exported from LR 4.4?
Say I have a preset that I use upon import. I import some raw files using that preset but decide to tweak the settings a bit per each image. IOW, now they are different than my preset.
I now export from a tweaked raw file a jpeg. If I later import that jpeg back into LR 4.4 but don't apply any presets upon import (just leave it blank, I don't even check None), when the image is in the Library the "Saved Preset" line over on the upper right says "Custom" so I figure my settings were "embedded" into that jpeg when I exported it.
However, when I then go into the Develop module, all the Develop settings are zeroed out. Is there any way to have the setting sliders represent what I actually did to the raw before I exported as a jpeg? I can't just hit the preset I used upon import because, in fact, the current settings have been tweaked.
Along that same line, is there a choice I can select upon import (of an exported jpeg or tiff or whatever) that says "show current Develop settings" or some such instruction that would take care of this during import. Thanks.No it’s not possible but you have a record in the history panel for your master (raw file) It will show the date you exported the jpeg etc. If you click on that line it will show all the develop settings to the right e.g. the slider values etc.
You can in fact save them as a snapshot; so if you make further tweaks to your raw file, the settings you used for your jpeg will always be saved.
Most users don’t re-import jpegs because they can export a fresh one at any time. It’s also possible to create a virtual copy from the menu (Photo >> Create Virtual Copy) which can have different settings to your master (original raw file). You can create as many VC’s as you like and they take up no extra space on your hard drive. Because they are virtual they are simply stored in the catalog as metadata. -
Problems with LR4 - Develop Module - Edit in CS5
I've just upgraded from LR3 to 4
When I make adjutments on a RAW or JPEG file in the develop module, and then send it to PS5 for more work, not all the adjustments show up in CS5.
Example, I cropped an image, and then made local exposure adjustments using the 'brush' tool.
Exported to CS5 using 'Photo' 'Edit in', and the image goes to CS but only the crop adjustment is showing.
I've done all the updates on CS, but this is a pain.
I'm running a MAC with Snow Leopard OS
Can I uninstall the upgrade and reinstall..? Would that be any use...??I was greatly confused by all this for a while, but think I finally figured it out, thanks to CSS Simon and others here (I'm new to Lightroom, having only used Ps/ACR previously).
What happens is that "render using Lightroom" doesn't involve ACR at all. It goes straight to Photoshop (and puts the rendered file alongside the raw). The other option, "open anyway", renders the file through ACR. But ACR 6.6 and before can't read PV2012, that's why you need to install the ACR 6.7 Release Candidate, which can (although it doesn't give you access to the 2012-specific sliders).
Another thing that tripped me up at first was that no Lightroom edits at all would show up in Bridge or ACR, even with ACR 6.7 installed. I finally discovered that I had to set Lightroom catalog settings to "automatically write metadata changes to xmp" - otherwise all Lightroom edits would just exist in the Lightroom catalog and not be visible to other applications.
This is of no importance if you only use Lightroom, but it certainly is if you have a mixed workflow with Photoshop and Bridge. -
Rendering issue in Develop Module
Slow rendering has been discussed in many threads, but can anyone explain what is going on with this specific issue I am having?
If I am working in the Develop Module and I render two raw files at 1:1, after the initial rendering delay I can generally toggle between the two and they are rendered almost instantaneously. I assume this is because some info has been stored in the ACR Cache and Lightroom can quickly display them. Now if I render a 3rd raw file at 1:1 and try to toggle between 3 images, one of them always needs 10 seconds or so to load/render. What is happening here? I thought the purpose of the ACR Cache was to allow for fast rendering of previously rendered images. I currently have my ACR Cache set to 10GB and I have recently purged it, so I am nowhere near the limit. Other system/software specs as follows:
LR 5.2
NEF files from Nikon D7100 (approx 30MB)
iMac 27-inch 2560x1440
OS 10.8.5
Processor: 3.06 GHz Intel Core 2 Duo
RAM: 16GB
Video Card: ATI Radeon HD 4670 (256MB)
Storage: 1TB SATA 7200rpm, 25% fullLanceBenedict wrote:
Thanks for the explanation on the RAM caching. If I am understanding you correctly on the ACR Cache, it sounds like it is essentially useless once you have applied some editing to the image because you need to wait on those edits to be rendered.
No, I wouldn't agree that it's useless. When you load an image into Develop you'll be presented first with a brief view of your Library preview, which should quickly be replaced with the ACR Cache "scene-referred" preview that will have any existsing edits applied before you see it. That should all happen quite quickly, and when that preview is loaded the sliders will be activated. When that happens you can start work, even though the full file is being rendered in background, and there is no need to wait until the "Loading" indicator goes out (as I said earlier, you can turn that off if you prefer).
So the benefit of the ACR Cache entry is that it allows you to start work in Develop whilst the original file is still being fully converted.
Note that although we are talking specifically about the ACR Cache entry, the same holds true for DNG Fast Load Data and/or Smart Previews. Which one of those 3 is initially used depends on what exists at the time of loading, and what file type is being used. But the same principle applies to all three.
In terms of reducing the rendering time, that's a more problematical issue as there are various factors in the pipeline which come into play, any one (or more) of which may be sub-optimal. These factors include:
1. Size of the files being loaded. It should go without saying that 36mp files from a Nikon 800 are going to take quite a bit longer that the 10mp files from say a Canon 40D.
2. Location of the files and speed of the interface, i.e. expect image files on a USB2 connected hard drive spinning at 5400rpm to be a lot slower to load than if they were on a 7200rpm drive internally connected on a 6gb/s Sata hub.
3. Once the data has been read, how fast is the CPU.....rendering a raw file will be quite a CPU-intensive task, so the faster the processor the better.
4. User expectation.....one man's "painfully slow" could be another's "quite acceptable".
With that in mind, I have no idea if what you are experiencing is "typical" or too slow. Putting it into context, all my original files are on a fast internal drive on a 3gb/s connection, I have an i7-930 quad-core processor (now over 3 years old, so not leading edge by any means), 12gb of RAM. Full loading times in Develop are now about 3 seconds per image when using 22mp files from a Canon 5D3.
Looking at the things you've tried, purging the ACR Cache and increasing its size would have no effect unless:
a) There was a problem with the existing cache, and
b) You regenerated new cache entries
Discarding old previews and rebuilding would have had no effect on Develop loading times, nor would downsizing the dimensions of the develop window.
Increasing system RAM should certainly be beneficial to other areas of Lightroom, I'm just not sure it would have a specific benefit to image loading into Develop. That might be dependant upon what else was running in the system at the time.
Maybe you are looking for
-
Why does Flashplayer for Firefox create 1000's of FAP####.tmp files and never cleans then up?
Version Info FlashPlayer Plugin version: 11.9.900.117 (and many version before) Firefox version : 24.0 (and many versions before) Windows Version : Windows 7-SP1 Directory of Files : C:\Windows\Temp Deta
-
Hard Drive not detected through SATA, but it is through USB.
This week my hard drive seemed to crash, I got the file with the question mark and it wouldn't show up in disk utility. I went out and bought a new hard drive, popped it in and it too doesn't show up. I put my old hard drive in an enclosure and plugg
-
Just wondering ... wich mac is better??
Which mac is better?? The Mac Book Pro or Mac Book Air. I already have the Pro, but I want to buy a new one. Which one should I buy?
-
ObservableSet/Map as items for List/TableView
In quite a few cases I have a model in which underlying data has no inherent sorting - it comes as an unordered set of items. They might be added/removed/updated at random time. I would like to use Set<MyItem> or Map<Key,MyItem> and let the sorting '
-
"Organize by Conversation" Bug -- newest message isn't always attop of thread
Has anyone else experienced this? Any workaround? Also, because of this, when I hit reply, it will often pick the wrong message to reply to. Help anyone?