Sidecar files
Opened LR this evening and an error message appeared - sorry, didn't make a note of it.
Anyway, went to one of my folders and approx 14 images (dng files) reverted back to their original state and orientation. Each photo then had, in the top right corner in grid view, the ? telling me that the sidecar file was missing.
What's going on here and how do I get this sidecar file back or, more importantly, stop other sidecars going missing?
Try what John says. It may well be that somehow you moved them, etc, or LR simply lost rack of them.
However, LR will also put up ?s when in fact the images are not lost. Usually just clicking on the ? will make it disappear in this case. You can open images that are reported lost when they are not and work on them. If they are truly lost, you can't.
I have 20,000 images in LR for testing purposes and at any given time LR will report up to 289 images with ?s, but in fact only 4 or 5 are truly lost. Next time I open LR it may say 179 or some other number are lost. Go figure. Others have had the same glitch. It is annoying to say the least, and sooner or later it will be fixed.
Similar Messages
-
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 force lightroom to (re)load an XMP sidecar file?
Good morning from Boston!
I am new to Lightroom and just finished importing my Aperture library into Lightroom 5 on a Mac. For that, I followed the instructions on Adobe's landing page and Lightroom solutions. For those not familiar with the instructions, you essentially export all your originals with an XMP sidecar file and then export all the adjusted/edited files as 16-bit TIFFs. Then you add them all back into Lightroom and get everything back into Catalogs, Labels, Ratings, and such by using keywords that were added while in Aperture. It took forever, but worked pretty well overall. I had about <1% fewer images in LR5 than in Aperture, which were likely suspected duplicates. So far, so good.
Here's is my problem. My keywords didn't always transfer over (the Keywording panel is empty). I did search forums and plug-ins, but seem to only find issues related to EXIF and GPS data. I also used "Metadata:Read Metadata from File" and "Metadata:Update DNG Preview & Metadata," which didn't do anything. I am suspecting that "Read from File" means "read from the image file itself but not from the sidecar file." Take file IMG_5888 as an example. This particular one was taken as RAW (.CR2) + JPEG on a Canon Rebel XS, but I am having the same issue with RAW only on my Canon EOS 6D. Same goes for JPG + XMP. Puzzling thing is that other files loaded just fine.
In the directory/folder where the file is, it looks like this:
IMG_5887.CR2
IMG_5887.JPG
IMG_5887.XMP
IMG_5887.dng
IMG_5888-2.JPG
IMG_5888.CR2
IMG_5888.JPG
IMG_5888.XMP
IMG_5888.dng
IMG_5889-2.JPG
IMG_5889.CR2
IMG_5889.JPG
IMG_5889.XMP
IMG_5889.dng
The .dng were generated by Llightroom. Now, the sidecar files typically have something like so in them (I cut out some keywords for clarity—you get the idea):
<rdf:Description rdf:about='' xmlns:photoshop='http://ns.adobe.com/photoshop/1.0/'>
</rdf:Description>
<rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1/'>
<dc:subject><rdf:Bag>
<rdf:li>Black Head Trail</rdf:li>
<rdf:li>Cliffs</rdf:li>
<rdf:li>Maine</rdf:li>
<rdf:li>Monhegan</rdf:li>
<rdf:li>RAW</rdf:li>
<rdf:li>Sunrises</rdf:li>
<rdf:li>United States</rdf:li>
<rdf:li>Waves</rdf:li>
</rdf:Bag></dc:subject>
</rdf:Description>
So, the keywords were exported from Aperture, but for some reason, Lightroom isn't always loading them from the XMP file.
On a related note, the keyword hierarchy that was exported as text file from Aperture and imported into LR5 worked well. Everything appears to be there and in its place.
Any ideas for a Lightroom rookie as to how I can get LR5 to read those XMPs? Over 20,000 didn't tag, so I would rather not do this by hand!
Many thanks in advance,
PaulJohn, what a pleasure. Well, here is the update. First, copying over 300GB of pictures to a drive and then backing up said drive takes a bloody long time. But here is what happened, for others who might run into the same issue.
I first tried a small set of files to narrow down whether the issue was the Aperture export or the Lightroom import.
Conclusion: the "issue" is mostly on the Lightroom side.
What I found: Although Aperture will export an XMP sidecar for a JPEG, Lightroom will not read it, ignoring all keywords. I exported a set of JPEGs only and then opened the XMPs with an editor (well, the UNIX cat command, to be exact). The information was there, keywords and all. However, LR appeared to ignore XMP for JPEG. That said, if you have a RAW+JPEG in Aperture, the RAW XMP sidecar will overwrite the JPEG one, effectively leaving you with only the keywords for the RAW version. That shouldn't be an issue for most, but just in case you have different keywords for your RAW and JPEG images, be aware of this.
What I did:
Back up all the images and catalogs/libraries from Aperture and LR.
Make sure #1 worked out.
Make sure #1 worked out (not a typo; you really need a backup, as you will find out below).
Delete the old JPEG files that were uploaded into LR. I had them in a From Aperture folder, as instructed by John's article and Adobe's landing page (referenced in John's article), so I deleted all JPEGs in that folder. My Aperture database was not affected and in fact resides on a different drive.
Run find . -iname "*.JPEG" -delete [if you do not know how 'find' works, ask someone, as this can potentially delete every single file accessible to your computer!]
Run find . -iname "*.JPG" -delete [ditto! Don't tell me I didn't warn you!]This is why you need to backup everything. I was deleting copies/exports of the originals in Aperture (again, read John's article for the difference) and still had the originals in Aperture, on a different drive.
[I didn't worry about the unmatched/orphaned XMP files for the JPEGs only; they are tiny and don't hurt.]
In LR, select 'Library:Find All Missing Photos.' If asked, remove them from the Catalog only.
Create a Smart Album in Aperture and include only 'Filetype is JPG.'
Select all images in that album.
Export those original images per Adobe's landing instructions, but for this set of images, select 'Include IPTC' instead of creating a sidecar file.
When Aperture is done, open LR and Add the whole 'From Aperture' folder back to LR (make sure 'Ignore suspected duplicates' is selected.
John, as you rightfully pointed out, this is tricky. If my experience is any indicator, I would suggest migrating in 3 steps:
Export all RAW originals with IPTC in XMP sidecar files.
Export all non-RAW originals (which I would guess are mostly JPEGs) with IPTC included. (not a sidecar)
Export all versions as 16-bit TIFF.
If #2 is added, then the process is actually most straightforward. Steps 1–5 in the first block above were to clean up the mess that I had created and should not happen otherwise (famous last word...)
If the above is unclear, please let me know and I will expand on it. If I had the issue, I suspect others will as well.
Thank you for your help and suggestions. I am officially migrated to LR and up and running!
Cheers from Boston,
Paul -
Looking for answers on XMP files - where should they be stored as sidecar files? With the original raw file or in a separate folder?
Relatively new user of Adobe LR5 and PS CC, about a year old.
If they should be stored somewhere beside the folder that contains the originals, where and how to change the settings?
If I choose to write metadata to the original files, is that sidecar files or does the XMP file show separately?
To be honest, I usually find a video and I cannot figure this out. I have never received an answer on any of my questions by the way.Hi there,
You answered a prior question from me so I wanted to reach out to you about this. I just need a step by step on how, if possible, to View LRCC on my MacBookPro when the main interface is on my iMac -
Write xmp sidecar files without need to export masters - script
I've written a script to write xmp sidecar files for referenced and online images (the 2 conditions in the script) of the selected images. I looked for a while at system events and other stuff to be able to write the xmp file, but i'm not a programmer, so in the end i chose the long and dirty way to do it.
This script will export all iptc expanded fields as aperture does (creating basically the same file). It can be easily adjusted to include other tags, even custom ones. I don't know how to get at the adjustments for images, otherwise those could be included as well.
If anyone has the energy to clean this up and make it faster, feel free to do so. Next, I'm going to try to write a script to do the opposite, import xmp sidecars for imported online and referenced files.
Here it goes (thanks to Brett Gross for the database part to find the master filename):
--script to create sidecar xmp files for referenced files without having to export masters. parts of the script (finding the file name) are by brett gross
property p_sql : "/usr/bin/sqlite3 "
global g_libPath
on run
my getLibPath()
--counter for processed images, reset, just in case
set mastercount to 0
tell application "Aperture"
if not (exists selection) then
display dialog "You have to select at least one image" buttons {"OK"} default button 1
return
else
display dialog "You have selected " & (count of selection) & " images." & return & "Continue?" default button 1
end if
set theSel to selection
--run through the selected images
repeat with currentpic from 1 to count of theSel
tell item currentpic of theSel
-- only apply to referenced and online images
if referenced and online then
set mastercount to mastercount + 1
set curID to id
--find the master file path and name - this part by brett gross, thanks
set libPOSIX to POSIX path of g_libPath
set libDBPOSIX to (libPOSIX & "/Aperture.aplib/Library.apdb") as string
set theScript to p_sql & (quoted form of libDBPOSIX) & " \"select ZFILEUUID from ZRKVERSION where ZUUID='" & curID & "'\""
set ZFILEUUID to do shell script theScript
# ---------- Get the master's path
set theScript to p_sql & (quoted form of libDBPOSIX) & " \"select ZIMAGEPATH from ZRKFILE where ZUUID='" & ZFILEUUID & "'\""
set ZIMAGEPATH to do shell script theScript
# ---------- Get the master's disk name
set theScript to p_sql & (quoted form of libDBPOSIX) & " \"select ZFILEVOLUMEUUID from ZRKFILE where ZUUID='" & ZFILEUUID & "'\""
set ZFILEVOLUMEUUID to do shell script theScript
set theScript to p_sql & (quoted form of libDBPOSIX) & " \"select ZNAME from ZRKVOLUME where ZUUID='" & ZFILEVOLUMEUUID & "'\""
set diskName to do shell script theScript
set imgPath to (diskName & "/" & ZIMAGEPATH)
--end brett gross part
--strips extension, seems to work for files and paths with more than one period
set oldlim to AppleScript's text item delimiters
set AppleScript's text item delimiters to "."
try --remove last extension only
set contador to text item -1 of imgPath
set noExtension to Unicode text 1 thru -((count of contador) + 2) of imgPath
on error --handle files with no extensions
set noExtension to imgPath
end try
set AppleScript's text item delimiters to oldlim
--create the file and path name with the .xmp extension for writing
set xmpPath to "/Volumes/" & noExtension & ".xmp" as Unicode text
--convert posix path to alias for easier write and read handling
set xmpPath to POSIX file xmpPath as file specification
-- header for xmp file
set xmpheader to ("<?xpacket begin='' id=''?>
<x:xmpmeta xmlns:x='adobe:ns:meta/' x:xmptk='XMP toolkit 2.9-9, framework 1.6'>
<rdf:RDF xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#' xmlns:iX='http://ns.adobe.com/iX/1.0/'>") & return
-- footer for xmp file
set xmpfooter to ("</rdf:RDF>
</x:xmpmeta>
<?xpacket end='w'?>") & return
--xmp content, part 1
--check for existence of iptc tags, create content or empty string depending on existance of tags
if (exists IPTC tag "Contact") or (exists IPTC tag "Country/PrimaryLocationCode") then
set xmpcontentpartone to ("<rdf:Description rdf:about='' xmlns:Iptc4xmpCore='http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/'>") & return
try
set CountryCode to value of IPTC tag "Country/PrimaryLocationCode"
set xmpcontentpartone to xmpcontentpartone & tab & "<Iptc4xmpCore:CountryCode>" & CountryCode & "</Iptc4xmpCore:CountryCode>" & return
end try
try
set CreatorContactInfo to value of IPTC tag "Contact"
set xmpcontentpartone to xmpcontentpartone & tab & "<Iptc4xmpCore:CreatorContactInfo>" & CreatorContactInfo & "</Iptc4xmpCore:CreatorContactInfo>" & return
end try
set xmpcontentpartone to xmpcontentpartone & ("</rdf:Description>") & return
else
set xmpcontentpartone to ""
end if
--xmp content, part 2
--check for existence of iptc tags, create content or empty string depending on existance of tags
if (exists IPTC tag "Category") or (exists IPTC tag "City") or (exists IPTC tag "Country/PrimaryLocationName") or (exists IPTC tag "Credit") or (exists IPTC tag "DateCreated") or (exists IPTC tag "Headline") or (exists IPTC tag "Province/State") or (exists IPTC tag "Source") or (exists IPTC tag "SpecialInstructions") or (exists IPTC tag "SupplementalCategory") or (exists IPTC tag "Writer/Editor") then
set xmpcontentparttwo to ("<rdf:Description rdf:about='' xmlns:photoshop='http://ns.adobe.com/photoshop/1.0/'>") & return
try
set Category to value of IPTC tag "Category"
set xmpcontentparttwo to xmpcontentparttwo & tab & "<photoshop:Category>" & Category & "</photoshop:Category>" & return
end try
try
set City to value of IPTC tag "City"
set xmpcontentparttwo to xmpcontentparttwo & tab & "<photoshop:City>" & City & "</photoshop:City>" & return
end try
try
set Country to value of IPTC tag "Country/PrimaryLocationName"
set xmpcontentparttwo to xmpcontentparttwo & tab & "<photoshop:Country>" & Country & "</photoshop:Country>" & return
end try
try
set Credit to value of IPTC tag "Credit"
set xmpcontentparttwo to xmpcontentparttwo & tab & "<photoshop:Credit>" & Credit & "</photoshop:Credit>" & return
end try
try
set DateCreated to value of IPTC tag "DateCreated"
set xmpcontentparttwo to xmpcontentparttwo & tab & "<photoshop:DateCreated>" & DateCreated & "</photoshop:DateCreated>" & return
end try
try
set Headline to value of IPTC tag "Headline"
set xmpcontentparttwo to xmpcontentparttwo & tab & "<photoshop:Headline>" & Headline & "</photoshop:Headline>" & return
end try
try
set State to value of IPTC tag "Province/State"
set xmpcontentparttwo to xmpcontentparttwo & tab & "<photoshop:State>" & State & "</photoshop:State>" & return
end try
try
set Source to value of IPTC tag "Source"
set xmpcontentparttwo to xmpcontentparttwo & tab & "<photoshop:Source>" & Source & "</photoshop:Source>" & return
end try
try
set Instructions to value of IPTC tag "SpecialInstructions"
set xmpcontentparttwo to xmpcontentparttwo & tab & "<photoshop:Instructions>" & Instructions & "</photoshop:Instructions>" & return
end try
try
set SupplementalCategory to value of IPTC tag "SupplementalCategory"
set xmpcontentparttwo to xmpcontentparttwo & tab & "<photoshop:SupplementalCategory>" & SupplementalCategory & "</photoshop:SupplementalCategory>" & return
end try
try
set CaptionWriter to value of IPTC tag "Writer/Editor"
set xmpcontentparttwo to xmpcontentparttwo & tab & "<photoshop:CaptionWriter>" & CaptionWriter & "</photoshop:CaptionWriter>" & return
end try
set xmpcontentparttwo to xmpcontentparttwo & ("</rdf:Description>") & return
else
set xmpcontentparttwo to ""
end if
--xmp content, part 3
--check for existence of iptc tags, create content or empty string depending on existance of tags
if (exists IPTC tag "Byline") or (exists IPTC tag "Caption/Abstract") or (exists IPTC tag "CopyrightNotice") or (exists IPTC tag "Keywords") or (exists IPTC tag "ObjectName") then
set xmpcontentpartthree to ("<rdf:Description rdf:about='' xmlns:dc='http://purl.org/dc/elements/1.1/'>") & return
try
set creator to value of IPTC tag "Byline"
set xmpcontentpartthree to xmpcontentpartthree & tab & "<dc:creator><rdf:Seq><rdf:li>" & creator & "</rdf:li></rdf:Seq></dc:creator>" & return
end try
try
set description to value of IPTC tag "Caption/Abstract"
set xmpcontentpartthree to xmpcontentpartthree & tab & "<dc:description><rdf:Alt><rdf:li xml:lang='x-default'>" & description & "</rdf:li></rdf:Alt></dc:description>" & return
end try
try
set rights to value of IPTC tag "CopyrightNotice"
set xmpcontentpartthree to xmpcontentpartthree & tab & "<dc:rights><rdf:Alt><rdf:li xml:lang='x-default'>" & rights & "</rdf:li></rdf:Alt></dc:rights>" & return
end try
--keywords, slightly different, as they need to be written as a list and not as a string
--i don't think it's a problem if we create an empty list if there are no keywords present.
set xmpcontentpartthree to xmpcontentpartthree & tab & "<dc:subject><rdf:Bag>" & return
--make list item for every keyword
try
repeat with n from 1 to count of keywords
set cursubject to name of (keyword n)
set xmpcontentpartthree to xmpcontentpartthree & tab & tab & "<rdf:li>" & cursubject & "</rdf:li>" & return
end repeat
end try
set xmpcontentpartthree to xmpcontentpartthree & tab & "</rdf:Bag></dc:subject>" & return
try
set title to value of IPTC tag "ObjectName"
set xmpcontentpartthree to xmpcontentpartthree & tab & "<dc:title><rdf:Alt><rdf:li xml:lang='x-default'>" & title & "</rdf:li></rdf:Alt></dc:title>" & return
end try
set xmpcontentpartthree to xmpcontentpartthree & ("</rdf:Description>") & return
else
set xmpcontentpartthree to ""
end if
--part four. aperture doesn't seem to export anything there
set xmpcontentpartfour to "<rdf:Description rdf:about='' xmlns:photomechanic='http://ns.camerabits.com/photomechanic/1.0/'>
</rdf:Description>" & return
--part five. rating
set xmpcontentpartfive to "<rdf:Description rdf:about='' xmlns:xap='http://ns.adobe.com/xap/1.0/'>" & return
try
set Rating to main rating
set xmpcontentpartfive to xmpcontentpartfive & tab & "<xap:Rating>" & Rating & "</xap:Rating>" & return
end try
set xmpcontentpartfive to xmpcontentpartfive & "</rdf:Description>" & return
--join everything
set xmptext to xmpheader & xmpcontentpartone & xmpcontentparttwo & xmpcontentpartthree & xmpcontentpartfour & xmpcontentpartfive & xmpfooter
--write file
my writexmpFile(xmptext, xmpPath)
end if
end tell
end repeat
display dialog "Processed " & mastercount & " referenced and online image(s)." buttons {"OK"} default button 1
end tell
end run
-- write xmp sidecar file routine
on writexmpFile(theContents, xmpFileName)
--tell application "Finder"
try
open for access xmpFileName with write permission
set eof of xmpFileName to 0
write (theContents) to xmpFileName starting at eof
close access xmpFileName
on error
try
display dialog xmpFileName
close access xmpFileName
end try
end try
--end tell
end writexmpFile
--this part copied from Brett Gross-------------------------------------------------------------------------- --------------------------------
on getLibPath()
tell application "System Events" to set p_libPath to value of property list item "LibraryPath" of property list file ((path to preferences as Unicode text) & "com.apple.aperture.plist")
if ((offset of "~" in p_libPath) is not 0) then
-- set p_posix to POSIX file p_libPath
set p_script to "/bin/echo $HOME"
set p_homePath to (do shell script p_script)
set p_offset to offset of "~" in p_libPath
set p_path to text (p_offset + 1) thru -1 of p_libPath
set g_libPath to p_homePath & p_path
else
set g_libPath to p_libPath
end if
end getLibPath
--end brett gross partimigra wrote:
I've written a script to write xmp sidecar files for referenced and online images (the 2 conditions in the script) of the selected images. I looked for a while at system events and other stuff to be able to write the xmp file, but i'm not a programmer, so in the end i chose the long and dirty way to do it.
This script will export all iptc expanded fields as aperture does (creating basically the same file). It can be easily adjusted to include other tags, even custom ones.
Excellent stuff!
I don't know how to get at the adjustments for images, otherwise those could be included as well.
They are stored as binary data in the Version XML files at the bottom level of the Library package. You can also have a look around in the ZRKIMAGEADJUSTMENT table, but again the actual settings for each adjustment are in binary form.
If anyone has the energy to clean this up and make it faster, feel free to do so.
As far as I can remember, Aperture uses the 'proper' IPTC tag names when accessing them via AppleScript, so you may be able to do a loop through all the IPTC tags for each image, rather than picking out each specific one. But that would need checking. The EXIFTools site is a good place to find out about the different ways that IPTC data can be described.
Next, I'm going to try to write a script to do the opposite, import xmp sidecars for imported online and referenced files.
Don't rush unless you feel like it - I've already started planning out a free (as in beer and speech) XMP importer with a GUI so that you can choose how to map the XMP CORE tags that don't exist in Aperture. You've given me an extra idea, though - if we can decide on a set of custom tags, my importer could map the XMP CORE tags to them and your exporter could export those tags.
Thanks for the work!
Ian
P.S. I'll check through your script tomorrow, some of the database tables changed between 1.5.6 and 2.0, so you might need to add in a version check to be really thorough. -
Pages '09 Does Not Have "Sidecar" File?
I read somewhere that a difference between Pages '08 and '09 is that '09 no longer stores formatting data, etc. in a .xml "sidecar" file. Is this correct?
A couple of times I have had Pages '08 files that would not open because the file was no longer "viable" (or similar terminology...) and I assume that the problem was with the .xml file. (The problem may be related to an encryption program that I use.)They were mostly in the early postings for '09, so do what I did go back to the older posts, I also searched on "packages".
A few I found:
http://discussions.apple.com/thread.jspa?threadID=1868842&tstart=300
http://discussions.apple.com/thread.jspa?threadID=1867325&tstart=345
http://discussions.apple.com/thread.jspa?threadID=1866132&tstart=360
http://discussions.apple.com/thread.jspa?messageID=8793268�
http://discussions.apple.com/thread.jspa?messageID=8854053�
http://discussions.apple.com/thread.jspa?messageID=8763471�
http://discussions.apple.com/thread.jspa?messageID=8829762� -
Replacing .xmp sidecar files not recognized in Lightroom 3.6- Lr 'Guru' Question Alert!
- I have 'Automatically write changes ino XMP' checked
- I have not moved my catalog or files for years and only continue to add files to my catalog.
ISSUE:
I made some accidental global changes to about 600 .cr2 raw images and to save me time in recovering from each change I made, I closed Lightroom and then deleted the sidecar .xmp files in the folder. I then copied the .xmp files from a backup created and then launched Lightroom again- there was no indication that the metadata had been changed and thought that was odd. I right-clicked on the folder and slected 'Synchronize Folder' and the only option was 'scan for metadata updates' so I tried to synchronize from there- still no changes made to the image previews. The Metadata -> Sync Metadata option was grayed-out so that wasn't an option either.
What I finally had to do was highlight all the files in the Library module and select Photo -> Read Metadata From Files and ONLY after that did the previews update and read from the newly imported .xmp files.
So, my question is WHY did Lightroom not see that the .xmp files were changed as I have experienced in the past?I would have done Read Metadata from Files as my first choice.
From what you say, the LR metadata data was newer than the XMP metadata date and LR’s metadata updated date was newer than the XMP file-modification date so why would LR overwrite its newer metadata with older XMP metadata with a Synchronize? It might have worked the way you wanted if you had changed the file-modification date to be something current, by using a “touch” command or editing the contents of the XMP files, but LR seems to have done the right thing by not updating its internal metadata from and older XMP file using Synchronize and requiring an explicit command to do so.
It used to be impossible to update XMP files to the current set of edits if LR thought the metadata was current even if you explicitly commanded it to Write Metadata to Files, so Adobe has made adjustments to how LR and sidecars work together.
If LR used to revert edits based on older XMP sidecar files, that sounds wrong, and probably Adobe has fixed things to work in a more safe manner.
Do you remember if you saw an ! on the thumbnails indicating a metadata conflict or was LR completely unaware that the XMP files had been reverted to an earlier copy? -
A way to force XMP sidecar file use with JPEG files?
I have a nice camera but it only saves in JPEG format. Once I rename the files and put my basic copyright info into the metadata, I like to mark them as read-only for safety. However, I want to be able to save the metadata that I enter in Lightroom 1.1 out to disk along with the files so that other programs can read it. I see that Lightroom will save in a separate XMP sidecar file if the photo is in one of those snobby RAW formats but not if it is in one of the low-life formats like JPEG. ;^)
Is there any way at all to get Lightroom to use a sidecar file with JPEGs or do I have to just risk it and let it edit my JPEG files every time I do anything? I'm sorry, but my lowly JPEG files are just as important to me as a RAW file is to someone else. They are my photographs and I want to protect them.I'm not a pro so my backup routine is a little slip-shod. Sometimes I just grab a few files off the card, process them, and send the processed version out to whichever friend or relative is waiting impatiently for them.
I guess, I am most concerned about:
A) LR corrupting the working file and losing all the virtual edits. It is not easy for me to re-figure out what I did in the first place. Knowing about the safe-write technique helps.
B) Backing up just the edits. If the virtual/non-destructive edits were stored in separate .XMP files then I could back up those files to the same media as the original files and have them both together for future recovery operations. As it is, I now have to back up the entire working copy of the file in order to back up the edits. This creates two different versions of the file on my backup media, which will be harder to keep track of. Besides, .XMP files are small enough, and I would only be creating them for my better photos, so I could squeeze them onto the original backup media if I saved a bit of room. If I have to back up the entire modified file then it is less convenient.
C) When I write the metadata to the JPEG file, does it change the Windows modified date or creation date? -
Exporting XMP metadata sidecar files by themselves.
Is there a way to export sidecar files without exporting another master somewhere? I run a referenced library referenced to an archive on my HDD that I can easily back and manage. I may want to export sidecar files for the pictures as a yearly thing or so. As far as I can tell you can only creat sidecar files when exporting a new master which would then created an IMG_1(1) master and double the store space usage. By using the export metadata function you end up with a single text file.
Right now I just plan to manage and backup my metadata via a Vault but the option would be nice to be able to export sidecar files separately from a new master. Maybe I'm asking too much and just need to use the app as it is designed...Sorry I can't answer that, the script was written a while ago and came from here..
http://www.creativescripting.net/BridgeScripts/barredrock.html
It might be best to write one from scratch, but that would mean knowing what fields were required and what file types. -
"Sidecar file has conflict", keyword changes in LR not being written to JPEGs
I am new to Lightroom and evalutating 3.6 on a trial.
I performed the following test:
1. Imported 3 pictures into Lightroom from my hard drive
2. In Lightroom, I made a keyword change to one photo (removed a keyword).
3. All three photos' Metadata icon show the arrow, indicating that there has been a change. (I only changed the keyword on one photo.)
4. I click the icon for the photo whose keyword I changed.
5. I get the message "The metadata for this photo has been changed in Lightroom. Save the changes to disk?"
6. I click "Yes".
7. The photo's Metadata icon shows an exclamation point. When you hover over the exclamation point, it shows the message "Sidecar has conflict".
I have two questions:
1. My expectation is that when I changed a keyword, or any other metadata, in LR, it will show up on the photo outside of LR. My understanding is that this is a functionality of LR. Am I wrong? (The Help files seem to indicate that this is a reasonable expectation.)
2. I am assuming, having read many posts on the forum, that the error message "Sidecar has conflict" is a bug. Am I right? (My understanding is that JPEGs don't have sidecar files, which just makes this message even more odd.)
I am on Windows 7 Home Premium (upgraded from Vista Home Premium), 32 bit.
Thanks for your help,
--Elisabeth.Beat, Thanks for taking the time to answer.
Your expectation is not quite right:
Any change to metadata will primarily be recorded in your catalog, and nowhere else. Only if you perform "Save Metadata to File" (which can be set to be done automatically in your catalog settings) or "Save the Changes to Disk" after pressing the arrow, the changes will be written into your JPEGs (or into *.xmp sidecard files for Raw images) and can be seen from outside of LR.
Yes, you are right. What I should have written was: My expectation is that when I change a keyword, or any other metadata in LR, the change will show up outside of LR, after I "Save Metadata to File". This is not happening, instead I get the error message and different keywords in LR than outside.
Where do your originals reside? Could it be you don't have the proper authority to rewirte the JPEGs?
My originals reside on my Public drive: I definitely have rights. In fact, I did many other change to photos in the same drive after I posted this on the forum. -
I've just discovered a few directories containing my CR2 Raw files are showing a question mark in the Lightroom Gallery. This says that
"The following files (related to this photo) were present before, but are now missing", with the name of the .xmp file, and "The photo negative file is still present. Do you want to forget about the sidecar files, or continue to track them?"
I searched the forum and found one question on the same issue, but no answer.
I have copied over a few of these files from by back-up directory, but the question marks have not dissappeared.
Any ideas how I might have done this. (I didn't knowingly delete xmp files). and how can I rescue the situation. Do I risk losing my keywording and devlop settings?
Thanks
ColinI'm pretty certain that the ? does not relate to the image's location being moved, as there has been no movement there at all.
The xmp files in fact contain GPS data. TThe images still show the gps data in the metada column so does that mena the lrcat file hold that as well?
If so it seems that I can tell LR to "Forget" the xmp file.
Is there a way to find all images where the sidecar is missing?
Ta
Colin -
"Sidecar file missing" - LR 1.1 can't read XMP files
I am getting a "sidecar file missing" icon for 150 out of 2,500 photos I've imported into Lightroom. The .XMP files are present in the same folders as the photographs, LR is just not recognizing them. It is just a few files from several different folders, but not all the files in any folder. The photos appear as "Missing Files" in the Library heading on the left panel in Library mode.
The metadata appears correctly saved in the LR cache. I have tried writing the metadata from the cache to the disk, but that does not help. If I try to import the files or folders again, Lightroom will not allow it saying that the images are already in the catalog.
Sometimes I add metadata (i.e. rankings) to the files in IMatch 3.6, but I seriously doubt that has anything to do with this problem.Robert, thanks for the reply. I did find a work-around, eventually, but still haven't figured out what went wrong; I'm still investigating that.
The work-around:
1) I went to the Missing Files "filter" in Library mode.
2) I selected the missing files
3) I went to "Metadate/Write to File" and chose that.
4) If Lightroom said that the metadata had been updated in a different program, I chose the "Overwrite" option.
5) I then Removed the selected files from the Catalog (Alt-Backspace on my PC)
6) I then Imported the folder(s) with the missing files again.
Lightroom then read the XMP files without a problem.
I previously had tried your suggestion of opening the file in Breezebrowser Pro, modifying the metadata and saving the file. This did not cause Lightroom to able to read/find the XMP files.
I printed out various versions of the XMP files from instances where Lightroom could and could not find the XMP file and am going to compare them when I get a chance.
Thanks for your help -
Importing .xmp sidecar file doesn't populate IPTC info??
Good evening everyone. I've been trying to import .xmp files alongside some of my old movies to save me from having to retype the IPTC info such as location, etc. I have a folder which contains the .mov file I want to import, along with the .xmp file of the exact same name. I thought this was automatic (at least from my perspective), put I guess not? The .mov file imports just fine, but Aperture doesn't seem to populate any of the metadata fields with any info from the .xmp file. I've tried this with different videos/xmp sidecar files with no luck. Am I stuck re-entering all the metadata by hand? I really don't have much info, but I have several hundred files I'm trying to re-import, so it could be a long week. In case it helps, here's the xmp sidecar file that was created when I used iView Media Pro software pre-Aperture:
Thank you!!
sample .xmp file:
<?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?>
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Public XMP Toolkit Core 4.0">
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<rdf:Description rdf:about=""
xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/">
<photoshop:City>Venice</photoshop:City>
<photoshop:Country>Italy</photoshop:Country>
<photoshop:DateCreated>2005-09-19</photoshop:DateCreated>
</rdf:Description>
<rdf:Description rdf:about=""
xmlns:dc="http://purl.org/dc/elements/1.1/">
<dc:creator>
<rdf:Seq>
<rdf:li>Philip H. Sterling</rdf:li>
</rdf:Seq>
</dc:creator>
<dc:description>
<rdf:Alt>
<rdf:li xml:lang="x-default">The world famous Venetian gondolas!</rdf:li>
</rdf:Alt>
</dc:description>
</rdf:Description>
<rdf:Description rdf:about=""
xmlns:mediapro="http://ns.iview-multimedia.com/mediapro/1.0/">
<mediapro:Event>Italian Vacation</mediapro:Event>
<mediapro:CatalogSets>
<rdf:Bag>
<rdf:li>Venice</rdf:li>
</rdf:Bag>
</mediapro:CatalogSets>
</rdf:Description>
</rdf:RDF>
</x:xmpmeta>
<?xpacket end="w"?>The Photoshop and/or Bridge forums would be more likely places to get answers to your questions. This forum is inhabited more by programmer types interested in implementing the XMP specification in applications we write.
I'd expect CS2 to ignore CS1 panels so I doubt that's the issue. Panels don't interfere with each other--they just offer different views of the data. In any case, move the extra panels to your desktop and see what happens.
As far as I know, all you need to do on the Mac is drag the CS1 application folder to the trash to uninstall it. -
Feature Request: Metadata Export to Sidecar Files
I want to be able to export an image file's metadata to a sidecar XMP file that is named after the image file but with an .xmp extension. For proprietary raw files, that's the default. For DNG files, I can tediously force it by locking the file, loading it into Camera Raw, and selecting the "Export Settings to XMP" function. However I want to do this for several hundred or some thousand image files at once—so loading them all into Camera Raw just to make it export the metadata is not really a feasible method.
Worse yet, for JPEG files exporting the metadata to a sidecar file is not possible at all, as far as I can tell. When the JPEG file is writable then the exported XMP metadata will go into the file itself. When the JPEG file is write-protected then Camera Raw will entirely refuse to export the XMP metadata. This behaviour is inconsistent with other file types, as Camera Raw will happily export the XMP metadata to sidecar files for write-protected DNG files. By the way, there is another inconsistency between write-protected DNG files and proprietary raw image files, as Camera Raw will export XMP metadata for both into sidecar files but Bridge will export XMP metadata to sidecar files only for proprietary raw image files but not for write-protected DNG files. That doesn't make sense.
If an image file is write-protected then any changes to the metadata must go into sidecar files—as simple as that. Why are proprietary raw image files, write-protected DNG files, and write-protected JPEG files behaving differently in this respect? Sidecar files are fully supported for proprietary raw files, half-way supoorted for DNG files, and not supported at all for JPEG files.
Anyway—I need a way to select an arbitrary number of image files of any kind (in Bridge, not in Camera Raw) and then export all their metadata to sidecar files, one sidecar file for each image file, at the push of a button. It would be nice if I weren't forced to tamper with file locking first, just create those damn sidecar files when I'm asking for them. I'd even be happy with a createMetadataTemplate() or saveMetadataToSidecar() function in Bridge's scripting interface. There, I found a function to load a thumbnail's metadata from a metadata template (i. e. an XMP file; see applyMetadataTemplate() function)—but no way to save a thumbnail's complete metadata to a metadata template. If there is a way then please tell me. If there is no way yet then please provide one as soon as possible!Curt Y wrote:
My first question is why you want to export metadata to sidecar files. With DNG one of the touted advantages is that all the metadata is written to the file and no XMP file is needed or created.
This actually is a disadvantage that keeps me from using DNG format. XMP sidecar files are extremely useful to transfer updated metadata from the working set to the backup archive. Sidecar files do make life a lot easier.
Usually I will download the memory cards' contents to the computer's internal hard disk. Then I will add some bulk metadata, rename the files, and make a backup to at least one, preferably two external hard disks. Then I will continue working on the images—refining captions, adding more keywords, add labels and rankings, apply ACR settings. Finally I'll want to update the metadata in the backups. With sidecar files, that would require the transfer of kilobytes. Without, I'll need to transfer gigabytes because I'm forced to update the whole image files when actually I only want to update the metadata ... just because Bridge is too dumb to let me export the metadata to sidecar files. Or actually, it does let me export the metadata to a sidecar file—but only for one image file at a time which is totally useless when I need to update the metadata of hundreds or thousands of image files.
The DNG format does support sidecar files. DNG files can have their metadata internally 'under the hood' or externally in a sidecar file. When there is a sidecar file accompanying a DNG file then Camera Raw or DNG Converter will read and use it just as they would for proprietary raw files ... that's very convenient. Only Bridge doesn't allow the user to take advantage of that flexibilty but forces him to use internal metadata always, whether it makes sense or not.
Maybe you are looking for
-
Acrobat X external document linking problem
Hello, I have been using Acrobat 6 standard for our user manuals for years and have recently started using Acrobat X. It seems that the external document linking has changed though. I used to put all of our 3rd party literature (PDFs) in a separate
-
Why is there no AT&T service in Skagway at the moment
Super frustrating season this year with our cell service. Every tuesday, wednesday, thursday, our community can count on calls being dropped, delayed messaging, or no service available at all! As a small business owner that uses Square and relies o
-
Stopping Quicktime opening MP3 files in IE8 on Vista
When I updated to iTunes version 9, Quicktime was also updated to version 7.6.4 Now, whenever I click on a link to an mp3 file in IE8, it opens in a new browser in Quicktime, and, as I do not have and do not want Quicktime pro, I am unable to save th
-
Unable to see effect changes in program monitor
Hi Guys, I have tried applying an effect (3 way color corrector) onto a clip. When clicking on the white balance dopper and then onto the frame in the program view, the colour of the white balance changes to that colour, but the clip itself in the pr
-
Sql server opendatasource not connected after server changed?
hi. We used to fetch data from one server (SQL Server 2008). Now, we have changed to New Server. After changing to new server, we are unable to fetch or connect with sql server. No Error or Warning Messages after execution. pls mention the reason and