ABC, this is for you!
I just installed Pitstop Pro 13 (update 2) as a 30-day trial (Acrobat DC on Mac 10.11.6.)
I have a file that I want to convert RGB images to CMYK using the out-of-the-box Action List called "Convert all RGB to CMYK".
When color management is off, it converts. However, since this results in crappy images, I turned on CM to US Prepress Defaults and it won't convert, giving me the following error: "Failure (Color conversion was not possible because the requested CMM engine was not available.) occurred during Convert color"
What's up with that?
I'm not ABC but I know why this is. You need to go into Pitstop Preferences and edit the profile you want to use and change the CMM engine to something other than than the Adobe one. The Adobe one only works 32-bit while Acrobat DC is 64-bit.
So, if I change it to one of the other options, will I get the same conversion? What is yours set to?
I know who doesn't have Alzheimer's :cane:
Joe remembers that and the only reason I remember breakfast is because it's repeating on me.
Quote from: DCurry on October 07, 2016, 08:57:43 AMSo, if I change it to one of the other options, will I get the same conversion? What is yours set to?
I use Little CMS. I don't think it will change the conversion. It is still using the same profiles. At least I haven't noticed any issues. Test it by using Acrobat 11 with the Adobe CMS and compare it to one converted in DC using Little CMS.
Thanks, Joe. I trust your setting and do not feel like running any tests since I'm sure you probably did at some point!
Quote from: Joe on October 07, 2016, 08:35:00 AMI'm not ABC but I know why this is. You need to go into Pitstop Preferences and edit the profile you want to use and change the CMM engine to something other than than the Adobe one. The Adobe one only works 32-bit while Acrobat DC is 64-bit.
Yes, Joe is right.
But did I have to tell anyone that Joe was right?
:drunk3: GO BLUE JAYS :drunk3:
Who?
I don't know, you guys were talking about animals so....
There is an animal called 'Rangers'? ;D
Quote from: Joe on October 07, 2016, 11:53:02 AMThere is an animal called 'Rangers'? ;D
That Odor guy on the Rangers is an animal, when he punched Bautista in the face last year.
Quote from: DCurry on October 07, 2016, 08:30:22 AMABC, this is for you!
I just installed Pitstop Pro 13 (update 2) as a 30-day trial (Acrobat DC on Mac 10.11.6.)
I have a file that I want to convert RGB images to CMYK using the out-of-the-box Action List called "Convert all RGB to CMYK".
When color management is off, it converts. However, since this results in crappy images, I turned on CM to US Prepress Defaults and it won't convert, giving me the following error: "Failure (Color conversion was not possible because the requested CMM engine was not available.) occurred during Convert color"
What's up with that?
As I am finding out here, it has to do with ICC profile embedding. If there are items tagged with an ICC profile, you'll have to strip those off before it will do the conversion. I got burned on a job like that recently.
I need someone to elaborate, but I think there's a PitStop feature that allows you to remove profiles from items. If not, I think you can place the PDF in InDesign, and distill a new PDF, which will be free of profiling (provided you don't have that turned on when you distill it).
Spoiler
GO GIANTS!
That doesn't make any sense, that's not how it should work.
If there are embedded profiles they should be honoured as the source profile.
Can you contact our support team please so they can take a look. support@enfocus.com
abc, are you suggesting that DigiCorn contact support, or me? I changed to Little CMS per Joe's suggestion and the action list worked as expected. I did not strip out any profiles.
Switch the color management settings in the PitStop preferences to use Little CMS. There is no more Adobe CMS available. Little CMS will give you excellent results and is cross platform.
You'll probably want to tweak the profiles used for the conversion. But at least changing the CMS should fix it.
If an object is tagged with an ICC profile, that profile will be used as the source profile.
If an object is NOT tagged with an ICC profile, then the Enfocus color management default profiles are used.
Your target/destination color space is dictated by the output intent if one is available. If one is not available, then the default destination profile in the color management preferences is used.
There is an order in which the profiles are used if you are really worried about it. But the fundamental lesson is when an object is not tagged with a profile AND you use PitStop to convert color, then you are using the PitStop color management settings. Get those wrong, get junk results. Get them right, get good results.
You really don't want to be stripping away profiles. It is ideal to convert them between spaces. Understandably many people simply strip them because "it works".
This still basically holds true: http://automatetheworkflow.com/cms/