When I launched the new App-to-Camera Recipe Transfer Protocol (ATC RTP) in the Fuji X Weekly App a few days ago, which allows you to send Fujifilm Recipes from the App to your camera, I said, “I do anticipate some bug reports, and hopefully they’re all very minor.” So far, they’ve all been pretty minor, but I think you should be aware of them.
First, if you have an older iPhone that uses a Lightning plug, in order to get this feature to work, you will need a Lightning-to-USB-C adapter. I’ve had two reports that doing this works, although I don’t have a Lighting cable iPhone to test it with personally. Those who have older iPhones, let me know if the adapter works for you.
Second, if you are an App Patron and attempting to transfer Recipe sets, and your iPhone iOS is 18 or older (and not 26), the app crashes. This was identified pretty quickly and has already been fixed. So if this is happening to you, either update the iOS on your iPhone or update the Fuji X Weekly App to the latest version, either option will fix the issue, and allow you to transfer Recipe sets.
Third, and probably most notably for most people, is that DR-Auto Recipes set Dynamic Range in the camera to DR100 instead of DR-Auto. This was working correctly in a beta before launch, so I’m not sure why it’s not now. It’s likely an easy fix once the issue has been identified. Sometimes with apps, a small change somewhere affects something else that is seemingly unrelated, and that’s my best guess for this. I’m hopeful that a fix will be in by Wednesday or Thursday, maybe sooner, so be on the lookout for an App update.
Fourth, Recipes with Grain set to Off will transfer correctly, but give a (false) warning that Grain was not able to be transferred. The bug in this case is the warning itself, and not the transfer. The App will set Grain to Off in the camera, so just ignore that error message.
Right now, that’s it. But please, no matter how small, if you encounter any issues let me know. I’d love to get this running as cleanly as possible. Your feedback helps to improve it, and is greatly appreciated.
In related news, I posted about the App update on Instagram; however, the next day, Meta removed my post for supposedly violating community standards, and they put some restrictions on my account. Specifically, Instagram claims that the post made “unrealistic claims or promises about economic gain” and violated their rules on “financial fraud and scams.” Of course, that’s complete nonsense and just boggles my mind how they came to that conclusion. It could be that their AI bots are not very good and are flagging and banning innocent content, or it was falsely (and maliciously) reported by someone trying to disrupt or sabotage the announcement, or maybe something else entirely. I have no idea. But, whatever the reason, it wasn’t right or fair. I’m being punished by Meta for something I didn’t do. I have appealed, but who knows how long that takes or what the outcome will be. If it was from a false report, will that person be punished for making the claim should the appeal return in my favor? Probably not.
In my IG Stories, I posted about this situation, and asked if this has ever happened to anyone else. To my surprise, I received close to 50 messages from people who have had nearly identical issues. Some of them even shared with me what they posted that got removed, and it was normal (non-controversial) content, similar to most other posts on the platform, and not a violation of community standards whatsoever. In other words, this is a very widespread problem that could happen to anyone. Any and every post has the potential to be falsely flagged and deleted, and the author punished for the next 365 days. It’s not cool, but this is what you and I agree to when we sign up. Mark and company make massive profits off of our content, and we sometimes get treated like dirt for no other reason than we agreed to their terms of service.
There are two ways that I can respond to this. On one hand, I could stop using Instagram. Why am I allowing them to treat me this way? This seems like an abusive relationship that I’m enabling by staying. On the other hand, if it was removed due to malicious behavior by someone who dislikes Fujifilm, Recipes, or Fuji X Weekly (a competitive app developer, perhaps?), they win if I quit. I don’t even know if that’s the case, and I really hate to make any assumptions, so it might not be that at all. It might just be the terrible AI bots that Meta is using. So I’m not sure how to respond to this whole situation, other than to say Instagram really sucks, and I’m not happy with their platform right now. Maybe it’s a good time to consider an alternative.
I’m excited to announce a new feature in the Fuji X Weekly App: sending Recipes straight from the App to your camera! This will make Film Simulation Recipes much more accessible because it removes the necessity to manually program them into your camera’s C1-C7 Custom Settings presets. I’ve been working on this for about a year-and-a-half now, and I believe it will transform and significantly improve the Fujifilm experience for many people. There’s a lot that I need to discuss regarding this, so let’s dive right in.
The new feature is called App-to-Camera Recipe Transfer Protocol (ATC RTP), and it uses something called Picture Transfer Protocol (PTP), a standardized camera-to-software communication system that’s been utilized by all major camera brands for over 25 years. Fujifilm uses PTP for X RAW Studio and other programs. I was able to create the ATC RTP using publicly available information from both Fujifilm and the Fujifilm community, combined with lots of trial-and-error, plus a little assistance from AI.
Using PTP is generally considered very safe; however, there is a small inherent risk in unofficial, unlicensed, unsupported programs. While there’s not a lot that can go wrong with PTP, there is a minor chance of adverse affects, especially if not handled carefully by the developers. To mitigate those risks, we built-in many safeguards and heavily tested it (I tried my best to break my Fujifilm cameras using ATC RTP, and couldn’t—don’t attempt that yourself, though). I’m extremely confident in the safety of this feature, but I want to be upfront and transparent about the inherent precariousness. It’s better to lay out all the cards so that you can make an informed decision that you are comfortable with, and it’s important to me that you’ve read this disclaimer before connecting your camera to the App. If you do decide to use ATC RTP, it’s an experimental feature, and it is at your own risk. I do believe that this is about as safe as possible from an unofficial program, and I doubt you’ll find another option with as many safeguards or as heavily tested before release. Still, like with any new software feature, I do anticipate some bug reports, and hopefully they’re all very minor (be sure to let me know if encounter any, no matter how small).
Very importantly, connecting your camera to any unofficial, unlicensed, unsupported program may void your camera’s manufacturer warranty. Fujifilm confirmed this with me. I tried very hard to obtain a license from Fujifilm so that it wouldn’t risk voiding your warranty, but ultimately that didn’t work out (they told me that they only give licenses to large companies “like Adobe”). While that significantly delayed the release of this feature, if I had been able to obtain a license, that would have made the wait worthwhile. Since I was not able to get a license, using the ATC RTP may void your camera’s warranty. Manufacturer warranties vary from country-to-country, and warranty laws vary from region-to-region, so read your specific warranty information very carefully, and research the laws that apply specifically to you. Some people are better protected than others; however, even if your warranty is technically voided, it’s possible that Fujifilm may decide to honor it anyway (or not realize it was voided) should something fail on your camera. It’s up to you if you want to take that risk, but my recommendation is to wait until after your camera’s warranty has expired (one or two years after purchase for most, but up to five years, just depending) before connecting to any unofficial, unlicensed, unsupported programs (pretty much any software that connects to your camera that’s not from Fujifilm or a major brand like Capture One or Adobe), including the Fuji X Weekly App. Whether you connect today, wait awhile before doing so, or never use this feature, that is a personal choice based on what you are comfortable with, having been well informed (and I hope you appreciate that I’m not keeping this secret from you). I have connected all of my compatible cameras to the Fuji X Weekly App, including my brand-new GFX100RF, but that was my own decision based on my personal confidence in the App’s programming and in Fujifilm’s quality.
With all that out of the way, let’s talk about how this new feature can transform your Fujifilm experience. What ATC RTP does is push Recipes from the Fuji X Weekly App to your camera’s Custom Settings presets (C1-C7 for most cameras, C1-C6 for some, and C1-C4 for others). You can pick a single Recipe, and choose which Custom Settings slot to send it to, or—if you are a Patron subscriber—you can create and send sets of Recipes. No more manually programming them into your camera! This makes saving Recipes in your camera extremely simple, and changing them a breeze. You can also do it with your Custom Recipes, not just the 400+ Fuji X Weekly Recipes. Sending a Recipe from the App to your camera is completely free—use it as often as you’d like, as many times as you’d like. Going one-at-a-time, you can fill up your C1-C7 pretty quickly. Sending multiple Recipes at once is reserved for Patrons, and I included three Recipe Sets—Starter, Street and Travel—to get you started (with more to come). I have not yet figured out how to send Recipes to FS1-FS3 on the X-E5, so those will still need to be set manually.
Not every Fujifilm camera is compatible, but most newer ones are. Specifically, as of this writing, you can use the ATC RTP with the Fujifilm X-Pro3, X100V, X-T4, X-S10, X-E4, X-T30 II, X-H2s, X-H2, X-T5, X-S20, X100VI, X-T50, X-M5, X-E5, X-T30 III, GFX100S, GFX50S II, GFX100 II, GFX100S II, and GFX100RF. Presumably all new cameras released in the future will also be compatible, but I won’t know for certain until they are available to test. Unfortunately, older models (such as X-Trans I, X-Trans II, X-Trans III, X-T30 and X-T3, X-series Bayer, and the first few GFX models) are not able to connect to the Fuji X Weekly App.
There are a bunch of important notes, so let’s work through them. First, as of this writing, the ATC RTP is only available on iOS. It’s being worked on for Android and is coming soon, but it’s not ready yet, so it’s only on Apple to start with. Second, you need a USB-C (2.0 or 3.0) cable that is no longer than 4.9 feet (1.5 meters), preferably a good quality one. If ATC RTP is not working, try a different cable. Also, Lighting cables don’t work, but I’ve had reports that Lightning-to-USB-C adapters do work. Third, you need to make sure that your camera’s Connection Mode is set to USB RAW CONV./BACKUP RESTORE. This is found in the Network/USB (Connection) Settings section of the Menu. Next, you might need to set the USB Power Supply/Comm Setting to SUPPLY OFF/COMM ON (or just OFF, depending on your model), although most of the time AUTO seems to work. The USB-C cable needs to be connected to both the camera and the phone (try reconnecting if the App doesn’t recognize that your camera is connected). Your camera must be powered on for this feature to work (the camera’s screen will go dark when connected). Do not power off the camera or phone or disconnect the cable during a Recipe transfer. ISO and Typical Exposure Compensation are not transferred via ATC RTP, and should be set manually. Also, Video Recipes are not included in this feature.
It’s possible to get error messages after a transfer. If the camera rejects a setting, it will either be left unchanged or set to a default, which is a safeguard, and you’ll be notified. Some common settings that will get rejected are Dynamic Range and Clarity. Since Dynamic Range is ISO dependent, if the ISO is set lower than the minimum for the Dynamic Range (for example, DR400 with ISO 200), the camera will reject it. To fix it, increase the ISO and either try again or set Dynamic Range manually. Since Clarity is dependent on the Drive mode, if you are in burst (Continuous Low or Continuous High), HDR, etc., and not Still Image (a.k.a. Single or S), it will reject Clarity set to anything other than 0. To fix it, set the camera’s Drive mode to Still Image (S) and either try again or set Clarity manually. If you’ve never saved Custom Setting presets into your camera before, you may encounter some errors on the initial Recipe transfer, especially with the PASM models that require shooting modes to be set. You will need to fix the errors in the camera, such as selecting a shooting mode and adjusting the ISO within each preset, plus selecting the correct Dynamic Range setting. Within Custom Recipes, any free-form text must be spelled correctly in English in order to work; otherwise, use the dropdown menus. Also, for any Custom Recipe Sets that you create, make sure that the selected Recipes are compatible with the camera you are transferring to (if not, you will receive error messages when transferring).
That was a lot to lay out, but I hope you can appreciate why it all needed to be said. If the Fuji X Weekly App on your iPhone didn’t automatically update, be sure to manually do it now. You may also want to update your iOS version if it’s old. To begin using the App-to-Camera Recipe Transfer Protocol to send Recipes directly to your camera, tap the camera-with-arrow icon at the top of the Recipe list page or at the top of any Recipe within the Fuji X Weekly App. You’ll have to agree to the TOS and select OK a number of times. If you are a Patron, to create Recipe sets, tap the three dots at the top-right of the Recipe list page and select Manage Recipe Sets. I think many of you will really love this new feature, and it will transform your Fujifilm experience. Right now it’s only available on iOS, but it will be on Android pretty soon, too, so stay tuned!
Find more than 400 Fujifilm Recipes in the Fuji X Weekly App! Consider becoming a Patron subscriber to unlock the best App experience and to support Fuji X Weekly.
Earlier this week I released a new Fuji X Weekly App update, which I’m excited to share with you. I didn’t announce this right away because there was a minor bug that I wanted to fix before telling everybody about this, which has since been fixed and updated, so, as of late last night, that’s no longer an issue. There are two major new features, plus several really minor things you’re unlikely to notice—we’ll just focus on those two big things in this article.
First up is something that’s been under development in one way or another for five years. I explored many different ways to implement this idea in principal, and there were a couple failed attempts, just because of the complications in making it function smoothly. Ultimately, the approached that worked best and most consistently was less intuitive than what I would have ideally preferred, but it was the best option all things considered. I actually rolled it out first in the Ricoh Recipes App, just so I could work out any unforeseen issues before adding it to the Fuji X Weekly App. What is this new feature? Backup/Restore.
Notes, Favorites, and Custom Recipes are stored locally on your phone within the App’s data, and there has not been a way to share them among devices. If, for example, you have both an iPhone and iPad, you’d need to manually input all your Custom Recipes into both devices—they don’t synch. If you switched phones or lost your phone, it was possible to lose your Notes, Favorites, and Custom Recipes. Now, with Backup/Restore, you can save a copy, and share it among devices.
To save a backup, tap the Gear icon, then choose Back Up Data. You’ll be prompted to either Cancel or Continue. If you select Continue, you’ll have the opportunity to choose where you want the .zip file to be stored—it can be on your device or in cloud storage. Once saved, you can share this .zip file with any device that has the Fuji X Weekly App. To restore, simply choose Restore Data, locate the .zip file and tap on it (if it’s a different device, you may need to download the .zip file onto that device). One note of caution: when you Restore Data, it will override and replace whatever you may have added and/or changed since the Backup file was created. For instance, if you have a Custom Recipe on your iPad that’s not on your iPhone, but you Back Up Data on your iPhone and Restore that .zip on your iPad, you’ll lose the Custom Recipe on the iPad. It doesn’t add the backed up data on top of what’s already there; instead, it replaces it.
My recommendation is to periodically Backup the Fuji X Weekly App, even if you don’t have intentions of sharing it to another device. If you add a new Custom Recipe, or you made some changes to your Favorites, that might be a good time to select Back Up Data and create a new .zip file. Cloud storage is probably the most ideal place to keep it, just so if you lose your phone or change devices, you’ll have it available. Should something unforeseen happen, which does occur now and then, it’s better to be safe than sorry. With Backup/Restore, you can now have that peace of mind, and also match up your Notes, Favorites, and Custom Recipes between multiple devices.
The other big feature of this update is a major overhaul to Custom Recipes. Not only is adding Custom Recipes easier and more intuitive now, but they look and behave more like the 400+ Fuji X Weekly Film Simulation Recipes that come in the App. For example, you can add them as Widgets. You can Filter them, and Search them. You can add them as Favorites. If you sort alphabetically A-Z/Z-A, they will be in the correct place. This is a very significant improvement.
All of the fields (except Sensor generation) are freeform text; however, many have a dropdown menu or -/+ field for easier selection. If (for example) you type Velvia instead of selecting it from the dropdown list, the App will still include this Recipe in Filter by Velvia (just as long as it’s spelled correctly). Custom Recipes created prior to this update are fully compatible and will automatically be transformed to the new system (which was probably the trickiest part of revamping it). If you leave a field blank, that field will not appear in your Custom Recipe in the App. For instance, those with X-Trans III cameras can skip Color Chrome Effect, Color Chrome FX Blue, and Clarity, since X-Trans III cameras don’t have those options, and they will simply not show in the finished Recipe. Once you save it, at the very bottom of the Recipe you’ll notice a Notes field, which wasn’t available in the old system.
Those who use the Custom Recipes feature of the Fuji X Weekly App will absolutely love this update. This has been in the works for a long time, and I’m very happy with how it turned out. And it needed to be done prior to the implementation of Backup/Restore. In a sense, as far as the coding goes, these two features go hand-in-hand, and that’s why they were done together. While this update is mostly beneficial to Patron subscribers, there are some small under-the-hood improvements that affect everyone, so even if you are using the App for free, I do recommend updating to the latest version, if your phone did not do so automatically.
The Fuji X Weekly App is free to download and use. Consider becoming a Patron subscriber to unlock the best App experience and to support Fuji X Weekly.
There’s a brand-new Fuji X Weekly App update that I’m really excited to share with you. The main headline is a new feature called Categories, which can be interacted with in two different ways. The goal of Categories is to help you find Film Simulation Recipes for the specific situation that you are photographing in. This update is beneficial for both Patrons and non-Patrons.
The first way to interact with Categories is if you choose a Recipe—any Recipe, it doesn’t matter which one—and scroll towards the bottom just above Notes, you’ll find a Category Tag or maybe a handful of them (the amount varies from Recipe-to-Recipe). This tells you that the particular Recipe you selected has been identified as good for those specific situations and/or aesthetics. Now, tap on a Category Tag and it opens Discover Recipes, except instead of showing you all of the photos in the entire App to browse through, it shows only those that share that tag. This can help you to find Recipes based on image aesthetic. Each time you tap on a Category Tag, the order of the photos is reshuffled. For Patron subscribers, Category Tags can be used in conjunction with Filter by Sensor or Filter by Camera.
The second way to interact with Categories is only available to Patron subscribers. If you tap Filter, you’ll see By Category has been added to the list of options. You can choose one or more Categories—as many as you like, but the more you choose the fewer results you’ll get. You can Filter By Cameras (say X100VI), Film Simulation (say Classic Negative), White Balance (say Auto, Auto Ambience Priority and Auto White Priority), and Categories (say Film-Like and Street), and you’ll get a few results that match your request quite well. You can get real specific. If you are looking for (let’s say) a Film-Like Recipe that’s good for Portraits on Cloudy days for your X-Pro3, you can find that.
This is such a fun new way to interact with Film Simulation Recipes, and I anticipate that it will be extremely helpful to those who don’t know which Recipes to try. I’m really excited to introduce Categories to you because of all that, and also because so much work went into it. I didn’t keep careful tabs on the exact number of hours spent on this project, but it was a lot! The task of categorizing the various Recipes (over 400!) was pretty daunting on its own. I’m sure that it’s not perfect, and some might disagree with a certain Recipe’s inclusion or exclusion from a specific Category, but overall I think it turned out quite well. I really hope that some of you will find it to be a useful feature.
***Update: We were able to get the bug identified, fixed, and the app update submitted and approved by Apple in record time. On your iPhone, if the Fuji X Weekly App crashes immediately, make sure that you update to version 1.12.1 (and not 1.12.0) or update the iOS to the latest version (either option will fix it). I’m sorry for any trouble that this may have caused anyone.***
The Fuji X Weekly App is available to download for free from the Apple App Store and the Google Play Store! Consider becoming a Patron subscriber to unlock the best App experience and to support Fuji X Weekly. If your device didn’t update automatically, be sure to update it now.
Over the weekend I released a very small update to the Fuji X Weekly App, for both Apple and Android. This was supposed to be included in a much larger and more significant update (that’s coming soon), but I’m still working on some of the upcoming features and improvements, so I decided to just get this smaller one out now. It fixes a minor bug that most of you probably didn’t notice. It also changes the functionality of something, which I thought deserved an explanation.
The functionality change has to do with Filter by WB and Filter by DR. Prior to this update, both of those Filter options were “choose one” types, which means you picked the one option that you wanted. By request, both of those are now “choose one or more,” which means that you can select as many as you’d like.
The reason why you might wish to select more than one White Balance type is that, perhaps, you want to choose all three of the Auto options (Auto, Auto Ambience, and Auto White). Before you couldn’t do that, and you had to pick only one of the Auto options at a time, but now you can select all three if you want. For Dynamic Range, you can select (say) DR-Auto, DR100, and DR200, and filter out all of the Recipes that use DR400 and DR-P (this seems more helpful for reprocessing RAW files in-camera or with X RAW Studio).
This isn’t a game-changer type update, as it will likely have a minimal impact for most people (if at all). But for some, this will help them out a little. The upcoming update, which I’m hopeful will be ready later this month or maybe early next month, will be much more robust, and will directly help all users, providing an improved experience for everyone.
There’s a brand-new Ricoh Recipes App update, and I want to bring your attention to it because it is a foreshadowing of the next Fuji X Weekly App update. Specifically, Custom Recipes—a new feature for Ricoh Recipes, but not a new feature for Fuji X Weekly—is intuitive and integrated into Filtering, Favoriting, Random Recipes, and the Selected Recipe Widget. In other words, it’s much better in the Ricoh Recipes App than how it currently is in the Fuji X Weekly App. This is something I’ve been working on for a long time, and I cannot wait to incorporate the improvements into the Fuji X Weekly App soon. You’re going to love it!
I want to also bring your attention to the new Backup/Restore feature, which allows you to save a backup file of your Custom Recipes, Favorites, and Notes. You can restore that file later, and you can also send the file to another device and restore it there. If you want to ensure your inputs are not lost, if you want to share those with another device, or if you are upgrading to a new device, Backup/Restore is a great new tool. This will be coming to the Fuji X Weekly App soon, too.
While the Ricoh Recipes App update does not directly affect most of you, it indirectly does, because these two significant improvements are coming to the Fuji X Weekly App in the near future. I’m very excited to incorporate these, because I think many of you will greatly appreciate them. I don’t have a specific timeline, but I’m hoping to get it out as soon as I can, perhaps in a month-ish, so definitely stay tuned!
