Jump to content

Recommended Posts

Posted

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?

Intel i7-10700 Gen10 CPU, 32GB RAM, Geforce GTX 1660 OC 6GB
Windows 10 Pro 22H2, 1x 1TB M.2 NVMe, 1 x 2TB M.2 NVMe. Affinity APh, APu, ADe

Posted

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?

Intel i7-10700 Gen10 CPU, 32GB RAM, Geforce GTX 1660 OC 6GB
Windows 10 Pro 22H2, 1x 1TB M.2 NVMe, 1 x 2TB M.2 NVMe. Affinity APh, APu, ADe

Posted
7 minutes ago, Greyfox said:

Is there a reason for this?

...and that thread didn't get a response from Serif either.  So is this a lost cause?

Hard to tell, since best answered by the Affinity devs then. - I'm guessing here, that probably some change/update event is missing for the EXIF data, or doesn't throw in such JPG update cases.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Posted

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.

Intel i7-10700 Gen10 CPU, 32GB RAM, Geforce GTX 1660 OC 6GB
Windows 10 Pro 22H2, 1x 1TB M.2 NVMe, 1 x 2TB M.2 NVMe. Affinity APh, APu, ADe

Posted
26 minutes ago, Greyfox said:

That EXIF tag can be used to determine if an photo is an original ex camera, or if it has been edited ...

See therefor related ...

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Posted
53 minutes ago, Greyfox said:

and that thread didn't get a response from Serif either. 

Given that Serif does not comment on requirements in principle, there is nothing to be surprised about.

 

6 minutes ago, v_kyr said:

I personally use ExifToolGUI which makes using ExifTool and managing EXIF in images significantly easier.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Posted
14 minutes ago, Pšenda said:

I personally use ExifToolGUI which makes using ExifTool and managing EXIF in images significantly easier.

Well that's sadly a Win only frontend to ExifTool. - Even there are some MacOS  alternatives, which all are based/do rely on ExifTool, I honestly would prefer to use Phil Harvey's own build GUI frontend then for/under MacOS too!

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Posted

@Pšenda 

I too have been an ExifTool user for some years.

31 minutes ago, Pšenda said:

Given that Serif does not comment on requirements in principle, there is nothing to be surprised about.

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.
 

 

Intel i7-10700 Gen10 CPU, 32GB RAM, Geforce GTX 1660 OC 6GB
Windows 10 Pro 22H2, 1x 1TB M.2 NVMe, 1 x 2TB M.2 NVMe. Affinity APh, APu, ADe

Posted
57 minutes ago, Greyfox said:

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.

Serif does tag images processed with their software, Affinity, along with the specific version of that software, in the Exif, Raw Data. It's found at the bottom of that data. The screenshot is showing the Raw Data, from an image I shot, and processed in AP, and exported to JPEG. I researched images I shot from 7-10 yrs ago, looking at that field in those files, and it too had the software I used to process them. It's not found in the EXIF table you first see, in fact I think most software does not publish that info there.

exif_rawdata_AP.jpg

Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win11 Home Version:24H2, Build: 26100.1742: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD; Wacom Intuos 3 PTZ-431W

Posted
6 minutes ago, Greyfox said:

Sorry I don't understand what that means.

It's quite simple - you're surprised that Serif doesn't react/respond to "requests" for features, which it doesn't do in principle - it simply doesn't respond to feature requests and doesn't promise anything.

The fact that he has not yet implemented the mentioned function is a different matter, and it has nothing to do with "not responding" to requests.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Posted
54 minutes ago, Ron P. said:

Raw Data

I just exported in APhoto to JPEG, and this is what its Metadata looks like.
image.png.a36232080df7e8aacdd2ef7d76694616.png

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.5.7.2948 (Retail)
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 24H2, Build 26100.2605.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Posted

Yours has no History section, which is where that data is entered. The photo from my screenshot, I did not choose to save history with my image/document. So AP done that on it's own.

Affinity Photo 2.6..; Affinity Designer 2.6..; Affinity Publisher 2.6..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win11 Home Version:24H2, Build: 26100.1742: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD; Wacom Intuos 3 PTZ-431W

Posted
3 hours ago, Ron P. said:

Yours has no History section, which is where that data is entered. The photo from my screenshot, I did not choose to save history with my image/document. So AP done that on it's own.

I get the History metadata item if in the Export panel I enable "Embed Metadata." If I do that, I get a raw data item like <xmpMM:softwareAgent>Affinity Designer (Sep 22 2019)</xmpMM:softwareAgent," in this instance for a file I last modified in AD 1 on that date.

All 3 1.10.8, & all 3 V2.6 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
A
ll 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Posted
10 hours ago, Greyfox said:

…further searches I made show this subject was raised in February 2018 …So is this a lost cause?


Even earlier than that, I mentioned it in January 2017 (a few weeks after it was released on Windows) in the below post about the "Date Taken" field.

 

 

The problem is, although Affinity Photo adds the software name to the file metadata, it adds it to the following metadata tag.

[XMP-xmpMM] HistorySoftwareAgent

While there is nothing wrong with adding it to XMP Media Management metadata, it's not much use if other software (DAM, Windows File Explorer, etc.) is looking for that metadata in the below metadata tag instead and therefore doesn't read it.

[IFD0] Software

Screenshot:

Exif.thumb.png.f67c0e0f29abb8b7314db15c6bd03f8a.png

 

Posted

@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.

 

Intel i7-10700 Gen10 CPU, 32GB RAM, Geforce GTX 1660 OC 6GB
Windows 10 Pro 22H2, 1x 1TB M.2 NVMe, 1 x 2TB M.2 NVMe. Affinity APh, APu, ADe

Posted
3 minutes ago, - S - said:

While there is nothing wrong with adding it to XMP Media Management metadata, it's not much use if other software (DAM, Windows File Explorer, etc.) is looking for that metadata in the below metadata tag instead and therefore doesn't read it.

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.

 

Intel i7-10700 Gen10 CPU, 32GB RAM, Geforce GTX 1660 OC 6GB
Windows 10 Pro 22H2, 1x 1TB M.2 NVMe, 1 x 2TB M.2 NVMe. Affinity APh, APu, ADe

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.