pfi

Yes, these crashes, as described above, have only occurred after focus merge. What I do now, is focus merge images, safe the merged image as jpg, reload the image and then do the RGB/16 conversion. and that works fine. I have saved the .afphoto file and I cannot get it to crash when converting to RGB/16. Source images are JPG, from a Nikon Z7

After a successful Focus-Merge I attempted to convert the Document>ConvertFormat from RGB/8 to RGB/16. In 7 attempts (each time with different images) to convert, APh crashed 5 times, crash reports are attached. Hardware acceleration is disabled. My hardware and OS, see signature. No further editing was done before the conversion attempts. When restarted, APh re-loads one image. I have seen these crashes on different APh versions, and as far as I remember, these happened in combination with focus-merge (many of the APh crashes that I have observed, seem to happen after a focus merge). dd884b5b-69a7-44f3-8612-e142107a1d78.dmp 818c90e9-d1e0-4dbd-9d09-79855259ec38.dmp 661c8fbd-b1b3-4068-b6b7-e554ce6887cc.dmp 40f14d60-062b-45a9-bf19-783deead003a.dmp 6c3f054e-e580-46d6-aebb-60ca9f4fd812.dmp

I have disabled hardware acceleration, and restarted APh. I then opened 7 JPG images, have processed 3 of them and closed them, because APh started to run painfully slow (like lag time of 7sec+ to execute any adjustments). No crash (yet) happened in this case. For the image (featured in the attached video) I changed the Document>ConvertFormat>Format from RGB/8 to RGB/16 and got the strange effects that I mentioned in my previous post above (2nd point). The attached image shows my current PerformanceSettings, as well as the Win10-TaskManager top CPU usage - cooling fans running at the highest level by just hovering&moving the 'cursor' over the image while showing the APh PerformanceSettings. (The other image shows the TaskManager performance chart) I am NOT a PC expert, but I have been wondering if my PC configuration is wrong, wrt. CPU allocation, memory allocation, swap file etc. - any help would be appreciated - thanks. Affinity Photo 2 2024-04-04 17-42-22.mp4

Thank you for moving this topic to the right forum. I probably have mentioned the following observations before, but maybe they are worth repeating. - As I keep seeing crashes immediately after start-up or on early activities after startup (I just had another crash on focus-merge and clove action). Uninitialized attributes/variables? - Once APh is stable and I have worked on maybe 20+ images, some weird behavior starts showing, like saturated pixels in the image, or clearly zoned areas (rectangular) of the image suddenly appear different to the rest (like brightness, contrast, saturation..). For me this is usually a sign to save what I can and exit and restart APh. Memory leak?

I agree, normal masking would be image specific. But Luminosity/hue/band-pass masks are applied differently. In my case, I took some photos in a cave, stitched them with Microsoft ICE and processed them with APh. For all images I used the luminosity mask on the brightness/contrast adjustment to brighten up the distant, darker areas, because I could refine the brighten effects with more control than I could with the shadow/highlights adjustment. I then copied and pasted that adjustment+mask to all the other cave images, which worked fine.

(See attached video) I am playing with Filters>HazeRemoval, adjusting Expose Correction and Distance on a separate pixel layer. I turn visibility off -> darker areas of image turn bright ==>OK. I turn visibility back on -> areas that should turn dark briefly turn dark (as they should) then they turn bright again, ignoring the current haze Removal adjustments. I haven't figured out how to show floating APh windows (like the Haze Removal sliders) when screen recording, but the window with the Haze Removal sliders should show on the bottom right corner. Affinity Photo 2 2024-04-01 11-02-32.mp4

Thanks for your reply, Thomas. Yes, I can save it as an asset and it works fine. The asset panel, unfortunately, only 'shows' it as as a blank square, i.e. it's invisible, unless you hover the mouse over it, then the name of the adjustment shows up. I'll check to see if there is a setting to show the asset names in the asset panel.

I know I can do the following with the shadow/highlight adjustment, but this is more a general question. I have a Brightness/Contrast adjustment and added a luminosity filter for the dark areas so I can brighten them up. I add a preset with the adjustment/mask combination. When I then use the preset the mask has gone and the adjustment is applied to the full image. The same seems to be happening if I use the adjustment's Blend options "Source Layer Ranges". When saving the preset and then using it the blend options are reset and the adjustment is applied to the whole image. So, is it possible to save an adjustment with a mask (luminosity/hue/band-pass)? Should I create a macro instead? Are there other options? Thanks.

Again, I am getting so frustrated with APh because it keeps crashing on me. After some time I have been using APh today and I have already had a number of crashes, doing normal things. It frustrates me, because I spend a lot of time editing my images, and when APh crashes it provides absolutely no recovery and I have to start again. I have paid for this software and I have several times reported crashes. I am honestly trying to make APh work for me, but I am getting close to asking for my money back. I am not hearing back from Affinity, other than that my hardware is not at fault and that other people experiencing similar crashes. What can I do, please? Attached the latest crash reports. f56c8d85-112a-497d-abf1-1835db931a01.dmp ccfac932-a06a-4132-b9d0-f2ba0c9b1dde.dmp abe1017f-ad3e-456e-89b6-48e9604957b2.dmp

Not a good start to Affinity-Photo 2.4 - more crashes, more frustration. Downloaded AP-2.4, loaded 4 images, a few adjustments, a few strokes with the clone brush and - crash. Am I the only one who experiences these crashes? And again, I have to ask whether AP is incompatible with my hardware. I just have not had a good run with AP, no matter how hard I try to make it work for me. d3306465-a40d-4875-a96b-aa725119c0d4.dmp

Hi NotMyFault, sorry for the late reply. As I mentioned above, after A-Photo reset (after hardware acceleration setting change) I was not able to reproduce the problem and, unfortunately, I did not save the project before the reset. I am happy to share the image, but I don't think you'll be able to reproduce the issue. btw. My usual workflow is: - run a macro, which makes a copy of the background image and ads my most often used adjustments and filters, most unmodified, some with minor pre-adjustments. - in this particular image I had a few clone brush actions, dodge and burn, and I used the perspective tool to balance up the image. (I am quite suspicious of dodge and burn and clone and heal actions, but maybe that has to do with the 'long' lag) - I then do adjustments - Unsharp Mask and Noise Reduction are usually last - Affinity Photo runs even slower with these two enabled. (I want to add color format RGB/16 to the macro) When weird stuff happens again, I will try to remember and do your suggestions. - thanks

When opening the Exporting Dialog (shift-ctrl-alt-S), the JPEG Quality setting always starts with the default preset (High) or the last selected preset. But it does not retain the last Quality setting, which is not assigned a preset. This is different to previous behavior.

Yes, I have seen it in a release version, but I seem to remember that it happened when using the HSL adjustment. I have changed the hardware acceleration setting - disable/reset then enable/reset. The issue has gone with either setting. But, this reminds me of something I have mentioned in another issue. When I run a photo edit session I have Affinity Photo (AP) running for days and I cannot help but notice that AP, which is already frustratingly slow when cloning, healing or dodging, starts getting slower and deteriorating. AP then shows artifacts like banding, or the issue of this discussion, or in many cases AP crashing, or hanging for 10s of seconds with 'AP not responding'. And now, that I think about it, that was the issue with the just mentioned HSL adjustment. A reset of AP got rid of the issue, and I wonder when changing the H/W acceleration with a subsequent reset fixed this particular issue as well?

I changed Document>ConvertFormat>Format from RGB/8 to RGB/16 and found that sections of the image got darker. See video - cursor follows lines of affected sections. It is repeatable. I have seen this before with other actions/adjustments on other images, so not a regression. Affinity Photo 2 2024-01-22 11-40-25.mp4

I have not used v1, but compared to other (cheap!?) photo editors I am using (FastStone for clone-and-heal, or Sagelight, my old goto-editor), Affinity Photo v2 (now v2.3.0) is frustratingly slow. Cloning, dodging, simple adjustments like Brightness&Contrast have such a lag, that it is often painful to use, even without any sharpening of noise-reduction filters turned on. Am I doing something wrong? Should I be looking for another, more powerful PC, or for another photo editor? Or do I keep waiting for improvements? I am usually not a cynical person, but for an acclaimed (and paid-for) photo editor, I expect smoother operation from Affinity Photo.