Apple & Olympus E-M5 DNGs

I've asked this on other forums without luck. Has anyone been able to use Adobe DNG Converter 6.7 to create DNGs from their Olympus EM-5 that work on Mac OS 10.7? For some reason, DNGs created from the sample ORFs on dpreview work just fine, but it doesn't recognize DNGs created from the ORFs from my camera.
—Andreas

This is largely OBE given Apple's recent raw update v3.13.
Apple did not support the raw files from my Olympus E-3 and Nikon D700 when I first got them. However, I was able to run the raw files through Adobe DNG Converter, import them into Aperture, and go about my business. No such luck with my Olympus E-M5—Aperture said that the DNGs were an unsupported file type.
Turns out the Adobe DNG Converter generally creates linear DNGs from m4/3 raw files, which Aperture does not support.
—Andreas

Similar Messages

Apple's support of DNG format is fallacious

on the Aperture brag page http://www.apple.com/aperture/ it purports "It also supports the Adobe DNG format."
I went to Bridge/ACR, grabbed five tweaked nikon NEFS and saved them as DNG files.
I imported this new folder of these five tweaked DNG files into Aperture. It did open the DNG files, but none of the adjustments to the image where evident and the display was the unaltered RAW file.
Sorry Appleture, that does not constitute SUPPORT of the DNG format. DNG is not just another RAW format, it is a RAW format with the adjustments included.
This is the last straw for me. Time to cut my losses.
I am going to eBay my Academic copy of Aperture for $200. I am a huge fan of Apple products, but not Aperture. IF this was an intro price of $49 then I would not complain.
This is nothing more than a improvement to iPhoto, but not enough to be called "iPhoto Pro".

I absolutely agree, never did argue the point that Aperture did not pick up the DNG info. Just said that Bridge embeds info into the DNG. I also agree that this is a very large sticking point I have with Aperture. I just hope they offer the option of embedding informaition into the exported files as well as the ability to change the name of the file after importing. I understand their desire not to touch the files, but given that I would bet 99.9% of photographers would want to edit down first and then change the names on the keepers I think the developers need to change their paradigm on not touching the original files, after all, that was the idea behind DNG.
Imagine 2 workflows.
The current Aperture:
Open Aperture
Import 500 files
Cull out 200 files.
Keep 300 files
Don't bother correcting because of the need to export and all the metadata will be lost.
Export the keepers.
Delete the remaining 300 files in Aperture
Open Bridge
Open the just exported files.
Wait for them to load.
Rename the files to what you want because Aperture forces a space in the name and you do not want that space.
Enter all the file shoot info so if you export from Aperture, the metadata info that was imported within Aperture stays with the file and only that info.
Close Bridge
Reimport 300 renamed files back into Aperture
Done, I think.....
A new Aperture (Hopefully)
Open Aperture
Import 500 Files color correcting on the fly to see if they are keepers.
Cull 200 Files
Rename the remaining 300 files.
Enter all file shoot info.
Done
The new Aperture now writes all the info back to the original file including filename, metadata etc. Everytime you export or open in Photoshop, Aperture passes the filename and metadata info along. Life is good.
Granted they currently do not want to write into the file, but most of us would prefer it so when we send something to a client we do not have to keep reentering it. Furthermore, all of us would be doing it anyway, just in a different app., so whats the difference? I am very very hopeful they will correct this quickly in a future version, if not, it is a deal breaker for me, not to mention the other deal breakers it currently has.

Odd Maze Pattern with Olympus E-P1 & DNG Converter

Hello. I wanted to report an odd maze pattern when I convert a raw file from the Olympus E-P1. It seems to happen when using wide angle lenses (Zeiss 21/4.5 C Biogon and Zeiss 25/2.8 Biogon. The maze pattern is very prominent in the right corners of the image attached, where some softness is exhibited by the lens. Anyone else experiencing this? I do not get these patterns when converting with Olympus Studio or CaptureOne. -Norm

Hello Eric,
Many thanks for your reply. I sent two RW2 files; 295 made with the
Voigtlander Super Wide Heliar 15mm II at f/11, and file 299 with the
Leica Summicron-C 40 mm at f/8.
The maze artifacts are most visible in the top righthand corner. The
longer the focal point of the lens the less visible seem the artifacts.
Although I have seen posts on Flickr that the artifacts can change
with the same focal point lenses of different brands. A 35mm Zeiss
showed maze artifacts while a 35 Leitz did not.
I had some more interesting pictures with nice blue skies but these
had already been converted to DNG (still showing strong maze artifacts).
If I can supply any more files or information please do not hesitate
to ask.
Best regards,
Herb
Op 1 nov 2009, om 03:01 heeft MadManChan2000 het volgende geschreven:
Herb 19, can you please send me sample raw files (.RW2 files) taken
with these lenses that show the problem? You can use YouSendIt.com
with a target email address of mailto:[email protected]
>
Thanks,
Eric
>

Did Apple remove support for DNG files generated out of Capture One?

I use Capture One to convert my Leica Dlux-4 RAW files into DNG format and then use Aperture2.1.4 as my photo processing tool.
After I ran the latest OS update - Aperture gives a "Unsupported file format" message for all the DNG files.
Is it possible that Apple removes support for photo formats in the OS updates?
Anyone encountered the same issue and found a solution?
Thx

Go in the adjustment tab, and the first thing you'll see under the histogram is "Raw fine tuning". By default, "2.0" is selected. When importing DNG, you can switch it to "2.0 DNG" this is used to read DNGs from cameras Aperture doesn't support.
Maybe the update made it go back to its default "2.0" while before you where on "2.0 DNG". If I'm right, setting it to "2.0 DNG" will fix the problem.
P.S. sorry if I said "raw precision" instead of "Raw fine tuning" in the first place. My Aperture is in French and the name in French is "Réglage de précision raw" and I did a bad translation.
Message was edited by: Manusnake

Aperture 3 will not read LX3 .dng files

I was a Lightroom user for the past several years, but have decided to give Aperture a try. I converted files from my Panasonic Lumix LX-3, Canon 5D Mark II, and Canon s90IS to .dng when they were imported into Lightroom. I no longer have the original RAW files.
I have imported these .dng files into Aperture 3. The two sets of Canon files import properly and our easily edited. The .dng files from the Panasonic Lumix LX3 do not import properly. I get the "unsupported image format" message on the thumbnail.
I have installed the latest Apple update that allows for support of the LX3.
This has happened on both my Mac Pro and Macbook Pro.
Is anyone else experiencing a similar issue?
Thanks,
Fred
Message was edited by: Fred Campagna

Hi Fred. Saw your post about this on dpreview, too. I'll repost my response here for other Apple folk.
I'm seeing this with DNGs from my G1, too. The problem seems to be that Aperture 3 lacks support for lens corrections in DNG.
It is probably not a problem with Linear DNGs -- though you'd have to check yours. Adobe forced Linear DNGs on G1 and LX3 users for only one version of DNG converter (5.4, if I remember right). After that, they figured out how to do lens correction inside regular raw DNGs -- the kind that Aperture supports.
Except that the lens correction in those DNGs seems to confuse Aperture 3. It's odd because for the G1 and LX-3, Aperture supports those same corrections in the native RW2 format. Let's hope it's a bug that the same corrections don't work in DNG.
In the meantime, there are a couple of options:
1. Wait for RW2 support. For the GF1, this is your best choice. And save those RW2 files! Extract your original RW2 files from the DNGs or pull them from a backup (you did embed the the RW2, right?). If you've shot with Panasonic micro 4/3 lenses, this is your best option.
2. If your DNGs were shot with legacy lenses, there is a good work-around. Only native Panasonic (and maybe Olympus) micro 4/3 lenses add the lens metadata. If you don't have that, the only thing keeping Aperture from recognizing your photos is the camera model name embedded in the DNGs. You can use something like exiftool to change it to one that doesn't do lens correction. Here's what I use to get my G1's legacy lens DNGs to work in Aperture 3. (This is not terribly dangerous, as exiftool can just as easily undo this change.)
exiftool -Model=DMC-L10 blah.dng
3. If your DNGs do have lens correction (as they must with the LX3) you could use a tool like DNGSanitize http://punainenkala.livejournal.com/588.html, which purports to strip the lens correction from the DNGs. This is a last-resort sort of thing to do, you will lose that lens correction data. You would probably also have to change the camera model name, as in option 2 (try DMC-FZ50 for the LX3). Keep backups. And, really, don't do this -- wait until the next release of Aperture when we'll find out if Apple intends to fix DNG support.
Whatever you do, test this with your DNGs -- especially if you're trying option 2 or (especially) 3. Just because option 2 works for me, that doesn't mean it will for you. And I've not had to try option 3. And pray you don't have linear DNGs, as only Adobe can help you then.
I can't believe that Apple would mess up DNG support this badly on purpose. In the meantime, please file a bug report to let Apple know that losing DNG support for these cameras is a big deal. You can do this from inside Aperture itself. Choose Aperture > Provide Aperture Feedback from the menu.
Here are the gory details, with links to helpful resources -- http://elstudio.us/notes-on-aperture-3-and-panasonic-gf1-rw2-and
Good luck! And let us know how it works out.

DNG files showing no thumbnails mac osx 10.8.2

when i convert raw photos from my olympus omd em5 into DNG's and export them to my external hard drive , i do not get any thumbnail previews , they can only be seen if i view the files through lightroom4 import , if however i export in other formats such as jpeg ,tiff etc.. i get a preview thumbnail . Iam using latest imac and running osx 10.8.2 , does anyone have a fix for this , many thanks in advance , as i really like the idea of DNG, but would love to have a thumbnail preview, if anyone has a soloution i would be most grateful

Yup, as I said, luckily there's no problem for me with my NEFs either. And from memory (my iMac's in having its hard drive replaced so I can't check), I think it could read my old Fuji X100 RAFs without any issues too.
The point is that the Apple raw engine can read some but not all DNG files.
According to Apple, it's "most" if the camera produces native DNGs (which are as rare as rocking horse poop) or it can read some non-native DNG raw conversions, but for some others, only if you modify the DNG conversion by unchecking "Convert to Linear Image".
It may turn out that some DNG conversions can't be read by the Apple raw engine at all, or maybe are readable but Finder can't extract the JPEG for a thumbnail. In either case you'll have to stick to using Bridge or Lightroom or some other browser/DAM software that can interpret DNGs if you can't see them in the Finder & want to.
By the way, because it uses the Apple raw engine, shonky DNGs are blacked out in Aperture too (along with, I presume, iPhoto).

Olympus OM-D E-M5 and Ligthroom 3?

Sorry if this is a dumb newbie question but I've been searching these boards and the web for 30 minutes without a definitive answer so will finally just ask.
I'm about to get an Olympus OM-D E-M5, but I have Lightroom 3. Is this camera supported in LR 3? Will it ever be? Do I need to download a plug-in?
I'm still running XP so can't upgrade to LR 4 and don't want a new computer because I'm getting a new camera.
Thanks.

Guys, didn't mean to start an argument, but at least I know the answer to my question wasn't necessarily straightforward!
The transfer from Olympus RAW to DNG (or TIFF should I chose) will be a workable solution until I eventually get a new computer, and perhaps beyond if I'm pleased with that workflow.
That said I've spoken with four friends who use LR. Three of the four can't upgrade to LR 4 due to the XP issue, so one is left wondering if this was a good Adobe decision? One can imagine all kinds of reasons why they made this call, but it is obvious (to me) that leaves a large segment of their users unhappily SOL.
Anyway, glad to hear there is an OM-D in my near future!
Thanks much.

Why cant i see previews of my DNG in finder (on Mac), I can see previews of my original raw camera files but not when I use lightroom to convert to DNG.

s

I am guessing that Apple is responsible for DNG decoding, now, rather than Adobe, although Adobe should still be responsible for keeping their website up-to-date, and not have dead-end pages without any explanation.
From what I remember, there were some cameras with lens corrections built-in that Apple refuses to show DNG previews of—the DNG Version was too new, but it wouldn’t hurt to check and see if there is a Apple Camera update in case they have fixed this.

DNG files labeled as Unsupported Image Format

I have used the Adobe DNG Converter and LIghtroom 3 to convert some raw image files from a Fujifilm S100fs camera, and then tried to import them into Aperture 3. In all cases, DNG files from this particular camera are labeled Unsupported Image Format, while DNG files converted from other unsupported cameras have been imported successfully into Aperture.
I think this is clearly a defect in Aperture that should be fixed, and I would like to know how a user is informed by Apple that a behavior has been identified as a defect and put on a list of problems to be fixed.

I can now add more details to my problem with Apple's treatment of DNG files originating from .RAF files created by the Fujifilm S100fs camera.
I took this issue to the Adobe DNG Converter forum, to investigate whether the DNG Converter was creating a Linear DNG file from these originals. I had read on Apple forums that the MAC OS would reject DNG files that were linear, and that this sometimes happens when the Adobe Converter encounters raw file parameters that it cannot handle, such as barrel distortion correction figures.
I have established that these DNG files from my S100fs camera RAWs are NOT linear DNG's. I found a helpful reader on the Adobe forum who had the tools and knowledge to look inside my DNG files, and ascertain that they were not Linear DNGs.
So I have exhausted the possibilities that the MAC OS is rejecting my DNG files for a recognized valid reason, and I return to my opinion that this is an Apple bug and needs to be fixed.

Why are my RAW files created by Vuescan so dark in Aperture?

I've been scanning images using Vuescan and saving as 16/48 bit RAW images. These images always look great in Vuescan but when I import these images into Aperture, the images are very dark. I need to do an exposure correction of +2 just to start seeing anything in the midtones. Ed Hamrick, the author of Vuescan, says this is because the RAW files have a gamma of 1.0 (coming straight of the CCD). If I save the same scan in TIFF format, the images look pretty much the same in Aperture and Vuescan.
My question is what benefits does saving in RAW bring given the large adjustments that I must make. I know I can automate the adjustments at import which might make this less of an issue but I wonder if saving in TIFF is nearly as good. Some of the pictures have a wide dynamic range with lots of shadow detail.
Any suggestions?
Thanks for any help.
Bob

My frustration has been that I am doing the processing twice which is pointless. I need to choose a workflow. Mind you that if Apple supported the full DNG specification, it would be able to deal automatically with these RAW scanned DNG files (I believe they are linear DNGs) and automatically compensate during import just as Lightroom does. I am using the trial version of Aperture - which I feel really comfortable using - but I think I may take Lightroom for a spin prior to making a final choice of software.
As I tried to clarify, there is no benefit in saving as RAW from a scanner. Just save as a normal 16-bit TIFF and you'll and up with a simplified workflow and no loss of data nor detail. Actually, a DNG is internally just a TIFF.
Mind you that if Apple supported the full DNG specification, it would be able to deal automatically with these RAW scanned DNG files (I believe they are linear DNGs) and automatically compensate during import just as Lightroom does. I am using the trial version of Aperture - which I feel really comfortable using - but I think I may take Lightroom for a spin prior to making a final choice of software.
If Apple fully-supported the DNG specification, then the RAW Fine Tuning adjustment would be available with its auto-exposure button to get a good starting point for tweaking the images.
You could provide Apple with feedback via, Aperture>Provide Aperture Feedback.
If I continue with Aperture, I am thinking that I will save these files as RAW TIFFs and do the gamma adjustment at import. This should streamline the workflow by making it possible to scan two 4x5s at one without the need to tweak each one in the scan and then do all my processing in Aperture (or Lightroom). I will just trust the scanner.
You shouldn't trust your scanner, just as you shouldn't always trust matrix metering or 'I'll fix that in post". Aiming for the best starting material is aiming for the best results. So instead, carefully examine each scan, which will not take you that long BTW.
I will still create the scanner profile of the IT8 target which I should then be able to use as a proofing profile to compensate for any color bias in the Fuji Provia film used. Perhaps I am wrong about this.
Actually, you're wrong on this. The IT8 provides an input profile, and not an output profile or working space. Imagine scanning a slide and printing it. Softproofing for IT8, then you can't softproof for your printer and vice versa.
Your post has allowed me to really think through my workflow and I really appreciate the input I've received in this thread. Now, I just wish I could get Apple to add support for Linear DNG (or whatever format Vuescan RAW DNG is which I know contains three colors per pixel rather then one as in Camera Raw) which would provide the additional tools to deal with these DNGs at import.
Although linear DNG support would indeed be nice for unsupported camera's, it is not necessary here. If Vuescan DNG has three channels, than it is a TIFF. (since demosiacing MUST have been applied, there are no scanners with a Foveon sensor as of yet)
Well to cut a very long story short just use TIFF for scans. It's a necessity for proper colormanagement and will simplify your workflow.

I can't open most files from DNG Converter 5.5b (Olympus E-P1)

I have a bunch of E-P1 photos taken in RAW (.ORF files) and was waiting eagerly for support by ACR. I tried the DNG Converter 5.5b today and converted all my images to DNG.
When I tried to import the DNGs in iPhoto, it imported only 32 files out of 800.
These 32 images also have a proper icon (with the preview of the photo).
I can't open the others with either iPhoto, QuickLook or Preview.app
All DNGs were opened successfully with Photoshop CS4 or Lightroom once I updated ACR to 5.5b
It seems that, for some reason, Apple apps can't open this "new breed" of DNG files.
Does anybody have the same problem ?

David, I'm afraid you will probably have to follow up with Apple on this
one. (If I'm understanding your post correctly, you have no trouble using
Adobe software to process the E-P1 files.)
Eric
Sorry, I updated my original post because I realized I wasn't making much
sense !
The DNG Converter did convert all my files to .DNG
I can open all of them in Photoshop CS4 (or Lightroom).
But I can only open a few of them with Preview.app, iPhoto.app or QuickLook on
Mac OSX.
I found out that the one I am not able to open are the photos taken with the
kit lens (Olympus 14-42mm).
The ones I shot with my Voigtlander 35mm 1.4 ( + adapter) were imported
successfully in iPhoto.

Should Apple punt with RAW and/or DNG support ?

It seems that Apple is taking a very detailed approach to profiling cameras before adding support to Aperture. Consequently Aperture may always be later than others apps to add new camera support. Also there will always be legacy or specialty cameras deemed not worth the trouble that don't get added too. I wonder if rather than asking Apple to support every camera made past and present it wouldn't be better to punt and ask for feature changes that make it easier to integrate other RAW developers into an Aperture workflow.
Further for a few of my most valuable images, maybe 1 out of 1000, no matter how good Aperture's RAW conversion I will always want to try other RAW developers to see if they might do slightly better on a top select image. An professional app that wants to host my entire photo archive must logically offer a workflow that supports any camera past or future that I may use even once.
The tools already exist to export a master and develop it with other RAW converters also to manage different master files of the same image using stacks. All that Apple would need to do to make the unsupported camera workflow in Aperture a useable alternative is make a few minor changes to already existing features:
1. In the RAW + JPEG workflow the JPEG is the second class member. You can expose it and have it stacked with the RAW master but you have to manually make it the stack pick. Otherwise when you close the stack you see only the unsupported master file which means nothing. It's not a problem restacking one image and not thinkable with thousands of images. I haven't found a way to get around this with Automator/Applescript. MAYBE: If the JPEG were the first image in the stack then I could still use Aperture for sorting, DAM, keywords, rating, etc. and just process my unsupported images with an external application.
2. I can use Export Master to save out a master file but the process of doing that then reimporting the master file and stacking it with the original is a tedious manual effort. Again Automator/Applescript can help here but more would be needed. MAYBE: If I could duplicate a master file inside a project or stack and if Aperture had an 'Open Master file with external editor" command then it would be easy to have a duplicate master file stored by Aperture that might be used with any other RAW processing application.
3. When I use 'Export Master' now to process some images with ACR or Nikon Capture then I can reimport the TIFF file or JPEG that I create but I can't easily associate them as versions or as externally edited files with their proper masters. MAYBE: There should be a way to link master files with the rendered versions of those files created by external RAW processors.
4. I started my photographic life with film. Most current 'pros' did the same. If I want to have one home for all my photo archive then it has to support film scans of larger sizes and export them to an external editor in something other than Adobe RGB. Automator and Applescript are will make this work in v1.5 but just barely. MAYBE: Give me a way to have my hi-res film scans stored in Aperture and send them to Photoshop without compressing them to Adobe RGB or downsampling to fit Aperture's current filesize (aprox. 250MB) limitation.
I can't imagine having many different databases and apps for unsupported images from a camera I may only use once. If Apple would just streamline and tweak a few features that exist in v1.5 then Aperture could be the home to all my digital images even if some of them had to be developed by another program.
I can't imagine a better workflow than using Aperture with any of it's supported cameras. That shouldn't stop Apple from opening the door for making use of Aperture's great database and DAM features with unsupported cameras too.
Pro Mac 2.66Ghz/8GB/250GB + 1TB RAID 0 wi SoftRAID in bays 2,3/X1900 Mac OS X (10.4.8) MacBookPro 2.16Ghz/2GB/100GB 7200rpm

Eric: Great, Aperture 3 might be out by spring 2010? That's only 6 months or so from now. [/sarcasm]
I appreciate the pointer to the AI article, but personally I'm more interested in whether Apple is working on adding additional RAW support for Aperture/Mac OS X any time soon, and certainly before Aperture 3 is out. Both Aperture 2 and Lightroom 2.5 are more than capable for my workflow and editing needs.
This week only added to my dismay re: Aperture v. Lightroom update likelihood and frequency; still radio silence from Apple, and Adobe releases a public beta of Lightroom 3, even as Lightroom 2 was released subsequent to Aperture 2 and has had more updates since its initial release than Aperture 2.
Brian, can you elaborate on the DNG conversion process that worked for you? Having tried every possible profile (I believe) in the latest release of the DNG Converter app, I have to say I'm skeptical that there's a setting that works with the GF1. But I'm ready to be pleasantly surprised!

Why will CS4 not open DNG files converted from Olympus E-M1 raw files?

For several years I have been able to use the DNG Converter to convert .ORF raw files from my Olympus E-M1 and then open them for processing in CS4. Suddenly CS4 quit recognizing these DNG files saying "Photoshop could not complete your request because Photoshop does not recognize this type of file"
I have not changed any preferences. I'm using E-M1 v3.0, DNG Converter v8.3.0.141 on a Mac. I have deleted DNG converter several times, even reinstalled an earlier version but nothing changes.
However, CS4 will open DNG files converted from Pentax raw .PEF files from my K-5. Weird. It's the Olympus raw DNG conversions that won't open.
I can view the DNG converted files in question in Mac's Preview just fine but not CS4. Any ideas will be appreciated.

Be sure the DNG Converter's compatibility is set to provide support for your version of ACR:
Benjamin

Can you tell me when RAW (ORF) support for Olympus E-PL7 in Lightroom or DNG Converter is coming? The camera is no use to me until you provide support!

I recently bought the new Olympus E-PL7 an dam finding ti incredibly frustrating that Lightroom still doesn't support it. Is there any news on that?

First of all, this is a user-to-user forum. Nobody here can tell you when/if that camera will be supported. Secondly, Adobe doesn't make announcements like that in advance. The camera will be supported when it is. All of the previous models of that series are now supported in Lightroom, so I suspect it will only be a matter of time until your model will be supported. I know that isn't what you want to hear, but that is the reality of things. There is a release candidate of the next Camera Raw and DNG converter, but your camera is not listed as one of the newly supported cameras. That does not mean that it wouldn't be included in the final version. You just have to wait and see.

DNG Converter 5.5 RC misidentifies Olympus E-P1 17mm lens

After using the DNG Converter 5.5 release candidate on Mac OS X to convert .ORF files from an Olympus E-P1 and the 17mm fixed focal length lens, I get the following erroneous lens description in the metadata of Lightroom once the DNG files are imported: "17.0-16657.0mm f/2.8"
Alas, I'm not getting that kind of zoom range out of this particular lens.
Anybody else seeing this? I don't have a problem with the 14-42mm zoom.

Stephen, can you please provide an example .ORF file shot with the 17mm? You
can use YouSendIt.com with target email address [email protected]
Eric
After using the DNG Converter 5.5 release candidate on Mac OS X to convert
.ORF files from an Olympus E-P1 and the 17mm fixed focal length lens, I get
the following erroneous lens description in the metadata of Lightroom once the
DNG files are imported: "17.0-16657.0mm f/2.8"
Alas, I'm not getting that kind of zoom range out of this particular lens.
Anybody else seeing this? I don't have a problem with the 14-42mm zoom.

Apple & Olympus E-M5 DNGs

Similar Messages

Maybe you are looking for