List of RAW 9 bugs

Question

Created 4d

Replies 1

Boosts 0

Participants 2

Thanks for adding CoreML into the Apple RAW decoder. I'm excited with what it can bring. But I'm having a number of issues with it.

My code base is written in Objective-C, and I'm using my custom MTKView. Now when I enabled RAW 9 support, the render is extremely slow (instant vs seconds). The UI would appear to hang with a spinning color wheel. It feels like CoreML processing is being delegated in the rendering thread, which runs on the main queue. How can I improve performance?
As someone has reported, there is a black horizontal line in the middle of the image. The image that I was testing came from Fuji X-T5.
If I enable EDR (Extended Dynamic Range), RAW 9 stops rendering, and will return ANE error. My app does HDR rendering of RAW files.
I cannot get something like Sony A7R IV ARW image to load. Same ANE error. Is there a memory setting I need to tweak?
When I render the X-T5 image, the colors appear to be overly saturated, which is different from the result of RAW 8. I cannot speak for the color rendering of other types of RAW files.

I was told code base with Catalyst (and perhaps Swift) works without issue, other than being slow (except for large RAW files), but there seems to be an issue with Objective-C?

Answer 1

Engineer OP

Apple

8h

There are some performance fixes/improvements coming in the next developer seeds. For example, one expected fix will allow the draftMode to work in Raw9
I expect this will be fixed in a future seed.
This is unexpected. Can you describe the ANE error log? Does this depend on hardware?
Same as above.
I do not see Raw9 as more saturated then Raw8 for X-T5 images. That said, one online discussion of this was comparing Raw9 to other renderers. Apple's color calibration is typically more saturated than other renderers. That said, is your app setting the CIContext working colorspace? That may cause color shifts.