Update 08-08-2021: I’ve shared some new Fuji recipes here. One of the things that I was also hoping to achieve by shooting jpg was to get a more consistent look in my photos, but looking back that never really happened because I kept changing back and forth between all of those recipes! So in order to simplify my shooting process and get more consistent results, I decided to stick with just one color simulation and one black & white simulation recipe. Some jpg examples shot using Ritchie’s Vintage Kodachrome and Fuji Superia 800 recipes My favorites so far have been the Kodachrome simulations (both the Vintage Kodachrome and Kodachrome II) and Fuji Superia 800, but they’re really all quite excellent and cover an enormous range of looks. This site was a real game changer, as it allowed me to emulate directly in the camera many of the looks that I was trying to recreate using Lightroom presets.
![capture one presets vs styles capture one presets vs styles](https://enviragallery.com/wp-content/uploads/2020/06/screenshot-1.jpg)
I began exploring different possibilities using the in-camera film simulation settings and came across Ritchie Roesch‘s “ Fuji X Weekly” blog, which features some really excellent Fujifilm recipes inspired by classic films. Choosing between them became an extremely time consuming task and it got to the point where I would sometimes spend over half-an-hour with a single photo going back and forth between different looks.Įarlier in 2018 I realized that I should really spend less time editing and more time shooting, so I decided to use the jpgs instead of the raw files as much as possible. You can get as many different looks as you want, none necessarily “better” than the others, just different. But the greatest thing about working in raw quickly became my biggest problem: the endless possibilities provided by editing these files means it’s a never-ending task. It’s nothing short of amazing the range you get when editing Fujifilm’s raf files, especially when it comes to recovering shadows and highlights. That being said, as much as I appreciated the quality of the jpgs, I almost always ended up working on the raw files for the added post-processing flexibility and to get a more stylized look.
![capture one presets vs styles capture one presets vs styles](https://www.freepresets.com/wp-content/uploads/2019/12/Free-Capture-One-Preset-Analogue-Before-and-After-Presetpro.com_.jpg)
The colors and details are just stunning, and as someone who grew up with film photography in the 80s, the idea of having film simulations directly in the camera was just perfect! I think the main pitch was to persuade potential buyers that having a vast selection of styles available was a justification for purchasing the software even though they would be unlikely to use most of what was offered.Like so many other Fujifilm users out there, one of the main things that drew me into the X series system was the quality of their jpg files and the film simulations. However, in all cases a lot of scrolling was evident (quantity of styles being important for sales?) even though the presenter, using his own images, almost always used exactly the same 2 or 3 styles for all of his images no matter what the content subject matter. I recall, perhaps a decade or more past, watching some sales video guides for a different product that offered a huge number of styles. It seems to me that the Built-in and Paid-for packs would need to be offered just as they are and it should be left to the user to turn them into User Styles and Presets, sitting alongside their own Styles, in order to manage how they are grouped (and, as now, permit multiple copies of the same Style or Preset to make grouping in preferred "sets" simpler? Also to provide consistent use of the Keyboard Shortcut feature.) (I am not sure as I do not have any paid for Packs.)
![capture one presets vs styles capture one presets vs styles](https://www.freepresets.com/wp-content/uploads/2019/12/Free-Capture-One-Preset-Snowy-Peak-Before-and-After-Presetpro.com_.jpg)
The same goes for Style Packs with the difference that, potentially, they would bot be automatically updates with each update or version upgrade. (There may be some issues about managing those styles and who has the rights to modify them if working in a Multi-User environment but that probably goes beyond the scope being discussed here.)įor Built in styles that are not copied to be User styles one can still modify the structure (i.e the Style Sets groups) used for delivery as part of the application installation BUT as the next new installation the styles and presets will be re-installed (potentially with some updates for functional compatibility reasons). However, as a thought challenge for how to work with a development design, there are certain considerations.įor User Styles (including copies of Built in styles and presets, as Okular has previously described) there is already the possibility to create and save a folder structure containing the required styles. I'm not a great Styles user so this does not really concern me much.