![]() ![]() ![]() I still occasionally use NX-D to see how it stacks against the competition. ![]() If the camera's Picture Control is set to Vivid when you take the photo, and you change it to Landscape later, it's the exact same as if you took the picture with the camera set to Landscape. If you're shooting Nikon RAW (.nef files), the data collected by the sensor is the same no matter what Picture Control preset the camera is set to. Picture Control consists of: sharpening, clarity, contrast, brightness, saturation, and hue. Shadow recovery and highlight recovery aren't even part of the Picture Control, and neither is Active-D Lighting. If the camera's Picture Control is set to Vivid when you collect the raw data, and you change it to Landscape later, it's the exact same as if you took the picture with the camera set to Landscape. I don't think there's edge-detection (or local laplacian pyramids) in the highlights recovery in NX-D, nor is there any highlights reconstruction for blown-out channels, so the outcome won't be as good as in Lr, C1 or dt, at least that's my experience. That is the opposite of my experience with the files from my Coolpix A - using the Standard Picture Control for wide dynamic range images (optimally exposed) damages the highlight detail past recovery, so I prefer to start from as neutral as possible and carefully shape the tonality with the curve. The default Picture Control, for example, is probably "Standard," which is a bit flat and drab. If you didn't adjust any of the settings in the camera, then the camera's settings are still on the factory defaults. ![]() Raw converted to jpeg in Capture NX-d (no corrections)Ĭapture NX-D will read the in-camera settings that are embedded in the. I find that darktable gives me much more control over shadows and highlights than what Capture NX-D gives me. If these methods are too difficult for you, you can always use multiple instances of the Exposure module (or Levels), modifying the tonality separately for highlights, midtones and shadows by using the parametric mask option (using the gray value).Īlternatively you could output a flat, linear 32-bit or 16-bit, ProPhoto RGB file and work on the tonality with the Gimp or the Nik plug-ins.Īll of this can become a one- or a two-click solution in darktable when you establish the typical values for the types of exposures you take and then create a processing style suitable for your aesthetics. You could combine that with the usage of the shadows and highlights module (for highlights recovery I usually set it to the bilateral filter softening, rather than the default Gaussian - more subtle haloing). I usually switch the module's view (scale) to logarithmic (to better see what's going on in the shadows) and leave the upper part of the base curve flat - a gentle S-curve with a dip starting from the value of 0.5 and 1, and a hill around the value of 10 (later on it plateaus gently).įor wide dynamic range images you might want to experiment with the exposure fusion modality of the base curve: I got really nice results with it.Īnother way you could try is creating the midtone contrast with the local laplacian pyramids method while leaving the base curve relatively flat in the highlights area. I have custom, DCamProf-made ICC profiles for my cameras which mimic the Adobe tone curve which is embedded in their DCP profiles, so my base curve gets a rather subtle contrast treatment, mainly in the first quarter. The default one for your camera might need some tweaking if you're not happy with your highlights recovery. If you use the default, linear input colour profile for your camera, you need to add contrast e.g. In Capture NX-D, it is simple and I am yet to get better at handling base curves in DT. However I still have not gotten hold of editing an underexposed image in DT. This is exciting for me since I get to work with Raw rather than tiff. Now I can launch Raw in GIMP through DT seamlessly. Thanks for your help sankos and I see you are there on pixls upgraded my OS and it fixed it without any further effect. I plan to upgrade my OS and hence do not plan to debug now. I referred the pixls forum and looks like few others face it too. What happens if you copy all the GitHub folders from that repository into your "lua" folder? The luarc file should contain this line: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |