Adobe RGB choice affects only the JPG file, your raw file is not colour-corrected in any way (that’s what they mean by raw), and you need to apply the corresponding colour profile in software. Seems easier to just leave it on color matrix and change it if I have an issue with a specific file maybe? Other than clipping different parts of the color gamut to handle artifacts is there a logic to picking one over the other? I usually leave my cameras in Adobe RGB for RAW as it’s the wider of the two choices (the other being sRGB) so it seems logical to have Darktable use the Adobe RGB value here but that means another step and messing with the unbreak input profile module. I noticed you didn’t mess with the color input profile in your edits and left it on the standard matrix where as others and myself changed it to Adobe RGB. I believe the version in Darktable 2.6 defaults to “no.” Just to be clear filmic v2 you’re referring to is the one in Darktable 2.6? Filmic RGB in Darktable 3.0RC1 defaults to “max RGB” on my machine. My apologies for abusing backlighting so much. Sensors are linear and once a photosite clips the data is gone and in this image smoothing that transition is the goal. The tree isn’t lit from the side facing the camera so it’s EV is very far away from the sky and sun behind it. I guess I got lucky with this shot! Indeed “halos” is just the colloquial term around these parts, it’s caused by the sharp transition. Usually digital sensors are far more red sensitive than anything else and that channel is the first to clip. Yes that looks similar to what I have in my secondary edit. This what I get with switching the chroma preservation mode in filmic to “luminance Y” and the highlights reconstruction to “reconstruct color”: I know X-trans demonstrating can be peculiar compared to Bayer and maybe that has something to do with it? I tried the single and three pass settings included in demosiac and they didn’t seem to make much of a difference. These were shot on a Fuji X100s if that makes a difference, haven’t messed with an Nikon RAWs in 3.0 yet. These photos were imported straight into DT 3.0 RC1 without any legacy 2.6.x edits. Since a photo is worth 1000 words here are a couple of examples. In RC0 and RC1 I’ve noticed this strange halo effect with filmic RGB that seems to depend on white balance. I haven’t messed with the ordering of the modules in the pixel pipeline in Darktable 3.0 so they are as they are set out of the box. I was getting what I considered to be good results out of it at any rate, much better than base curve the vast majority of the time. I was a pretty happy with the old flmic module and thought I had my head wrapped around the workflow. I’ve been experimenting with Darktable 3.0 RC0 and RC1 for the last week or two and have been noticing strange halo effects with the new filmic RGB module.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |