Leica M Monochrome DNG support

It doesn't seem like Aperture supports this file format, can someone help as I seem to have exhausted every other option.

Unfortunately Apple still does not support the Monochrom RAW/DNG file. Actually Apple does not support any non-Bayer sensor (Fuji Xtrans for example).
The workaround suggested by leonieDF unfortunately does not work. The Adobe DNG converter generates dng files that are still not supported (regardless of "convert to linear image", "compression" options or any raw version chosen).
Bruce's option works. Unfortunately the TIFF file generated is usually 3x the size of the DNG and does not seem to be as good to be manipulated (shadow detail for example). You can use Adobe Camera RAW but there are at least 2 other RAW converters (RPP and Photo Ninja) out there that now supports MM DNG's.
There are a number of programs that now support the DNG for the Monochrom. Lightroom would be the obvious one since comes with the Camera. PhaseOne C1 also now supports the DNG.
I understand that Apple is working on getting the MM files supported. It seems that it may require not only a RAW support update but also OS update. I would suggest to send a feedback to both Aperture team and Apple OS team. The more feedback, the more they will know we want support for this camera.
What I have been doing so far is to shoot JPG+DNG and editing the JPG. Once support is released, I can just use the RAW as primary and the edits will then be done at RAW level (may need more adjutments though). Not ideal (far from) but I am not ready to move to Lightroom.
Cheers
Rafael

Similar Messages

LR CC Panorama fails on Leica Monochrom DNGs

Just installed LRCC on my Mac (v10.10, MBP) and it seems to have problems creating panoramas from Leica Monochrom DNGs.
It only says "Unknown errors occured" (very helpful error-msg by the way!).
For a test i tried using NEF files from a NikonD700, and it works as expected.
The panoramas work fine in PSCC, so it seems to be a LR problem to me...
Would be neat if this could be made to work, as it would be great not to have to go outside of LR for this!
Thanks a lot!
Chris

Yes it is that simple. Just do a google search for Lightroom and Photoshop preference file locations and you should find them. The next time you start the programs, they will rebuild them. Of course, you'll have to re-enter any custom preference settings you've used. Good luck. Of course, when you think you've located them. Just rename them and move them into another folder first. That way, if you've picked the wrong file, you can easily move it back. Once things are working, you can just delete them.
BTW, this is a good troubleshooting tool for any mac applications that are acting wonky. Just delete that preference file, and more often than not, the problem will be fixed.

Leica X Vario DNG files support @aperture?

Leica X Vario DNG files support @aperture?

Aperture's camera support comes from the OS. Does not look like the Leica X Vario is currently suppored. See http://support.apple.com/kb/HT5371.
-scott
<Link Edited by Host>

Lightroom 4 and the Leica M monochrom

When I import files from the M Monochrom there are no actual previews in the import dialog window. Also LR4 does not indicate the aperture used in either the library or develop module. Any suggestions?

I'm assuming that you're on a Mac, as this bug does not (to the best of our knowledge) occur on Windows. Unfortunately, this is an Apple bug. On the Mac, Lightroom uses Image Capture (Apple software that's installed as part of the Mac OS) to display thumbnails in the Import dialog. Image Capture version 6.2 broke support for monochrome DNG previews. We have reported the bug to Apple. If and when they fix it, the problem in Lightroom should just go away. But without eliminating reliance on Image Capture, fixing this issue is out of Adobe's hands. (For any interested Adobe employees reading this, the Watson bug number is 3463549 and the Radar bug number is 13569454.)
Regarding the problem of aperture not showing up in Lightroom, my guess is that (at least for a given lens), the Leica Monochrom is not correctly writing that metadata into the file. That's just a guess though. If you'd like to provide me with a sample file, I can examine the file's internal metadata to see if the aperture value is missing, or if it's present and Lightroom is just not reading it correctly for some reason. Probably the easiest way for you to send me a file is to upload it to Dropbox or YouSendIt or a similar service, and then post the link here.
Thanks,
Ben

HT201070 Leica M Monochrom and Aperture.

Why won't Aperture open Leica M Monochrom images even though I have all updates up to 4.09 ?

Apple is working on it. The Monochrome has a non-bayer sensor and until recently Apple wound not support non-bayer sensors. Apple has recently released a RAW update with support for the Xtrans Fuji cameras (also non-bayer). I understand that Apple usually get the camera in their labs in order to make the sensor profile. The MM was a hard to get camera until recently but this is non-issue now as far as I know.
Regarding the delay, I know it is taking too long. I wish it was out the day I got my camera. But to be honest, I rather wait and have a great decoder/rendering of the raw than a premature support and then later multiple updates (this would make me process my files twice or three times).
For the Fuji cameras, it also took long time, but it seems they got it right. From what I read on the net and from feedback from Fuji users, the rendering is equal if not better than the one provided by Adobe RAW/Lightroom.
My current workflow involves shooting DNG+JPG, once DNG support is release, I use the RAW as Original and process it futher if needed.
cheers
ps. do not forget to send Apple a feed back requesting MM DNG support.

New process in LR 4.2 RC for Leica M Monochrom?

There is a message when importing DNG files shot with a Leica M Monochrom with LR 4.2 RC indicating some new process is implemented for the camera and prompted the user for update?
What new process is implemented in this regard? does LR4.2RC turn off the demosaic algorithm for the M Monochrom files now?
Thanks a lot.
Simon

I see no message when importing a few Leica M Monochrom sample DNGs, either.
Could the message be related to the application of an Import preset that does not have the Process Version or perhaps has the PV2010 Process Version coded in it, and it has nothing to do with the camera, itself?
Or if you’re importing LR3 images that already have an XMP with PV2010 and you add those to your new LR4 catalog, perhaps there is some sort of warning about upgrading the Process Version. And similarly, if these are old photos with PV2010 in the XMP and you click on the warning triangle on the Loup view for the images then you will see a message about upgrading to PV2012.

DNG Support

Can you tell me when Apple will support Leica DMR RAW in Aperture?
I bought the productv in good faith expecting DNG support, but it will not work with my camera. Are there any plans ? Is it the fault of Leica? , of Adobe ?
I am baffled by this - is it bec asue not many people wil lbuy the DMR.
If so i will persevere with the Lightroom beta

<...>
I bought the productv in good faith expecting DNG
support, but it will not work with my camera. Are
there any plans ? Is it the fault of Leica? , of
Adobe ?
<...>
That's a mix of Adobe misleding people as to what DNG actually is, and every company around (not just Apple) playng fast and loose with what DNG support actually means. It would be easier to be upset with Apple if there were anyone but Adobe who actually supported DNG fully instead of only convienient parts of it (and they usually wont tell you which parts).
I am baffled by this - is it bec asue not many people
wil lbuy the DMR.
Now as to your camera support, I imagine Apple will add support eventually but it may take a little while. It's a combination of the camera companies cooperating with Apple and Apple's priority for camera suppport which is I think driven in large part by sheer marketshare - they want Aperture to be useful to as many people as possible, which is understandable. They wanted to get good quality conversions for the largest camera makers (like Canon and Nikon) and should now be branching out in terms of supporting other brands (I'd estimate Fuji next though).
If so i will persevere with the Lightroom beta
You can also simply export TIFF's from a RAW converter you like and import those into Aperture. That's how I use the program today.

Aperture lack of DNG support unfortunate

It's difficult to understand why Aperture does not offer support for Adobe DNG files.
DNG/RAW files are being used by some camera manufacturers that I work with, and they contain a wealth of metadata as well as the broadest range of image data, including "altitude", which is now very useful in my professional work.
This lack of support has forced me to go back to Lightroom, and to reconsider that application as my primary media catalogue and editing application.

A JPEG saved as a DNG isn't really a DNG file.
It is true that Aperture doesn't have "comprehensive" DNG support. It doesn't support linear DNGs, and it doesn't support some of the newest DNG extensions that Adobe has added (lossy compressed DNGs, etc.). I don't know the exact version of the spec that Aperture supports.
But do note that DNG is a lot of things. It's a fairly comprehensive spec that has many versions, with lots of different things. Aperture does support many DNG properties, but not all of them. If you want the latest, greatest, most comprehensive DNG support, then Adobe will have it, as it's their specification.
I personally just use the RAW files that come out of camera - whether they be NEF, CRW, CR2, or DNG. I _never_ convert my camera RAW files into DNG, because that actually strips some data (in my case, focus point informatin from CR2 files that Aperture can display, is removed from the converstion to DNG). There are many long-winded discussions on the "value" that DNG provides, and I don't subscribe to them. It provides no legay-proofness today that's unavailable other places.

Any solution for Panasonic Raw files and/or DNG support?

Hi folks - in addition to my Nikon cameras I shoot with a Panasonic LX3 and soon a GF-1 - and so far I haven't had any luck getting any sort of raw files from the panasonics to be read by Aperture. I had thought that with Apple's DNG support that there would be a way to convert the files to DNG and then import, but so far I have had no luck.
I realize that the GF1 is brand new, but the LX3 is over a year old and supported by all of Apple's competitors. I really don't want to switch to lightroom, but it is getting harder and harder to stick with Aperture.

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!

Monochrome dng

Hello,
I have been writing my own DNG headers to raw sensor grabs successfully for a while now. These have all been CFA sensors but now I have a monochrome sensor in the mix and I would like to save these as DNG as well. I have tried a variety of settings with the PhotometricInterpretation, CFAPattern, CFARepeatPatternDim tags and have had no success. Excluding the latter two tags will produce a greyscale image with dcraw but photoshop will not open these DNGs. I could just save these images as PNG but everything else is DNG and it just looks nice when everything is the same.
Any ideas on header tags for a monochrome DNG?
Thanks!
jt

Have you tried these options:
- Make a monochrome TIFF file instead of DNG. It should be fairly easy. You need about 12 tags.
- For DNG, don't make a CFA file, but a "linearRaw" file. PhotometricInterpretation = 34892 = LinearRaw

HT201071 And still no Pentax K3 support? At least improve the DNG support so the K3's DNG can be read.

And still no Pentax K3 support? At least improve the DNG support so the K3's DNG can be read.

http://www.apple.com/feedback/macosx.html

Aperture DNG support.

Hi,
As a new Aperture user I must say that I am really very impressed and prefer it to Lightroom. However, whilst my main camera (a Konica Minolta 5D) IS supported, my old Fuji isn't.
Now I appreciate that there are many threads about DNG support and or the lack of support for many popular cameras. But wouldn't it make more sense for people to ask Apple to concentrate on supporting DNG proper, rather than adding lots of support for old cameras.
If it did truly support DNG the problem would be solved. They could continue to add support for the majority of major new cameras, but those of us with large collections of files, from old and unsupported cameras wuld also be catered for.
Surely proper DNG support is more important than supporting XY or Z camera. With DNG everything would be supported.
Makes sense, does it not?
iMac Intel Core Duo 17" Mac OS X (10.4.8) 1 GB Ram

I thought that conversion to DNG was suppose to
protect you if the original raw format went out of
use and there were no converters available for that
raw format.
This is a false hope.
As noted, DNG only stores the RAW photosite data, translated into a form that programs can easily get at. It actually cannot even do this much for all cameras today, but let's pretend it could.
So you have the raw photosites - now what? Now you have to do the hard job of de-mosaicing the data, converting all of the seperate r,g,b values into real pixels. But wait, not all of the cameras use the same pattern - in particular Fuji. So you have a RAW converter reading a DNG that may run into an "unexpected" pattern it knows not how to convert.
The sad thing is, the worry you had about not being able to read RAW files in the future is already solved by a program called "DCRaw". This source code, free for all, lays out exactly how to read this exact same RAW photosite data from a file and even de-mosiac it (though a simple de-mosaicing). If you save off a RAW file on a disc along with a copy of DCRaw I can guarantee that in 100 years you will be able to use that code to parse that file.
Consider from this the other aspect of DNG I really don't like - if you have a DNG file, you have no way of knowing what is REALLY in that file. Is is pre-converted linear RAW data? Is it straight-up bayer pattern data? Is it a Fuji rotated data with extra dynamic range sensors? You can't know from the extension, and as a result have no idea if any programs you have will parse it correctly or not. At least with JPG or TIFF or even a normal RAW file, either a program reads that format or it can't. With DNG you will pretty much always have a subset of DNG files you cannot read.
So my question is, if you can always be sure you can read a RAW file in the future, and you can't be sure conversion to DNG will let any program but Photoshop read your file - what is the point? There are two things it gives you that make life a little easier, one is smaller file sizes (if you opt not to keep the original RAW and trust the conversion drops no data), the other is ease of adding metadata into the file itself. The first I would say is not as crucial as HD space is pretty cheap, the second is useful but you can always use sidecar files with RAW files - and that's only a burden if you need to move away from a managed editing solution like Lightroom or Aperture.
Some cameras are starting to use DNG directly as a native RAW format but I've already stated why I think that is not a good idea - with DNG you don't know if it's a RAW file direct from some camera or an alien format that holds data you don't know how to parse.

Adobe DNG support ?

Hi all,
In Aperture documentation there is "support" mention about DNG files. I have Leica Digilux-2 camera which makes "Leica/Panasonic" RAW files. These RAW files are not in Aperture list, but I can convert them with Adobe DNG converter. But Aperture nod not open these DNG files ? Is there some other DNG format than Adobe DNG ? Or have I miss something. I really like to use RAW format also in my Leica.
PowerBook 17" Mac OS X (10.4.3)

Actually it is true. DNG is NOT a standard. It is in fact a proprietary specification. Adobe has released SOME of the DNG spec to outside vendors, but there's no way to prove they've released the entire spec. It is their system and they control it.
For a file to work within the DNG format, enough of the information supplied by the camera manufacturer's SDK has to be DNG compliant. I've spoken with Apple engineers who explained that the DNG format is too limited to get a good decode unless the SDK offers enough corresponding good information. For instance, a certain camera may support parts 1, 2, 5, 7 and 9 of the spec, but not 3, 4, 6, and 8. While technically, you could open the DNG file under these circumstances, you couldn't get a good decode.
Apple simply decided not to let a poor decode creep into the system just so that they could say they supported a camera.
While I am sure that some of the limited RAW support we're seeing is indeed the result of miscues or miscalculations by Apple, I believe that the camera manufacturers share an equal portion of the blame.
We already know that Nikon for instance has a history of refusing to play well with others when it comes to their "as shot" data. While that's been resolved with some Nikon cameras, it is still an issue with others and a perfect illustration of why users should be putting heat on their camera manufacturer to get the RAW file format support they want.
Scott Bourne
www.aperturetricks.com

Why dosen't Lr see my Leica M9 only DNG it does not covert the images?

Why does Lr not see my Leica M9?

The three Leica M9 DNGs on this page work fine in LR 5.6, and have been supported for many years, already:
http://www.kenrockwell.com/leica/m9/sample-photos-3.htm
Are you asking why LR won’t import from the M9 as a USB-attached device, or what is your question, exactly?

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!

Leica M Monochrome DNG support

Similar Messages

Maybe you are looking for