ID 544555 - When using the Channel Presets to import textures, the colorspace option doesn't change the colorspace of the image being imported, rather it uses the Projects Settings default colorspace

Follow

Problem summary
When using the Channel Presets to import textures, the colorspace option doesn't change the colorspace of the image being imported, rather it uses the Projects Settings default colorspace


It does change the values in the paint node created, but not in the Viewer
 
Customer reported version
mari.5.0v4
 
Customer reported platform
n_a_linux
 
Steps to reproduce
 
1) Download that attached test.tif and test02.tif files (they are identical except the name)
 
2) Open Mari 

3) Click Help>Create Example Material Design Project, then open the project

4) Open Channels>Channels Presets
 
5) Change the root path to where you downloaded the test tif files and press Quick Scan
 
6) Create and Import both textures, setting on image Colorspace to be sRGB and the other to linear:

 
7) Press OK, then compare the Base Paint nodes created in the UV Viewport, they both have the same colorspace applied visually.

 
8) In File>Settings>Colorspace, set 8-bit Color to linear
 
9) Repeat steps 4-7, the images now have a different colorspace applied to the first imports, but still the same colorspace between the different imports:
 

 
*If you import textures using the right click menu on a Paint node, then File > Import, changing the import colorspace does work
 
Expected behaviour
For the Channel Presets dialog to override the project colorspace setting when importing textures
 
Actual behaviour
Textures are always imported with the color transform from the project colorspace settings
 
Workaround
Don't use the Channel Presets dialog, and right click paint nodes, then use File > Import to import the textures with the correct colorspace
 
Reproduced by support
This bug has been reproduced in:
Mari 6.0v2 - Windows 10, CentOS 7.9
Mari 4.2v1 - Windows 10
 
 
Earliest version tested
Mari 4.2v1 - This issue appears to be in all tested versions of the product
 

    We're sorry to hear that

    Please tell us why