I wonder if something about this explains why Fuji RAF files are the only RAW files that make Lightroom struggle.

I never heard the fans on my M1 mac until I started processing those RAF files, they're not even that large but something about them makes Lightroom struggle. And judging by posts on photography forums, I'm not the only one either

I'm not sure what causes the terrible RAF handling in Lightroom, but it's a fairly well-known issue. Lightroom produces so-called "worming" and apparently this is related to the X-Trans sensor which requires a different decoding algorithm. On my end, I can recommend Capture One - the handling here is perfect, though you do have to get used to the UI unfortunately

Lightroom struggles with Fuji's unconventional sensor pattern. Other programs like Darktable, GraphicConverter, Luminar Neo or FastRawViewer don't make fans of my M1 audible.

I moved away from Adobe recently and ended up trying out Affinity Photo. Opening a RAF file would regularly seize my entire computer.

I always wondered if it was a deadlock situation, because it doesn't spit out any overflow errors.

Lightroom still is terrible for fuji raws from a worm standpoint. Almost looks like they use bilinear debayering. Dcraw is night and day better.

It's not just you. From one of the main contributors to Ruby Video[0]:

2024 is the year with the most Ruby talks in a single year, ever! This is the first time we beat the previous all-time record from 2015! Ruby is so back!

[0]: https://ruby.social/@marcoroth/113665539397868492

Nice to see this project here! I've been using it with the Steam API to publish a list of the games I've been playing on my personal website: https://yboulkaid.com/games

I found that separating data from content on a Jekyll site is a really powerful way to have anything from photo galleries, blog entries, book lists, easily changeable menus etc...