@martbetz Thank for the quick reply. I’m an iOS Developer by trade. I went ahead and cloned the repo and built 5.9 development branch for now until the macOS version is released. It was pretty straight forward (once I resolved some of the dependencies via Homebrew). Unfortunately, I think support for the Fujifilm X-T5 will most likely have to wait until Apple updates their Digital Camera RAW support to support the X-T5. The last Fujifilm X series camera supported is the X-T4 and with the caveat that it only supports uncompressed RAW files Not sure if I can look into the dcraw library and hack it to support the X-T5 without the Apple OS Support. But, from what I read about RAW support for the Fuji cameras in RawTherapee, is that it also only supports uncompressed RAW files from Fuji cameras (due to a limitation with draw perhaps). I guess, for now, I’ll convert all the RAF files from the X-T5 to DNG using Adobe DNG Converter. It’s a bit of extra storage on my cloud drive, but at least I’ll be able to edit on my iPad using Adobe Photoshop.
UPDATE: So, it appears that, as long as I don’t compress the RAW file, RawTherapee does in fact allow me to process the X-T5 RAW files. Yay!
UPDATE 2: Also discovered, for all you X-T5 owners, that X-T5 RAW Lossless Compressed files also open without a problem. The only one that it had a problem with is the compressed version, which is lossy and, well, when shooting in RAW, why would one ever want to use that Sure the file size is about half of the lossless, but don’t we shoot in RAW to gain the most accurate pure digital negative of our captures? Anyway, all good news.
I don’t think RT depends on any macOS component for raw support, as you found out
As mentioned above, you can probably try to add better support to X-T5 by hacking away at the camconst.json file: you can for example use the values from the darktable/rawspeed support table, they should have a 1:1 correspondence. (And these are identical for the X-H2 btw.)
I think it would be wise to postpone translation. There is a more urgent need to bring the current documentation fully up to speed with the currently released version and all its features, and to do general editing on the text.
If you are willing and able to help with that, it would be much appreciated.
@marter I can give you access once you register, see “How To” Translating RawPedia - RawPedia but what do you want to document? The information entered in RawPedia must be technically correct, and that often requires understanding code.
@Morgan_Hardwood , Thanks for your answer. As i realised, a lot of the documentation for RT5.9 already exists in other languages but not in german. I was considering, to copy those pages and translate them into german, to complete the german part of rawpedia as a start.
Did i understand correctly, that your link tells me to ask for access here in this forum?
Edit: when registering, i get a php- error message:
Thank you for releasing this new version. I was wondering, will there also be builds optimized for more modern CPU architectures like Zen 3? I found one link in the Rawpedia download section pointing to builds from André Gauthier / gaaned92. It seems he used to build previous versions for several different architectures, but for 5.9 there is only a “Skylake” version for download. Any ideas?
Because I have to install from source (chromebook… it’s complicated…) and I simply do not understand git or its idiosyncracies I’m having to rely on the build-rawtherapee script to do the job - which it doesn’t because it hasn’t been changed from the dev stream. So it tells me there’s nothing to do and a string of instructions which I don’t understand…
It could take 2 minutes to compile, it could take 30 minutes. Depends on your hardware and compilation settings.
Do not abort the compilation process if you think it “hangs”. It’s not hanging, it’s just working in the background.
If you run into any more problems, please open a new topic so we don’t hijack this one, and make sure to paste a log of all your console commands, as well as the full compilation log if there are issues compiling.