Olympus OM-D EM5
The new Olympus EM5 is out and I, along with many other Aperture users, would like to see the Apple support team issue a RAW converter ASAP. Actually, I would feel better if I knew that Apple was even going to issue the update.
Steve
Aperture->Provide Aperture Feedback
Apple isn't here only us users so if you want them to know something you have to tell them.
Similar Messages
-
Olympus .ORF from OM-D E-M5 in Lightroom 3.6
1. is there a way to import the Olyimpus RAW .ORF fro the OM-D E-M5 directly in Lightroom 3.6 like I was used with the Nikon .NEF format?
2. is there a step-by-step how-do description?
Thanks,
AngeloCamera support for raw files is provided by regular updates. Each and every new camera model has to be done individually.
Support for the Olympus OM-D-EM5 was introduced in LR 4.1. Since this is a new version of Lightroom and LR 3.6 will not have any further updates you will either have to
a. Upgrade to LR 4 or
b. Utilize the latest DNG converter to convert the .ORF files from your camera to .dng and you will then be able to use LR 3.6 to process the .dng copies. (best to also retain a copy of you .orf files if you also wish to utilize the software provided by Olympus.) -
Sony - when will you step up to fix A7r and lossy compression?
Sony - Nikon was sued for their D600 issues. Why not do the right thing and address the A7r and lossy compression? You have a number of experts discussing the A7r shutter shock and Sony's lossy compression scheme and not yet a response from Sony. Sony advertises that their cameras provide 14 bit color but the Sony compression algorithm never delivers more tha 8 bits of color depth according to file sizes. This is deceptive and may amount to fraud. Users want a camera that at the least provides an option for TRUE 14 bit color depth (even at the expense of frames per second) and a software update that eliminates shooting in the shutter range where shutter shock and blur are an issue. http://www.josephholmes.com/news-sonya7rshuttershake.html http://blog.kasson.com/?p=4674 http://diglloyd.com/blog/2014/20140212_2-SonyA7-RawDigger-posterization.html http://diglloyd.com/blog/2014/20140116_1-Sony-A7R-shutter-vibration.html
I'm interested in the upcoming A7S, before releasing it I hope, this time you make sure: 1) There is no light leaks of any kind, whatsoever. 2) Implement same kind of anti-shutter-shock 2s delay as in Olympus OM-D EM5 has in firmware, if you can't fix the shutter vibrations mechanically. 3) Provide a way to store truly lossless raw (should be easier with the smaller 12mpx sensor, maybe..?) Just ask some of the professionals who have wined about these issues have a go with the A7S before release to make sure it doesn't have these or some other similiar issues that hurts your reputation after release.. Tnx
-
Micro 4/3rd's lens profiles
Are there lens prfiles available for micro four-thirds lenses, in particular, a Panasonic 8mm used with an Olympus OM-d EM5 dslr?
Bob, you would need to make a profile.
However, surely it would be better to apply lens corrections to RAW images before subjecting them to HDR treatment?
Tony Jay -
Process Version 2012 for photos taken with Olympus OMD EM5
I have just purchased an Olympus OMD EM5. When I download images to Lightroom (v4.4) I have to manually convert to Process 2012. Am I doing something wrong? Why does this not happen automatically?
I can't tell you why it is doing that. Are you applying a preset on import that includes the older PV? Just a suggestion; you could create a preset that applies to the 2012 PV when images are imported.
Pardon my ignorance, but does that camera shoot DNG natively? If it does, I wonder if it is using an older spec. Don't know anything at all about this, just wondering. -
RAW support for Olympus OMD EM5
Outfitting for a year long back pack trip. My MacBook Pro is going. Am in processof purchasing an Olympus OMD EM5 micro 4/3 camera for the trip. I use Aperture for photo processing. Any idea when or if Aperture will add support for developing the RAW shots from the EM5?
thnxThe usual interim approach for raw support has been to use Adobe's DNG converter to create DNGs that Aperture could read. This has always worked with the esception of non-Bayer sensors like the Foveon in Sigma cameras. But I can't get Aperure to read DNGs created from my E-M5's ORFs using DNG Converter v6.7 and have no idea where the problem lies.
It's taken Apple months to support Olympus cameras in the past, so I'm not optimistic.
—Andreas -
Olympus EM5 - profile issue (probably), raw file example provided
Olympus EM5 - profile issue (probably)
raw file in question, posted by somebody in dpreview forum = https://dl.dropbox.com/u/50147350/P8261159.ORFAs evident from your screenshot, those letters are not blown in raw - there are only a few pixels where one of the channels (blue) is reaching saturation. However, that blue color is very saturated and is mostly falling outside output color space (which is usually sRGB or Adobe RGB) or in other words, your monitor isn't able to display that color
Conversion from raw color space to output color space is done using profiles and can be colorimetric or perceptual. If conversion is colorimetric, colors outside output color space are simply clamped into the range (for instance RGB -15, -30, 270 --> 0, 0, 255). If conversion is perceptual, colors that would fall outside color space are compressed into it (for instance it could be -15, -30, 270 --> 10, 5, 253). In first case, colors inside output color space are 'correct', while those outside are wrong - less saturated and possibly with wrong hue. In the second case, colors outside color space are 'less wrong', but colors inside color space are also 'less correct', but overall result is mostly more pleasing to the eye. This compression is performed differently by each manufacturer.
Each camera model has own set of profiles. Most simple profile is an 3x3 array named color matrix, used for this color conversion - it is embedded in ACR for all supported cameras and can be also written in raw file. It is colorimetric. Then there is Adobe standard profile for all supported cameras in form of dcp file. It is a combination of matrix and lookup table conversion, which is still close to being colorimetric (however, there are several versions). Other profiles that are emulating camera rendering are perceptual (on some cameras there is also one profile said to be colorimetric, for instance Faithful profile in Canon cameras). Unfortunately, there are no camera profiles for Olympus yet, so colorimetric conversion is the only option (ok, another option is using new version of sRGB profile and its perceptual rendering intent, but it is not possible directly in ACR).
In this particular case, you can improve the look of those letters by moving saturation slider of blue primary (camera calibration tab) from 0 to about -15, which will modify color matrix used for conversion and desaturate whole blue range. Or do the similar thing with slider in HSL tab
If PV2010 used, some of blown blue color turns violet. It's also a know issue, actually I also reported it several years ago, and is caused by usage of Photo pro color space as intermediate and some clamping of values in ACR workflow. In this case it may be corrected in calibration tab by moving blue hue slider a bit to left, which will change hues of blue range towards cyan.
Etc. This area is quite complex, I'm familiar only with a small part of it, which I needed for making camera profiles -
I'm sure I'm being a bit premature but when could we possible see support for the Olympus OM-D EM-5? The camera is getting in the hands of the consumer (I now have one WOOHOO) and would love to have LR support it
The original thread was about raw support, and your first post out of the blue almost three years later, merely said "2 years and still nothing..." so a reasonable person might consider it an uncalled for troll post in itself, since it was an unspecific negative reply and clearly false in the context of the original thread it was replying to.
Now that you've explained a little more, the initial question could have been something more like "Why doesn't my Olympus OM-D E-M5 have selectable lens profiles after more than two years of its raws being supported?"
The answer to that is simple: The selectable lens profiles in your screenshot are for DSLRs not mirrorless cameras because mirrorless cameras have built-in lens support that is always on with no need to select a profile.
The reason lens support is built in for mirrorless cameras like your Olympus and not DSLRs is that mirrorless cameras have had lens corrections already applied on the fly by internal camera software before the image is shown on the LCD panel at the back of the camera and also applied to any JPGs the camera produces, so you never actually see the uncorrected image. Adobe products also apply this same lens profile to their onscreen and exported/saved output from LR and Photoshop so you never see the uncorrected version.
DSLRs have selectable profiles because there is an entirely optical path via mirrors and prisms from the lens to the viewfinder without any internal camera processing, so the photographer actually sees the uncorrected image, and as such Adobe products make the correction of it optional, with selectable lens profiles, that can be turned off in case the photographer meant their composition to be exactly what the optical viewfinder showed.
To help address the confusion about whether mirrorless cameras have lens profiles or not, Photoshop’s ACR 8.4 and newer will indicate lens support has been built in, but there wasn’t any UI change mid-version-stream in LR 5 to add this information. ACR 8.x is part of Adobe cloud releases that promises continuous development so it makes sense Adobe adds something to the UI as soon as it was available, whereas LR isn't a cloud product so users have to wait until a new payfor upgrade to have functionality changes, other than new camera support. One would hope that Adobe adds this information to LR 6 to avoid confusion.
Here is an example of the information that PS/ACR shows in the lens correction area for a built-in profile. This isn't your Olympus but the idea is the same:
For reference, here is what the uncorrected image looks like if you open it in a raw converter that doesn't have the lens profiles applied automatically, in this case raw analysis software, RawDigger: -
When will Elements and Lightroom support the RAW files from the Olympus em5 Mark 2 camera?
Camera was launched in Feb 15. As far as I understand, neither product will open the RAW files for some months. When will that be, does anyone know?
Adobe Camera Raw gets updated three or four times per year in an orderly fashion.
Beyond that, Adobe does not comment on unreleased software.
It should not take over nine (9) months, but it could be as early as at the time of the next orderly release -
LR5 does not recognize Olympus OMD-EM 5 II
How do I get Adobe Lightroom 5 to work with my Olympus OMD-EM 5 II camera?
Support for the OMD-EM5 11 was introduced with the Adobe Camera Raw Plugin version 8.8 for Photoshop CS6 and CC. There has been no corresponding update to LR 5.8, the latest version is 5.7.1.
See the link below which provides additional info.
Quote "Lightroom Customers –
If you’re using one of the newly supported cameras listed above, please download the DNG Converter. We’re working to add support to these cameras and they will be added in the next Lightroom release."
Lightroom Journal | Tips and advice straight from the Lightroom team. -
10.6.8 stops me importing photos from Olympus camera
1. Recently bought a new Olympus VR310 digital camera. I couldn't get either Image Capture (6.0.1) or iPhoto (9.1.5) to import images from day one, onto my Mac Mini running Snow Leopard 10.6.8. However, if I took the SDHC card out of the Olympus and put it into an older Canon Ixus digital camera , and used that to upload, then both Image Capture and iPhoto worked perfectly. So it's not the card. Or the USB connection. It's something special to the Olympus and the Mac. Obviously I tried all the usual stuff about dumping plist files etc. Nothing worked.
2. The problem manifests itself, when the Olympus is connected, as Image Capture being unable to show more than one, if any, thumbnails, and it is unable to import at all. In iPhoto the problem manifests immediately it calls up the Olympus as a connected camera. The dreaded spinning beachball of death kicks off, and the program 'stops responding'. Even after I quit iPhoto and unmount the Olympus, iPhoto will not open without the spinning ball of death until I restart.
3. Anyway, I tried connecting the Olympus to my son's Macbook, (System 10.6.7, Image Capture 6.0.1 and iPhoto 9.1.1) and all worked perfectly. Hmm… so it's NOT just down to the Olympus. It's something to do with my setup.
4. I also have a bootable USB drive connected to the Mini, so I booted into that, so I then have my computer and my user preferences etc running under the bootable drives System 10.6.6, Image Capture 6.0.1, and iPhoto 9.1.5. That worked perfectly with the Olympus too. So it's not my the combination of my user settings, Image Capture 6.0.1, or iPhoto 9.15, or the Olympus.
5. My guess then was it was some corruption of the system on the Mac Mini. So I reinstalled the Mac Mini system, from the install DVD, so I had a nice fresh Snow Leopard 10.6.0. That gave me Image Capture 6.0.1 and iPhoto 9.1.5. When I attached the Olympus, everything worked perfectly. Great.
THEN, I updated the system from Apple's Oftware Update, all the way to 10.6.8, which is where I started from.
6. And guess what. Nothing works anymore. Immediately before the update, the Olympus importing worked. Immediately afterwards it didn't. I'm back where I was at the beginning, with exactly the same problem.. I can't import from the Olympus but the Canon is fine. (see 1 and 2 above)
So, it seems to me that the Upgrade straight to 10.6.8 is what caused the problem. And given I could get the Olympus to work on my son's computer (system 10.6.6) it's something between 10.6.6 and 10.6.8. Why the Canon works on all the permutations, and not the Olympus, I don't know. I don't know why the Olympus ONLY doesn't work with 10.6.8.
7. Obviously there are tedious workarounds (but none that lets iPhoto capture the photos directly) which I can use to get the images into iPhoto eventually, but hey, this is an Apple Mac, who wants to be doing tedious workarounds all the time.
I've had Macs since 1984 (I'm that old…) so I'm a fan, and I'm reasonably competent, but this has me stumped.
Any ideas, anyone.
Any help much appreciated.
Ian WaterstonYou launched iPhoto and from its Preferences you selected Connecting camera opens.....
-
Upgraded to 10.6.8 and now can't import photos from Olympus camera
1. Recently bought a new Olympus VR310 digital camera. I couldn't get either Image Capture (6.0.1) or iPhoto (9.1.5) to import images from day one, onto my Mac Mini running Snow Leopard 10.6.8. However, if I took the SDHC card out of the Olympus and put it into an older Canon Ixus digital camera , and used that to upload, then both Image Capture and iPhoto worked perfectly. So it's not the card. Or the USB connection. It's something special to the Olympus and the Mac. Obviously I tried all the usual stuff about dumping plist files etc. Nothing worked.
2. The problem manifests itself, when the Olympus is connected, as Image Capture being unable to show more than one, if any, thumbnails, and it is unable to import at all. In iPhoto the problem manifests immediately it calls up the Olympus as a connected camera. The dreaded spinning beachball of death kicks off, and the program 'stops responding'. Even after I quit iPhoto and unmount the Olympus, iPhoto will not open without the spinning ball of death until I restart.
3. Anyway, I tried connecting the Olympus to my son's Macbook, (System 10.6.7, Image Capture 6.0.1 and iPhoto 9.1.1) and all worked perfectly. Hmm… so it's NOT just down to the Olympus. It's something to do with my setup.
4. I also have a bootable USB drive connected to the Mini, so I booted into that, so I then have my computer and my user preferences etc running under the bootable drives System 10.6.6, Image Capture 6.0.1, and iPhoto 9.1.5. That worked perfectly with the Olympus too. So it's not my the combination of my user settings, Image Capture 6.0.1, or iPhoto 9.15, or the Olympus.
5. My guess then was it was some corruption of the system on the Mac Mini. So I reinstalled the Mac Mini system, from the install DVD, so I had a nice fresh Snow Leopard 10.6.0. That gave me Image Capture 6.0.1 and iPhoto 9.1.5. When I attached the Olympus, everything worked perfectly. Great.
THEN, I updated the system from Apple's Oftware Update, all the way to 10.6.8, which is where I started from.
6. And guess what. Nothing works anymore. Immediately before the update, the Olympus importing worked. Immediately afterwards it didn't. I'm back where I was at the beginning, with exactly the same problem.. I can't import from the Olympus but the Canon is fine. (see 1 and 2 above)
So, it seems to me that the Upgrade straight to 10.6.8 is what caused the problem. And given I could get the Olympus to work on my son's computer (system 10.6.6) it's something between 10.6.6 and 10.6.8. Why the Canon works on all the permutations, and not the Olympus, I don't know. I don't know why the Olympus ONLY doesn't work with 10.6.8.
7. Obviously there are tedious workarounds (but none that lets iPhoto capture the photos directly) which I can use to get the images into iPhoto eventually, but hey, this is an Apple Mac, who wants to be doing tedious workarounds all the time.
I've had Macs since 1984 (I'm that old…) so I'm a fan, and I'm reasonably competent, but this has me stumped.
Any ideas, anyone.
Any help much appreciated.
Ian WaterstonYou launched iPhoto and from its Preferences you selected Connecting camera opens.....
-
Photoshop CS2 obsolete with an Olympus E-3
I just received my new Olympus E-3 this week and it is a very impressive professional DSLR camera. I have to say that I am exceedingly disappointed with Adobe right now as it looks like they are no longer supporting Photoshop CS2 even though it is only one revision old. With the latest updates I can use their digital negative converter (which I wish more camera manufacturers would support) and my Photoshop Elements 5.0, including Camera RAW, works with the E-3 ORF/RAW files. Photoshop CS2 apparently has no plug-in for it, the latest Camera RAW doesn't work in it or in Bridge, and it no longer accepts new .dng files sent to it from PSE5. It is now largely useless to me as I can't used it until the photos are degraded .jpg's.
I am on Vista, so is their anything I need to do, or is my analysis above correct? CS-2 over CS had enough to make me upgrade, CS-3 over CS-2 didn't.Nobody likes the fact that to get the latest raw support for the latest
camera (without hoop jumping) you have to upgrade Photoshop. Most of don't
think it is fair. However, there are some things to keep in mind.
1. Each new major release of Photoshop brings massive updates to ACR. These
updates would not be an easy or really cost effective thing to do for older
versions of ACR.
2. It is very likely that updates to ACR are not solely in ACR itself. I
would imagine that some changes have to be made to Photoshop to. This means
they couldn't update ACR to work with CS2 because CS2 is lacking things that
would be needed. Things that are only in CS3.
3. Even if Adobe charged $19.95 for the ACR upgrade for Photoshop CS2 if
they couldn't bring it inline with CS3's ACR but only could add support for
new cameras people would still complain.
4. There is a work around, download the latest DNG converter program, it is
free and convert your raw images to DNG. This is in my book a good thing
anyways. Just as soon as DNG becomes and ISO standard it will be the safest
raw format available. In other words it will be the most future proof raw
format we will have. Once your files are converted to DNG you can then load
them in to the ACR that comes with CS2.
Myself, I think the mistake Adobe made was not making the camera support a
plug-in for ACR. By doing this they could have simply updated ACR as they
wished giving you the new version with each new version of Photoshop, but
allowed people with the old versions to use new cameras because you would
only have to download new profile plug-ins for new cameras. I don't see new
cameras as being a major reason to upgrade ACR. I see the new features and
improvements made to each new version of ACR more of an upgrade draw than
new camera support. I think Adobe would have lost very little income by
designing ACR to support new cameras by doing plug-ins. I would still have
upgraded from CS2 to CS3.
Of course there is also the new upgrade policy. Photoshop 7 is the oldest
version you can now use to upgrade to Photoshop CS3. If you have a version
older than 7 you have to buy the full Photoshop package, you can't upgrade.
When Photoshop CS4 comes out then CS1 will be the oldest version you can use
to upgrade. So sooner rather than later unless you like to buy full packages
instead of upgrades one is going to have to upgrade anyways.
Myself I would use the DNG converter now and then upgrade Photoshop when CS4
comes out. I figure CS4 is less than a year away. -
Hello, I am getting a Kern Protection failure error message when trying to start up my Olympus DSS Player dictation software. I have been using the software without issue for years until last month. I have uninstalled and reinstalled the software and don't recall installing any new software before the issue began.
Any help would be greatly appreciated, I will post the error message below. Thanks.
Process:
DSS Player [186]
Path:
/Applications/DSS Player/DSS Player.app/Contents/MacOS/DSS Player
Identifier:
com.olympus.DSSPlayerV7
Version:
7.4.0 (0.1)
Code Type:
X86 (Native)
Parent Process: launchd [98]
Date/Time:
2013-11-23 11:44:03.999 +1100
OS Version:
Mac OS X 10.6.8 (10K549)
Report Version: 6
Interval Since Last Report:
209192 sec
Crashes Since Last Report:
4
Per-App Interval Since Last Report: 273602 sec
Per-App Crashes Since Last Report: 4
Anonymous UUID:
EDE95D54-CA0A-4ABC-8241-167C27AAFC1D
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000007ff4005
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.OlympusSys.OlympusDSSFile
0x005e1fa3 DSSFile_GetDSSIndexMark + 1091
1 com.olympus.DSSPlayerV7
0x0004e5cf -[DSSFileManager setActive] + 61
2 com.olympus.DSSPlayerV7
0x0004a939 -[DSSFileManager setFileInfo:needMusicInfo:] + 698
3 com.olympus.DSSPlayerV7
0x000486f8 -[DSSFileManager initWithFilePath:needMusicInfo:] + 124
4 com.olympus.DSSPlayerV7
0x00009470 -[DSSMainWindowController createFileInfosNew:folderId:] + 742
5 com.olympus.DSSPlayerV7
0x0000ccd6 -[DSSMainWindowController updateFolderInfos:folderIds:] + 622
6 com.olympus.DSSPlayerV7
0x00020bdb -[DSSMainWindowController awakeFromNib] + 3665
7 com.apple.AppKit
0x0114e21c -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1646
8 com.apple.AppKit
0x0114c1a4 loadNib + 257
9 com.apple.AppKit
0x0114b7f7 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 831
10 com.apple.AppKit
0x0114b4ad +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 158
11 com.apple.AppKit
0x011dafcb -[NSWindowController loadWindow] + 223
12 com.apple.AppKit
0x01171f22 -[NSWindowController window] + 89
13 com.apple.AppKit
0x013d6dbc -[NSWindowController showWindow:] + 36
14 com.olympus.DSSPlayerV7
0x000035b4 -[DSSAppController applicationDidFinishLaunchingAfterShowSplashWindow] + 464
15 com.olympus.DSSPlayerV7
0x000065d0 -[DSSAppController completeCheckRemoteConnWhenAppLaunch] + 86
16 com.apple.Foundation
0x021b0738 __NSThreadPerformPerform + 705
17 com.apple.CoreFoundation
0x032bc42b __CFRunLoopDoSources0 + 1563
18 com.apple.CoreFoundation
0x032b9eef __CFRunLoopRun + 1071
19 com.apple.CoreFoundation
0x032b93c4 CFRunLoopRunSpecific + 452
20 com.apple.CoreFoundation
0x032b91f1 CFRunLoopRunInMode + 97
21 com.apple.HIToolbox
0x02537e04 RunCurrentEventLoopInMode + 392
22 com.apple.HIToolbox
0x02537af5 ReceiveNextEventCommon + 158
23 com.apple.HIToolbox
0x02537a3e BlockUntilNextEventMatchingListInMode + 81
24 com.apple.AppKit
0x0118e595 _DPSNextEvent + 847
25 com.apple.AppKit
0x0118ddd6 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
26 com.apple.AppKit
0x011501f3 -[NSApplication run] + 821
27 com.apple.AppKit
0x01148289 NSApplicationMain + 574
28 com.olympus.DSSPlayerV7
0x0000257a _start + 216
29 com.olympus.DSSPlayerV7
0x000024a1 start + 41
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib
0x00f44382 kevent + 10
1 libSystem.B.dylib
0x00f44a9c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib
0x00f43f59 _dispatch_queue_invoke + 163
3 libSystem.B.dylib
0x00f43cfe _dispatch_worker_thread2 + 240
4 libSystem.B.dylib
0x00f43781 _pthread_wqthread + 390
5 libSystem.B.dylib
0x00f435c6 start_wqthread + 30
Thread 2:
0 libSystem.B.dylib
0x00f43412 __workq_kernreturn + 10
1 libSystem.B.dylib
0x00f439a8 _pthread_wqthread + 941
2 libSystem.B.dylib
0x00f435c6 start_wqthread + 30
Thread 3:
0 libSystem.B.dylib
0x00f43412 __workq_kernreturn + 10
1 libSystem.B.dylib
0x00f439a8 _pthread_wqthread + 941
2 libSystem.B.dylib
0x00f435c6 start_wqthread + 30
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x070a5400 ebx: 0x070a5c00 ecx: 0x001b4955 edx: 0x00000024
edi: 0x07ff400e esi: 0x00000000 ebp: 0xbfffdbc8 esp: 0xbfffdb60
ss: 0x0000001f efl: 0x00010217 eip: 0x005e1fa3 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x07ff4005
Binary Images:
0x1000 - 0x118fec +com.olympus.DSSPlayerV7 7.4.0 (0.1) /Applications/DSS Player/DSS Player.app/Contents/MacOS/DSS Player
0x187000 - 0x187ff7 com.apple.Cocoa 6.6 (???) <5A785062-1ABB-2A54-BAAC-8FEF95275E05> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x18a000 - 0x484fef com.apple.QuickTime 7.6.6 (1800) <D3538A45-5F4B-262A-06AB-64C1EBAC4A33> /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
0x530000 - 0x5aafff com.apple.audio.CoreAudio 3.2.6 (3.2.6) <156A532C-0B60-55B0-EE27-D02B82AA6217> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x5dc000 - 0x5e5fff +com.OlympusSys.OlympusDSSFile 1.3 (1.01) /Library/Frameworks/OlympusDSSFile.framework/Versions/A/OlympusDSSFile
0x5ec000 - 0x5ecff7 com.apple.Carbon 150 (152) <2539A94A-34D9-45CB-8F3E-AD53149E0BD5> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x5ef000 - 0x5efff7 com.apple.CoreServices 44 (44) <51CFA89A-33DB-90ED-26A8-67D461718A4A> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x5f7000 - 0x85dff7 com.apple.security 6.1.2 (55002) <E88E133F-5FB3-446F-B753-2B8AD577B46A> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x93a000 - 0xa77fe7 com.apple.audio.toolbox.AudioToolbox 1.6.7 (1.6.7) <423BDE4D-5082-B6CA-BB2C-E22A037235A4> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0xae7000 - 0xae8ff7 com.apple.audio.units.AudioUnit 1.6.7 (1.6.7) <93EC71F1-4D4E-F456-8EFE-32E7EFD7A064> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0xaed000 - 0xb39fff +com.yourcompany.yourcocoaframework ??? (1.44) /Library/Frameworks/OlympusDeviceManager.framework/Versions/A/OlympusDeviceMana ger
0xbe1000 - 0xc3eff7 com.apple.framework.IOKit 2.0 (???) <3DABAB9C-4949-F441-B077-0498F8E47A35> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0xc5e000 - 0xda1fef com.apple.QTKit 7.7 (1800) <9DD27495-3020-0928-B3F2-D418C336E163> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0xe58000 - 0xec2fe7 libstdc++.6.dylib 7.9.0 (compatibility 7.0.0) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
0xf1d000 - 0x10c4ff7 libSystem.B.dylib 125.2.11 (compatibility 1.0.0) <2DCD13E3-1BD1-6F25-119A-3863A3848B90> /usr/lib/libSystem.B.dylib
0x1146000 - 0x1a29ff7 com.apple.AppKit 6.6.8 (1038.36) <A353465E-CFC9-CB75-949D-786F6F7732F6> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x1ec5000 - 0x1ff3fe7 com.apple.CoreData 102.1 (251) <87FE6861-F2D6-773D-ED45-345272E56463> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x2057000 - 0x2057ff7 com.apple.ApplicationServices 38 (38) <EAF1BC8C-4FD4-4300-B8F7-4B24E49125E2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x205f000 - 0x2139fff com.apple.DesktopServices 1.5.11 (1.5.11) <800F2040-9211-81A7-B438-7712BF51DEE3> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x2184000 - 0x23f5fef com.apple.Foundation 6.6.8 (751.63) <69B3441C-B196-F2AD-07F8-D8DD24E4CD8C> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x2503000 - 0x2827fef com.apple.HIToolbox 1.6.5 (???) <21164164-41CE-61DE-C567-32E89755CB34> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x2967000 - 0x2cd2ff7 com.apple.QuartzCore 1.6.3 (227.37) <E323A5CC-499E-CA9E-9BC3-537231449CAA> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x2da2000 - 0x2dacffb com.apple.speech.recognition.framework 3.11.1 (3.11.1) <7486003F-8FDB-BD6C-CB34-DE45315BD82C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x2db5000 - 0x2dfbff7 libauto.dylib ??? (???) <29422A70-87CF-10E2-CE59-FEE1234CFAAE> /usr/lib/libauto.dylib
0x2e08000 - 0x2f8afe7 libicucore.A.dylib 40.0.0 (compatibility 1.0.0) <60FF302E-5FAE-749B-BC70-0496DC2FBF2D> /usr/lib/libicucore.A.dylib
0x2fec000 - 0x30ecfe7 libxml2.2.dylib 10.3.0 (compatibility 10.0.0) <BE7FCD73-03B5-25A4-FCA4-D4980F1488D6> /usr/lib/libxml2.2.dylib
0x3110000 - 0x311efe7 libz.1.dylib 1.2.3 (compatibility 1.0.0) <33C1B260-ED05-945D-FC33-EF56EC791E2E> /usr/lib/libz.1.dylib
0x3123000 - 0x3167ff3 com.apple.coreui 2 (114) <2234855E-3BED-717F-0BFA-D1A289ECDBDA> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x3186000 - 0x318fff7 com.apple.DiskArbitration 2.3 (2.3) <6AA6DDF6-AFC3-BBDB-751A-64AE3580A49E> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x3199000 - 0x3199ff7 liblangid.dylib ??? (???) <FCC37057-CDD7-2AF1-21AF-52A06C4048FF> /usr/lib/liblangid.dylib
0x319d000 - 0x31afff7 com.apple.MultitouchSupport.framework 207.11 (207.11) <6FF4F2D6-B8CD-AE13-56CB-17437EE5B741> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/Multit ouchSupport
0x31bc000 - 0x3269fe7 libobjc.A.dylib 227.0.0 (compatibility 1.0.0) <9F8413A6-736D-37D9-8EB3-7986D4699957> /usr/lib/libobjc.A.dylib
0x327d000 - 0x33f8fe7 com.apple.CoreFoundation 6.6.6 (550.44) <F88C95CD-1264-782D-A1F5-204739847E93> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x34f0000 - 0x3cdf557 com.apple.CoreGraphics 1.545.0 (???) <1D9DC7A5-228B-42CB-7018-66F42C3A9BB3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x3da7000 - 0x3f6afeb com.apple.ImageIO.framework 3.0.6 (3.0.6) <AE641FAD-DF38-AE31-B45B-85AEE7AF3A45> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
0x3fc9000 - 0x402afe7 com.apple.CoreText 151.13 (???) <23F359DA-D845-5C50-4DF3-19E858CF2B2C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
0x4062000 - 0x40fdfe7 com.apple.ApplicationServices.ATS 275.19 (???) <2E83B3E9-AF39-36FC-5D05-CC1E952098AB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x4124000 - 0x41e0fff com.apple.ColorSync 4.6.8 (4.6.8) <920DD017-8B41-7334-E554-A85DB99EBD5A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
0x4217000 - 0x426aff7 com.apple.HIServices 1.8.3 (???) <1D3C4587-6318-C339-BD0F-1988F246BE2E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x4295000 - 0x42a6ff7 com.apple.LangAnalysis 1.6.6 (1.6.6) <3036AD83-4F1D-1028-54EE-54165E562650> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x42b3000 - 0x435bffb com.apple.QD 3.36 (???) <FA2785A4-BB69-DCB4-3BA3-7C89A82CAB41> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
0x4388000 - 0x439cffb com.apple.speech.synthesis.framework 3.10.35 (3.10.35) <9F5CE4F7-D05C-8C14-4B76-E43D07A8A680> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x43aa000 - 0x43befe7 libbsm.0.dylib ??? (???) <B328FA0A-899C-4FC4-F2AC-2FDC08819CD2> /usr/lib/libbsm.0.dylib
0x43c7000 - 0x43cafe7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
0x43cd000 - 0x43d9ff7 libkxld.dylib ??? (???) <9A441C48-2D18-E716-5F38-CBEAE6A0BB3E> /usr/lib/system/libkxld.dylib
0x43dd000 - 0x46fdff3 com.apple.CoreServices.CarbonCore 861.39 (861.39) <5C59805C-AF39-9010-B8B5-D673C9C38538> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x4773000 - 0x481ffe7 com.apple.CFNetwork 454.12.4 (454.12.4) <DEDCD006-389F-967F-3405-EDF541F406D7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x4884000 - 0x48c8fe7 com.apple.Metadata 10.6.3 (507.15) <74F05E64-2A68-BA10-CCD4-128D164E5A0F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x48ef000 - 0x49bafef com.apple.CoreServices.OSServices 359.2 (359.2) <7C16D9C8-6F41-5754-17F7-2659D9DD9579> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x4a19000 - 0x4a99feb com.apple.SearchKit 1.3.0 (1.3.0) <7AE32A31-2B8E-E271-C03A-7A0F7BAFC85C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x4acd000 - 0x4b00ff7 com.apple.AE 496.5 (496.5) <BF9673D5-2419-7120-26A3-83D264C75222> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x4b18000 - 0x4bb5fe3 com.apple.LaunchServices 362.3 (362.3) <15B47388-16C8-97DA-EEBB-1709E136169E> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x4bf4000 - 0x4c1affb com.apple.DictionaryServices 1.1.2 (1.1.2) <43E1D565-6E01-3681-F2E5-72AE4C3A097A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x4c30000 - 0x4c3dff7 com.apple.NetFS 3.2.2 (3.2.2) <DDC9C397-C35F-8D7A-BB24-3D1B42FA5FAB> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x4c46000 - 0x4cfffe7 libsqlite3.dylib 9.6.0 (compatibility 9.0.0) <52438E77-55D1-C231-1936-76F1369518E4> /usr/lib/libsqlite3.dylib
0x4d0d000 - 0x4d4aff7 com.apple.SystemConfiguration 1.10.8 (1.10.2) <50E4D49B-4F61-446F-1C21-1B2BA814713D> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x4d67000 - 0x4d8fff7 libxslt.1.dylib 3.24.0 (compatibility 3.0.0) <E761F29A-328B-29D9-3DF0-023F2C21E500> /usr/lib/libxslt.1.dylib
0x4d9a000 - 0x4d9aff7 com.apple.Accelerate 1.6 (Accelerate 1.6) <3891A689-4F38-FACD-38B2-4BF937DE30CF> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x4d9d000 - 0x4dedfe7 libTIFF.dylib ??? (???) <AB182CEC-188A-F2BC-21E1-0059FD3B2598> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x4df9000 - 0x4dfdff7 libGIF.dylib ??? (???) <2251F789-B187-0837-6E38-A0E5C7C4FA3C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x4e02000 - 0x4e20fe7 libPng.dylib ??? (???) <6C0B95D7-9634-E044-0B79-F1DD56961C33> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
0x4e29000 - 0x4e2bff7 libRadiance.dylib ??? (???) <090420B3-CB65-9F7B-5349-D42F2F9693B6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x4e2f000 - 0x4e53ff7 libJPEG.dylib ??? (???) <50E17B4D-63D6-24D3-702F-6A6E912A55EA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x4e5a000 - 0x4f3afe7 com.apple.vImage 4.1 (4.1) <D029C515-08E1-93A6-3705-DD062A3A672C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
0x4f48000 - 0x4f48ff7 com.apple.Accelerate.vecLib 3.6 (vecLib 3.6) <ABF97DA4-3BDF-6FFD-6239-B023CA1F7974> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
0x4f4b000 - 0x4f8dff7 libvDSP.dylib 268.0.1 (compatibility 1.0.0) <8A4721DE-25C4-C8AA-EA90-9DA7812E3EBA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x4f96000 - 0x5005ff7 libvMisc.dylib 268.0.1 (compatibility 1.0.0) <595A5539-9F54-63E6-7AAC-C04E1574B050> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x500e000 - 0x5424ff7 libBLAS.dylib 219.0.0 (compatibility 1.0.0) <9D89FCB3-24C9-8FCF-DB49-27B184AC3222> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x5466000 - 0x589bff7 libLAPACK.dylib 219.0.0 (compatibility 1.0.0) <4D2F47EF-BD32-1E3C-6A0A-438896ADE2BE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x5a21000 - 0x5b23fe7 libcrypto.0.9.8.dylib 0.9.8 (compatibility 0.9.8) <EB34F049-D9E1-BF19-CF03-B26A0352D40C> /usr/lib/libcrypto.0.9.8.dylib
0x5b77000 - 0x5b78ff7 com.apple.TrustEvaluationAgent 1.1 (1) <2D970A9B-77E8-EDC0-BEC6-7580D78B2843> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/Tru stEvaluationAgent
0x5b7c000 - 0x5c34feb libFontParser.dylib ??? (???) <D2D0C922-5ED1-3AE9-6F99-707C74DF3E62> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontParser.dylib
0x5cc4000 - 0x5cfeff7 libcups.2.dylib 2.8.0 (compatibility 2.0.0) <A6C207E3-7B42-926D-9C93-BE3F50B92496> /usr/lib/libcups.2.dylib
0x5d0b000 - 0x5d2bfe7 libresolv.9.dylib 41.1.0 (compatibility 1.0.0) <8C2B5FA8-2469-21C7-D297-F95A0FFE5F19> /usr/lib/libresolv.9.dylib
0x5d35000 - 0x5d35ff7 com.apple.vecLib 3.6 (vecLib 3.6) <FF4DC8B6-0AB0-DEE8-ADA8-7B57645A1F36> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x5d38000 - 0x5d42fe7 com.apple.audio.SoundManager 3.9.3 (3.9.3) <DE0E0EF6-8190-3F65-6BDD-5AC9D8A025D6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
0x5d4a000 - 0x5d9aff7 com.apple.framework.familycontrols 2.0.2 (2020) <C96C8A99-A40C-8B9C-1FBA-A0F46AC92F17> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyCon trols
0x5db2000 - 0x5e60ff3 com.apple.ink.framework 1.3.3 (107) <233A981E-A2F9-56FB-8BDE-C2DEC3F20784> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x5e8a000 - 0x5ea9ff7 com.apple.CoreVideo 1.6.2 (45.6) <EB53CAA4-5EE2-C356-A954-5775F7DDD493> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x5ec0000 - 0x5eceff7 com.apple.opengl 1.6.14 (1.6.14) <82622F67-E032-0BF6-A78D-50B346E8D0FD> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x5ed6000 - 0x5f07ff7 libGLImage.dylib ??? (???) <D18E2E76-DBF4-6930-039A-F66CA0D120B3> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
0x5f0f000 - 0x5f30fe7 com.apple.opencl 12.3.6 (12.3.6) <B4104B80-1CB3-191C-AFD3-697843C6BCFF> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x5f39000 - 0x5f3dff7 IOSurface ??? (???) <D849E1A5-6B0C-2A05-2765-850EC39BA2FF> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
0x5f45000 - 0x5f88ff7 libGLU.dylib ??? (???) <6CC3CE6A-7024-C685-EADA-7F9DC27128E2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x5f96000 - 0x5fa1ff7 libGL.dylib ??? (???) <3E34468F-E9A7-8EFB-FF66-5204BD5B4E21> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x5fb0000 - 0x60bcfe7 libGLProgrammability.dylib ??? (???) <6167CEB0-D8D6-C4D9-DD74-49755ADB540F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgramma bility.dylib
0x60db000 - 0x60deff7 libCoreVMClient.dylib ??? (???) <37F56237-4ABA-E5B5-968D-70FFE357E8E0> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClien t.dylib
0x60e3000 - 0x60e7ff7 libGFXShared.dylib ??? (???) <09540618-2ED1-72C4-61CB-938B35927568> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.d ylib
0x60ec000 - 0x616effb SecurityFoundation ??? (???) <A8D248DE-8670-970D-39E3-A9738CFDBEE1> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
0x61a5000 - 0x61aaff7 com.apple.OpenDirectory 10.6 (10.6) <C1B46982-7D3B-3CC4-3BC2-3E4B595F0231> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x61b2000 - 0x61b8fe7 com.apple.CommerceCore 1.0 (9.1) <521D067B-3BDA-D04E-E1FA-CFA526C87EB5> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/C ommerceCore.framework/Versions/A/CommerceCore
0x61bf000 - 0x61d7ff7 com.apple.CFOpenDirectory 10.6 (10.6) <F9AFC571-3539-6B46-ABF9-46DA2B608819> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
0x61e8000 - 0x6235feb com.apple.DirectoryService.PasswordServerFramework 6.1 (6.1) <136BFA48-D456-B677-3B5D-40A6946C3A09> /System/Library/PrivateFrameworks/PasswordServer.framework/Versions/A/PasswordS erver
0x6251000 - 0x6273fef com.apple.DirectoryService.Framework 3.6 (621.16) <5566E769-6459-78A7-DD2C-1D3068BD3932> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x627d000 - 0x628dff7 libsasl2.2.dylib 3.15.0 (compatibility 3.0.0) <E276514D-394B-2FDD-6264-07A444AA6A4E> /usr/lib/libsasl2.2.dylib
0x6294000 - 0x62d7ff7 com.apple.NavigationServices 3.5.4 (182) <8DC6FD4A-6C74-9C23-A4C3-715B44A8D28C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
0x6300000 - 0x6302ff7 com.apple.securityhi 4.0 (36638) <E7D83480-77BB-72F9-72F3-AEE198CE589F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x6307000 - 0x630ffeb +QualityPlay.dylib ??? (???) /Library/Application Support/OLYMPUS/DSSPlayer/lib/QualityPlay.dylib
0x632b000 - 0x6333feb +StandardPlay.dylib ??? (???) /Library/Application Support/OLYMPUS/DSSPlayer/lib/StandardPlay.dylib
0x635e000 - 0x6370fcf +LongPlay.dylib ??? (???) /Library/Application Support/OLYMPUS/DSSPlayer/lib/LongPlay.dylib
0x6375000 - 0x6388fdf +DSSAES.dylib ??? (???) /Library/Application Support/OLYMPUS/DSSPlayer/lib/DSSAES.dylib
0x638c000 - 0x6392fff com.apple.CommonPanels 1.2.4 (91) <CE92759E-865E-8A3B-1488-ECD497E4074D> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x639a000 - 0x639dffb com.apple.help 1.3.2 (41.1) <8AC20B01-4A3B-94BA-D8AF-E39034B97D8C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x63a2000 - 0x6406fff com.apple.htmlrendering 72 (1.1.4) <0D22B190-513B-7FF6-39FC-9D336285DE08> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
0x6428000 - 0x643dfff com.apple.ImageCapture 6.1 (6.1) <B909459A-EAC9-A7C8-F2A9-CD757CDB59E8> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x6453000 - 0x646ffe3 com.apple.openscripting 1.3.1 (???) <2A748037-D1C0-6D47-2C4A-0562AF799AC9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x647f000 - 0x64eafd7 +com.yourcompany.yourcocoaframework ??? (1.53) /Library/Frameworks/OlympusServiceProvider.framework/Versions/A/OlympusServiceP rovider
0x657c000 - 0x65b9ff7 com.apple.CoreMedia 0.484.60 (484.60) <8FAB137D-682C-6DEC-5A15-F0029A5B226F> /System/Library/PrivateFrameworks/CoreMedia.framework/Versions/A/CoreMedia
0x65d4000 - 0x6701ffb com.apple.MediaToolbox 0.484.60 (484.60) <A7FE2739-64A7-40EB-A6E7-69FBCE3C87D4> /System/Library/PrivateFrameworks/MediaToolbox.framework/Versions/A/MediaToolbo x
0x6765000 - 0x6c20ff7 com.apple.VideoToolbox 0.484.60 (484.60) <B53299EC-E30F-EC04-779D-29B7113CC14A> /System/Library/PrivateFrameworks/VideoToolbox.framework/Versions/A/VideoToolbo x
0x6cc9000 - 0x6d10ffb com.apple.CoreMediaIOServices 140.0 (1496) <DA152F1C-8EF4-4F5E-6D60-82B1DC72EF47> /System/Library/PrivateFrameworks/CoreMediaIOServices.framework/Versions/A/Core MediaIOServices
0x6d31000 - 0x6dacfff com.apple.AppleVAFramework 4.10.27 (4.10.27) <BFD2D1CA-535C-F16F-0EB5-04905ABD65CF> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA
0x6f9d000 - 0x6fa8ff7 libCSync.A.dylib 545.0.0 (compatibility 64.0.0) <287DECA3-7821-32B6-724D-AE03A9A350F9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x6ff2000 - 0x6ff5ff7 libCGXType.A.dylib 545.0.0 (compatibility 64.0.0) <4D766435-EB76-C384-0127-1D20ACD74076> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib
0x7c00000 - 0x7c3bffb libFontRegistry.dylib ??? (???) <19ED5DE0-D3AF-B229-9193-35D58FE377E5> /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Resources/libFontRegistry.dylib
0x7e04000 - 0x7e37fff libTrueTypeScaler.dylib ??? (???) <8ADB7D19-413E-4499-C874-13C383F97685> /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Resources/libTrueTypeScaler.dylib
0x7e43000 - 0x7e84ff7 libRIP.A.dylib 545.0.0 (compatibility 64.0.0) <80998F66-0AD7-AD12-B9AF-3E8D2CE6DE05> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x7fef000 - 0x7ff0ff7 +com.olympus.DSSPlayerV7.LeopardSupportForDSSPlayer 1.1 (1.0) <2AAA1454-CEBA-AA58-0DA1-D8E02A7EDBB4> /Applications/DSS Player/DSS Player.app/Contents/Resources/Leopard.bundle/Contents/MacOS/Leopard
0x1aed5000 - 0x1b3e7feb com.apple.RawCamera.bundle 3.14.0 (646) <27962422-EA30-43CF-2B3E-E662BB4C46C7> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
0x20000000 - 0x20098fe7 edu.mit.Kerberos 6.5.11 (6.5.11) <F36DB665-A88B-7F5B-6244-6A2E7FFFF668> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x64b00000 - 0x64b07ff3 com.apple.print.framework.Print 6.1 (237.1) <F5AAE53D-5530-9004-A9E3-2C1690C5328E> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <39AC3185-E633-68AA-7CD6-1230E7F1CEF4> /usr/lib/dyld
0xfa100000 - 0xfa192fe7 com.apple.print.framework.PrintCore 6.3 (312.7) <7410D1B2-655D-68DA-D4B9-2C65747B6817> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
0xffff0000 - 0xffff1fff libSystem.B.dylib ??? (???) <2DCD13E3-1BD1-6F25-119A-3863A3848B90> /usr/lib/libSystem.B.dylib
Model: MacBookPro7,1, BootROM MBP71.0039.B0B, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.62f7
Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.10.131.42.4)
Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: TOSHIBA MK2555GSXF, 232.89 GB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0x24600000 / 2
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0x26100000 / 2
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x06600000 / 4
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8213, 0x06610000 / 5
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x06500000 / 3
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0236, 0x06300000 / 2Hi,
Please review the link below, here is a useful article for you.
Tips and Tricks for Deploying the Application Catalog in System Center 2012 Configuration Manager
http://blogs.technet.com/b/configmgrteam/archive/2012/07/05/tips-and-tricks-for-deploying-the-application-catalog-in-system-center-2012-configuration-manager.aspx
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. -
Loss of Captions only in Olympus Camera photos
Loss of Captions only in Olympus Camera photos after migrating from Mac OS 10.5.11 and AP2 to Mac OS 10.6.4 and AP 3.03
I have had a problem where the captions written in Aperture 2 on a PowerMac G5 PPC running Mac 10.5.11 are no longer visible after migrating the photos to a new iMac running Mac OS 10.6.4 and AP 3.03. This occurs only in photos taken on Olympus Digital Cameras, no other brands are affected that I’ve seen (i.e. Nikon, Casio, Canon, Pentax). It occurs in both Preview and Aperture 3, replacing the previous Caption data with “OLYMPUS DIGITAL CAMERA”. However, if the same photo is returned unchanged to the older Mac, the correct captions are still visible. Also, Graphic Convertor and CS2 are able to read the correct captions in the IPTC data on the new system. Brand new photos imported directly into AP3 in the new system do not seem to be affected, although I have not used it enough to be sure that it will not happen in the future.
I believe that this is a problem with a change in how the new Mac OS reads IPTC data. I think the new system reads data from the EXIF (and XMP) fields in preference to the IPTC information, and if there is any information in those other fields, it will not read the IPTC caption. For most camera brands this is not much of a problem, because they do not automatically place any caption information in these fields. However Olympus seems to desire to place it’s name everywhere in the metadata, and their standard metadata include writing “OLYMPUS DIGITAL CAMERA” in the EXIF caption field (a very good reason never to use Olympus cameras in my opinion). If you ever have used Photoshop or Photoshop Elements (I have used fairly old versions only, this may have changed) to edit your photos in Aperture or previously in iPhoto and then migrated to Aperture, I noticed that the photos then have XMP metadata with “Olympic Digital Camera” written in many different fields, which also takes precedence over the IPTC caption in the Mac OS 10.6.x.
It is a very difficult problem, as once the AP2 library and referenced masters are brought over to the new system and upgraded to AP3, everything looks fine initially in the AP3 Library - even the captions are still there. However, pretty soon Aperture will start to realize that something has changed in the masters (even though nothing has really changed in the photo itself, just the way the system reads the IPTC metadata) and it will start to update the library, replacing your captions with “Olympus Digital Camera”. If you catch it early and try to stop the “updating” by using the “Write IPTC metadata to Masters” command, it will often not do anything, sometimes it will fix the problem for some photos and other times it will proceed to overwrite your previous captions with the Olympus caption - so don’t do that! I have tried all kinds of work arounds, and many of the more obvious options don’t help. I contacted Apple Support and Aperture, their response was that it was Olympus’ problem and a problem with the IPTC conventions. Olympus had no useful options either.
The best solution I have found so far is using ExifTool to remove the EXIF image description field, and the whole XMP box if the photo has been edited with Adobe products in the past. It’s time consuming process and a little intimidating for a terminal neophyte like me, but it’s easier than rewriting thousands of captions (and even if you do rewrite them in Aperture, Aperture will still change it back to “Olympus Digital Camera” once it decides that the master is somehow different than before). I will try to describe what has worked for me - some situations may be different. In particular, I suspect that writing the IPTC data to the masters upon exporting them for migrating to the new system makes this problem worse, as it causes Aperture 3 to realize that something has changed in the masters and make it update them; however often the masters without the IPTC will not be recognized for reconnecting. Consolidating the photos projects to be exported to the new system seems to help prevent problems within Aperture with the captions, but if you ever export the masters or use referenced masters, the problem will still be there until the EXIF caption is removed. I previously exported the masters (with the IPTC written them upon export in AP2) and then reconnected them in AP3, but this often seems to cause more problems with lost photos, time changes (mostly in the Adobe edited photos) and AP3 recognizing the master as “changed” and updating it, thereby losing the original captions.
Rule No. 1 - if at all possible, keep a copy of your original masters and Aperture 2 libraries as back ups (and it’s nice to be able to use them on your old system) - I’ve had to re-use them several times until I got things right. If your AP Libraries and masters are on a external HD, it may be best to make an exact clone of it (with the exact same name for the HD), so that you will not have to reconnect or relocate your masters.
You will probably want to see if you really have this problem before trying to fix it. Open the master taken with an Olympus camera that had a caption written to it in Aperture 2 in Preview and look at the caption information (command-I) under IPTC - if it says “Olympus Digital Camera” where you previously had something else, then it’s a problem. Under the TIFF (which is really from the EXIF data) box in Preview information, it will say the same thing under image description. With the same photo, if you import it into Aperture 3, it will also have “Olympus Digital Camera” as the IPTC caption. If it is already in Aperture 3 from a previous version, if you click on the photo for a full view, you may see the previous caption “update” to “Olympus Digital Camera”. Your actual master is okay (you can look at it in CS, Graphic Convertor, or an older Mac running 10.5. If you have never written anything in the IPTC caption, this problem is not visible, but you still have the EXIF Olympus caption waiting there to cause trouble in the future.
If you already have problems with changing captions on several photos in Aperture 3 Libraries, it is usually easier to just start over than to fix the photos one by one. Most fixes keep on reverting back until you get rid of the EXIF:ImageDesription box with “Olympus Digital Camera” in it. My process has been as follows:
Export the Aperture 2 Projects with consolidated masters to an external HD or your new computer.
2. Prior to opening an Aperture Library that you are migrating to MacOS 10.6 - Aperture 3, importing a project , or reconnecting to the masters from an imported Library or Project, use ExifTool to remove the EXIF image description in the masters. If you have used Photoshop or Adobe products which leave an XMP metadata field, it is probably better to remove this also at the same time.
To use ExifTool:
I will describe this in more detail for those of us (like myself) who know nothing about using terminal.
A: Download and install the free EXIF-tool. (Many, MANY thanks to Phil Harvey, I think that it’s thanks to people like him that the world progresses).
B: I found it helps to have just one folder where I run ExifTool on the same HD where I am planning to store my Aperture Libraries and-or referenced masters. Name it something like “EXIF-ProcessingFolder”, and then you can move the projects or the folders with your masters in and out of it without having to copy them, and you can always use the same script - which help prevent errors! Put the unopened projects or folders with the masters you want to remove the EXIF image description into this folder. Don’t forget to keep a back-up copy of your photos!
C: Open Terminal (under Utilities in Applications). You will see
“last login: xxxx on ttys000
Network name: ~username$” and an open box (which becomes solid grey when active in terminal)
Note that your mouse will not work in Terminal, you must use the keyboard and arrow keys to move around the text (copying and pasting does work).
D: First we will “change directory” to get to the place we want to work on:
-in the open box at the end of the last line in the terminal, type “ cd “ (space-cd-space, no quotation marks) - the space after cd is important - and then drag and drop the icon for the “EXIFProcessingFolder” that you made in the previous step on your HD to the open box after “ cd “. Before you hit return, copy the file path (it will look something like ” /Volumes/NameofYourHD\ Folder/ Subfolder\EXIF- ProcessingFolder”), and copy it into the PASTEFilePathHERE part of the command line below. (I keep several copies of the command line on a document to paste and copy from). THEN hit return, and terminal will tell you where it is at like this: “NetworkName:EXIF-ProcessingFolder UserName$”.
E: I like to check where I am at this point, so I type in “ls” (I remember it as “let’s see”) and hit the “return” key to see the contents of the folder where the terminal is at. It should return a list of the different projects, folders or files in the EXIF-ProcessingFolder. That’s good. (If it doesn’t do this, start over with the “ cd “ command to change directories until you’re in the right place).
F: Now copy the entire command line including the substituted “PASTEFilePathHere” from below and paste it into the open box in the terminal and hit return. It will start processing your photos. You can watch its progress if you want by looking at the Date Modified of the Subfolders (but not files). When it is all finished, there will be a message in the terminal stating how many files were processed, how many were changed and how many unchanged. It may take a while; often I will receive some error messages in the terminal while it is working, mostly about duplicate rotation information - I just ignore it.
G: When it is finished, type “exit” in terminal, it will reply with “logout [Process completed]”, and then you can quit Terminal. I have not found out the way to stop the process if I need to while it is running, so if I need to I quit terminal, and that stops the process.
Here are the command lines to use with ExifTool
(copied and modified from Casamagnolia-wSzxs8’s post)
To delete the EXIF:ImageDescription of photos in a folder without subfolders: (you do not have to paste the folder location with this command, but the terminal must be in the correct directory)
exiftool -P -overwriteoriginal_inplace -m -EXIF:ImageDescription= *.jpg
To delete the EXIF:ImageDescription of Aperture Projects, Aperture Libraries or photos in a folder with subfolders (i.e. if your folders are separated by dates) - (it’s all one line without a return, you need to paste the File Path from step D above over the “PASTEFilePathHere” and then copy the whole thing and paste it into the terminal; mind the spaces; if you include the return at the end it will run as soon as you paste it into the terminal.):
exiftool -P -r -overwriteoriginal_inplace -m -EXIF:ImageDescription= PASTEFilePathHERE
(an example of final script for recursive folders): exiftool -P -r -overwriteoriginal_inplace -m -EXIF:ImageDescription= /Users/userName/Desktop/EXIF-ProcessingFolder
please note that this script will change files in the file path pasted into the command, even if you are not currently in that directory from step D above.
To delete the EXIF:ImageDescription AND the entire XMP metadata fields (for files previously processed with Photoshop, which now have the Olympus Digital Camera in several XMP fields) of photos in a folder with subfolders (i.e. if your folders are separated by dates) - (it’s all one line without a return, you need to paste the File Path from step D above over the “PASTEFilePathHere” and then copy the whole thing and paste it into the terminal; mind the spaces; if you include the return at the end it will run as soon as you paste it into the terminal.):
exiftool -P -r -overwriteoriginal_inplace -m -EXIF:ImageDescription= -XMP= PASTEFilePathHERE
(my limited explanation of the commands are -P saves the date-time of the original format; -r processes the sub-folders recursively; -m decreases the number of error messages; -overwriteoriginal_inplace copies the original file and pastes it onto the changes; -EXIF:ImageDescription removes the EXIF:ImageDescription metadata box; -XMP removes the entire XMP metadata file (I couldn’t figure out how to get rid of just the fields with Olympus Digital Camera written in them, and I don’t see any loss of information that I use, and as an added benefit, I suspect that it helps prevent incongruencies in reading the time & time zone between Aperture and PhotoShop).
After processing the files with the ExifTool, I then move the projects or folders of referenced masters back to where I intend to keep them permanently (so that I don’t have to relocate them in Aperture later on after reconnecting with them).
Import the project or upgrade the library in the new system with Aperture 3. If the Aperture Library is already connected to the referenced masters, do not to open it before you have removed the EXIF:ImageDescription from the masters, as it will start to change the caption information in Aperture, and then you will have to manually change the captions back in Aperture.
If the library is using referenced masters and these are in a new place from the last time the library was open, reconnect to the masters by going to Located Reference Files under the File menu, and navigate to where the masters are and reconnect all. Sometimes some photos will not reconnect, in which case you’ll have to re-import them. You will not need to reconnect the photos if you have already been using the Aperture Library and the photos are already connected, but it would be good to make sure they are all still connected.
Check to see that the problem is fixed - open some of the previously affected masters in Preview and you should see the correct Captions now. If you had already been using the Aperture Library and the caption still shows “Olympus Digital Camera”, check the master in Preview to make sure it’s fixed, and then change the caption in Aperture. Check your library for captions with “Olympus Digital Camera” (in the search box - Add Rule - IPTC - Caption includes...); if you have used Photoshop in the past to edit your photos and didn’t remove the XMP boxes, check them also (by searching in EXIF:Software - Adobe in the search box) for “Olympus Digital Camera” captions and check the time of the photos (they may be 1 or more hours off). Be sure to click on a photo to make sure it won’t “update” and change the caption again.
I hope this helps other people with the same problem. It took me ages to get it figured out and it is a very tedious and time consuming process. I wish Apple would consider how this could all be avoided. Please feel free to add suggestions or comments.Loss of Captions only in Olympus Camera photos after migrating from Mac OS 10.5.11 and AP2 to Mac OS 10.6.4 and AP 3.03
I have had a problem where the captions written in Aperture 2 on a PowerMac G5 PPC running Mac 10.5.11 are no longer visible after migrating the photos to a new iMac running Mac OS 10.6.4 and AP 3.03. This occurs only in photos taken on Olympus Digital Cameras, no other brands are affected that I’ve seen (i.e. Nikon, Casio, Canon, Pentax). It occurs in both Preview and Aperture 3, replacing the previous Caption data with “OLYMPUS DIGITAL CAMERA”. However, if the same photo is returned unchanged to the older Mac, the correct captions are still visible. Also, Graphic Convertor and CS2 are able to read the correct captions in the IPTC data on the new system. Brand new photos imported directly into AP3 in the new system do not seem to be affected, although I have not used it enough to be sure that it will not happen in the future.
I believe that this is a problem with a change in how the new Mac OS reads IPTC data. I think the new system reads data from the EXIF (and XMP) fields in preference to the IPTC information, and if there is any information in those other fields, it will not read the IPTC caption. For most camera brands this is not much of a problem, because they do not automatically place any caption information in these fields. However Olympus seems to desire to place it’s name everywhere in the metadata, and their standard metadata include writing “OLYMPUS DIGITAL CAMERA” in the EXIF caption field (a very good reason never to use Olympus cameras in my opinion). If you ever have used Photoshop or Photoshop Elements (I have used fairly old versions only, this may have changed) to edit your photos in Aperture or previously in iPhoto and then migrated to Aperture, I noticed that the photos then have XMP metadata with “Olympic Digital Camera” written in many different fields, which also takes precedence over the IPTC caption in the Mac OS 10.6.x.
It is a very difficult problem, as once the AP2 library and referenced masters are brought over to the new system and upgraded to AP3, everything looks fine initially in the AP3 Library - even the captions are still there. However, pretty soon Aperture will start to realize that something has changed in the masters (even though nothing has really changed in the photo itself, just the way the system reads the IPTC metadata) and it will start to update the library, replacing your captions with “Olympus Digital Camera”. If you catch it early and try to stop the “updating” by using the “Write IPTC metadata to Masters” command, it will often not do anything, sometimes it will fix the problem for some photos and other times it will proceed to overwrite your previous captions with the Olympus caption - so don’t do that! I have tried all kinds of work arounds, and many of the more obvious options don’t help. I contacted Apple Support and Aperture, their response was that it was Olympus’ problem and a problem with the IPTC conventions. Olympus had no useful options either.
The best solution I have found so far is using ExifTool to remove the EXIF image description field, and the whole XMP box if the photo has been edited with Adobe products in the past. It’s time consuming process and a little intimidating for a terminal neophyte like me, but it’s easier than rewriting thousands of captions (and even if you do rewrite them in Aperture, Aperture will still change it back to “Olympus Digital Camera” once it decides that the master is somehow different than before). I will try to describe what has worked for me - some situations may be different. In particular, I suspect that writing the IPTC data to the masters upon exporting them for migrating to the new system makes this problem worse, as it causes Aperture 3 to realize that something has changed in the masters and make it update them; however often the masters without the IPTC will not be recognized for reconnecting. Consolidating the photos projects to be exported to the new system seems to help prevent problems within Aperture with the captions, but if you ever export the masters or use referenced masters, the problem will still be there until the EXIF caption is removed. I previously exported the masters (with the IPTC written them upon export in AP2) and then reconnected them in AP3, but this often seems to cause more problems with lost photos, time changes (mostly in the Adobe edited photos) and AP3 recognizing the master as “changed” and updating it, thereby losing the original captions.
Rule No. 1 - if at all possible, keep a copy of your original masters and Aperture 2 libraries as back ups (and it’s nice to be able to use them on your old system) - I’ve had to re-use them several times until I got things right. If your AP Libraries and masters are on a external HD, it may be best to make an exact clone of it (with the exact same name for the HD), so that you will not have to reconnect or relocate your masters.
You will probably want to see if you really have this problem before trying to fix it. Open the master taken with an Olympus camera that had a caption written to it in Aperture 2 in Preview and look at the caption information (command-I) under IPTC - if it says “Olympus Digital Camera” where you previously had something else, then it’s a problem. Under the TIFF (which is really from the EXIF data) box in Preview information, it will say the same thing under image description. With the same photo, if you import it into Aperture 3, it will also have “Olympus Digital Camera” as the IPTC caption. If it is already in Aperture 3 from a previous version, if you click on the photo for a full view, you may see the previous caption “update” to “Olympus Digital Camera”. Your actual master is okay (you can look at it in CS, Graphic Convertor, or an older Mac running 10.5. If you have never written anything in the IPTC caption, this problem is not visible, but you still have the EXIF Olympus caption waiting there to cause trouble in the future.
If you already have problems with changing captions on several photos in Aperture 3 Libraries, it is usually easier to just start over than to fix the photos one by one. Most fixes keep on reverting back until you get rid of the EXIF:ImageDesription box with “Olympus Digital Camera” in it. My process has been as follows:
Export the Aperture 2 Projects with consolidated masters to an external HD or your new computer.
2. Prior to opening an Aperture Library that you are migrating to MacOS 10.6 - Aperture 3, importing a project , or reconnecting to the masters from an imported Library or Project, use ExifTool to remove the EXIF image description in the masters. If you have used Photoshop or Adobe products which leave an XMP metadata field, it is probably better to remove this also at the same time.
To use ExifTool:
I will describe this in more detail for those of us (like myself) who know nothing about using terminal.
A: Download and install the free EXIF-tool. (Many, MANY thanks to Phil Harvey, I think that it’s thanks to people like him that the world progresses).
B: I found it helps to have just one folder where I run ExifTool on the same HD where I am planning to store my Aperture Libraries and-or referenced masters. Name it something like “EXIF-ProcessingFolder”, and then you can move the projects or the folders with your masters in and out of it without having to copy them, and you can always use the same script - which help prevent errors! Put the unopened projects or folders with the masters you want to remove the EXIF image description into this folder. Don’t forget to keep a back-up copy of your photos!
C: Open Terminal (under Utilities in Applications). You will see
“last login: xxxx on ttys000
Network name: ~username$” and an open box (which becomes solid grey when active in terminal)
Note that your mouse will not work in Terminal, you must use the keyboard and arrow keys to move around the text (copying and pasting does work).
D: First we will “change directory” to get to the place we want to work on:
-in the open box at the end of the last line in the terminal, type “ cd “ (space-cd-space, no quotation marks) - the space after cd is important - and then drag and drop the icon for the “EXIFProcessingFolder” that you made in the previous step on your HD to the open box after “ cd “. Before you hit return, copy the file path (it will look something like ” /Volumes/NameofYourHD\ Folder/ Subfolder\EXIF- ProcessingFolder”), and copy it into the PASTEFilePathHERE part of the command line below. (I keep several copies of the command line on a document to paste and copy from). THEN hit return, and terminal will tell you where it is at like this: “NetworkName:EXIF-ProcessingFolder UserName$”.
E: I like to check where I am at this point, so I type in “ls” (I remember it as “let’s see”) and hit the “return” key to see the contents of the folder where the terminal is at. It should return a list of the different projects, folders or files in the EXIF-ProcessingFolder. That’s good. (If it doesn’t do this, start over with the “ cd “ command to change directories until you’re in the right place).
F: Now copy the entire command line including the substituted “PASTEFilePathHere” from below and paste it into the open box in the terminal and hit return. It will start processing your photos. You can watch its progress if you want by looking at the Date Modified of the Subfolders (but not files). When it is all finished, there will be a message in the terminal stating how many files were processed, how many were changed and how many unchanged. It may take a while; often I will receive some error messages in the terminal while it is working, mostly about duplicate rotation information - I just ignore it.
G: When it is finished, type “exit” in terminal, it will reply with “logout [Process completed]”, and then you can quit Terminal. I have not found out the way to stop the process if I need to while it is running, so if I need to I quit terminal, and that stops the process.
Here are the command lines to use with ExifTool
(copied and modified from Casamagnolia-wSzxs8’s post)
To delete the EXIF:ImageDescription of photos in a folder without subfolders: (you do not have to paste the folder location with this command, but the terminal must be in the correct directory)
exiftool -P -overwriteoriginal_inplace -m -EXIF:ImageDescription= *.jpg
To delete the EXIF:ImageDescription of Aperture Projects, Aperture Libraries or photos in a folder with subfolders (i.e. if your folders are separated by dates) - (it’s all one line without a return, you need to paste the File Path from step D above over the “PASTEFilePathHere” and then copy the whole thing and paste it into the terminal; mind the spaces; if you include the return at the end it will run as soon as you paste it into the terminal.):
exiftool -P -r -overwriteoriginal_inplace -m -EXIF:ImageDescription= PASTEFilePathHERE
(an example of final script for recursive folders): exiftool -P -r -overwriteoriginal_inplace -m -EXIF:ImageDescription= /Users/userName/Desktop/EXIF-ProcessingFolder
please note that this script will change files in the file path pasted into the command, even if you are not currently in that directory from step D above.
To delete the EXIF:ImageDescription AND the entire XMP metadata fields (for files previously processed with Photoshop, which now have the Olympus Digital Camera in several XMP fields) of photos in a folder with subfolders (i.e. if your folders are separated by dates) - (it’s all one line without a return, you need to paste the File Path from step D above over the “PASTEFilePathHere” and then copy the whole thing and paste it into the terminal; mind the spaces; if you include the return at the end it will run as soon as you paste it into the terminal.):
exiftool -P -r -overwriteoriginal_inplace -m -EXIF:ImageDescription= -XMP= PASTEFilePathHERE
(my limited explanation of the commands are -P saves the date-time of the original format; -r processes the sub-folders recursively; -m decreases the number of error messages; -overwriteoriginal_inplace copies the original file and pastes it onto the changes; -EXIF:ImageDescription removes the EXIF:ImageDescription metadata box; -XMP removes the entire XMP metadata file (I couldn’t figure out how to get rid of just the fields with Olympus Digital Camera written in them, and I don’t see any loss of information that I use, and as an added benefit, I suspect that it helps prevent incongruencies in reading the time & time zone between Aperture and PhotoShop).
After processing the files with the ExifTool, I then move the projects or folders of referenced masters back to where I intend to keep them permanently (so that I don’t have to relocate them in Aperture later on after reconnecting with them).
Import the project or upgrade the library in the new system with Aperture 3. If the Aperture Library is already connected to the referenced masters, do not to open it before you have removed the EXIF:ImageDescription from the masters, as it will start to change the caption information in Aperture, and then you will have to manually change the captions back in Aperture.
If the library is using referenced masters and these are in a new place from the last time the library was open, reconnect to the masters by going to Located Reference Files under the File menu, and navigate to where the masters are and reconnect all. Sometimes some photos will not reconnect, in which case you’ll have to re-import them. You will not need to reconnect the photos if you have already been using the Aperture Library and the photos are already connected, but it would be good to make sure they are all still connected.
Check to see that the problem is fixed - open some of the previously affected masters in Preview and you should see the correct Captions now. If you had already been using the Aperture Library and the caption still shows “Olympus Digital Camera”, check the master in Preview to make sure it’s fixed, and then change the caption in Aperture. Check your library for captions with “Olympus Digital Camera” (in the search box - Add Rule - IPTC - Caption includes...); if you have used Photoshop in the past to edit your photos and didn’t remove the XMP boxes, check them also (by searching in EXIF:Software - Adobe in the search box) for “Olympus Digital Camera” captions and check the time of the photos (they may be 1 or more hours off). Be sure to click on a photo to make sure it won’t “update” and change the caption again.
I hope this helps other people with the same problem. It took me ages to get it figured out and it is a very tedious and time consuming process. I wish Apple would consider how this could all be avoided. Please feel free to add suggestions or comments.
Maybe you are looking for
-
How can I include the data from a field in the subject of the notification email?
Instead of having a static subject line for each form response, I would like to have something like: Form Response Received from <<Name>> That way, each email would have a unique subject line and make it easier to use conversation view in my email. T
-
Specs: iMac 10.8.5 3,4 GHz Intel Core i7 32 GB 1600 MHz DDR3 Can't read or write some files, internet is failing, youtube won't load, security software I tried to install was in Slovenian, not dutch or english like in my systempreferences settings, p
-
Olá Pessoal, Gostaria de saber como estão focadas as abordagens aos clientes no que diz respeito a SOA, desde o final de 2006 que de uma forma ou de outra estou envolvido com o assunto, tive oportunidades de vivenciar diferentes abordagens aos client
-
I HP Computer was stolen. Can i trace it from Windows Licence Key
My Laptop was stolen. However I have installed Windows Licence key on it. Is there a way to track the computer by the licence key
-
Vendor+sub contract material tracking
Dear all Please add your inputs for below requirements The users raising the PO no: 1 for some vendors, then they will despatch the ROH materials to another vendor. Then 2nd vendor will finish the materials and return back to the company. (This is 2