Paule96

Thank you for the tip. It worked. But still, I guess it should be fixed with hardware acceleration enabled. I mean does it mean that I need to switch always this setting for other work that I do, that really has the benefit of hardware acceleration?

I so far also did a memory dump from the running affinity photo instance that is stuck. (can't upload here, it's bigger then 2 gigabites.) But so far what I can see is that it makes around 30 calls to `ntdll!NtWaitForSingleObject+0x14`, but so far windbg doesn't see any obvious locks. But so many simultaneously WaitForSingleObject calls lock a bit suspicious to me. Also what I can see from the output of `!locks -v` is that some `contention` numbers are really high. (over 9) So basically that says many threads are waiting for another thread to finish it's open 'thing' so they can use it too. In this case 93 Threads. (at 15 pictures) So it looks at least weird. But what I find more weird is that this is something from GDI32. So normally something that should draw a window or so. I mean it can be used for image manipulation but as far as I understand Affinity Photo uses its own library for that. So maybe this information helps the development team in any way.

If I try to use batch job since Affinity Photo 1.x up to 2.x batch jobs never completes if I use parallel processing. Like you see in the following picture I have 15 pictures that I want to convert from `.afphoto` to `.jpeg` files. But it never finishes. Affinity Photo stays just in this state forever. (longest test 15h) Because I saw always here in the forum some issues with parallel processing I was hoping it would get fixed over time. But I have had this issue now so long that I hope someone can take a look. In special because my system has with it's 64 Cores (AMD Threadripper 3970X) enough power to handle 15 parallel tasks. Here some maybe important side notes: - while Affinity Photo is in this state the system idles - while Affinity Photo is in this states the menubar and settings windows work and are accessible - if you try to load another picture into Affinity Photo it show in the upper right corner that the document is loading but also nothing is happening For me, it just sounds like a deadlock in Affinity itself. If needed I can provide the `.afphoto` files. But they are just RAW files from Canon, with slightly editing. (contrast, whitebalance, saturation, maybe size adjustments)

Yes same here. My CR3 files from my Canon EOS R are also not supported...

Hi @Dan C maybe this helps to implement it. I know this is only reversed engineered from CR3 files and not an official supported CR3 description, but it describes a lot of the file content and how to handle it.

@Lee D any updates here? I have tryed the new 1.7.xx Version and this can't open C3 files. (Windows)

@Mithferion Is this only the behavior for Mac? or works this for windows beta too?

Are there any updates to support .cr3 file format?