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.
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.
I'd expect a cause is that most camera makers are Japanese, and it's not uncommon in Japan to uppercase words written in Latin alphabet for aesthetic reasons
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.
To be fair, it's essentially de facto convention at this point in the ecosystem, regardless of what's "right" or "correct". No one is gonna bat an eye regardless if you write RAW or raw either.
I saw it used both ways. My question about which one is right was answered as soon as I bothered to look up what it is, which I did when I got interested in raw photography.
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).
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.
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.
> 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
> 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.
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.
I always recommend RawTherapee for serious photography work. In addition to having been (at least originally) written by a complete colour theory geek and featuring a treasure trove of knowledge in the form of its companion RawPedia, it supports a whole host of raw formats, X-Trans RAFs among them (although Foveon X3Fs regrettably still an open issue).
I appreciate RawTherapee too and used it for a long time, but I started to notice that it really can’t match DPP for rendering Canon raw images. The denoising is nowhere near as good and it takes a lot of work to make the colors come out as good as DPP which has same processing profiles like “Faithful” that just look great out of the box.
Smart move of Fujifilm. That will the future of software licencing with AI breaking copyright. Software will come encrypted and only run on secure processors. AI will push us further into an age of cloud, software DRM and software patents. The rest will be effectively public domain.
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.”.
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
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.
https://www.canon-europe.com/pro/infobank/image-file-types/
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.
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)
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.
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.
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.
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.