So, you at least need to drive the highlights in these images to white. The over-exposure in the upper images should be of no consequence to the amalgam.Įdit: I downloaded the raws and tried to do a hdrmerge hdr, and indeed, the overexposed images polluted the amalgam dng with “pink-ness”. Thing is, you’re using these images to make an amalgam HDR, so the important data in this particular capture are the lowest values, and the “pink” regions will be supplied by 144, 145, the lower exposed images in the sequence. My surmise is that, thinking each image stands on its own, Lightroom is applying aggressive highlight reconstruction to “make nice”, darktable is just spitting in your eye for egregious overexposure… The data piles up at the respective channel maximums, then those piles are pulled apart by the white balance - TaDa! Pink! (or more specifically, magenta). I have adjusted levels and white balance prior to applying the film. I downloaded P1170150.RW2 and opened it in rawproc with the default processing to a linear RGB, and the “pink” is definitely the result of blowing the snot out of the highlights in the camera. Portra 160 gives digital photos the unmistakable and timeless look of the classic. Most cameras do work fine (all of mine but the old Canon D60 work fine, for example), but there are a few bugs with others. Related issues & PRs to a few black point issues in various cameras: (It’s probably similar or same black points for all the rest of the raw files from your camera too, so you could work around this in a similar manner without having to manually check and set for future photos.) Ideally, darktable would just figure this out itself (and it usually does for most files), but if your camera also has this same problem, then manually checking and setting is the workaround fix for now. It’s not 100% perfect (as the values vary a slight bit sometimes), but it’s 99% of the way there for most of my files and totally better than what darktable was giving me by default.įor your one file, run exiftool on the file, look at the black point, and make sure it matches inside darktable. ![]() Then, I made a preset of that and have it auto-apply to all of the D60 files. My workaround, at least until the next version of darktable (or the one after or whenever it’s fixed), was to run exiftool (and dcraw -i -v might also work) on a good number of raw files (especially daylight), note the black setting values, and set them accordingly. I have the black point issue with my old Canon D60 camera when the white balance is set manually (which is most of my photos, as I used a grey card back then, as its in-camera white balance was often a good bit off). If there is a problem with with black point settings, you can adjust that within darktable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |