unecessary colour profile conversion

[stuck]

I have a Nikon CoolScan V ED film scanner.  If I set its working colour space to 'Wide Gamut RGB' then the colour profile of the output scans is described as 'Nikon AdobeWide RGB 4.0.0.3001'.

If I open such a scan in Photoshop, with Photoshop's working colour space set to 'AdobeWide RGB' then the file opens with no warnings.  If I set Photoshop's working colour space to anything other than 'AdobeWide RGB' then Photoshop warns of the profile mismatch.

So far so as expected because 'Nikon AdobeWide RGB 4.0.0.3001' is identical to 'AdobeWide RGB'.

If I open such a scan in Photo 2, with Photo 2's working colour space set to 'AdobeWide RGB' then the file opens with a notification that Photo has converted the file to the working colour space of AdobeWide RGB.

I can see why Photo does that (the profile names are different) but should it not, like Photoshop, be clever enough to know that 'Nikon AbobeWide RGB 4.0.0.3001' is  identical to 'AdobeWide RGB' and thus open the file without any notification?

[Dan C]

Hi @stuck,

Thanks for your report - I'm not personally aware of how Affinity detects and changes Colour Profiles when importing images, like you I suspect that this based on the profile name itself rather than the profile values, but I can understand how this could be improved to be 'smarter', as seen in Photoshop.

Are you able to attach a copy of the 'Nikon AdobeWide RGB 4.0.0.3001' profile, such that I can log this as an improvement request with our developers?

Many thanks in advance

[stuck]

Hi @Dan C ,

Thank you for the quick response.  I looked in:

C:\Windows\System32\spool\drivers\color

which is where I expected to find the Nikon profile but it wasn't there.  I next ran a search for '*.ic*' on my 'C:' drive and again didn't find anything.  I've also done a Google search and not found it (yet).  Thus at the moment the best I can offer you is this JPEG which has the Nikon profile embedded in it.

Does this help?

 

[Dan C]

No problem at all, thanks for providing that for me!

Looking online, this profile may appear under 'C:\Program Files (x86)\Common Files\Nikon\Profiles\' however I have also been able to find a copy of the 'NKWide.icm' available for download - so I will log this with our developers now.

I hope this helps

[stuck]

@Dan C Yes it does help, thank you!

It's also embarrassing though because now you point me at 'C:\Program Files (x86)\Common Files\Nikon\Profiles', you're right 'NKwide.icm' is there.  I wonder why my search missed it?  I also wonder how I failed to find that path when I was searching on-line.  Plus how I couldn't find NKwide.icm for download either!

Moving swiftly on...

When you log this with the developers, please can you include a request that when Photo opens a file and meets a profile conflict that it doesn't automatically convert the file to Photo's working colour space but, like Photoshop, provides options (in PS these are under 'color settings') that allow the user to control what happens.

[stuck]

PS the reason it helps is that I can now copy NKwide.icm into 'C:\Windows\System32\spool\drivers\color' and that then means (temporarily, when I'm processing scans) I can set Photo to use that as it's working colour space and Photo correctly handles my scans.

[Dan C]

You're welcome, I'm glad to hear this helped!

21 hours ago, stuck said:

When you log this with the developers, please can you include a request that when Photo opens a file and meets a profile conflict that it doesn't automatically convert the file to Photo's working colour space but, like Photoshop, provides options (in PS these are under 'color settings') that allow the user to control what happens.

I'll be sure to add this to the request for you