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...
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!
But it would be interesting if AI coding agent could potentially reverse engineer the algorithm.
MacOS 15.6.1 - could see the camera via PTP but couldn't connect (clicking "connect" didn't do anything, no error)
I also personally find the original app infuriating to use, takes a lot of click & wait to modify a profile.
You will have to wait until the WebUSB support lands in Safari.
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
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.
Fujifilm writes "RAW": https://fujifilm-dsc.com/en/manual/x100vi/connections/raw/
Nikon writes "RAW": https://onlinemanual.nikonimglib.com/zf/en/raw_processing_59...
Canon writes "RAW": https://www.usa.canon.com/learning/training-articles/trainin...
Leica writes "RAW": https://leica-camera.com/sites/default/files/pm-73002-Leica-...
Even Adobe writes "RAW": https://www.adobe.com/creativecloud/file-types/image/raw.htm...
Descriptively yours,
However many examples you point out, there is no limit on poor editorial standards and lack of literacy, and I have no issue with that. That doesn’t mean we should stop calling out misspellings in official documentation.
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.
There’s no need to be lowkey rude about it either way.
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".
And isn't that the point?
“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?
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.
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.
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'd also recommend checking out Fuji X Weekly [0] for recipe ideas and example shots if you want some inspiration.
