Sidecar file has conflict
* I imported several thousands photos (JPGs) into lightroom.
* I edited metadata of these photos before import in lr with some other tools
* I selected "Automatically write changes into XMP" in lr catalog settings
* I reorganized my keywords
==> I saw that some of those photos has "Sidecar file has conflict" (the "!" sign at the upper right corner in grid view)
* I searched for the error and I saw, that some of the photos did only have IPTC and no XMP metadata included.
* If I copy IPTC data to XMP, I can save metdata to file in lr
==> My question: Because there are thousands of photos: Is there a way to search only those photos which have "Sidecar file has conflict" in lr?
To all contributing on this thread -
A .bat file called from a Shortcut Icon works as Rob suggested: only two lines (in Windows).
Start sqlite3.exe "Lightroom 3 Catalog.lrcat" ".read BadToFile.sql"
Start "" "C:\Program Files\Adobe\Adobe Photoshop Lightroom 3.3\lightroom.exe"
The BadToFile.sql includes the code previously suggested with a couple of lines to define file name and turn headers off. I then set up a smart collection for LR marked images. Now occasionally when I want to update image, instead of selecting all and updating them with Ctrl-S, I:
1. Exit LR and re-enter;
2. Run the LR Tranporter routine to mark images that are in the file list just created before start-up;
3. Select the smart collection and the select all images in there; then
4. Hit Ctrl-S.
Not a bad short-term solution. Also, if I then exit and repeat the step, it leave in those few images that can't ever seem to get updated with Ctrl-S and I can work on them individually by clicking the update icon or Updating DNG Previews (sometimes these work).
Anyway thanks for this thread.
Jeff
PS - The marking "Red" also works similarly but the downside is that when selecting the collection of those that are "Red", you can't save them before removing the "Red" or they will continue to have a mis-match when the "Red" is removed. You have to first save a quick or dumb collection to not lose the selected group. Also, if you have color labels in use, it overwrites them in "Red" and can't remember what color it was before - can be a bummer.
PSS - After playing with the sqlite command window, I agree that the table structures of this LR database seem a bit of a mess. It has probably morphed over time and may not be the best design if one were starting from scratch. I therefore wouldn't want to spend too much time working with this database as a re-structure seems in order sometime in the future.
Similar Messages
-
Error: Sidecar File has Conflict
Hi
I've just tried to work on a collection of files, previously edited in Lightroom, and found they are marked with a '!', which, when hovered over indicates that 'Sidecar File has Conflict'
Does anyone know what this means?
ThanksWhen you have metadata conflict:
If you edited them in Silver FX, without going through "proper" Lightroom (Edit In) channel, and haven't edited them in Lightroom (since xmp was saved), then it's a bug. What Lr should have done is set the up-arrow icon (indicating external changes need to be incorporated in Lightroom). If you have changed photo in Lightroom too (since xmp was saved), then it's not a bug, since Lr doesn't know which changes to keep and which to discard - settings from one source must replace changed settings in the other source, to resolve conflict.
If you edited them by going through proper Lr-involved procedure (i.e. Edit In...), then it's a bug, because Lr (and companion app) should always "do the right thing" in this case.
Dunno if that answers your question, since I couldn't be sure what happened exactly based on your description.
The thing to do is make sure metadata is squared away (e.g. no down-arrow, no up-arrow, no exclamation icon..) before editing externally, then there should be no conflict - it there is, it's a bug and you can resolve (safely) by reading metadata from disk (Lr's metadata menu).
Conversely, if you haven't edited externally, there should be no conflict, and if there is, it's a bug, and you can safely resolve conflict by saving metadata to disk.
PS - Change Manager (a plugin I wrote) can be used to see exactly what is different between settings and metadata in catalog vs. disk (xmp).
Hope this helps,
Rob -
Lightroom 1.3 "Sidecar file has conflict" on .PSD files...
I've got some .psd files that I changed in Lightroom - they're layered photoshop files, saved with maximize compatibility. The change is to keywords on these files. At present I have about a dozen (that I know of) that appear NOT to be able to update their metadata. The error that displays when I put the mouse on the image's metadata icon is "Sidecar file has conflict".....
Mayhap I'm missing something, but there are no sidecar files that I know of. They're PHOTOSHOP files, not RAW. The only change to these files in Lightroom was to add, delete, or alter one or more keywords. Other files write metadata successfully, but these fail. How do I get LR to fix this?Don, not that I'm doubting your statement, and in truth I can't recall whether or not there were jpegs with the same name, but if having a jpeg with the same filename causes this kind of problem, isn't that pretty much the definition of a BUG? Again, this seems a pretty major problem, although I suppose if it only happens occasionally and the people affected don't mind losing their changes, its no big deal...
-
LR3 coversion Sidecar file has conflict
I converted my LR2.7 catolague to 3.0. The photo have all loaded but in the library mode I am getting an exclaimation stating that the Sidecar file has a conflict. How do I correct this?
I've been having this problem along with the host of other performance issues that make Lightroom 3.0 unsuitable for anything more than aggravation.
If one is on any sort of deadline or timeframe, Lightroom 3 is an unmitigated disaster.
Wasted time, frustration, risk to past and ongoing work. Incredible sloth, associated compromises general system performance and freezes, forced frequent reboots that lose work in LR and other open applications, the list goes on and on.
I've reverted to 32 bit on my modern Mac, attempted all the bandaid 'fixes" in the voluminous "Slowness" thread offered by both well intended participants and condescending jerks that need to get a life. Some have had small benefit. Nothing has had impact enough either singly or collectively to remove this newfound disdain from LR or it's incompetent founders. Since Adobe itself has been unwilling or unable to respond in any meaningful way to convert this inexcusable sow's ear into it's intended silk purse, I've gone back to 2.7, lost more than two weeks since needing to redo on 2.7 what 3.0 confounded me to do, and determined to never again so stupidly entrust Adobe with my livelihood or scarce resources.
As concerns Sidecar File conflicts, in side by side comparison the same files have no such issues in 2.7 while 3.0 is wildly resplendent with such episodes scattered across my 66,000 photo catalogue. Recreating catalogues, optimizing, etc are inappropriate little bandaids instead of solutions that don't seem to do much for this or the other failures rampant in LR3, other than to waste further time and frustration. We spend our good money and time and faith on LR3 from prior sponsorship of Adobe, and should not have to "try" scores of little fixes for these multitudes of PROBLEMS that remain non-issues in 2.7, or at least are reasonably workable there.
Early on I thought (and hoped) that something must have gone terribly wrong at Adobe to permit some isolated issue to cause this fiasco, which would be quickly and readily addressed upon subsequent discovery. I haven't actively participated much here, expecting instead that the company would respond (and in part because of some holier than thou cheerleaders here encouraging working professionals who have real life problems as a result of LR3 with the likes of "just suck it up").
It's been sad to see so many others so significantly negatively impacted as I have been by this unfortunate episode of Adobe continuing to pump out sales without any public recognition of the disaster this is. I and many others will not forget. Very short sighted. More current sales to more unwarily duped former Adobe fans not a good idea. What are they thinking? -
"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. -
Lightroom support suggests that I continue and ignore the icon on the image until it becomes a problem. Will the conflict message have any effect on my using any LR programme. Can I easily get rid of the message. It is scatterred on many images with no obvious pattern of selection
Pete, you wrote:
"Unfortunately this is not the case...a sidecar file will not move "automatically" with the file it relates to if you move the file in the OS."
I recently moved a lot of image-files to a different drive; the move was done by my OS (Win XP). I just checked, and xmp-files are there.
I haven't worked with any of these images since the move (they are copies that are not imported into LR), so the xmp-files are not re-created new.
WW -
- 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? -
So all the sudden some of the photos I'm editing start to pop up with a "metadata has conflict" sign. It says the metadata was changed in Lightroom and another application. I don't know where else it would have been changed. I wasn't using any other application. It wants me import settings from disk or overwrite settings. Not sure what to do. Please help. Thanks.
Lightroom 4The best way to determine which option is the correct one is to check out all the metadata on that image.
If it is correct and up to date as far as develop edits and metadata that you have added such as IPTC metadata and keywords then one can overwrite the settings in the XMP sidecar files or in the TIFF, DNG, or JPEG images.
The other way around is a bit harder since it would take Bridge or another application to see all the data in the XMP file or the other files and then decide on the best option.
Ultimately unless you need to write metadata to disk it is fine just to make sure that the catalog has the right metadata.
You do not necessarily need to let Lightroom bully you into changing things in this context.
Tony Jay -
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. -
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. -
The full message reads 'The file contains conflicting spot color information. Spot and process colors cannot share the same name. Please resolve the spot color conflict and try reopening this file.'
The problem is the file just closes after that. If anyone has had this problem before and managed to resolve it, please please help!This turned out to be a links issue. One of the psd's had corrupted. In the end we found out by making sure the file couldn't connect to the links in the illustrator document allowing it to open in the basic vector format. We disconnected from the network, another way would be to move the links folder. Once the file was open the links could be deleted/replaced seems it didn't close the file straight away.
I hope this helps anyone else that has this problem, there really wasn't much information on it, especially not up to date information.
Vicky -
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 -
Option to always use sidecar files for XMP
Lightroom gives you the option to write metadata to XMP files, which is convenient if you want to share data with other programs (ACR, various DAM programs). In the beta versions, this data would always be stored in .XMP sidecar files, presumably for safety reasons. However, V1 writes the XMP data into the image file itself for those formats that support it (DNG, JPG, TIFF).
I would really like to have the option to *force* Lightroom to use sidecar files for XMP data, like the betas did. The current V1 behavior (embedding data) is quite inefficient for fairly common backup scenarios.
For example, I tend to back up all my raw files onto DVD after importing and culling. In addition I make a daily backup of all metadata that gets sent over the internet to a web server - a relatively small upload. What happens if I use DNG for my raw files and update something as small as a keyword? Indeed, *all* of the corresponding DNG files are modified, and because my backup software cannot know that only the XMP data has changed, all files must be burned to DVD again. If the metadata were stored in sidecar files, a simple, efficient metadata backup would take care of things.
To implement this, a simple switch in the preferences would suffice, and the necessary code is already there. The only possible problem is the occurrence of two files with identical names, excluding the extension. For this case, I can see four different 'solutions':
1) Force XMP metadata to be synchronized between files with equal names
2) Make an .XMP sidecar file for only one of the files (always the raw file, for example)
3) Update the XMP specification to specify what should be done in this situation (maybe include the file extension in the XMP data)
Reards,
SimonActually, I don't (notice the 'if' :)). And this is only one of the reasons. I just picked DNG as an example, to keep things simple and because it seems Adobe wants DNG to work well for photographers.
However, the same applies to JPG and TIFF images. I often end up changing details in the metadata after the image has been finished. For example, to correct the spelling in a keyword that has been applied to half the images in my database... Talking about a nightmare scenario!
Simon
Maybe you are looking for
-
BOE 3.1 SR3 on Solaris SPARC - how to for Int kit for SAP Solutions ?
Hi, this is my first BOE installation and I've just installed the BOE SR3 Enterprise Server on Solaris SPARC with SAP WAS 7.0 and Oracle 11.2.0.2 providing the CMS database location and the Java application server for the BOE applications. The instal
-
DB 13 Calender-DB check is getting Failed
Hi Team, Configured DB check job is getting failed in DB13 Calender with the following error. Job started Step 001 started (program RSDBAJOB, variant &0000000000015, user name BATCHJOBS, language E) Execute log. command SAPDBA on host ukcbx001 __Para
-
Pretty simple Eclipse question... about imports
hi, i am developing with Eclipse. I am relatively new with it. So say I have two folders: \source\java\Folder1 and \source\java\Folder2\Package1 I want to import a class from Folder1 and some classes from Package1. How do i do that in Eclipse? i trie
-
Branch Wise Reporting /Region Wise Reporting
Hi Guru's We have 1 Company Code 7 Regions 24 Branches The client wanted to see the Region wise Reports & Branch Wise reporting as their current software is providing the same.So they are required Region wise Reports &
-
Probleams para reproducir swf playerwpress en la pagina de radio formula
No se puede abrir el archivo de musica