166 points by notcodingtoday16 days ago | 60 comments
How to play: Some comments in this thread were written by AI. Read through and click flag as AI on any comment you think is fake. When you're done, hit reveal at the bottom to see your score.got it
Great to see more Fuji X attention, their native software isn't great. Looking forward to trying it out with my older X-T20, which appears supported[1] surprisingly
I was about to mention the Fudge[2] app and its underlying library, but its already listed as a reference, nice!
Love this - had contemplated different setups for getting raw studio running on linux but gave up before even trying. This is exactly what I wanted - a way to play with different recipes, no install required.
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.
The only reliable raw converter that can handle Fuji color is Capture One. But they have collaboration with Fuji, I don't believe that conversion algorithm is open sourced.
But it would be interesting if AI coding agent could potentially reverse engineer the algorithm.
While file format (RAF, DNG) often is an acronym, “raw” by itself simply references raw image data; it is not an acronym, not a trademark, and does not need all caps.
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.
This is one of those "well actuallys" battles that has been lost a long, long time ago my photographic friend.
Yes, "RAW" itself isn't a format like TXT or an acronym like JPEG, but in practice RAW appears alongside other all-caps names like JPG, DNG, TIFF, etc. in menus and documentation and so the industry has mostly converged on writing it RAW for consistency.
Never thought about that. Always wrote it all uppercase because that’s what camera maker Canon consistently does from what I’ve seen.
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.
RAW gets all caps the same way TXT, JPG, CMD, SH, BAT, and etc. get all caps. That is, you are also perfectly free to say raw files, text files, JPEG files, command files, shell scripts, and batch scripts, or .txt files, .jpg files, .cmd files, .sh scripts, and .bat scripts, and not everyone uses the same convention (or even consistently a single one).
I don't really see "SH" being used instead of "sh". JPG and JPEG get the uppercase treatment because it is actually an initialism (Joint Photographic Experts Group) unlike "raw".
Same thing happened with SQL in the 80s. Three-letter initialisms just get capitalized in practice, regardless of what they technically are. Happens with RAM, ROM, too. Prescriptivists lose this battle every time.
But practically speaking, does it really matter? The goal of language is to communicate, and in this case we all understand what the author is referring to when they reference "RAW".
It's like chastisting someone for saying "Band-Aid" instead of "bandage". One refers to a specific company that makes small adhesive bandages and the other is the thing itself. But we all understand what you mean when you say "band-aid".
But where does that logic end? "Band-Aid" works because there's no competing meaning. If documentation says "RAW" instead of "raw", someone unfamiliar might reasonably assume it's an acronym and go searching for what it stands for. That ambiguity has a real cost.
I would not chastise anyone for saying anything, especially in a casual setting, but I will point out a misspelling in written documentatation.
“Band-aid” or even “bondage” is fine, as long as you’re understood, but would you be happy to see that written in some medical guidelines? Would you feel confident that whoever wrote it even knows what they are talking about?
The Adobe argument cuts both ways though. Adobe also uses "Photoshop" as a verb despite it being a trademark. Industry conventions aren't governed by what one company does correctly. When every camera manufacturer ships a "RAW" button, that spelling becomes the de facto standard regardless of etymology.
This is really cool! I see you’ve got screenshot of it running on Android, could this ever also work on iOS? I tried in iOS on Chrome, but I just see “WebUSB not supported. Use Chrome, Edge, or Brave.”.
> 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
The interesting bit here is that the camera's ISP is doing the work — as far as I know, Fujifilm's film simulations aren't documented publicly, so offloading to the hardware is really the only way to replicate them faithfully without reverse engineering.
> 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.
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.
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.
I love how you styled the interface. The UI elements are minimalist and great looking. Did you take inspirations somewhere, or was it a from-scratch design?
When taking photo's on the Fuji it stores both RAW and JPG file - the camera's settings (film simulation, exposure, white balance, grain etc.) are all 'baked in' to the JPG. This app (and the official X RAW Studio) allows you to use the camera's onboard processor to modify the RAW files with these settings (or recipes, to use the term adopted by the Fujifilm community) after the fact, and re-export the photo as JPG. It's super useful for figuring out which recipes you prefer for different types of shot!
I'd also recommend checking out Fuji X Weekly [0] for recipe ideas and example shots if you want some inspiration.
Running this in a browser cuts the biggest support headache we always had -- "works on my machine" stuff. The PTP connection over USB is the part I'd watch; that's where things get weird across OS versions and browser permissions. Curious how it holds up at scale.
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...
[2] https://github.com/petabyt/fudge