Affinity Photo Error: 'Metadata could not be embedded'

[RW73]

Affinity Photo Error:  'Metadata could not be embedded'

Hi there,
I am in Germany, so exuse my english.

I bought Affinity Photo V1.9.2 in June 2021.
All went fine.
At 31. Oktober 2021 affinity-photo-1.10.4.exe was installed.
All went fine.
Without travel in 2021 there were only few photos (JPGs from my Panasonic Camera LF1).

Now, in January 2022, I wanted to edit the last photos.
Affinity works ok, but exporting any photo results always in 'Metadata could not be embedded' error.

Installed at 19.12.2021  Win10 21H2.   The reason!!!!??
My Computer:
Intel(R) Core(TM) i7-9700K CPU @ 3.60 GHz
16 GB Ram
64-Bit Operating System, x64 based processor
Windows 10 Home, 21H2, build 19044.1466
Windows Feature Experience Pack 120.2212.3920.0

The situation now:
I open an up to now untouched xxx.jpg, 4000x3000pixel with Affinity Photo.
Then I export this foto directly as xxx2.jpg.
Format JPEG, use document format, Bilinear, not embed ICC-Profil,
Quality 96% or similar, embed Metadata

This result *always* in
'Fehler beim Export in: xxx2.jpg - Fehler beim Einbetten der Metadatei'
Wonderful!!!

Solution - Workaround:
Turn off embedding metadata??? No!!!!

You remeber Serifs PhotoPlus X8 e.g.??

Use it and open xxx.jpg.
Use Affinity Photo and open xxx.jpg. Do all changes you want.
Copy reduced, then Paste the Affinity picture as new layer (german Ebene) into the X8 Program. There delete the Background layer and export the Picture as xxx2.jpg.
Result: all needed Metadata are correct included.
Do this with e.g. 500 fotos and you are very pleased!!!

Serif Photplus X7 / X8 still works absolut ok as well as CyberLinks PhotoDirector, MAGIX PhotoDesigner, MAGIX Photo&GraficDesigner, Canons old Zoombrowser, Panasonics PhotoFunStudio ... you need more??

In the Forum I find several entries reporting about 'Embedding Metadata'.
Some are years old. It seems Affinity has still an unsolved problem with
'Embedded Metadata'.

So please look for a final solution.
Thank you and best regards
 

[Dan C]

Hi @RW73,

Welcome to the Affinity Forums and I'm sorry to hear you're having trouble!

I can confirm that this is working correctly for me, so it may be something already embedded in your images metadata that is causing Affinity to fail. 

Can you please provide a sample image file here, that is showing this error in Affinity when exporting? I'd like to investigate the existing metadata in the image, and see if I can replicate this myself using your file.

Many thanks in advance  

[RW73]

Hi Dan C,
yesterday i saw your reply, thanks.
So of course I immediately loaded a photo and exported it directly - and an absolute miracle - it was exported without any errors!! Marvelous!!

I think you should destroy my message to Affinity.
But I think it must have been a Windows bug!?!

So I will try to show you the timline:
========================================
- June 2021 - I bought Affinity Photo V1.9.2 >> all ok
- 31.10.2021 - affinity-photo-1.10.4.exe  installation >> all ok
- end of Nov - my last works on the october photos >> all ok
- No more works with Affinity Photo because of no new photos
- 19.12.2021 - Win10 21H2 installation
- 1. January week - the Christmas photos are to be worked through
    >> error as discribed
- 11.1.2022 - Deinstallation of V1.10.4
  Restart of the Computer
  Installation of V1.9.2 >> error as discribed
  Installation of V1.10.4 >> same error
- Friday 14.1.2022 - Message to Affinity
- 15.+16.1.2022 - I worked with Christmas photos >> same errors
- 17.+18.1.2022 - Your message + my test >> all works fine ??!!

I add a screenshot showing my update history up today.
Hopefully this may help you to find out what happens.

Thank you very much and my best regards

[Dan C]

No problem at all, I'm very glad to hear this issue has since been resolved for you!

That's certainly strange behaviour, but it's possible that Windows updates was causing Affinity to fail. Many thanks for providing this information, I'll be sure to pass this through to our team internally, should another user report a similar issue.

If you have any further questions, please don't hesitate to ask