![]() By doing this, I can tweak the VSCO Film version to tone down the often over the top results they give. Then I often go back and forth between the ‘pure digital’ version and the ‘analogue-ised’ VSCO Film version to see the difference. The photo from the original post is a good example, with the face needing a new Adjustment Brush to bring up the exposure. Also, often I find I need to apply extra local adjustments after applying a VSCO Film preset. In particular, it is often necessary to use the “Orange Skin Fix” options when doing portraits. Then, I go over any of the local adjustments that need post preset tweaking to make them fit better with the new VSCO Film preset results.īecause I’m working on a TIFF file and not a specific to camera model RAW file at this stage, I use the “Standard” film pack presets, and not the “Fujifilm” specific film pack presets (although I still install the Fujifilm film pack presets when doing the initial VSCO Film install).Īnother thing I should add, with the VSCO Film presets it is often necessary to use the “Toolbox” sections to get things looking normal. This will overwrite any of the global adjustments with the preset’s own if it used the same global controls, but I can usually quickly tweak these if I don’t like what has happened. Then I make a virtual copy and apply a VSCO Film preset. I tend to work on the original version with global and local adjustments first to get it where I want (as mentioned above). It is in Lightroom that I use the VSCO Film presets. ![]() These (global & local) go back and forth a lot, as I play with things to see what looks the best, and sometimes the global stays at the new settings, and sometimes it ends up essentially back to what came out of Capture One. Once in Lightroom, I (typically) apply a little extra global adjustment if needed and then also local adjustments. However, I really do see a difference and prefer the results I get in the initial rendering from Capture One, and also, to be honest, as I have a significant investment in Capture One (from the days when it really was the only acceptable game in town if you wanted to work with RAW), I don’t want to abandon it and essentially give up on that investment. In part, it would make sense to work on the RAW file all in one programme. Maybe I should try to do everything in Lightroom to save myself the effort, as that would seem logical. 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 |