The mistake of “shouting” raw is perpetuated in the wild even by serious companies, but let’s not let Apple degrade our literacy[0]. I’ll point to Adobe which does, in fact, use the correct spelling[1].
[0] It is fine when used as part of idiomatic spelling of their product or trademark (“ProRes RAW HQ”, etc.), but IIRC their promotional materials and even developer docs do shout it when simply referencing raw image data, which is a little ridiculous.
[1] https://helpx.adobe.com/camera-raw/digital-negative.html
But it would be interesting if AI coding agent could potentially reverse engineer the algorithm.
I also personally find the original app infuriating to use, takes a lot of click & wait to modify a profile.
If I search for Canon raw on Google the Canon owned websites that I see writes it all uppercase; RAW.
One of their pages that I find even makes note of that:
> The letters RAW do not stand for anything – it's just a convention that RAW is usually written in capital letters – and the names of RAW files from Canon cameras do not end in .RAW.
Edit: There are some parameters:
> FilmKit communicates PTP (Picture Transfer Protocol) over USB, the same protocol that X RAW STUDIO uses. The camera does all the heavy lifting: it receives the RAF file and conversion parameters, processes them, and returns a JPEG.
Could someone explain what this software does?
And I'd also appreciate any software and workflow people use.
Would prefer Linux software, but macOS is okay if the quality/ ease of use is too different.
I was about to mention the Fudge[2] app and its underlying library, but its already listed as a reference, nice!
[1] https://www.fujifilm-x.com/en-us/support/compatibility/softw...
On a related note, Fuji’s simulations being locked to their walled garden has been an issue for third party tools forever. All “replications” of on device are just that. And never comparable.
I think a lot of people would like to study how they work to create true replications.
It bugs out for my XT30 because the profile is a different format, but claude was able to figure out a tweak to get it running and hide some of the features the XT30 is too old for - will do the wireshark thing from a windows machine at some point.
Thank you!
MacOS 15.6.1 - could see the camera via PTP but couldn't connect (clicking "connect" didn't do anything, no error)
Yeah, but Fuji X cameras are renown for their JPG processing so many people want the in-camera JPG. You could shoot directly to JPG but with an app like that you can later change the JPG profile, etc. while adjusting exposure parameters.
Perhaps the combination of that and the old .raw filename extensions on old filesystem implementations where everything appears uppercase (since camera firmware is slower to catch up, this persisted for years even though contemporary OS already had no such limitation) made it stick.
Browser-based preset manager and RAW converter for Fujifilm X-series cameras for desktop and mobile.
Desktop
Android
This is author's cat. Shoutout to Fuji X Weekly for awesome presets!
Note that the app is in BETA. It's currently tested on X100VI only. It likely works with other X-series cameras that support Fujifilm's RAW conversion protocol (X-T5, X-H2, X-T30, etc.), but this has not been verified. If you have a different camera and want to help, see Supporting New Cameras below.
Just like Fujifilm X RAW STUDIO, FilmKit uses WebUSB to connect directly to your camera, your camera's own image processor handles the conversion. FilmKit is a static client-side app, hosted on Github Pages.
Browser that supports WebUSB, this includes Chromium-based browswer like Google Chrome on desktop and Android.
Appropriate udev rule required if the browser is running in Flatpak, ex:
SUBSYSTEM=="usb", ATTR{idVendor}=="04cb", MODE="0666"
FilmKit communicates PTP (Picture Transfer Protocol) over USB, the same protocol that X RAW STUDIO uses. The camera does all the heavy lifting: it receives the RAF file and conversion parameters, processes them, and returns a JPEG.
For preset management, FilmKit reads and writes individual preset properties (D18E–D1A5) using standard PTP GetDevicePropValue / SetDevicePropValue operations.
See QUICK_REFERENCE.md for full protocol documentation.
FilmKit's protocol implementation was built with the following reference materials:
The camera's native d185 profile format (625 bytes) uses different field indices and encoding from the format in RAF files. FilmKit uses a patch-based approach: copy the base profile byte-for-byte, only overwrite fields the user changed, to preserve EXIF sentinel values.
FilmKit has only been tested on the X100VI. If you have a different Fuji X-series camera and want to help expand support, you can capture USB traffic with Wireshark:
USBPcap1:\\.\USBPcap1).pcapngFilter Wireshark with usb.transfer_type == 0x02 (bulk transfers) to see only PTP traffic.
Open an issue on GitHub with:
.pcapng filesAdditional captures may be required with various property values (ex. for ranged-based value, typically preset save or profile read of min/max values are good enough, but we may face another case of HighIsoNR weirdness).
This project does not accept any pull requests.
What is welcome:
When filing a bug report, please include:
Made with ♥ by eggricesoy · @eggricesoy