In early 2023, Artificial Intelligence burst onto the Film Simulation Recipe scene, and, at the request of photographers across the world, AI began creating all sorts of camera settings to emulate all sorts of different aesthetics for Fujifilm models. I was on the leading edge of this, and in March published Using AI to Create Film Simulation Recipes, which included the ChatGPT-created Urban Dreams Recipe.

I didn’t stop there. In April I published a YouTube video (which you’ll find below) entitled Kodachrome X Fujifilm Recipe made by ChatGPT vs Fuji X Weekly Kodachrome II. I don’t publish very many YouTube videos (only three in 2023); however, I felt this topic was important enough to dedicate a video to it. Shortly thereafter, also in April, I published a companion article called Can AI Make a Fujifilm Recipe?, which included the ChatGPT-created Kodak Ektachrome E100VS v1 Recipe (along with the non-AI v2).

I didn’t quit there—not even close! In June, on the SOOC Live broadcasts, Fujifilm X-Photography Nathalie Boucry and myself chatted twice (for about three hours in total) about ChatGPT Film Simulation Recipes. If you’re curious about this topic, that’s probably the most informative discussion you’ll find. I’ve included both of those videos below.

Also in June, as a companion piece for those two SOOC Live episodes, I published an article entitled Shooting with ChatGPT AI Fujifilm Film Simulation Recipes. That article included two more AI-made Recipes: Soft Blue Classic and Vivid Summer Glow. I’ve published a total of four ChatGPT Film Simulation Recipes on this website. I think two are pretty good, and two are very mediocre—only the two that are “good” are in the Fuji X Weekly App.

While I’ve published four AI-made Recipes, I’ve asked ChatGPT to create probably close to 50 (using multiple accounts). Most of them weren’t good, so they never saw the light of day. I’ve talked about all of this before, but just to quickly rehash, here are some of the big issues with using ChatGPT to create Film Simulation Recipes for Fujifilm cameras:

• AI will always give you an answer, but whether that answer has any value is another question entirely.
• AI can’t see, and doesn’t know how the various camera settings translate to real-world use. It can only attempt to match descriptions.
• If you ask it to create the same Recipe—using the same exact wording—on multiple accounts, you will get multiple answers, often quite divergent from each other.
• I’ve never experienced an instance where all of the required Recipe parameters were included in the first try. Each time, I’ve had to identify the missing camera settings, and ask AI to add those to the Recipe.
• AI will sometimes include nonexistent or nonsensical settings.
• ChatGPT is very predictable, and will not usually stray outside of certain box. Ask it to make enough of these, and the box is easily identifiable.
• ChatGPT doesn’t cite its sources, even when asked. It definitely operates unethically, and probably (in my opinion) illegally—eventually courts will make various rulings as they hear different lawsuits.

So why bring this up again? First, I’ve had several people over the last month comment that ChatGPT is a wonderful resource for Fujifilm Film Simulation Recipes. I strongly disagree with that for the reasons mentioned above, and I thought it worthwhile to discuss those reasons again for those who might be unaware. Second, someone asked if Google’s Bard AI was any better than ChatGPT at creating Film Simulation Recipes. I wasn’t sure, so I spent some time over Thanksgiving putting it to the test. So let’s find out!

The first question I asked Bard was, “Make me a Film Simulation Recipe for my Fujifilm X-T5 that mimics the aesthetic of Kodachrome 64 film.” Well, I could tell very quickly that this wasn’t going to work out well, as the first setting it gave was the Acros film simulation. It included the nonsensical setting of Color +2 (you cannot select Color when using Acros). The settings that Bard failed to provide were Dynamic Range, White Balance Shift, Color Chrome Effect (although it did give Color Chrome FX Blue), and Clarity. I assume that it would have also missed Grain size, but it said to set Grain to Off.

Obviously that “Kodachrome 64 Recipe” will not look anything like actual Kodachrome 64 slides, even if it did somehow make sense. I asked Bard to cite its sources, and to my surprise it did! It gave me (broken) links to my website, including these articles: Kodachrome 64, Kodachrome 25, and Monochrome Kodachrome. Apparently, Bard has been trained using Fuji X Weekly (or to search for it… Bard is a Google product after all), but it’s not very good at it. In my opinion, AI should provide a bibliography of its sources upfront without being asked. Even Wikipedia does that, and apparently it’s not a reliable enough source for serious work. Bard will cite its sources when asked, which is better than nothing, while ChatGPT won’t even do that. If Wikipedia can’t be taken seriously, than AI should be taken even less so. It’s super sketchy that AI doesn’t cite it’s sources, but at least Bard will do so when prompted to.

I asked Bard to tell me why it chose the settings that it did. This demonstrates very clearly that trying to match descriptions of camera settings with descriptions of the film is an unrealistic method for achieving accurate approximations of various looks. For example, “Acros is a black and white film simulation that provides a good starting point for replicating Kodachrome’s tonal range and contrast.” And, “Kodachrome had a tendency to lift shadows, creating a slightly brighter and more open appearance. Raising the shadow setting by 0.5 replicates this effect.” And, “Kodachrome had a subtle ability to retain detail in highlights, preventing them from becoming blown out. Lowering the highlight setting by -1 helps achieve this result.” If you know even a little about Kodachrome 64 film and Fujifilm camera settings, you should have no issues identifying the problems there.

I didn’t stop with that one Recipe. I asked Bard to make many more. After a number of tries, I began to ask it for ridiculous Recipes, just to see what it would do. Make me a Film Simulation Recipe that mimics Kermit the Frog juggling Elmo. Make me a Film Simulation Recipe that mimics the look of digesting rotten apples that are crawling with spiders. Make me a Film Simulation Recipe that mimics the aesthetic of comedian Brian Regan hitchhiking across the Delaware River during the Clone Wars. In each case—instead of responding with “you are nuts” or “that makes no sense”—it provided me with a Recipe. It always will. For the Brian Regan Recipe, it tells me, in order to capture the essence of his adventure, I should photograph him on a rural road next to a river bank with some fog. Sounds intriguing, but there’s a problem.

You see, Bard has a bigger tendency than even ChatGPT to include nonexistent settings. Some of these are Color Chrome FX Red (which, arguably, could be just Color Chrome Effect), Color Chrome FX Green, Grain Effect Medium, WB Shift +1, and Image Enhancement On. This is in addition to the missing settings that are required for a Recipe but weren’t included, and the occasional nonsensical ones (like Color +2 with Acros). Sometimes it’s hard to make sense of what Bard provides when asked to make a Recipe.

For those wondering about Color Chrome FX Green, Bard had this to say: Color Chrome FX Green increases saturation and vibrancy of green pixels and slightly lifts green shadows for a more balanced tonal range. Use sparingly, as a subtle application of Color Chrome FX Green can produce pleasing results. Excessive use may make the image appear unnatural. Of course, there is no such thing as Color Chrome FX Green, but even if there was, it wouldn’t work as described by Bard.

The conclusion of this whole article is that ChatGPT and Bard are not good resources for Film Simulation Recipes for Fujifilm cameras. They are both capable of making Recipes (they will always give you one if you ask), but whether or not those Recipes are worth using or resemble what they’re supposed to is another story entirely. A broken clock is correct twice each day, and sometimes you can get a good Recipe by chance when using AI, but most often that won’t be the case. However, because these chatbots tend to stay within a box and don’t often stray outside of it, the Recipes that they make are often not terrible, they’re usually okay-ish. But you have to put up with the missing, nonexistent, and nonsensical settings. And you have to be alright with the unethical nature of it. My personal advice, if you want a Recipe that is more likely to give you good results, is to look no further than my website.

Someone said that AI will usually do a better job than a complete novice, but never as good as an expert. I agree with that assessment. I think if you ask ChatGPT or Bard enough times for Film Simulation Recipes, you are bound to get some that are trash, a bunch that are so-so, and a couple that are actually good. You could probably have as much luck rolling dice or throwing darts to create Recipes. That’s just the way it is. However, the technology is advancing rather quickly, and it’s only a matter of time before AI will be able to analyze pictures, have a good understanding of Fujifilm camera settings, and be able to approximate an accurate replication of picture aesthetics with the available JPEG settings. We’re not there yet, though. There’s a significant gap. I don’t doubt that the technology will get there eventually, perhaps in another five or ten years.

That will put me out of business. I understand that day is eventually coming, and that’s ok. It is what it is, as they say. The sad thing is that AI is using my own words and work against me. The more I publish, the more resources OpenAI and Google have to train their AI. It’s a type of theft. I do think that the courts will eventually rule that much of what they’ve done doesn’t qualifying as “fair use” under the law, but the damage will already have been done, and folks like me wont be compensated a dime for it. That’s the way life goes sometimes. The big guy walks all over the little guy. But, when life throws you punches, bob and weave (I’ve heard that quote attributed to Joe Frazier, but I’m not certain), which simply means that I have to evolve. As Bob Dylan sang, the times, they are a changin’. They always have been, and always will be. That’s why I spent so much time this year exploring the topic of AI Film Simulation Recipes. I had to know where Fuji X Weekly stands in all of it. This website has evolved a whole bunch since its launch in 2017, and it will continue to do so in the coming months and years. I appreciate all of those who have come along for the ride, and I look forward to seeing where this Fuji X Weekly thing goes as the future unfolds. If anything, it will be an interesting adventure, perhaps like Brian Regan’s hitchhiking escapades along the foggy Delaware River during the Clone Wars.