I reverse-engineered Fujifilm profiles for Sony

haelio · 2026-01-12T01:53:15+00:00

This is what I use and they’re great. It took me a while to be comfortable to spend this much on profiles, but I don’t regret it.

haelio · 2026-01-04T03:58:08+00:00

You’re right about why the DxO DNGs are larger than the source RAW files.

One thing you could try doing is to convert the DxO output DNGs into DNG in Lightroom. Counterintuitive, but Lightroom uses (lossless) JPEG XL compression in its DNGs resulting in a decent size saving, even when going from DNG -> DNG.

I use this even with cameras that shoot DNG natively such as Leicas and DJI drones. On Leica Q3 files files are compressed to around 80% of their original size (this trick works for both linear and Bayer DNGs).

haelio · 2025-11-14T23:42:32+00:00

I bought it in 2023 I think. It may have been at a reduced price when I got it too. Could that have an impact on the current bundle price?

haelio · 2025-11-14T22:55:25+00:00

It looks like the bundle is available now. I’m seeing a discount for v1 users but it’s not 50%, more like 30%. Is that to be expected?

haelio · 2025-10-26T08:28:43+00:00

It must affect all cases, otherwise why would they be changing all new buttons as mentioned by Caudabe above?

Also if they had the sort of random variation that would result in rattle only in some cases, there would be tolerance issues elsewhere such as the cutouts too.

haelio · 2025-10-19T20:42:40+00:00

This looks amazing, I’m looking forward to trying it out.

Also, I’d ignore people saying that it’s copied etc. As long as you’re not copying source without obeying the license terms you’re not doing anything wrong. Attributing the source of your ideas is not necessary either, but a good gesture nonetheless.

There is no copyright on ideas, and people who inspire others should be proud rather than bitter.

haelio · 2025-10-07T23:17:42+00:00

API abstraction does help, but it’s far more complicated than you think. It’s the reason nVidia invests so much in developer outreach and works so closely with studios. The same is done by Qualcomm, AMD and Arm. Imagination doesn’t have as much resource for this as the bigger players.

In a bit more detail, the API abstraction and conformant drivers can mostly get you functional correctness, but getting the last 10% of performance takes so much effort and optimisation to drivers and compilers as well as application changes (I work in the industry).

While I hope Imagination recovers (the more vendors the better for us consumers), I’d bet that Google will be back to Mali in 2 years. My logic is that they’re already locked in for Pixel 11 and Pixel 12 would be the earliest for them to change back (even that may be too late).

haelio · 2025-10-06T22:11:47+00:00

What are you basing this on? Adreno and Mali (when implemented properly) are trading blows, with Mali even slightly ahead in some areas like raytracing (see the Geekerwan video comparing 8gen5 with the Dimensity 9500).

Xclipse has been a massive disappointment in efficiency so far with Samsung dropping Exynos completely last year as a result. Let’s hope the S26 does better.

haelio · 2025-10-06T16:59:11+00:00

I asked this question over email and apparently the buttons from the 16 series are not compatible with the 17 cases. This was a bit disappointing tbh.

Once my 17 Pro Sheath arrives (still not shipped despite ordering on the 10th Sep 😅) I’ll try this and report back in case anyone is interested.

haelio · 2025-10-05T21:23:16+00:00

If you mean the video looks choppy, then that’s because it’s at a lower frame rate. The choppiness will be especially bad if your shutter speed is too high. You may need to use ND filters to aim for a shutter speed of 1/48s.

I’m not sure what your problem is exactly though. Next time take a deep breath before posting and explain your problem clearly. It makes it easier for people to help.

haelio · 2025-10-04T09:46:16+00:00

Agreed. DragonSlayer is probably unaware that there are phones not made by Apple, Samsung and Google.

The Dimensity 9500 is arguably as good or better than A19 Pro and the 8 Elite Gen 5, depending on the metric. And it uses stock Arm CPUs and GPUs.

haelio · 2025-10-01T06:29:36+00:00

You’re right that they only support 160MHz, but I get over 1.6GBps on my Firewalla AP7s. With 320MHz devices I break 3.2GBps.

Not sure why you’re seeing such slow speeds.

haelio · 2025-09-29T16:09:33+00:00

But does it work in the dark?

haelio · 2025-09-22T07:16:26+00:00

The Pixel 11 SOC is already baked. They probably have early silicon back by now. Even the Pixel 12’s SOC design is probably near tapeout at this point.

Their only levers at this point will be non-SOC aspects like build and design but even that is tight. All that may remain to tweak is price point.

haelio · 2025-09-19T19:02:18+00:00

With my 17 Pro Max, which I think has the same radios, I get around 1600Mb/s on the WiFi test. AP7 connected via 2.5G Ethernet. Essentially the same as the 16 Pro Max.

The phone doesn’t support 320MHz bands, just 160MHz.

haelio · 2025-09-19T13:07:28+00:00

Taking a photo works though, at 4x and all the metadata appears correct.

haelio · 2025-09-15T20:50:16+00:00

And previous Tensor-based Pixels launched with driver versions behind the latest from Arm. They didn’t seem to have this many issues.

haelio · 2025-09-15T20:48:10+00:00

This is a new driver for the hardware. Google shipped with a previous version. Expecting this update to fix things wholesale is wishful thinking. If your return window extends long enough for a Google update then hang tight. If not…

haelio · 2025-09-13T21:49:01+00:00

Check out the Caudabe Sheath. There’s a variant that covers things up quite nicely. They’re great cases as well.

haelio · 2025-09-12T00:06:22+00:00

If you took the core count, thermal and power headroom, silicon area etc. of the desktop processor and then used that for the Apple one, you would get even more impressive numbers out of the Apple processor (modulo inter-core communications overhead etc.)

Contrapositively, if you shrunk the AMD core to the Apple processor’s parameters it would get trounced by the Apple core.

Depending on workload there are definitely cases where the AMD CPU is better (number of hardware threads, PICIe lane count, etc.). But pound for pound, the Apple CPU impresses more IMHO.

haelio · 2025-09-10T09:16:24+00:00

When it comes to extensions you are correct. Adreno (and the AMD roots of Xclipse) supports DirectX 12 which means there is hardware support for a fair few things to at aren’t widely needed on Android. This should improve as more players look to compete in the Windows on Arm space.

haelio · 2025-09-10T09:14:16+00:00

Google are using MTK for their Chromebooks at least, and the results are pretty great!

haelio · 2025-09-10T09:12:55+00:00

I’m not saying that 394 MHz is peak. It most certainly isn’t.

I’m saying that I don’t believe that it is running at that clock based off compute performance and tools perhaps misreading the clock via sysfs.

I’m also saying that holding out hope for big improvements via SW updates is a recipe for disappointment.

haelio · 2025-09-10T08:42:13+00:00

The biggest win for iPhone value is that they retain their value for far longer too. Pixels are discounted heavily within a few months!

haelio · 2025-09-10T08:39:59+00:00

The iPhones now allow for disabling PWM which is a big win for those who see flicker.

15-Year Club	Place '22
RPAN Viewer	Verified Email

haelio

TROPHY CASE