Jono Slack over on the L-Camera-Forum was kind enough to post a raw DNG from Leica's new M Monochrom, so I a took a bit of a root around inside it. No surprises - it's very similar to a M9 DNG. For those interested, there's a field level dump of the interesting fields below, but the highlights are:
14 Bit data, much the same as an M9, with non-zero black level Uncompressed DNG version 1.0.0.0, so still the original DNG spec, none of the new stuff Camera name specified as "M9 monochrom" The MakerNote with its lens info still seems to be as for the M9; in this case the lens shows as "Apo-Summicron-M 75mm f/2 ASPH", which is consistent with what Jono reported The famous "blue dot" is still there The only thing that might surprise a few people is the "PhotometricInterpretation: LinearRaw" part. But that's actually quite correct - the way the DNG spec works, you can either set that to CFA (aka a Bayer array type camera) or to LinearRaw. And this sure isn't a CFA camera.
There is one slight side effect of LinearRaw though. When ACR or Lightroom load a normal raw, they apply a tone curve by default. However, with a LinearRaw, they don't. So, for those intent on comparing a M9 image to a M Monochrom image shot side-by-side, be aware that by default they have different tone curves.
I'd guess that once the M Monochrom is shipping ACR and LR will have a built-in M Monochrom camera profile that will probably have a tone curve.
The other issue to be aware of with LinearRaw is that most raw development programs don't support it, so until Aperture, Capture One, etc are updated, don't expect M Monochrom DNGs to load in much except Adobe products.
Hi Sandy, any plans to add decoding of new .XMP "Enhanced" preset-profiles - not XMP itself, but LootTable from inside of it for example into text presentation compatible with dcptool XML output (-d) ? just asking ...
ReplyDeleteHi deejjjjaaaaa. I can look at that. Are the enhanced profiles documented anywhere?
ReplyDeleteHi Sandy
DeleteAFAIK
1) http://www.adobe.com/go/profile-sdk
AND
2) those are XML files - only BLOB (char encoded) are LookTable, which I assume replaces LookTable from base dcprofile and 3D lut applied at the end of ACR/LR pipeline (after LookTable, after tone curve, etc) which is produced from CUBE format data
Ok, I took a look - there's no actual documentation on the file format in the Adobe documents. Which means that this will require some detective work on actual files. Do you any sample XML format files that you can send me? You can send them to the support site: https://mcguffogco.freshdesk.com/
DeleteI submitted .zip archive with some of .XMP files that Adobe installs (for example as a part of free DNG converter installation) - those XMP have LookTable encoded inside that replaces LookTable from Adobe Standard profile when selected in ACR as a camera profile...
DeleteThanks, will take a look.
Deletealso unrelated - why with recent Adobe dcp profils profiles (dual illuminant, with LookTable - like all recent Adobe Standard) applying dcptool -i, after dcptool -u will throw an error ?
Delete*** Error: Unknown error ***
*** Exception thrown in main routine - probably could not access a file
this is not about merit of doing so, but still doing -u, after -i does not throw such error
Interesting. Can you send me a sample?
DeleteOK, sent one Adobe Standard dcp profile through https://mcguffogco.freshdesk.com/ ... any new (~120Kb sized) such profiles will result in error when applying dcptool -u and then dcptool -i to the output of the first conversion
DeleteFixed in the new versions released today
Deletethank you !
Delete