![]() Yeah, man… those OpCodes… I knew they were there, just didn’t know what they’re called. Correct for nasty tones, etc… All of the above happens BEFORE you are presented with a “clean” image in CameraRaw or Lightroom, and I’m beginning to suspect that even RawTherapee hands you the image AFTER, at least some of the above has already been done to it.Upon some digging, I’ve learned, confirming what I’ve been suspecting, that with photos that come out of various devices as DNGs, there are almost always ‘hard-coded’ instructions which make the picture look prettier than it actually is: i.e. I was able to determine that just by looking at the same photos in various apps on my phone, then Lightroom, ACDSee and now, RT. I have long suspected that there was something shady going on behind the scenes in DNG files. Now, what happens when a DNG image file is imported to Lightroom and some adjustments are applied to it (and saved in the file as a set of instructions), does RT simply ignore those and load the image in its “untouched” form, or does it use those “settings” as a starting point? In RT, I want my DNGs to be as close to the original capture as possible (with no stupid sharpening or noise reduction). From what I’m seeing, RT does not write anything to the DNGs but rather, it saves everything in the pp3 files (please correct me if I’m wrong). I was hoping to address it, using flat-fields in RT, however, from what I’m seeing… The jury’s still out but I might have to just wing it.Ī couple of quick questions (so I won’t have to start another thread):ĭNG files are supposed to contain all the “develop” settings in them, not in a sidecar file. My real problem with this camera is the atrocious vignetting. I know, it’s not ideal but it’s better than not doing it at all. I work in a color-managed environment, so, for now, I should be able to tweak the colors “by sight” and save those adjustments as a preset. I actually do see myself investing in a solution which would allow me to create custom profiles but only because I’ll be able to use it to profile my future phones (and cameras), as well. It’s nice that RT supports it as much as it does, which allows me far greater flexibility than LR.įor what it is, the main camera module on my phone isn’t terrible but it’s not that great either, by today’s phone’s standards. I’ve been reading up on it myself, since, now, I have to deal with the format on a daily basis. I probably removed all the other extensions years ago. Apart from the NEF, there was nothing there, checked or unchecked. Yeah, that “file list”… I’ve gone over the settings a couple times but I guess I just missed the “file list”, because there was no list to speak of. The only known issue with RT is that there are metadata issues with many DNGs - work is being done on fixing that. ![]() The most common DNG screwup is an improper color profile, so if you have problems with unusual/difficult to work with colors, you may need to invest in a ColorChecker and profile the phone yourself. No guarantees of that, especially from Xiaomi. Apple’s “ProRAW” variant is, in fact, just that - DNG 1.6 resulting from the output of their multiframe superresolution algorithm.Īndroid DNGs can vary from manufacturer, but they SHOULD be standards compliant. There’s a subset of DNGs sometimes referred to as “Linear DNG” which may be demosaiced but still in camera color space, and it is alternatively possible to have a mosaiced or demosaiced DNG that was derived from a multiframe stacking approach. The majority of DNGs are true raw image files, that was the whole intent of them. So, I never thought that “RAW”-Therapee supported DNGs, since, technically, they are not “raw” image file
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |