It lays down a way back before it touches anything
Writing to the wrong slot is the one mistake that really destroys something — and you cannot see it afterwards, because the read-back check succeeds on the wrong slot. So the step is split in three, and you can stop at any of them.
What happens after you tap “Write to C4”
- Back up the whole slot. It reads what is in that slot right now and saves it as a recipe. If it cannot read all of it, it does not write.
- Write one setting at a time. Only the values that differ are sent, and each one is read back and checked immediately.
- Report. What was written, what was not, and anything it touched temporarily to get around an interlock — listed separately.
An OK response is not proof that the value changed, which is why every write is read back.
Nine things
Read a whole slot, as it is
Connect the camera and read the 23 image-quality settings currently in that slot, decoded into the words the camera menu uses — film simulation, grain effect, colour chrome, white balance shift, dynamic range, tone curve, sharpness, noise reduction. Not a row of numbers.
23 settingsEdit it on the phone
Each setting moves within the range this body accepts. Settings that cannot be changed do not pretend otherwise — it tells you what is stopping them.
EditorWrite it back
Back up, write setting by setting, read back and check. It is done only when all three are. If something goes wrong it stops and says which setting it stopped on.
With a way backRebuild from a photo
A straight-out-of-camera JPEG or HEIF still carries the settings it was shot with. Pick one and get that set back as a recipe.
Unedited filesA shelf of recipes
Everything you read out or rebuilt stays on the phone, ready to write to any slot.
On deviceModel differences, visible
Bodies do not all hold the same settings. Writing a recipe to a different body marks the ones that will not fit before you start, and says which kind of difference it is.
19 bodiesIt works around the interlocks
Some settings only go in after another one moves first (grain size, dynamic range priority). The app sets that up, puts it back, and lists those temporary steps separately — they are not changes you asked for.
Kept apartProperty codes on demand
For troubleshooting you can show each setting's USB property code. Normally you see the English name from the camera menu, so you can match it word for word.
ToggleLight and dark
Follow the system or choose, with four accent colours. Every pair of colours has had its contrast computed, not eyeballed.
AppearanceIt leaves these alone
Drawing the boundary is worth more than one more feature.
No whole-camera backup
It handles the image-quality settings in the custom slots. Every other menu item on the camera is neither read nor written.
It does not touch photos on the card
Not read, not deleted, not uploaded. The photo used to rebuild a recipe is one you picked yourself, from your phone's library or Files.
No network
No account, no server, no analytics, no ads. It works in airplane mode.
No promises about your body
The capability matrix covers 19 bodies, but only the X-M5 has been taken through the whole chain on real hardware. A body that is not in the matrix may not read, and may not accept writes.
Nothing leaves the phone
No network requests. There are none in the app at all. The model matrix, the property-code table and the decoding rules are all built into it.
Recipes stay on the phone. They are saved as readable files and can be exported. There is no account and no iCloud sync.
Only the photo you picked. The app holds no photo-library permission. It goes through the system picker, so it sees the one image you chose and nothing else.
Worth reading first
What do I need?
CONNECTION MODE to USB RAW CONV./BACKUP RESTORE. The default, USB CARD READER, is file transfer — the slot interface is not open in that mode.Which bodies are supported?
Can it damage the settings in my camera?
What about my warranty?
What language is the app in?
DYNAMIC RANGE and so on), so you can match them against the body word for word.