Here is another one for you gurus
When in Pitstop 7.something and doing a Spot Global colour change, the colour becomes a tint instead of a solid as it was before.
I'll try to explain better
I want to change a solid 100% magenta stroke with a Spot colour from a created repository document spot called Diecut.
Grab colour to change, global change it to Diecut and voila, the change is done but the diecut line is now 60 or 70% tint of the Diecut colour and not 100% :huh:
Any work around?
Thank you in advance
Adriano
I've been trying to accomplish something similar for the last week. Attached is a test PDF file and a Pitstop 7.5 action in which I am trying to remap the Cyan to Pantone 368C but I only get a 30% screen of the Cyan. Any ideas?
Back to you Adriano...I tried it on my test by grabbing the 100 Cyan and doing a global change to a spot color and the global change came out at 100% of the spot for me.
Dunno whether I'm grabbing the bull by the tail here, but I've done the odd process to Spot conversion recently, and have had to watch out to check the tint value in Inspector. Manually change to 100%. Could cause a bite on the bum if not checked.
It's possibly following a logical conversion path, but wouldn't mind some enlightenment on it too.
I'm just wondering where it pulled a 30% tint out of? Why not 20%? Why not 40%? Inquiring minds want to know. :smiley:
I took my Cyan scale attached to a previous post and changed it to Magenta and then modified it to remap the magenta to PANTONE 368C and it remapped it to 59% of PANTONE 368C. It did the Cyan at 30% and it did the Magenta at 59%. Any rhyme or reason where it's getting these values from?
More testing reveals it remaps the Yellow to 11% of 368C and a Black scale remaps to 100% of 368C. Truly baffled here.
Now you know what i' talking about
I use a lot of these actions because of a lot of incompetent designers give us every colour in the book instead as the right one for diecuts, uv spot or perforations
:huh: :huh: :huh: :huh: :huh:
Quote from: Adriano on March 15, 2008, 03:50:03 AMNow you know what i' talking about
I use a lot of these actions because of a lot of incompetent designers give us every colour in the book instead as the right one for diecuts, uv spot or perforations
:huh: :huh: :huh: :huh: :huh:
its not converting to grayscale and THEN to the spot, is it? aiming blindly in the dark, I only have PS 6.xx...
Wow.... been messing with it for a few minutes and it's a stumper! :huh:
No matter what I do, I cannot reproduce this problem. If I pick any color, and remap to a spot, it works and vice-versa, and holds the tint values, in this case 100%. I'm running PitStop 7.5.
....and running Acrobat 8.
Yeah, global change works for me too. It's the remap separation action list that doesn't work for me.
Yeah, I'm using PitStop 7.5... Acroshat 8. Global change works fine but that would mean selecting every value. If you set up an action to blast the whole document, it messes up the values just like Joe said. 100% = 30% :huh: Where's Matt Beals?
Yeah, still not happening. I run the action, my file does what I want... what am I missing here?
Are you using the cyan scale I attached earlier along with the action script I attached? It's changing the 100% cyan to 30% tint of Pantone 368.
Okay, I see what's going on... Sorry about the confusion. I can get different values by manipulating my color management settings, but I can't get it up over 47%, very bizarre. I'll keep hacking...
So far, I think PB was right about the Grayscale coming into play before the conversion. When I try to map to black, I get the same values. Color Management, can get the value to 50%, so I figure it is compositing the color from it's color values in gray, then mapping the color. Odd. I'm gonna go back to an earlier version of PitStop and see what happens.
Yep, it also happens in PitStop V6.5. I loaded Joe's Action, and got the same thing. I even created one in Pitstop 6.5, and it did the same thing. I have never noticed this before, and I swear I have done this successfully. Baffled too.
Quote from: DigitalCrapShoveler on March 21, 2008, 02:02:51 PMYep, it also happens in PitStop V6.5. I loaded Joe's Action, and got the same thing. I even created one in Pitstop 6.5, and it did the same thing. I have never noticed this before, and I swear I have done this successfully. Baffled too.
There is your homework for the weekend! :laugh:
Quote from: Joe on March 21, 2008, 03:58:11 PMQuote from: DigitalCrapShoveler on March 21, 2008, 02:02:51 PMYep, it also happens in PitStop V6.5. I loaded Joe's Action, and got the same thing. I even created one in Pitstop 6.5, and it did the same thing. I have never noticed this before, and I swear I have done this successfully. Baffled too.
There is your homework for the weekend! :laugh:
Homework, Homework... Give me a break? Where have I heard that before? Anyhoo, I'm on it. Report Monday. Wait, I don't have Pitstop at home...
I'll be at work tomorrow. Everyone else should be too. :police:
Quote from: Joe on March 21, 2008, 04:04:59 PMI'll be at work tomorrow. Everyone else should be too. :police:
I might be too. It all depends on our Press Scheduler. I'll find out 2 minutes before I have to leave... thanks!?! Why can they not tell you sooner?
Just talking to myselves.
myselves? How many of you are there? :grin:
Quote from: Joe on March 21, 2008, 04:09:43 PMmyselves? How many of you are there? :grin:
Never counted, some say we are Legion. LOL.
Have a good one Joe, everyone. It is 5:15, and I am outta here!!!
I see this all the time too (Acro 8) My workaround is change color, change tint to 100% and save in repository (as, for example 100_072_Blue). I have 20 of my most often used pantones saved there. A solution would be nice.
Quote from: tuff_gong on March 22, 2008, 12:36:29 PMI see this all the time too (Acro 8) My workaround is change color, change tint to 100% and save in repository (as, for example 100_072_Blue). I have 20 of my most often used pantones saved there. A solution would be nice.
I know, I know... I'm workin' on it. Scoured the net last night... still nuthin.
doubt there is. wheres mattbeals when you need him?
Quote from: Lucius on March 23, 2008, 05:43:48 PMdoubt there is. wheres mattbeals when you need him?
I actually looked him up, joined his forum, and asked the question... Here is what he said:
I don't recall this particular problem in PSP 6.x. I'm only aware of it in v7.x. The problem lies in how PSP moves/transforms colors. The way in which Enfocus moves the colors changed. I'm trying to find the email that explained the underpinnings of the new methods. Unfortunately there isn't any way of getting around this by changing the default behavior.
When I find the message I'll post it for you. In the mean time, you have to explicitly select a color and explicitly change it to a destination tint/color.
I will update when he gets back to me.
Well, he's quick... here is what he has to say...
Okay, here's a snippet of the message from Enfocus explaining the process.
Quote:
The reason this happens is that we do a convert color instead of a remap color. What we actually do in the background is translate CMYK to gray and the convert it to the spot color you want.
If possible, i.e. when the object has a single colorant (e.g. spot or gray) changing it to a spot on the inspector preserves the tint value. This allows e.g. 50% gray to be remapped to 50% pantone or one spot to another spot.
But if the object is not a single colorant (e.g. CMYK, RGB, etc.) we want to be able to preserve the relative difference in color. E.g. if you have a CMYK "shading" made from line art or e.g. our Enfocus logo with green and black pieces) we expected that you didn't want them all to become the same color. Hence the current implementation.
If you do want them to have the same color, you just need to move the slider bar to 100%. And yes, this is sometimes an additional click, but we thought that losing the color differences when going from grays to spot was worse.
End Quote
Thank you DCS
Now I know why I have to be extra careful when changing colours in Pitstop
Thank God for Illustrator (sometimes)
Thank you all for the interest
No solution but an explanation by Her Majesty Enfocus is better than nothing
:huh: :huh: :huh: :huh: :huh:
Quote from: Adriano on March 24, 2008, 04:39:37 PMThank you DGS
Now I know why I have to be extra careful when changing colours in Pitstop
Thank God for Illustrator (sometimes)
Thank you all for the interest
No solution but an explanation by Her Majesty Enfocus is better than nothing
:huh: :huh: :huh: :huh: :huh:
No problem, that's why we're all here.
Not what I hoped for, but you're right, an explanation from Enfocus does at least put my questions to rest.
Quote from: DigitalCrapShoveler on March 24, 2008, 02:11:15 PMWell, he's quick... here is what he has to say...
Okay, here's a snippet of the message from Enfocus explaining the process.
Quote:
The reason this happens is that we do a convert color instead of a remap color. What we actually do in the background is translate CMYK to gray and the convert it to the spot color you want.
If possible, i.e. when the object has a single colorant (e.g. spot or gray) changing it to a spot on the inspector preserves the tint value. This allows e.g. 50% gray to be remapped to 50% pantone or one spot to another spot.
But if the object is not a single colorant (e.g. CMYK, RGB, etc.) we want to be able to preserve the relative difference in color. E.g. if you have a CMYK "shading" made from line art or e.g. our Enfocus logo with green and black pieces) we expected that you didn't want them all to become the same color. Hence the current implementation.
If you do want them to have the same color, you just need to move the slider bar to 100%. And yes, this is sometimes an additional click, but we thought that losing the color differences when going from grays to spot was worse.
End Quote
Dear Enfocus,
That sucks!
Yours Truly,
Joe
Well, sounds like the "logical conversion path" I figured must be lurking in there. Looking like you can't have your cake and eat it too. But...maybe if they were to chuck in an extra dialogue box to ask you if you want "greyed" conversion or "solid", might be a nice option. In version 7.51? "Real soon now!" [apologies to IBM]. :shrug:
Quote from: frailer on March 24, 2008, 07:47:43 PMWell, sounds like the "logical conversion path" I figured must be lurking in there. Looking like you can't have your cake and eat it too. But...maybe if they were to chuck in an extra dialogue box to ask you if you want "greyed" conversion or "solid", might be a nice option. In version 7.51? "Real soon now!" [apologies to IBM]. :shrug:
I just noticed over the weekend the latest version is now 7.52 and it still works the same way.
Hey Enfocus, I did not ask for "convert to gray and then change to spot". I asked for REMAP COLOR!!! :angry:
The action script that ENFOCUS created is named REMAP COLOR...not CONVERT TO GRAY AND CHANGE TO SPOT!!!
Some things just really piss me off!!!!!!!
Joe, I think when I said I have done this before, it was in Neo. I wish I could talk the boss into getting it.
Yes, In NEO, remap color really does remap a color. Same company, different results.
Quote from: Joe on March 24, 2008, 10:39:37 PMYes, In NEO, remap color really does remap a color. Same company, different results.
Joe, I am not at work right now, so I can't test this, but, in the Cyan instance, couldn't you remap the cyan to black, then to the spot via remap color? I mean if the values of cyan would hold true to the black conversion...
It converts the 100% Cyan to 30% Black, just like the spot. :angry:
Quote from: Joe on March 24, 2008, 10:51:22 PMIt converts the 100% Cyan to 30% Black, just like the spot. :angry:
Damn. I am bound and determined to find a workaround for this...
I'll keep you posted.
Quote from: Joe on March 24, 2008, 09:02:43 PMQuote from: frailer on March 24, 2008, 07:47:43 PMWell, sounds like the "logical conversion path" I figured must be lurking in there. Looking like you can't have your cake and eat it too. But...maybe if they were to chuck in an extra dialogue box to ask you if you want "greyed" conversion or "solid", might be a nice option. In version 7.51? "Real soon now!" [apologies to IBM]. :shrug:
I just noticed over the weekend the latest version is now 7.52 and it still works the same way.
Hey Enfocus, I did not ask for "convert to gray and then change to spot". I asked for REMAP COLOR!!! :angry:
The action script that ENFOCUS created is named REMAP COLOR...not CONVERT TO GRAY AND CHANGE TO SPOT!!!
Some things just really piss me off!!!!!!!
I take it back. Your logic is right. It's an [illogical] sidestep, for what?
Quote from: frailer on March 24, 2008, 11:07:32 PMQuote from: Joe on March 24, 2008, 09:02:43 PMQuote from: frailer on March 24, 2008, 07:47:43 PMWell, sounds like the "logical conversion path" I figured must be lurking in there. Looking like you can't have your cake and eat it too. But...maybe if they were to chuck in an extra dialogue box to ask you if you want "greyed" conversion or "solid", might be a nice option. In version 7.51? "Real soon now!" [apologies to IBM]. :shrug:
I just noticed over the weekend the latest version is now 7.52 and it still works the same way.
Hey Enfocus, I did not ask for "convert to gray and then change to spot". I asked for REMAP COLOR!!! :angry:
The action script that ENFOCUS created is named REMAP COLOR...not CONVERT TO GRAY AND CHANGE TO SPOT!!!
Some things just really piss me off!!!!!!!
I take it back. Your logic is right. It's an [illogical] sidestep, for what?
Ya got me mate...Enfocus thinks they know best. They don't.