Jump to content

sandymc

Members
  • Posts

    1,444
  • Joined

  • Last visited

3 Followers

Profile Information

  • Member Title
    Erfahrener Benutzer
  • Country
    Schweiz/Suisse/Svizzera

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Not as regards sharpness. The Leica Monochrom, for example, produces a so-called "linear raw" file that LR or C1 will correctly understand to be a monochrome image. The issue is that for a modified sensor, the raw processor sees a M9 file, and assumes it is Bayer, which it's not. AccuRaw Monochrome has an override for such situations. A dedicated monochrome processor may still have advantages in tonality.
  2. Using a "normal" raw converter such as Lightroom will work ok, even though it will do a demosaicing process that is slightly counterproductive, but for maximum sharpness you want a raw converter that makes specific provision for debayered sensors, e.g., AccuRaw Mononchrome. Here's a comparison (using a MaxMax converted camera, btw): https://www.mcguffogco.com/accurawmonochromemac#difference
  3. For that those that aren't aware, Dan runs MaxMax, and is the go-to guy for camera conversion work, e.g., "de-bayering". I've worked with a number of cameras that he's converted. There's more information on his work on the Leica M9 here: https://www.maxmax.com/maincamerapage/monochrome-cameras/leica-m9
  4. I don't have DxO so can't actually test, but it's unlikely that DNG converter will help. Mononchrom files are "linear raw", not CFA, and nothing is going to change that. Sandy
  5. That's not quite accurate. DNG's typically (but not always) have two color matrixes, one at D50, and one at D65. The issue with RT is that RT assumes that typical == always. The correct way to read a DNG, from Leica or Adobe, is to read the tags to find out what color temperature each matrix is, and process accordingly. (CalibrationIlluminant1 and CalibrationIlluminant2, if you want the technical details). That's why other raw processors don't have that issue. Sandy
  6. Recent versions of CornerFix are 64-bit compatible.
  7. Interesting enough, Italian flag has been seen on other cameras - in fact, the phrase was coined for the old Kodak 14n Sandy
  8. CornerFix is a "universal" app - it incorporates both a 32-bit and 64-bit executable into the same package; the OS can run either. But there will be a new version coming out to support High Sierra, for other reasons. That will only come out once Apple ship a production version of Xcode for High Sierra. Sandy
  9. Technically, what the M10 DNG looks like is as below. So you need an app that can can extract IFD0, subIFD 1 ----------------------------------------- IFD 0: Offset = 12, Entries = 49 NewSubFileType: Main Image ImageWidth: 5984 ImageLength: 3992 SubIFD 1: Offset = 918, Entries = 12 NewSubFileType: Preview Image ImageWidth: 5952 ImageLength: 3968 SubIFD 2: Offset = 768, Entries = 12 NewSubFileType: Preview Image ImageWidth: 1440 ImageLength: 960 SubIFD 3: Offset = 618, Entries = 12 NewSubFileType: Preview Image ImageWidth: 160 ImageLength: 120
  10. Orientation sensors basically measure gravity. Years ago, a simple orientation sensor was just a drop of mercury in a small glass container with sets of contacts in various orientations. As you rotate the sensor, the mercury moves to the lowest point, and creates a short on whichever set of contacts is lowest in the sensor. Today, so far as I am aware most sensors are semiconductor based geomagnetic sensors - I think you'd get arrested if you tried to ship a commercial product with mercury in it. Sandy
  11. I think that the consequence of having the option on will be the Leica app will add a larger image non-raw representation to the files that are imported into the camera roll. The advantage of that will be that apps that can't process raw files will be able to process and display a full sized image, although not a high quality one. Most iOS image processing apps can't process raw data; apps such as PhotoRaw that can are an exception. The disadvantage is storage size, and the relatively low quality image.
  12. M10 DNG's already have a full sized image embedded in them, although a low quality one. So it's not really necessary to shoot JPG+DNG, if you set up the M10 app as discussed above. But equally, there's nothing wrong with it, and you can get a better quality jpeg. So far as I am aware, the new firmware doesn't change anything in this regard.
  13. The way that images are stored in the iOS camera roll is a bit unusual. In most desktop environment, e.g., Windows or macOS, you deal with single files - e.g., fred.jpeg. Under iOS however, what is stored on the camera roll is not necessarily a single image, but a set of images (in iOS speak, "representations"). Typically for a DNG file, one representation would be the original DNG file. But in addition to that, there would be at least one non-raw representation - usually a jpeg - so that any app could display the image. If you just import a DNG into Camera Roll, usually iOS grabs the smallest preview from the DNG, and assigns that as the non-raw representation. I would think that what the Leica app is doing is, at the same time that it stores the DNG to camera roll, it also allows you create a non-raw representation of whatever size you want. This is why M10 DNGs have a full size embedded preview image - see this thread.
  14. Yup. DNG orientation shows as 3. I'd say sticky orientation sensor on the camera is the most likely issue, or maybe a bug in the firmware. But LR is doing exactly what the metadata is telling it to do.
×
×
  • Create New...