Wayne Wilson

Updated on my Win10 system with no problems. I didn't try much yet, loaded a raw image and developed it ok.

Thank the developers for this. Yes, the 1.9.1.943 beta fixes the focus merge with opencl enable selected bug. Just curious, should we expect that with opencl enabled the merge would be faster? On my hardware, Win10, i7-7700 and GT-1050 video card, it's exactly the same time to process, enabled or disabled.

Same problem here, disabling opencl is a viable work around. I am using Nvidia, 1050 card with latest drivers, see beta forum where I gave more details and uploaded an image set that I am using to test on.

Go to Preferences, Performance and turn off (uncheck) OpenCL compute acceleration.

Go to Preferences, Performance and turn off (uncheck) OpenCL compute acceleration. It should work for you then. There appears to be a bug in the OpenCl support.

I just tried the .927 beta released 6 hours ago. The OpenCL fix didn't make it into this release.

Ok, I believe the OpenCL support is the culprit here. I disabled openCL and the merge works as expected. Here are my timings: No-opencl ------------------------------ 1:23 (one minute 23 seconds) opencl 4.60 driver 456.71 ------1:32 opencl 4.60 driver 461.4 over -4 minutes before I gave up on it. version 1.8.5.703 with GTX1050 selected -----------1:20 While trying to find out my opencl version, I discovered on NVidia's support site that there was a newer version of the driver package available, this is Nvidia 461.4. Now this installs the same core version of OpenCl, 4.6 but is a newer driver than I had installed (Nvidia 456.71 which windows installed on 1/6/21 but which was released by Nvidia 10/20/20). Curiously enough, the new Nvidia driver said this in it's release notes: "The January NVIDIA Studio Driver provides optimal support for the latest creative applications including Affinity Photo (now with GPU-acceleration) " That statement was what prompted me to upgrade to the latest driver package. Unfortunately, it has rendered the latest beta of photo unusable if opencl is enabled. It's curious that the stable version 1.8 has a different acceleration set of options than in the new beta. I have GTX1050 support enabled. Seems like a step backwards to me.

Well, as a result of my not saving the screen shots correctly, I have now done the jpg focus merge many times. I did two runs, i.e. from a closed program. In the first run, the first merge worked but the second one didn't. In the second run, the first two merges worked but the third failed. That's what this screen shot is from. Curiously it shows a grey main window, a corrupted source thumbnail but a good merged thumbnail in the sources panel and at the bottom in the navigator a good thumbnail. So, I tried to save the image, and it saves as a good image, it just doesn't display anything in the main window. i did some in program edits, just a gray screen. I sent the image out to a photoshop plugin, where it looked good, but came back just gray. very peculiar.

Just got back to this, I downloaded 923 and still have the problem. From the enclosed picture it looked like image 1028 had a problem so I did another merge without that image but still no luck. I will upload these files as you requested.

Enclosing screen shots of the result of focus merge from both jpegs and cr3 raw files, it does not work on my EOS RP.

Focus Merge problem with Canon RP files. I don't know how long this has been going on in the 1.9 betas as I have just recently taken focus stacked shots with an RP. These work fine on 1.8 production but do not work at all on this beta. I have tried both .CR3 files, which really mess up, giving a merged image that is total garbage to .JPG files which almost merge correctly, but leave many large blocks of black and noise in the merged image.