John Sh

!) it would be very handy if one could import macros in bulk, E.g. Dave Strykers large collection. 2) Can we move macro categories into a single overarching category. Again I refer to Dave's collection. Rather than have each category listed separately, drag them into sub categories in a single "Dave" category. and my old gripe, when are we going to see the film strip indexed? It is the only list in Affinity that is not indexed and is probably the most important to be indexed!

I have broached this problem on a number of occasions and it seems that Serif aren't interested or it is too hard. The"film strip", the list of images across the top of the screen, is the only area of Affinity Photo where the images are not sorted. When processing a number of sequential images they are scattered all over the strip. This makes it extremely difficult to process images in order, IE prior to stacking. Even when taking a shot from the overflow area, which is sorted, the next image out is totally random. I have been asking for this to be fixed from version 1 and the only responce from Serif is " we might look at it." Not good enough Serif. Any body that needs to process a sequence of images will thank you for fixing this obvious problem. I am happy to discuss this with you at any time but would be more happy to see it fixed. John Sharples

I have mentioned this problem a couple of times in the past, so here we go again. The list of images across the top of the main window is in random order. If one is working on a series of images, especially prior to a focus merge, it would be desirable to have those image in order taken, rather than placed haphazardly across the page. This area is the only place, that I can find,where images are not in a sorted order. If you are unable to achieve this, send me the code and I will fix it for you! John

After merging has finished you can no longer erase parts of the new, merged, image. Clicking "toggle source image" used to allow the clone brush tool to remove selected parts of the image and controlled by the original image selected. Now this simply displays the selected original without the ability to remove unwanted parts of the merged image. I'm reasonably certain this feature was still available in 2.1.

Thanks Gabe, and thank you all. I'll keep working on it and advise of any info that comes to hand.

Firstly this is not something I would do as a matter of course. It just so happened that I had a stack of 24 files to be focus stacked and I was checking them first. Affinity will focus stack 24 NEF files, loading them in seconds and then align and stack in a few minutes. A 24 shot focus stack is actually quite conservative. 80 to 100 files is common and by no means the upper limit. I would normally do the initial processing and conversion to JPG in Lightroom and then focus stack the jpgs but with such a small number of files I decided to forgo the Lightroom step.

I don't think it has any bearing on this problem but all of my folders are now read only. This seems to have occurred at or about the time of the first lockup but that is pure speculation.

Ok. I've got the event viewer open but can't see, recognise, anything to do with Photo. Is there a way o save this data and forward it to you?

Some more info. Running 1736 beta with 12 files, it opened them in 1:15sec which is comparable with your results. I then ran 2.0.4 and 24 files. CPU between 3 and 17% with the occasional jump to around 30%. Memory between 13 and 14 GB 😄 C drive at 100% The first file loaded after 24 minutes and the last loaded at 36 minutes. The computer was fully operative the whole time but Photo was showing "Not responding" for much of that time. Running 1736 beta with 24 files. CPU at 100% dropping to 80% Memory 14GB 😄 C drive at 100% The first signs of a lockup occurred at 50sec then after another 40 secs the computer was totally locked. Restarted with the power switch. I have uploaded another 12 images. Add them to the previous uploaded to duplicate my test load. _DSC2333.zip

I'm currently running the KB5023773 W10 update so I'll try again tomorrow and report back. I'll also try with hardware acceleration off. Is there a logging system I can activate that might shed some light. Also can you recommend benchmarcking software to check my computer's performance? John

1) your computer must be levels of magnitude faster than mine. I know my machine is not fast but the difference between 40.5 seconds and 15 - 20 minutes could only be described as "considerable". 2) is there some way to set up a fault log if I try it again? 3) what monitoring software are you using?

Photos attached. _DSC2290.zip

The performance settings in both versions are "as they came" so ostensibly the same. Not only does beta crash but it locks up the computer such that the power button was the only option for a restart. I will forward the images once zipped.

First post, didn't read the rules. It seems I used the MSIX file to load Affinity beta in the first instance. The files are stored on a local hard drive, G:\photos\weeds\Cassia\ and I used File>Open to load them. The files range in size from 13.5 to 16.9 MB I used exactly the same procedure to open them in v2.0.4. I'm more than happy to provide any other information they might require.

I am attempting to load 24 NEF files from a Nikon D500. Photo beta crashes after a couple of minutes and the computer freezes. Restart was via the power button. Tried it a gain, same result. I tried the same exercise in Photo version 2.0.4 and the photos loaded after about 15 - 20 minutes and the computer remained operative, albeit a bit slow, while the images loaded. My computer details are on the screenshot attached.