Strange RGB color conversion behaviour

[andreas_m]

Dear Forum,
i'm a little bit confused with my Color Mangement Settings.
As you see in 1. my rgb-profile is eciRGB v2.
In 2. you see that the selected picture has no profile embedded.
When i hit the color conversion butten (in 3.) PitStop suggests Adobe RGB (1998) as the profile where to convert from ...

Is that a bug or do i understand something really wrong? What am i missing?

Any help would be great ...

Thanx in advance

Andreas

[abailescollins]

That is a bit strange, I would expect the settings presented to you in the window is the same as the color management preferences.
Can you report this one to Enfocus support please so they can investigate please.

Obviously you can change the Profile in the dropdown to the correct one, but that's not the point!

[andreas_m]

Thanks for your answer.

I'll contact Enfocus support and will post the solution. Just in case anybody else has this issue.

Andreas

[abailescollins]

Great thanks, I will follow the case as I am interested to see what's going on.

[andreas_m]

But the support seems to be for free only for 90 days after activating the license ...

[andreas_m]

It's a little bit strange but the preferences seem to work - but with two exceptions:
- Use settings from acrobat
- Color management switched off

I created a local preference with the same settings as "Use settings from acrobat" by hand and everything works fine.

Seems to be a bug (or a feature? )

[Shawn_Anderson]

What are your preferences set to in Acrobat Preferences in the Color Management tab? Is your RGB working space set to Adobe RGB?

It could be pulling the RGB profile from there if the image is untagged and you have "Use Settings from Acrobat" selected. Try changing your RGB Working space to sRGB in the Acrobat pref window and see if the default in Pitstop changes.

You may also want to check the output intent of the PDF on the off chance that it was created with an output intent of Adobe RGB. It would be a little unusual but that would be another reason why it might assume Adobe RGB for your untagged image.

Shawn