Opening File w/o ICC Profile PI Suggest B/W not Color Profile

[andyschlei]

When opening a file without an ICC profile, PixInsight is offering the black and white profile (just left at the monitor profile) as the color profile.  It is not making the default color profile available.  I've double checked the settings.

--Andy

[Juan Conejero]

Hi Andy,

By "black and white profile", what do you mean exactly? Do you refer to a grayscale ICC profile?

Please select Edit > ColorManagementSetup, then click on Load Current Settings. Tell me which are your default color management settings.

I assume you have selected "Ask what to do" as the "On Missing Profile" policy. With that policy enabled, the Missing ICC Profile dialog opens when you open an untagged image (an image without an embedded ICC profile). This dialog provides three options:

* Assign the default profile - here you should see the default RGB profile that you have selected in ColorManagementSetup (or the default grayscale profile if the image is in the grayscale color space).

* Leave the image untagged. This is the default option. If you select this option, pixel values in the image are supposed to be expressed in the default RGB or grayscale profile, but no profile will be associated with the image explicitly.

* Disable color management for this image. Obviously you shouldn't select this option, unless you have a strong reason.

Also have into account that PixInsight, unlike other applications, has no problem to use RGB ICC profiles to manage grayscale images. In these cases, grayscale images are treated as RGB images with identical red, green and blue values for all pixels.

Does the above information help you? Or do you still think there's a bug here? I'd need some screen shots in order to understand where the problem is.

Thank you and keep bug reports coming

[andyschlei]

By "black and white profile", what do you mean exactly? Do you refer to a grayscale ICC profile?

Yes, I should have said grayscale

Please select Edit > ColorManagementSetup, then click on Load Current Settings. Tell me which are your default color management settings.

Going from memory (I'm at work, so I don't have PI here):  

Monitor:  Monitor profile
Color: Adobe
Grayscale: Old Monitor Profile

I assume you have selected "Ask what to do" as the "On Missing Profile" policy. With that policy enabled, the Missing ICC Profile dialog opens when you open an untagged image (an image without an embedded ICC profile). This dialog provides three options:

* Assign the default profile - here you should see the default RGB profile that you have selected in ColorManagementSetup (or the default grayscale profile if the image is in the grayscale color space).

* Leave the image untagged. This is the default option. If you select this option, pixel values in the image are supposed to be expressed in the default RGB or grayscale profile, but no profile will be associated with the image explicitly.

* Disable color management for this image. Obviously you shouldn't select this option, unless you have a strong reason.

Yes, that is the dialog, but the error is that the profile offered under "Assign the default profile" is the grayscale profile, not the RGB profile.

I'll send screen shots tonight.

Thanks,

--Andy

[andyschlei]

Juan,

Here are the screen shots.

First color management set-up:



Then the dialog that comes up opening an RGB JPG file:



Note that the color profile suggested is the grayscale profile, not the RGB profile.  This has worked in the past.  This has been repeated on other non-color profile assigned images with the same result.

Let me know if you need more information.

Clear skies,

--Andy

[andyschlei]

Have you been able to re-create the error?

[Juan Conejero]

Hi Andy

Yes. This is a bug and I have it perfectly identified (it is a silly thing like "if the image is grayscale then assign the grayscale profile, else assign the grayscale profile"). Unfortunately, I forgot to fix it in version 1.1  :oops:  :cry:  :cry:

Until I publish an updated core application (tomorrow), the workaround is obvious: Select your RGB profile as the default grayscale profile in ColorManagementSetup.

Thank you for catching this one