Greyfox

Done - RAW image from Sony SLT-A57 camera with DT 18-135mm f3.5-5.6 SAM(SAL18135) Lens uploaded to your link.

@walt.farrell @R C-R Thanks you both.,

I wanted to create a custom template for A4 documents that had my choice of font, font size, the text style defaulting to Body etc. And so I opened the help file, typed in template, and selected Document templates. And I was confronted with a screen shot that is obviously a Mac screen. Surely it can't be that much of a problem to use screen shots of the actual version in the help file. On to the para "To set up a target template folder" and it says "From the New Document dialog with Templates selected from the left side. Click Add Template folder." In the Windows version it is in the New dialog (accessed from the File Menu), not the New Document dialog. The New dialog does have a Templates button on the left hand side, but there is no "Add Template folder" visible, just a tiny, tiny icon? that on my 1920 x 1080 screen looks nothing like a folder. Fortunately the cursor wandering over it did bring up an Add Folder tool tip. So perhaps the help file could use some TLC. I've taken a punt and created an "Affinity Templates" sub-folder in my Documents folder, and I have exported a custom template to that. I don't know whether that is the best place to store templates for this new version. I would have preferred to have used a custom Preset from the File\New dialog because templates are too easy to save over, but the Presets don't appear to allow for the inclusion of a font type, font size, or allow me to have the new document default to Body style. Any suggestions welcome.

That is exactly my problem. What I don't know is why Affinity is not updating TAG 135. Is it not working as it should, is it an oversight or is it by intention. Only Serif Developers would know.

@R C-R @Ron P. Thanks for your input. I am aware of Affinity's use of the xmpMM:SoftwareAgent tag but unfortunately that tag isn't recognized by my asset management software. The more commonly used EXIF IFD Software TAG 305 is. and Tag 305 is supposed to be updated when the image has been rotated, trimmed or retouched.

@Pšenda I too have been an ExifTool user for some years. Sorry I don't understand what "requirements in principle" means. The use of that field is common practice in many applications, Photoshop, Gimp, ACDSee, Luminar 4, Microsoft, to name just a few. Is the fact that it isn't being updated in Affinity Photo a bug (in that it should be updating but for some reason isn't)? Is it by design for some reason? Or perhaps it is an oversight. Are you suggestion that Serif don't answer Support queries if they appear to be "a requirement in principle", what ever that actually means. - That has not been my experience with them in the past. It is a field I use in searches in my Asset Management system. It can be used with other software, and I would like to be able to use it with Affinity.

Thanks for response @v_kyr. That EXIF tag can be used to determine if an photo is an original ex camera, or if it has been edited, by what software. It is also a means of identifying what software created an image, or at least it is with most other photo editing software. I don't understand why Serif chooses to ignore it.

In addition to no response so far to my query (and it was now so far down in the forum pages that it wasn't likely to get a response), further searches I made show this subject was raised in February 2018back in 2018 ( and that thread didn't get a response from Serif either. So is this a lost cause?

Most of the other photo editing software I have identifies its use in the EXIF Software field when a change is made to a JPG image, however that doesn't appear to be the case for Affinity photo. Is there a reason for this?

Thank you, worked like a charm. 😃

I had Affinity Photo, Designer and Publisher 1 set in Window 10 Pro Graphics Settings to use High Performance. Now I have the three V2 applications, the browse button in Windows 10 Pro's Graphic settings seems unable to find the new versions. Is it no longer possible to force high graphics performance with the new version, or is there a work around?

Current version 1.0.9 of Topaz Photo AI is working quite OK here as plugin with Affinity Photo V2

Can anyone tell me exactly what version of Lensfun is currently in use in the Photo V2.0.0 installation?

The previous version Affinity Photo 1.10.5.1342 has no problem automatically selecting the correct lens profile for RAW images from my Sony SLT-A57 camera with DT 18-135mm f/3.5-5.6 SAM lens. V2.0.0 however says "A lens profile for this image could not be selected automatically". There is a DT 18-135mm f/3.5-5.6 SAM lens profile in the pull down list, but the program won't select it automatically. Is this a bug in the new version, or is there something I need to do to get the lens profile selected automatically? Windows 10 Pro, 22H2 build 19045.2251 Intel i7-10700 CPU 32GB RAM GTX1660 OC 6GB Graphics. Edit: I have managed to get a work around. The issue appear to be that the Lensfun database being used by V2 for the Sony SLT-A57 shows the lens as as simply "DT 18-135mm f/3.5-5.6 SAM", where as V2 is displaying it at the top of the Develop screen as "DT 18-135mm f/3.5-5.6 SAM (SAL18135). By placing a Lensfun xml file modified to add the "(SAL18135)" to the lens model in the Lens Proiles folder, V2 now automatically applies the Lens correction to the RAW images.

The bat file work around also doesn't work from ACDSee Ultimate. It too requires an exe file. I wish I had know about this before I purchased the Universal licence. My bad, I usually take advantage of the free trial, but in this instance I didn't. Edit: OK, have now seen the post from footeg and that has got it working with the batch file. On the other hand, the launcher doesn't work - Opens Photo but fails to open the image.