Lr4B XML sidecar files and Lr3?
Being somewhat paranoid i permanently have Write to (xml) file turned on in Lr3
Is this safe in the mixed environment ie will any Lr4 extensions be ignored if I were to reload the folder into Lr3?
Hi Rob,
Interesting idea although not quite the way I was using it. In my case I was using LR to manage a .fff file, which is a file that LR doesn't understand. In fact, it could have been any file and perhaps a good example might be a video project now that LR3 supports video. If anyone's interested in what I was doing with the .fff files let me know - happy to explain but it's very Hasselblad specific.
When you're done with editing etc and have your final .mov you could zip up all of the clips and the files for whichever editor you use into one file and call it 'moviename.zip' you then put this in the same folder as 'moviename.mov' and import into LR. The .zip file would be sucked into LR as a sidecar along with the .mov and managed along with it. In the future if you want to re-edit or get to any of the clips you go to the folder where the .mov is an you have your files.
This is exactly how LR2 worked and it would be nice to know why it's not working in LR3 and whether it can be re-enabled.
thanks,
...rob
Similar Messages
-
Creating XML file and transport to GIS (gentran integration suite)
Hello Experts,
I have a requirement. I need to convert the data from an internal table to XML Format file , and send that XML file to
GIS application [ gentran integration suite - middleware applicationa ]
i need to save that file to Unix-Filesystem and call an FTP transfer routine to GIS.
[ Purpose of GIS --> Transforming data (using services) from different applications so that it can be communicated to other
systems.Moving and communicating data between different systems external to Gentran Integration Suite,using adapters. ]
Please kindly reply me....
ThanksI do not think that you need to know more than the basics of Gentran, as you will have to upgrade PI, not Gentran.
Just check the Homepage of Gentran to find an overview about it:
http://www.sterlingcommerce.com/products/b2b-integration/sterling-integrator/
or find more information with google. -
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 -
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� -
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 -
Generated XML doc file contains comments from MFC source code
Hello, in my project I use the option /doc to generate XML doc file from my source codes but unfortunately in the output XML file there are mixed also comments from original MFC source codes, see the part of generated xml file:
Is there a solution to ignore these MFC cpp files?
Many thanks
Regards
Petr Stejskal
<?xml version="1.0"?>
<style xmlns="http://www.w3.org/1999/xhtml">@namespace html url(http://www.w3.org/1999/xhtml); :root { font:small Verdana; font-weight: bold; padding: 2em; padding- } * { display: block; padding- } html|style { display: none; } html|span, html|a
{ display: inline; padding: 0; font-weight: normal; text-decoration: none; } html|span.block { display: block; } *[html|hidden], span.block[html|hidden] { display: none; } .expand { display: block; } .expand:before { content: '+'; color: red; } .collapse
{ display: block; } .collapse:before { content: '-'; color: red; } </style><doc><assembly><assembly>
"Console" </assembly></assembly><members><members><member name="T:_RS"><member
name="T:_RS">Reed-Solomon codec control block</member></member><member name="M:MMask_makeMask(System.Int32,System.Byte*,System.Int32,QRecLevel)"><member
name="M:MMask_makeMask(System.Int32,System.Byte*,System.Int32,QRecLevel)">Mode indicator. See Table 2 in Appendix 1 of JIS X0510:2004, pp.107.</member></member><member
name="M:CMFCControlRenderer.IsScaled"><member
name="M:CMFCControlRenderer.IsScaled"><summary><summary>Tells whether this control
renderer works with scaled (resized) images.</summary></summary><returns><returns>Returns TRUE if this control
renderer works with resized (scaled) images.</returns></returns></member></member><member name="M:CMFCControlRenderer.SmoothResize(System.Double)"><member
name="M:CMFCControlRenderer.SmoothResize(System.Double)"><summary><summary>
Smoothly resizes images.</summary></summary><param name="dblScale" /><param
name="dblScale"> Scale ratio.</param><returns><returns>
TRUE if resize succeeds; otherwise FALSE.</returns></returns></member></member><member name="M:CDrawingManager.CreateBitmap_32(HBITMAP__*,System.UInt32!System.Runtime.CompilerServices.IsLong)"><member
name="M:CDrawingManager.CreateBitmap_32(HBITMAP__*,System.UInt32!System.Runtime.CompilerServices.IsLong)"><summary><summary>
Creates a 32 bit bitmap from the specified bitmap.</summary></summary><returns><returns> A handle to created
bitmap, or NULL, if creation fails.</returns></returns><param name="bitmap" /><param
name="bitmap"> A handle to the original bitmap.</param><param name="clrTransparent"
/><param
name="clrTransparent"> An RGB value specifying transparent color of the original bitmap.</param></member></member><member
name="M:CDrawingManager.CreateBitmap_32(CSize!System.Runtime.CompilerServices.IsConst*!System.Runtime.CompilerServices.IsImplicitlyDereferenced,System.Void**)"><member
name="M:CDrawingManager.CreateBitmap_32(CSize!System.Runtime.CompilerServices.IsConst*!System.Runtime.CompilerServices.IsImplicitlyDereferenced,System.Void**)"><summary><summary>
Creates an empty 32 bit bitmap.</summary></summary><returns><returns> A handle to created bitmap, or NULL,
if creation fails.</returns></returns><param name="size" /><param
name="size">Specifies bitmap size.</param><param name="pBits" /><param
name="pBits">When the function returns contains a pointer to bitmap bits.</param></member></member><member
name="M:CDrawingManager.DrawRotated(CRect,CDC*!System.Runtime.CompilerServices.IsImplicitlyDereferenced,System.Int32)"><member
name="M:CDrawingManager.DrawRotated(CRect,CDC*!System.Runtime.CompilerServices.IsImplicitlyDereferenced,System.Int32)"><summary><summary>Rotates
a source DC content inside the given rectangle by +/- 90 degrees</summary></summary><param name="rectDest" /><param
name="rectDest">Destination rectangle</param><param name="dcSrc" /><param
name="dcSrc">The source device content.</param><param name="bClockWise"
/><param
name="bClockWise">TRUE - rotate +90 degrees, FALSE - 90.</param></member></member><member
name="M:AfxRegDeleteKey(HKEY__*,System.Char!System.Runtime.CompilerServices.IsConst*,ATL.CAtlTransactionManager*)"><member
name="M:AfxRegDeleteKey(HKEY__*,System.Char!System.Runtime.CompilerServices.IsConst*,ATL.CAtlTransactionManager*)"><summary><summary>Deletes
the specified registry key.</summary></summary><returns><returns> If the function succeeds, the return
value is ERROR_SUCCESS. If the function fails, the return value is a nonzero error code defined in Winerror.h</returns></returns><param name="hKey" /><param
name="hKey">A handle to an open registry key.</param><param name="lpSubKey"
/><param
name="lpSubKey">The name of the key to be deleted.</param><param name="pTM" /><param
name="pTM">Pointer to CAtlTransactionManager object</param></member></member><member
name="M:AfxRegOpenKeyEx(HKEY__*,System.Char!System.Runtime.CompilerServices.IsConst*,System.UInt32!System.Runtime.CompilerServices.IsLong,System.UInt32!System.Runtime.CompilerServices.IsLong,HKEY__**,ATL.CAtlTransactionManager*)"><member
name="M:AfxRegOpenKeyEx(HKEY__*,System.Char!System.Runtime.CompilerServices.IsConst*,System.UInt32!System.Runtime.CompilerServices.IsLong,System.UInt32!System.Runtime.CompilerServices.IsLong,HKEY__**,ATL.CAtlTransactionManager*)"><summary><summary>Opens
the specified registry key.</summary></summary><returns><returns> If the function succeeds, the return
value is ERROR_SUCCESS. If the function fails, the return value is a nonzero error code defined in Winerror.h</returns></returns><param name="hKey" /><param
name="hKey">A handle to an open registry key.</param><param name="lpSubKey"
/><param
name="lpSubKey">The name of a key that this function opens or creates.</param><param name="ulOptions"
/><param
name="ulOptions">This parameter is reserved and must be zero.</param><param name="samDesired" /><param
name="samDesired">A mask that specifies the desired access rights to the key.</param><param
name="phkResult" /><param
name="phkResult">A pointer to a variable that receives a handle to the openedkey.</param><param
name="pTM" /><param
name="pTM">Pointer to CAtlTransactionManager object</param></member></member></members>Hi stejsky,
Thank you for posting in MSDN forum.
>>In my project I use the option /doc to generate XML doc file from my source codes but unfortunately in the output XML file there are mixed also comments from original MFC source codes.
Based on your issue, could you please tell me how you use the option /doc to generate XML doc file from your source codes?
If you use the option /doc to generate the XML doc file by right-click the your MFC project->Properties->Configuration Properties->C/C++->Output file->set the Generate XML document files as Yes(/doc) like the following screen shot.
(1)If yes, since we could not reproduce your issue in mu side, so if possible, I suggest you could share me your MFC project so that we will further help you support this issue.
You could upload your MFC project to the OneDrive and then copy link here.
(2)If no, please try the above way to generate XML doc file and then check if you still get same issue.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Hi,
I'm having issues generating a BCP XML format file using a fairly unusual column terminator, a double dagger symbol
‡ (alt + 0135) which I need to support.
I'm experiencing this problem with bcp.exe for SQL2008 R2 and SQL2012.
If I run the following command line:
bcp MyDB.TMP.Test_Extract format nul -c -x -f "C:\BCP\format_file_dagger_test.xml" -T -S localhost\SQL2012 -t‡
I end up with a XML format file like so:
<?xml version="1.0"?>
<BCPFORMAT xmlns="http://schemas.microsoft.com/sqlserver/2004/bulkload/format" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RECORD>
<FIELD ID="1" xsi:type="CharTerm" TERMINATOR="ç" MAX_LENGTH="255" COLLATION="SQL_Latin1_General_CP1_CI_AS"/>
<FIELD ID="2" xsi:type="CharTerm" TERMINATOR="ç" MAX_LENGTH="50"
.. and so on.
You will notice that the TERMINATOR="ç" (Minuscule c-cedilla) is output instead of TERMINATOR="‡". The
ç character, is strangely enough is alt + 135 (and not alt + 0135) so this might more than a coincidence! I know you can specify the codepage but this switch applies the data being imported or extracted and not for the format file
itself (I tried it anyway).
In order to use the XML file to bulk import I manually did a text substitution of 'ç' character for '‡' and then BCP imports '‡' data fine.
This character swap doesn't occur if I generate a non XML format file (the '‡' character is output in the format file correctly) however, this file produces other import errors, which I don't encounter if I use a standard delimiter like a comma. So I have stuck
with the working XML format file which I prefer.
Does anyone know why this is happening? I'm planning to automate the generation the of the XML format file and would like to avoid the additional step of text substitution if possible.
Thank you.Hi Ham09,
According to your description , we do a test and find that the character of the terminator is changed due to the code page of Operation System. When you choose the different time zone in Data and Time bar, and do the same bcp test, you will find it will
export the different TERMINATOR in your XML format file. For example, you can import the character "ç" (alt + 135) in (UTC-12:00)International Date Line West time zone and (UTC+09:00)Osaka, Sapporo, Tokyo time zone, and check if the terminators are different.
By default, the field terminator is the tab character (represented as \t). To represent a paragraph mark, use \r\n.
For more information, there is detail about code page(Windows), you can review the following article.
http://msdn.microsoft.com/en-us/library/windows/desktop/dd317752(v=vs.85).aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support -
Hi all!
I copied the business object EXTSRV to ZEXTSRV and created a new method zprocess that is mainly a copy of the Process method of the EXTSRV BO just that the creation part of the url is diffirent. I kept the call_browser function.
Then, I assigned this method to a task in the workflow this task is copy of the standard task TS50000075. I added the itemtype to the UWL XML config file and uploaded it to the system successfuly then i cleared the cash.
When i double click on the item in the UWL it partially works. I see the text written in the task but it is supposed to pop up a window. This window doesn't appear.
Can anyone help with that?
Thank you in advance,
HajarHi
Just check this out Please do not forget to give points
User Roles Restricts who can get work items via the user role. For example, you can assign a portal role here, such as buyer. Only users with the role buyer will see items from the provider system in UWL.You can have multiple user roles separated by semi-colon. By specifying user roles for the portal users, it can be restricted as to who gets the work items in UWL. For example, you can assign a portal role to a user, such as buyer. Only users with the role buyer will see items from a system, for example, B7QCLNT000 in UWL.
Pull Channel Delta Refresh Period (in Seconds) Delta Pull mechanism of UWL enables new items to be fetched from the back end SAP systems every minute by default every 60 seconds, and every 30 seconds for alerts. However, this can be configured. The user does not need to use the refresh function to update the inbox. Once items are retrieved, timestamps are updated for the users whose items are successfully retrieved. These retrieved items are updated in the UWL cache. Setup necessary from Business Workflow to enable Delta Pull MechanismSome configuration settings are required if you use the UWL and the Extended Notifications for SAP Business Workflow. Define the following two batch jobs:...● Background job (for example UWL_DELTA_PULL_1), consisting of a single step of ABAP report RSWNUWLSEL in FULL mode, using a report variant.Run the job once a day.1. ● A background job (for example UWL_DELTA_PULL_2), consisting of a single step of ABAP report RSWNUWLSEL in DELTA mode (default mode is delta, so report variant is optional).Run the job every one to three minutes (depending on the performance of the back end SAP system).Setup necessary from UWL to enable Delta Pull Mechanism The UWL service user in portal, with user id uwl_service, has to be granted access to the corresponding back end systems. This is a predefined service user provided by UWL. When the back end system is configured in the UWL administration page, an automated process is triggered to create a corresponding UWL service user in the back end system.Check role assignments and profiles status of this automated generated UWL service user and perform user comparison if necessary.● If SAPLogon ticket is used (without using user mapping), you first create the system entry. A message about uwl_service user appears. Then in the back-end system give the uwl_service user an initial password. Now edit the system entry.● If user mapping is used, you can first configure the back end system in the UWL administration page. Then access the respective back end system to initialize the password for the user uwl_service. Then, do user mapping in the portal as usual for service user uwl_service.In case uwl_service fails to be created in the back end and does not exist, you can manually create a back end user with the id uwl_service and assign the role SAP_BC_UWL_SERVICE and the rights as other end users.ORMap uwl_service to an existing back end user. Make sure that there is no multiple user mapping (there must not be two portal users mapped to the same back end user). This back end user must have the role SAP_BC_UWL_SERVICE.
Snapshot Refresh Period (in minutes) All items at the current time are fetched from the backend (for example from the SAP Business Workflow). The cache is synchronized thereafter. New / modified / deleted / updated items are fetched every session (every log on) if you leave the field value empty or enter a negative number.To specify a particular time frame for which the refresh occurs, enter the number of minutes
The above registration procedure is usually sufficient to use a UWL iView. Item type retrieval and registration requires a connection to the systems and may take a couple of minutes.
For each system, they are generated as the configuration named uwl.webflow.<system_alias> or uwl.alert.<system_alias>.
In Manager Self-Service (MSS), the Universal Worklist groups together in Workset: Work
Overview the various workflow tasks and alerts that are relevant for a manager.
The standard MSS delivery includes the configuration file com.sap.pct.erp.mss.001.xml for the universal worklist.
1. In the portal, choose System Administration →System Configuration →Universal
Worklist and Workflow →Universal Worklist →UWL Systems Configuration.
2. Create the following system connections:
If you have already registered a suitable connector to the system connected to
the system alias, the existing connector is sufficient and you do not have to
register an additional one.
○ System alias: SAP_ECC_Financials
Connection types:
■ WebFlowConnector
■ AlertConnector
○ System alias: SAP_ECC_HumanResources
Connection type WebFlowConnector
○ System alias: SAP_SRM
Connection type WebFlowConnector
Leave the Web Dynpro Launch System field blank for all system connections.
with regards
subrato -
LR2.7 "Missing Sidecar Files" issue
Hello,
LR2-7, Win32 Vista:
in a folder of 182 photos within catalog of 16 k photos:
suddenly, most photos show in Library view and the stripline a top right corner question mark and icon stating "sicedar file missing". In Catalog preferences the checkbox for "automatically write changes to XMP files" is not set (was never set), the folder does not contain any other files than the photos:
- in the beginning of this problem, these were cr2 files. It was then possible, to click on the icon/questionmark and trigger a dialogue "forget sidecar / continue?" but only for single files, NOT for a selection on click - come on.
- I converted the entire folder to dng files (my usual setting), NOW, the question marks all are still there, but NO dialog available any more on click.
- I pressed ctrl-S to create a sidecar file - zero reaction, nothing. Is there a secret place for sidecar files I would have to know?
I can of course remove photos from the catalog, and re-sync - this cures the issue.
- Up until now, I had a reliable catalog of approx. 16k photos - is this the end of it? I do do backups, but I can't afford a "sometimes" performance of Lightroom.
- what do I do about development settings already done when removing /re-syncing photos to get rid of the icons and "missing sidecars" (I don't miss them, why does LR)??
Anyways, this issue pops up on the forum on 1.1 and 2.3 versions... any sugggestions how to go about this on 2.7? Is this a feature?
thanks,
GerdDear dj_paige,
thank you for your note,
please see my comment to your email below in your text
DNG photos do not have sidecar files. So, their absence is not a problem.
- I know, I never generated any sidecar files and understand that there should be none for DNG. However, for the CR2 files, LR displayed the prominent ? and tooltip "sidecar file missing", and this persists even after converting to DNG.
I'm not sure what problem re-synching will cure. I do not recommend you "remove photos from the catalog, and re-sync", as you lose information that is catalog only (such as collection membership, edit history, color labels, pick flags and a few other things). In fact, I think it is a terrible idea.
- agreed. For this reason, I sent a note to the forum
If your catalog within Lightroom is working properly (and you haven't really convinced me that there is anything wrong), then again I don't know what the problem is.
- See above: for the CR2 files, LR displayed the prominent ? and tooltip "sidecar file missing", and this persists even after converting to DNG. Nothing else is wrong, HOWEVER, this icon and message is nonsense and should not be displayed
It sounds as if you are using the metadata as some form of backup of your catalog. It is not a backup; metadata enables you to share *some* information from your Lightroom with other applications. Other information in your catalog is not stored in the metadata written to files. The only way to create a backup of your catalog is to actually make a backup of the catalog file, which is a Lightroom option you can turn on. I consider making backups of your catalog file to be mandatory.
- NO, your assumption is incorrect. I do backup the entire catalog file.
Best regards,
Gerd -
Keywords in Master file and AP database-- Export Problem.
I believe that I have a conflict with keywords. I believe that I have "baked in" keywords by writing IPTC to the Master files and then added more keywords which I am guessing are in the Aperture database and not "baked in". When I then look at exported images using the XMP sidecar file with Adobe Bridge all of the keywords do not show up. I want to experiment with Lightroom and I want all of the keywords.
My process has been:
1. Add keywords to images from the keywords panel.
2. Write the IPTC metadata to the master files.
3. Add more keywords to the images from the keywords panel.
4. Export the images using the File/Export Masters/Create IPTC4XMP sidecare file.
5. Look at the exported images in other applications (Bridge and PhotoMechanic).
How can I export using XMP sidecar files and have ALL the keywords be exported???
DickBYes, this is a known problem; sqldev distinguishes between the Constraint and the Index although the former implies the latter...
Regards,
K. -
MSS UWL customization : Which .XML to modify and How?
Hello,
We have EP7 with MSS/ESS ERP 6.0 EHP4 and already configured the UWL system object with alias 'SAP_ECC_HumanResources'.
I am using the UWL iview from the MSS business package on portal.
I have a requirement to modify the task tab table removing few columns like 'Priority' and 'Status' etc.
Tried the option in UWL Admin as 'Click to Configure Item Types and Customize Views Using a Wizard' but that does not give me any dropdown option to modify any view.
I am going for the option to modify the xml file to implement the above change.
There are multiple .XML file's as below and I am not sure which one I should modify to change my view.
1. com.sap.pct.erp.mss.001 [Med]
2. com.sap.pct.erp.mss.tra [Med]
3. uwl.webflow.SAP_ECC_HumanResources [Low]
The UWL iview from business package has following properties as,
sap_uwl_viewname = com.sap.pct.erp.mss.AlertView
useNavigationId = com.sap.pct.erp.mss.Main
Can someone please advise which .XML file I need to modify and how?
After customizing the .XML fime do I need to make any change in the iview property as well?
Awaiting reply!
Thanks,
Smita ThoratIt would be nice if you can get some basics by reading the online help.
View - http://help.sap.com/saphelp_nw70/helpdata/en/a2/42e9ba01a5463ba10c797fb8e106d3/frameset.htm
Navigation Node - http://help.sap.com/saphelp_nw70/helpdata/en/e8/5a43bf9b8f406ea0776a3b428688a4/frameset.htm
Now, let me try to answer your questions:
Can you please help me understand why the system ID is 'ADHocSystem' and not my new system 'SAP_ECC_HumanResource' with connector 'WebFlowConnector which i have already registered ?
Is something missing in config?
The section "Current Item Information" provides information specific to the UWL item that is currently selected.
I am not sure which item you have selected in your UWL inbox but it appears to be using an XML configuration file that is related to Collaboration. That is the reason you are seeing the AdHocSystem in the properties.
What is the worflow task associated with this item ?
Make sure that your task is mentioned in your XML configuration files and also your XML configuration files have a higher priority.
I can see its pointing to the com.sap.pct.erp.mss.001 configuration.
Yes - the section "Current Navigation Information" is pointing to the com.sap.pct.erp.mss.001 configuration.
So as I understand from your response, I need to change the com.sap.pct.erp.mss.001 .XML file and rename it and then upload it to the configurations. and change the iview property UINavigation ID to <'>.
Is it correct, please advise?
This is not as simple as that.
Based on the changes you are trying to make, you will need to make XML changes and upload (with High priority) for various tasks, views, etc.
Please do some reading and get started with this and you can achieve this in a few steps.
- Shanti -
Xmp sidecar files- move/delete Bridge CS3
Hello
Anybody know a good way to hide the XMP files- or can they be moved to another folder? I don't suppose it is a good idea to delete these sidecar files
Is there a way for me to specify in Bridge CS3 that I do not want the .xmp files to be saved in the same folder as the images they are attached to?
How come .xmp files get saved for some of my tagged images and not others?
thanksI suppose you could go ahead and make them all hidden files. But you're going to have to do that every time you start working on another new raw file. If you're going to work with raw images you might as well just get used to seeing them. Another alternative would be to use the DNG converter to convert your raw images to DNG files. Then you wouldn't have to worry about XMP files at all because all the metadata is stored within the DNG. But that's up to you.
Another thing to consider. If you hide all those sidecar files and then decide to move your images you will have to go through the process of making them all visible so that you can copy them. Personally, I don't think it's worth it. -
EHP1 Installation - error during the XML stack file check.
Hello SAP fans and gurus.
I'm updating CRM with EHP1 and I'm stuck at the phase PREP_EXTENSION/SUBMOD_EXTENSION_NEW/SELSTACKXML. Something wrong with the XML stack file. I get this error:
Severe error(s) occured in phase PREP_EXTENSION/SUBMOD_EXTENSION_NEW/SELSTACKXML!
Last error code set: Error reading stack info, return Code = -1, Reason = 'The stack configuration is not valid for the system CRM, inst.-no. 0020652601'
The trouble ticket isn't saying much, but I'll post it anyway:
This trouble ticket was created by SAPehpi on 20110520102342
SAPehpi broke during phase SUBMOD_EXTENSION_NEW/SELSTACKXML in module PREP_EXTENSION / Extension module for start release >= 40B
Error Message: Error reading stack info, return Code = -1, Reason = 'The stack configuration is not valid for the system CRM, inst.-no. 0020652601'
Summary of SAPehpi:
SAPehpi Release: lmt_001
SAPehpi Version: 40.005
Start Release: 701
Target Release: 701
Summary of host system details:
SID: CRM
Host: sapvmcrm
MS Host: sapvmcrm
GW Host: sapvmcrm
Start Path: /usr/sap/CRM/DVEBMGS00/exe
Kernel Path: /usr/sap/CRM/DVEBMGS00/exe
Summary of operating system details:
OS Type: Linux X86_64
OS Version: 2.4
Summary of database details:
Database Type: ada
Database Version: 7.7.07.014
Summary of RFC details:
Host: sapvmcrm
GW Host: sapvmcrm
Client: 000
Destination: CRM
Language:
System No.: 00
There's one problem with the file SAPEXEDB_82-10007250.SAR, which was in the download basket, but is not available for download. I deleted the record in the XML stack file and tried the phase again... with no success. Going through the XML file and checking if the packages have been downloaded is a real pain in the ***.
Anyway, can I somewhere download this file SAPEXEDB_82-10007250.SAR?
Or can anyone help me, how solve this issue different way?
Thanks a lot in advance.
-StefanOK, I got it. Wrong installation number. We had to change the installation number in the stack file according the system in the Solution Manager via transaction SMSY. Then it worked like a charm.
-
.THM Sidecar Files Not Included When Importing Video Directly From Camera (Canon 7d)
Lightroom (3.4) has always copied the .THM sidecard files when I have imported video files from my Canon 7d using a card reader. However I am on a trip and have forgotten my card reader so I have been copying directly from the camera and for some reason Lightroom is not copying the .THM sidecar files and thus I am missing all my valuable metadata such as camera, exposure, focal length, ISO, etc. associated with the video files. Very frustrating!
Any ideas?Also because I do not have a card reader I cannot grab the .thm files myself. Mac OS X (and I think Windows) just see the camera as a "device" and offer to import but do not give me direct access to the files. Maybe if there is an app that will allow me to do that when the camera is connected I can work around this for now.
Maybe you are looking for
-
Help plz ipod id not recnized by computer
it norenizing my ipod i need help i used disk mode it dont work nither dose the 5rs my ipod was synic wit another compur and i need help plz
-
Having trouble opening the download for turbo tax 2013
having trouble with turbo tax 2013 for the macbook pro will not let me open it
-
Dear All, I tried to attach doc type to requisition thru network but while doing so following error shown when I specified 'AccAssCat SalesOrder ' Acct. assign. cat. "E" for purchase req. Sales order stock does not exist. Message no. CS076 Rgds [
-
Hi, We are providing consumables for thousands of HP 3015 printers, for security reason we would like to keep track of the consumable cartridges. Anyone know where is the serial number of cartridge is located . There are many sequence of numbers on t
-
Postal giro office entry is missing
Hi Guys, We are doing a payment method M for Switzerland. And we've carried out config of FBZP. But when we execute F110, we get the following error: Postal giro office entry is missing. In Payment method for country code> Required master record spe