Jump to content

Recommended Posts

Hi,

this is an old problem still present :
- image developed in Affinity Photo beta 243 and passed to Persona Photo,
- Color Efex call by the filter menu,
- the image appears desaturated in the Color Efex window without filter actived.

AF beta 243 - Color Efex.jpg

Share this post


Link to post
Share on other sites
3 hours ago, MEB said:

Hi laurentia,
This is a known issue as you noted. Unfortunately there wasn't progress here, sorry. I will bump our report/link to this thread to bring this to devise attention.
Thanks.

Hi MEB,

yes, I reported it in november 2017 ... Thanks for bumping this !

It's redibitory for some users ...

Share this post


Link to post
Share on other sites

Yes, I also reported the plug-in colour management issue when I bought the first version of AP for Windows in Dec. 2016. It's not just the Nik Collection but all the plug-ins that I have (Nik, Topaz, Noiseware, PortraitPro) lose the embedded colour profile when started from Affinity Photo. Those same plug-ins work fine when started from other applications or when using them in the standalone mode.

Here's a simple test to see what's happening:

  1. Go to this colour-management test page hosted by the author of the profiling program DisplayCal: http://displaycal.net/icc-color-management-test/
  2. Scroll down to Test No. 1 and right-click and save the first jpeg photo (the grey square).
  3. Open the jpeg in AP -- it should display a grey square. Non-colour managed programs which disregard the embedded profile show a red square, not grey.
  4. Invoke any plug-in that you have and you'll see that the grey square is now red (colour-management test failed).

Why matters

Share this post


Link to post
Share on other sites
1 hour ago, sankos said:

Yes, I also reported the plug-in colour management issue when I bought the first version of AP for Windows in Dec. 2016. It's not just the Nik Collection but all the plug-ins that I have (Nik, Topaz, Noiseware, PortraitPro) lose the embedded colour profile when started from Affinity Photo. Those same plug-ins work fine when started from other applications or when using them in the standalone mode.

Here's a simple test to see what's happening:

  1. Go to this colour-management test page hosted by the author of the profiling program DisplayCal: http://displaycal.net/icc-color-management-test/
  2. Scroll down to Test No. 1 and right-click and save the first jpeg photo (the grey square).
  3. Open the jpeg in AP -- it should display a grey square. Non-colour managed programs which disregard the embedded profile show a red square, not grey.
  4. Invoke any plug-in that you have and you'll see that the grey square is now red (colour-management test failed).

Hi sankos,

glad to meet you here.

Yes, you have been faster than me and unfortunately without more success ... I have to insist that I know some users who have given up Affinity Photo because of that!
There is not a plethora of reasons for this problem : it is enough to display a picture defined in a very large and unspecified space in a smaller space: the desaturation is purely mechanical. This is typically a color management problem.

Share this post


Link to post
Share on other sites
5 hours ago, laurentia said:

Hi sankos,

glad to meet you here.

Yes, you have been faster than me and unfortunately without more success ... I have to insist that I know some users who have given up Affinity Photo because of that!
There is not a plethora of reasons for this problem : it is enough to display a picture defined in a very large and unspecified space in a smaller space: the desaturation is purely mechanical. This is typically a color management problem.

Yes I can confirm that. Nik Plugins are very important for me too!

Günter

Share this post


Link to post
Share on other sites

I am writing this post just to let AP dev team see how important this bug is, at least for me...

I am currently evaluating AP - deciding whether I can end my CC subscription and bind myself with Serif.

This bug is going to make me stay with Adobe, since I planned to complement AP with plugins in case if I run into any missing / lesser implemented functionality for the time being, until AP matures.

More robust plugin integration would certainly make me buy AP license and stay loyal for many years while AP would be ramping up their system  

Share this post


Link to post
Share on other sites
19 hours ago, PaulAffinity said:

Why not edit in AP and then Call NIK externally, assuming you do clean up in AP and creative in NIK...

It's a dirty solution for this problem.

Share this post


Link to post
Share on other sites
10 hours ago, makspyat said:

Some plugins don't have a standalone version (most Topaz plugins do not).

They used to have independent plugins before Topaz Studio's introduction and a few are still available from their site. The others were already integrated in Topaz Studio itself but you can still access them running Topaz Studio as a standalone program.

Share this post


Link to post
Share on other sites
11 hours ago, MEB said:

They used to have independent plugins before Topaz Studio's introduction and a few are still available from their site. The others were already integrated in Topaz Studio itself but you can still access them running Topaz Studio as a standalone program.

Note that all Topaz Plugins can be run from Affinity Photo and the products that have been migrated to Studio will appear in the Topaz Studio plugin list such as this screenshot:

 

Topaz Plugins AP.jpg


Win 10 x64 System with Intuos Pen & Touch
 - Sys : Intel® Core™ i7-7700HQ CPU @ 2.80GHz (8 CPUs), 16GB RAM
 - GPU 1: Intel HD Graphics 630, GPU 2: NVIDIA GTX1050, 4GB

 

Share this post


Link to post
Share on other sites

Some note wrt DXO Nik plugins
I've seen that all plugins work are working in Affinity Windows except Vivenza2.
The color issue is there when AdobeRGB files are used. Once converted to sRGB colors are correct for all plugins except Vivenza2
Vivenza 2 also works, but in Vivenza you get wrong colors. Once back to affinity, the colors are correct, but in practice it is a nightmare to correct here.
However, I've noticed Vivenza 2 works correct within Affinity with lower resolution images. (I used a file from my old D70s, and Vivenza did show an issue.!)
So I tested some more, and found that Vinvenza is working correct with my 6MPix images (D70s).
I also changed color depths, because the D70s is using 12 bit color depth, and the D750 14bit, but this made no sense. I only found a dependency w.r.t. resolution.
The D700 (12mPix) and D750 (24MPix) images did not work correct. This is reproducible.!
I guess the issue has to do with the color pallets Affinity sends through... 
 

Share this post


Link to post
Share on other sites
Posted (edited)

I hope that Serif will fix integration with plugins and I hope that they will implement Live plugin filters. I can't see myself having to restart adjustments in a plugin every time from scratch. Photoshop does it really well with smart objects.

On a aside note I want to say that I am very impressed with Affinity Photo and I completely get how much work it takes.

I believe in AP and I want someone to bring healthy competition to the imaging, therefore I canceled my Adobe CC subscription and went with AP license.

Edited by makspyat

Share this post


Link to post
Share on other sites
13 hours ago, WMax70 said:

Some note wrt DXO Nik plugins
I've seen that all plugins work are working in Affinity Windows except Vivenza2.
The color issue is there when AdobeRGB files are used. Once converted to sRGB colors are correct for all plugins except Vivenza2
Vivenza 2 also works, but in Vivenza you get wrong colors. Once back to affinity, the colors are correct, but in practice it is a nightmare to correct here.
However, I've noticed Vivenza 2 works correct within Affinity with lower resolution images. (I used a file from my old D70s, and Vivenza did show an issue.!)
So I tested some more, and found that Vinvenza is working correct with my 6MPix images (D70s).
I also changed color depths, because the D70s is using 12 bit color depth, and the D750 14bit, but this made no sense. I only found a dependency w.r.t. resolution.
The D700 (12mPix) and D750 (24MPix) images did not work correct. This is reproducible.!
I guess the issue has to do with the color pallets Affinity sends through... 
 

Hi WMax70.

In fact, I tested an image of D800 in sRGB jpeg and I have the same desaturation in Viveza 2 ... but I saw on the contrary a super saturation of the same image in DFine 2 ... It's correct in Color Efex 4.
Despite this, there is no question of converting to sRGB in the processing flow. sRGB conversion is done at the end of the processing for the web outputs.

Share this post


Link to post
Share on other sites
11 hours ago, makspyat said:

I hope that Serif will fix integration with plugins ...

Hi,

I hope so ! I canceled my CC subscription in november 2015 ! And I still use old licenses ... but I wish to definitely switch to AP.

Share this post


Link to post
Share on other sites
5 hours ago, laurentia said:

Hi WMax70.

In fact, I tested an image of D800 in sRGB jpeg and I have the same desaturation in Viveza 2 ... but I saw on the contrary a super saturation of the same image in DFine 2 ... It's correct in Color Efex 4.
Despite this, there is no question of converting to sRGB in the processing flow. sRGB conversion is done at the end of the processing for the web outputs.

I re checked my statment and tested it again, and I found that I do not have that problem you discribe, maybe because I take an other route to go in affinity. Or again a resolution difference you and I have (I'm using the D750). As told before, my old D70s shots work well with Vivenza2 and affinity.

However, 
I start in Nikon NX-D, there I set / change all my camera setting (I use raw) and I can use the built in U-point in NX-D for local adjustments.
From here I port the file (as tiff) to Affinity.
I stopped importing RAW in affinity, because it was often way off from what I get when starting at Nikons NX-D.
Additionally I can use the Nikon built in Vivenza2 kind of, and if I really need Vivenza, I also can start Vivenza2 from NX-D before I move to Affinity. 
Using this flow, you'll see that it makes a different using AdobeRGB of sRGB within Affinity icmw the DXO plug-ins. 
It has nothing to do with DXO, because using the plugins started from NX-D, the DXO plug ins work fine, as well with sRGB and AdobeRGB.

1ste picture:  sRGB, started at NX-D, then from NX-D ported to Affinity. Here I started Color effects and as you can see, it matches pretty well. Colors are at least close.

SRGB_D750_Tiff_import_from_NX-D.thumb.JPG.f4ab94ee970b439d79e19f42629d4043.JPG

 

I repeated this for all (color)plug-ins to show you the behavior.
Analog effects: 
SRGB_D750_Tiff_import_from_NX-D_AE.thumb.JPG.bb3e4af6778232d87091258cf7df5295.JPG


Dfine2

SRGB_D750_Tiff_import_from_NX-D_D2E.thumb.JPG.6866bdcd09b4ab221d15abf76a3b0896.JPG

 

Then I did the same, just importing the NEF direct in Affinity, and started color effects again...
and now a bigger color mismatch could be seen...!
Having the screen-capture is it less good to see but look at eg the door and the yellows.


SRGB_D750_Tiff_import_from_NX-D_CE_AffIn.thumb.JPG.89edd7ff09d8135d43a6be117af35e4e.JPG
 

However, no matter the flow... if I start Vivenza2 from Affinity... I really get something which is way off. (not really usable)
SRGB_D750_Tiff_import_from_NX-D_V2.thumb.JPG.84262afd09c1494b6a23d7ffdaea9383.JPG

 

All pictures are from source. Nothing was corrected upfront. That's why you see also differences between the NEF. The first are comming from NX-D, the second from Affinty.
I learned, Affinity cannot handle Blue / purple correct using RAW import. That is really awe-full in affinity.

I'll show you later some differences on a night shot with blue-purple lights.
 

Share this post


Link to post
Share on other sites

As promised.
@Affinity, I'll upload the original NEF file. You can test it yourself.

Affinity NEF import
RawImport_Affinity.thumb.JPG.5e92c85c1318745200a93235b3a1a9a6.JPG

 

NXD-Raw import to AffinityRawImport_NX-D_to_Affinity.thumb.JPG.234fd0f2451fcd88ae3cccca39c72478.JPG

Share this post


Link to post
Share on other sites

@ WMax70,

I have never developed in Affinity, the lack of camera profiles is redibitory for me. I only use Affinity as a bitmap editor. I'll do tests again later ...

Share this post


Link to post
Share on other sites
9 hours ago, laurentia said:

Hi WMax70.

In fact, I tested an image of D800 in sRGB jpeg and I have the same desaturation in Viveza 2 ... but I saw on the contrary a super saturation of the same image in DFine 2 ... It's correct in Color Efex 4.

There are my last screencopies with a 8bits sRGB jpeg and Viveza2, Dfine2 and Color Efex 4. Only Color Efex 4 displays the right colors ... I precise that I use the DxO suite, I don't have the free Google suite anymore. And I use wide gamut monitors ...

with Viveza : desaturate

with Dfine : super saturate

with Color Efex4 : good

see the orange seat ...

AF b258 - CEfex4.jpg

AF b258 - Dfine2.jpg

AF b258 - Viveza2.jpg

 

I also precise that with the same image in my old CS6 and the same plugins, I always have the same good colors as the original. It's unfortunately unusable because the corrections are done on the image displayed by the plugin.

Share this post


Link to post
Share on other sites
On 3/9/2019 at 2:44 PM, WMax70 said:

As promised.
@Affinity, I'll upload the original NEF file. You can test it yourself.

Affinity NEF import
RawImport_Affinity.thumb.JPG.5e92c85c1318745200a93235b3a1a9a6.JPG

 

NXD-Raw import to AffinityRawImport_NX-D_to_Affinity.thumb.JPG.234fd0f2451fcd88ae3cccca39c72478.JPG

@WMax70,

I think it's a problem of non-truncation of gamut ...

Can you try to develop this image with CNX-D in ProPhotoRGB instead of sRGB, for example ?

Share this post


Link to post
Share on other sites
9 minutes ago, laurentia said:

@WMax70,

I think it's a problem of non-truncation of gamut ...

Can you try to develop this image with CNX-D in ProPhotoRGB instead of sRGB, for example ?

Laurentia, 

I'm a bit over asked here.

Not sure what you mean with the question if I can develop this image with cnx-d in ProphotoRGB? 

Is that a program or a camera setting or? 

Would like to help, but I need to understand is. 

I've sent the raw file already to the Dropbox of Affinity.

Share this post


Link to post
Share on other sites
11 minutes ago, WMax70 said:

Laurentia, 

I'm a bit over asked here.

Not sure what you mean with the question if I can develop this image with cnx-d in ProphotoRGB? 

Is that a program or a camera setting or? 

Would like to help, but I need to understand is. 

I've sent the raw file already to the Dropbox of Affinity.

With which software did you import into AF on the second screenshot? Do you own CNX-D from Nikon?

Share this post


Link to post
Share on other sites

Yes I did. 

Was confused by cnx-d. 

Of course you meant Capture NX-D (CNX-D :-) )

The second picture was opened as nef in cnx-d and transported is as tiff to Affinity. 

I also will add the screenshot from CNX-D when I'm at my office again. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | 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.