HerrBill

I have had regular picture freezing of late. Sometimes, when editing I get the alert ‘Affinity unresponsive’. The only course of action open to me is to power down and power up my computer. I can’t figure out what’s causing this problem but it is very frustrating. I would very much appreciate any suggestions as to solve this issue.

This morning I repeated my edit but this time I saved it as an .af file so i wouldn't loose my work. However when I tried to save as a tiff file the computer froze again. i believe there is a bug somewhere in the update 2.6.3. I hope somebody in Serif picks this up and responds.

Yes, I'm having a similar problem tonight. I had just completed an edit and was in the course of exporting the image as a tiff when the screen froze. I had to close down my computer and as a result lost all my editing. Never had this problem before. I wonder is there a bug in the programme?

Thanks Walt, but as you know I already have a macro recording of my edit flow which works fine. Unfortunately, when I run it in batch processing the final image is a merged one and does not save the individual layer steps to the final image which means I am unable to quickly apply fine tuning to the final image when necessary. This can be a bit of drag. I Presume there is no chance of Serif rectifying this?

Although, I no longer use Photoshop for editing but when I did, I do remember that it was possible to apply a single edit flow to multiple images. If I could apply this to Affinity Photo, it would save me considerable time. Does anybody know whether this is possible and if what the routine is?

Hi Paolo, If there is a mismatch, how do I check it out. Any ideas? Bill

Hi Walt, I have opted to save my edits as tiffs instead of .afphoto. As I use Bridge, which is free, it will allow me to read the tiff format with no problem. As Affinity will also allow me to save layers to the tiff file, I see no further need to save either the .afphoto or raw file. This should save me considerable file storage in the future. Thanks again for your input. Much appreciated. William

Thanks for filling me on the background to proprietary and open file formats. It explains a lot.

I recently acquired 'FastRawViewer' for viewing and culling raw images. In this respect it is really fine utility and a viable alternative to photo mechanic. Despite supporting a variety of image types, the utility does not support the Affinity format. when I queried this with them, i was informed that .Afinity is not an open source. Can anybody shed any light on their motive for not supporting the Affinity format?

My apologies to @old Bruce for inadvertently omitting to mention you in my despatches. I have to add that the assistance that i have received since jointing Affinity photo some years back has been superb. Cheers

Thanks to both Walt and Ldina for your responses. I am now able to record macros on raw images as well as batch processing multiple images. This will save me a lot of time in editing images in the future.

I'm trying to streamline my workflow and tried to record some steps in the develop persons as follows:- After opening the raw file in affinity, I checked that the raw embedded option was active. I then checked the Develop button and went directly to the photo persona. I open the macro and pressed record. I then clicked on the Develop persona and got the alert ‘Please end your macro recording session before using Develop’. Is it not possible to use macro in both the develop and photo personas?

Thank you both for your responses. I much appreciate them. I still don’t understand why Affinity went to the trouble to create duplicate files. Most photographers are the sole users of their computers and there is little danger of anybody else interfering with the saved edits. I now know, from trial and error, that if I want to open a locked file, I simply use the ‘Open Command’ in Affinity Photo and bingo it opens. Anyhow, locked files according to Affinity have a duration of 5 minutes. So what’s the big deal you might ask and rightly so!

I got a reply to the above subject which I quite can't follow. Also the blog was immediately closed down by affinity. Why I Don't know. Firstly, what useful purpose is there in locking a file after a re_edit? A further complication arises because the image on the thumbnail is blanked out by the AF logo which prevent one from quickly recognising what the image content is. Very frustrating to say the least. And in Windows 11, if I right click the image, it simply don't open in AF 2 and a message appears stating the this file not supported. Is there a way to stop this practice from occurring?

I refined an already edited .afphoto image and selected the command ‘Save’ and when I opened the folder it appeared with an ‘afphoto~lock~ file association which is unsupported by affinity photo. Can anybody explained how this came about?.