Tom Lachecki

I agree with the comments above, the selector should give me full control in case of manual selection. Maybe for the automatic detection more data is required, but manual settings have to be independent from exif. I just used exiftool to give you some information to work with. Nevertheless, it seems to make progress. Good job guys, thank you for taking care!

After determining the lens profile to use (be that automatically, or by manual selection), the resulting correction information still needs adjusting to account for focal length & aperture being different to when the correction data was generated.

Unfortunately, many fixed-focal-length lenses don't report that focal length to the camera, so the information is not in the image metadata. In those specific cases we can actually take it from the name of the lens instead, which we'll start doing in a future build (thanks for the report, @larsbre!).

A more general solution to missing metadata (e.g. when using a non-electronic zoom lens) would require sliders or similar in the Lens Correction panel.

Hi @larsbre,
For the lens correction to work, we would need a couple more arguments, not just -LensModel. 
exiftool -Lens="Samyang 12mm f/2.0 NCS CS" -LensModel="Samyang 12mm f/2.0 NCS CS" -ApertureValue="2.0" -FNumber="2.0" -FocalLength="12" FILENAME 
This should work on that specific Lens. I will pop an improvement in and see if we can work around this "issue" with manual lenses. 
However, modifying metadata can be dangerous/destructive (and we take no responsibility for the use of exiftool!)

Thanks; I lurk

After determining the lens profile to use (be that automatically, or by manual selection), the resulting correction information still needs adjusting to account for focal length & aperture being different to when the correction data was generated.

Unfortunately, many fixed-focal-length lenses don't report that focal length to the camera, so the information is not in the image metadata. In those specific cases we can actually take it from the name of the lens instead, which we'll start doing in a future build (thanks for the report, @larsbre!).

A more general solution to missing metadata (e.g. when using a non-electronic zoom lens) would require sliders or similar in the Lens Correction panel.

A lot of work has been done for 1.8 changing the EXIF panel into the Metadata panel, where editable elements are editable and read-only elements are presented. We look forward to your feedback during the forthcoming beta cycle

After determining the lens profile to use (be that automatically, or by manual selection), the resulting correction information still needs adjusting to account for focal length & aperture being different to when the correction data was generated.

Unfortunately, many fixed-focal-length lenses don't report that focal length to the camera, so the information is not in the image metadata. In those specific cases we can actually take it from the name of the lens instead, which we'll start doing in a future build (thanks for the report, @larsbre!).

A more general solution to missing metadata (e.g. when using a non-electronic zoom lens) would require sliders or similar in the Lens Correction panel.

Then I think you are going to like the forthcoming 1.8.0 Photo beta and the EXIF Metadata Panel

Hi Dan C,
I've just used DDU and updated both my graphic cards drivers (Intel P630 that I use and AMD Radeon RX580 that I don't use).
I'm attaching the before and after drivers status.
Now Affinity Photo is working!
Thank you very much for your very professional support!!!

Hey Michail,
We first found this internally but we aren't too sure what the cause is  
We can workaround it by copy and pasting the install directory location into the .exe 'Start in' box.
So, locate your beta shortcut .exe (in my example I'm using Photo) and right-click > Properties > Shortcut. Now you will see the 'Start in' box. Just copy and paste the app install directory into that box, for example - C:\Program Files\Affinity\Photo Customer Beta

Thanks for uploading the profile. I've compared it against the standardised sRGB profile, and whilst the RGB primaries are the same, the white point is not. Because the white point is defined in the sRGB standard, it means the Canon profile is not an official sRGB profile (regardless as to what they name it). Our understanding of the metadata field in question, is that you should only set it's value to "sRGB" if it's the official sRGB profile.

The 1.7.3.481 release fixes this problem. Once again, the Affinity crew shows why we buy their products.

Thanks for your help! Everything worked fine. 

Hi @HYR,
There's no guarantees it's the exact same issue - if you don't mind providing the file I will add it to the log/report to be checked as well - there's nothing to lose. Here's the upload link. Thank you.
---
Hi @design.stuff,
I or someone else from QA should update this post when the bug report is closed as fixed (currently it's marked as fixed but still open/have to pass QA tests).
Regarding trialling the app again, no, that's not correct - this fix will be included in the upcoming v1.8. You should be able to install/test the trial again (v1.8) without issues (we reset it for all major releases so everyone can try the new features).
Your file also doesn't open in the previous version (1.6.11). PSD, PSB's are not fully documented formats and as such we can't guarantee fully compatibility with them nor that there will be no issues when trying to open them. Adobe updates/make changes to their formats from time to time so they end up being moving targets - some of these changes may cause issues when importing files into Affinity.
This issue in particular doesn't affect all PSB files and shouldn't cause more problems in future imports, however as stated above we can't guarantee full compatibility in all cases. We are continuously improving our import/export routines to deal with the issues reported by users as best as we can and provide the best PSD support possible.

Hi @DrQ Just to update here, turns out we already had an issue like this logged with another Canon lens.  This should be fixed shortly  

Thanks Dan, good bughunting! :-) I can confirm that unchecking "Convert opened files to working space" resolve the problem in 1.7.2.
Attached is the LG HDR 4K.ICM File.
LG HDR 4K.ICM
Dirk

Hi nomi02118
The file is a panorama merged in Lightroom but we are treating it as an out-of-camera RAW file and applying lens profile corrections when we shouldn't. As a work around, in Develop go to the 'Lens' page and turn off chromatic aberration correction and the other lens profile corrections.
Hope that helps
Justin 

Thanks for that, it's likely the app is creating its own thumbnails, as can be seen from the following it certainly has the ability to in-app

One of our developers is already looking into this as an option when exporting - provided it doesn't clash with the export architecture - we certainly hope to add this into a future update, but I can't offer any guarantees currently, my apologies!

FITs compatibility is hugely important for Astro photography post processing. A lot of amateur astronomers grudgingly use photoshop as there is not suitable alternative. Affinity could fit in to this space if necessary tools are provided such as fits support and macros /tools more specific to Astro photography. 

Hi BC15
I've logged this with our developers as I'm not certain if our choice to not embed an EXIF thumbnail was intended to keep file sizes as small as possible. If this was intentional I've requested an option be added at export to embed an EXIF thumbnail if required. I hope this helps!

On the mentioned "Transport Layer Security (TLS) best practices with the .NET Framework" we can also read:
So I think AP should simply set TLS 1.2 if it detects it runs on Windows 7. I believe it's a pragmatic solution.

@R C-R thank you kindly for that info. I really confused the two lol. This helps. 
@Dan C That worked!!! Thank you so much for helping me with tthat and thx for the link. I'm eager to really get going. 

Hi guys, could you both upload a raw file into this private Dropbox folder so we can investigate?

Apologies, thanks for confirming that!
With these fix lensed cameras, RAW support & lens support differ from 'standard' RAW files - as the lens correction data is actually embedded in the RAW file itself.
We've recently been provided the spec to open and process the RAW image, however Panasonic have yet to provide us with the necessary information to read the embedded lens correction, meaning we cannot apply any correction to the image at this time, my apologies.
We hope to be able to include support for embedded lens correction in the future, however we have no timescale for this currently as it depends on external sources. I hope this helps  

Just did a group of 100 RAW/NEF pics, processed, cropped, tone mapped and custom exported. I used to be able to get some coffee drinking done and checking email etc. during each stage! Now APh is TOO FAST! I'm not even getting my coffee consumption where it needs to be! 
Thanks for getting this version working so much faster!