Then I export as a full sized 16 bit TIFF and import that file into Lightroom.** To tell the truth, I don’t really fully know why I do this. I kinda follow that approach, but aim to get much of what I want for the next stage, so I don’t need to take things too far in the resulting file (since it will be a TIFF, which while being far far better than a jPeg, is still not as flexible as the original RAW file). Some people develop really flat with the intent of having the greatest possibly leeway in other programmes. I aim for some global approximation of how I want the finished result to be. I go for a moderately flat rendering, but not as totally flat as others might do. In other words, I develop globally at this stage and don’t do any local adjustments. My basic and admittedly somewhat illogical workflow is to import and open the RAW file in Capture One Pro and to develop it to give a reasonably finished looking result at a global level. It’s all a bit subjective really though, so whatever makes people happy is best I guess. Sure, you can pick apart some aspects and show, at a pixel level, where other developers might do an arguably better job at some specific subset or localised aspect, but in the end it all comes down to overall rendering, and that’s where I find Capture One to be the winner. I’ve tried Lightroom,* Capture One, the now discontinued Aperture and Iridient Developer, and my feeling is this – overall Capture One gives the most pleasing results. One reason why is that I find it gives the nicest results from the Fujifilm X-Series RAW files. What follows is a slightly modified version. It turned out to be quite long, so I thought I’d turn it into a proper blog entry here. I just answered a comment query about my use of VSCO Film presets in this post.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |