Tom Lachecki

IPTC defines a set of metadata, which can be "encoded" in various ways - for example, in XMP, or in the older IIM format. This is similar to EXIF, though that is more confusing because the term "EXIF" is used for both a set of metadata, and the EXIF format (similar to TIFF), but similarly you can find EXIF metadata encoded in XMP. Affinity Photo can read metadata encoded inside EXIF and XMP blocks (and prefers to write it into new/exported files as XMP). We do also support IPTC, but unfortunately we currently do not support the IIM encoding format, so the app isn't recognising your metadata and that's why it gets lost. As Walt implied, though we don't "strip" anything from existing files, when you export a document to JPEG that is a whole new file that is built from scratch, so anything the app did not understand will not be recomposed into the new file. I'll report back here if/when we add support for IIM, at which point the app will recognise the IPTC metadata in these images. That's highly likely; XMP is the more contemporaneous transport mechanism of choice. If/when we add support for IIM, it is conceivable that this will only be for reading, and images exported from Affinity Photo will likewise transport IPTC metadata inside XMP.

Ah, excellent - I'll follow up over there.

Hi @jimh12345 - IPTC data should not be stripped from your images, though we don't currently parse IPTC data found in the original IIM transport format. Perhaps your images use that format to store IPTC? Would you be able to provide a sample image (in a ZIP so the forum doesn't rewrite it) so that we can investigate what's going on? We can provide a Dropbox link if you want to keep it private.

Hi @Nightshade, This indicates a problem with the data file used for this service. Looking in the "user" folder (visible at the far right of your screenshot), is there a file named ws.dat? If so, please close the app, rename the file to ws.dat.bak, then re-open the app and try again. If this fixes the problem, would you be willing to send over the ws.dat.bak file for analysis if we provide a Dropbox link? If not, please provide the full path to the Application Support directory shown so we can work out why that data file isn't being created properly. Thanks

An ISO number can be given on a number of different scales, ISO Speed being one and Standard Output Sensitivity being another. If a high ISO Speed were found in the XMP (working around the upper bound for the field in EXIF data) we would be able to report it. So for the most part I think we're showing the correct values in the correct place here, except that we could hide the out-of-bounds, placeholder ISO Speed value of 65535.

We update the lens profiles periodically; in the meantime, if there is a profile from LensFun that you'd like to bring into the app, you can import them. Here is the procedure on desktop: Go to Preferences Choose "Open Lens Profiles Folder in Finder" (Mac) or "Open Lens Profiles Folder in Explorer…" (Windows) Copy your downloaded XML file into the folder Restart the app Then, if the profile is not automatically detected by Develop Persona, you can still select it manually from the Lens Profiles list. Hope this helps!

For what it's worth, LensFun is still a very active project; the community continues to contribute on a regular basis. The last commit was just two days ago!

Just to add to the above, this is also so that you can click through the profiles and preview how your document will look with that profile applied, before settling on one that works for you.

I don't agree with that; the file contains about the amount of EXIF I'd expect straight out of camera, as well as a ton of Sony Makernote information.

Glad to hear it

That's right - loading metadata from XMP sidecars is a relatively new feature, but it is not what Brand is trying to do. It is possible that there was some bug in Brand's version of Affinity Photo that prevented metadata from being recognised in files created by that particular camera, but based on the screenshot it is a very old version, and the metadata is working for me in current versions. 👍

Hi @Brand. This is working for me in current versions: I recommend updating the software to the current version (1.10.1). Updates to 1.x are free.

EXIF data should be imported. If you are using XMP sidecar files, you'll want to check Preferences as Ron has shown. Otherwise, would you be able to provide an example file so we can see why its data is not being recognised? Thanks!

There is an issue in 1.10.0 and 1.10.1 that prevent registration on first launch for some macOS users. This has been fixed for the next release; in the meantime, restarting the app (just once!) will solve the problem.

Unfortunately the lens profiles embedded in raw files are in proprietary formats for which we do not have the definition. We have investigated the possibility of such a feature in the past, but manufacturers are generally reluctant to provide the required information except to a few "favoured" companies. Hopefully in future this may change and, in the meantime, we'll continue pulling new profiles from LensFun as and when they are accepted into the LensFun project.

Glad to hear it

The autofocus-region information is provided by the camera's metadata embedded within the image. It could be that we're parsing it incorrectly for your camera model. Would you be able to post an example RAW file and an indication of what AF regions you'd expect to see instead? Thanks!

Hi Thomas, I can't speak to their quality or accuracy, but there are some pending user submissions to LensFun for this lens: - https://github.com/lensfun/lensfun/issues/1054 - https://github.com/lensfun/lensfun/issues/1404 I have combined them into a single XML LensFun profile (attached). If you go into Preferences > General, then "Open lens profile folder", put the XML file in there, then restart Photo, that data will become available in the app. Hope that helps! Nikkor Z 14-30 F4.xml

Is the error message exactly the same as in the screenshots further up the thread?

This is not an ORF file, but a TIFF file. ExifTool ignores that and just reports the TIFF metadata (and uses the file extension for deducing a mime-type, albeit incorrectly). If you rename the file to .tiff then it will open in Affinity Photo as well. Just naming a file .orf doesn't make it an ORF file. Affinity cannot produce proprietary RAW formats.

Afraid not. It is true that most LCP profiles are those that ship with Adobe products. If you have access to those, and wish to use them, you should of course be sure to abide by Adobe's licensing restrictions/terms & conditions. There may be some "custom" lens profiles online in LCP format, though most are usually found in the LensFun XML format.

Excellent

Hi @araxara. We added support for ACM lens corrections in 1.10.0 so, hopefully, this is working for you now.

No problem - enjoy the app!

Hi Julian, The first character of that key is J, not 3. :)