Adobe Community: Trying to paste from Illustrator as smart object

Currently Being Moderated

1. Brett N,

Aug 23, 2012 5:07 PM in reply to KrisHunt

Report

You should actually see this fixed in CS6. Download a trial and give it a shot.

|

Mark as:

Currently Being Moderated

2. Chris Cox,

Aug 23, 2012 7:58 PM in reply to Brett N

Report

Not so much a fix (since it has always worked correctly), as CS6 added features for snapping objects to the pixel grid.

|

Mark as:

Currently Being Moderated

3. c.pfaffenbichler,

Aug 23, 2012 11:41 PM in reply to KrisHunt

Report

And wouldn’t switching to Nearest Neighbor for the Image Interpolation when pasting also have an effect on the issue?

|

Mark as:

Currently Being Moderated

4. Chris Cox,

Aug 24, 2012 12:16 AM in reply to c.pfaffenbichler

Report

Yes, but probably wouldn't give the desired result.

And still if you resize the smart object, you can get antialiased edges - because you're not just pasting pixels, but a vector shape that has to be rasterized at the desired size.

|

Mark as:

Currently Being Moderated

5. KrisHunt,

Aug 24, 2012 3:41 AM in reply to Chris Cox

Report

> since it has always worked correctly

So do tell, is it considered correct behavior to introduce unnecessary anti-aliasing when placing at 100%, or am I doing it wrong?

|

Mark as:

Currently Being Moderated

6. Mike Ornellas,

Aug 24, 2012 10:52 AM in reply to c.pfaffenbichler

Report

Just take the extra effort to mask the ghosting of your artwork. It's easy to do if you have enough time.

|

Mark as:

Currently Being Moderated

7. Chris Cox,

Aug 24, 2012 3:56 PM in reply to KrisHunt

Report

Rendering a vector shape -- will generally get antialiasing.

Photoshop is rasterizing what Illustrator sent, but you can't guarantee that it will rasterize exactly the same because of many factors.

The antialiasing is there because it is supposed to be there -- so it is correct.

CS6 has the option to snap the outer bounds of smart objects and vector shapes to the pixel grid -- but the inner edges can still be antialiased. And that is still correct behavior.

|

Mark as:

Currently Being Moderated

8. KrisHunt,

Aug 24, 2012 4:34 PM in reply to Chris Cox

Report

> Photoshop is rasterizing what Illustrator sent, but you can't guarantee that it will rasterize exactly the same because of many factors.

So Illustrator can display the pixel preview perfectly well without any such anti-aliasing problems, but that same pixel arrangement can't be translated to Photoshop intact. Not good enough. It's not like Adobe makes both products or anything.

|

Mark as:

Currently Being Moderated

9. Brett N,

Aug 24, 2012 4:46 PM in reply to KrisHunt

Report

You are taking vector information from a native vector application (Illustrator) to a native raster application (Photoshop). Even when you bring it in as a Smart Object, it still is being rendered into pixels in Photoshop. This is the same type of thing as translating from one language to another, there isn't always an exactly perfect equivolent between one and the other. Try placing your Illustrator object into a larger Photoshop document, less antialiasing will have to happen and give you better results.

|

Mark as:

Currently Being Moderated

10. Chris Cox,

Aug 24, 2012 4:48 PM in reply to Brett N

Report

Don't forget that Illustrator converted the vectors from it's native form to EPS or PDF, which can distort the shapes and results sometimes.

|

Mark as:

Currently Being Moderated

11. station_two,

Aug 24, 2012 5:11 PM in reply to KrisHunt

Report

KrisHunt wrote:

…Illustrator can display the pixel preview perfectly well without any such anti-aliasing problems, but that same pixel arrangement can't be translated to Photoshop intact. Not good enough. It's not like Adobe makes both products or anything.

Inconsistency between or among applications in the artificial "suites" should come as no surprise.

The "suite" concept is a fabrication of Adobe marketing and bean-counting types. The engineering teams are totally independent of each other, they are not only in different buildings but in different cities and states of the American Union, even in different countries.

The fact that they have little if any communication among them is highlighted by requests occasionally made in these forums by top Adobe engineers to let the other teams know when there are problems in one application that impact our workflow in another one.

|

Mark as:

Currently Being Moderated

12. c.pfaffenbichler,

Aug 25, 2012 2:27 AM in reply to station_two

Report

The fact that they have little if any communication among them is highlighted by requests occasionally made in these forums by top Adobe engineers to let the other teams know when there are problems in one application that impact our workflow in another one.

I would be interested to learn what’s a good way to let the Illustrator team know something; the members seem to avoid participating in these Fora, so a Bug Report seem the best approach – it’s just that with my »favorite« Illustrator-bug having been maintained for six versions by now I wonder how much good that is.

(And I am aware that this is not quite fair to the engineers … but the experience is a bit disheartening.)

|

Mark as:

Currently Being Moderated

13. Mike Ornellas,

Aug 25, 2012 8:26 AM in reply to c.pfaffenbichler

Report

Smell the magic~!

Learn to not care and you shall be free.

|

Mark as:

20,980 posts
Dec 23, 2006

Currently Being Moderated

14. Noel Carboni,

Aug 25, 2012 3:22 PM in reply to Mike Ornellas

Report

Mike, your little messages of stress reduction intrigue me.

Adobe: Wouldn't it be better to make things right (or document better to avoid misunderstandings) rather than have to have people who frequent forums and try to advise people not to care about bad quality?

-Noel

|

Mark as:

Currently Being Moderated

15. Chris Cox,

Aug 25, 2012 3:29 PM in reply to Noel Carboni

Report

Photoshop already is doing it right, and matches Illustrator pretty darn well.

But there are dozens of variables that could change things (position, size, etc.), in addition to the mistaken belief in some user segments that vectors work on pixel boundaries without antialiasing.

|

Mark as:

20,980 posts
Dec 23, 2006

Currently Being Moderated

16. Noel Carboni,

Aug 25, 2012 3:41 PM in reply to Chris Cox

Report

While I've seen many times that user misunderstandings are at the root of what are initially considered bugs, when I see enough experts commenting here that something's not right, well, I start to wonder whether something may not be right.

Could how to use these tools be better documented so that when someone tries to do what the OP above wants to do, he can actually accomplish his goal? Are you implying the answer has already been given (e.g., enable ''snap to pixel grid'' in Ps CS6) but KrisHunt is simply ignoring it?

-Noel

|

Mark as:

Currently Being Moderated

17. Chris Cox,

Aug 25, 2012 4:44 PM in reply to Noel Carboni

Report

>> Could how to use these tools be better documented so that when someone tries to do what the OP above wants to do, he can actually accomplish his goal?

I'm not sure. He seems to be expecting behavior that should not be expected. So I don't know what he thinks is happening, or what part he misunderstands. I can document how math and applications work, but not all the ways people incorrectly assume that they work.

The snap vector to pixel grid option will handle the outline of the shape - but the inside may be antialiased depending on the position and size of the shape plus the definition of the original vector shape. Most of the time, vectors are not going to align to the pixel grid, but we can force the outside edges to align. Inside edges generally can't be snapped to pixel boundaries without distorting the shape badly (in the cases where it's possible at all).

|

Mark as:

Currently Being Moderated

18. Mike Ornellas,

Aug 27, 2012 10:20 AM in reply to Chris Cox

Report

Though a software developer can not predict every combination of how a person shall use the application, it would be a good start to understand WHY people are using an app as such instead of stating it's wrong.

|

Mark as:

Currently Being Moderated

19. Wiinter,

Apr 10, 2013 6:39 PM in reply to KrisHunt

Report

Hi Kris - you're not alone. I noticed this on Day 1 of CS6, as I have about 300 icons that I had designed at 512x512 (smart object brought in from Illustrator) that work pixel-perfect in 64x64 when shrunk to exactly 12.5% of their original size. Meaning, all of the hard edges used to stay perfect in previous versions.

But now, in CS6, I'm terrified whenever I have to edit or resave any of these icons, as NONE of them look exactly the same as before. Specifically, hard edges now bleed the color to/from adjacent pixels despite all coordinates being mathematically perfect - like there's an error in the way anti-aliasing is conducted on smart objects. Here's the interesting part: I can open the original PSD, and if I export as-is, it's fine. But if I ever touch the Transform of that smart object, even if I don't change the values, the new anti-aliasing routine takes effect.

This is not a difficult thing to reproduce:

1) Start a new document in Illustrator. Canvas Size 512x512px.

2) Draw a black square with coordinates: X: -64 Y: -64 W: 640px H: 640px

3) Draw a white square with coordinates: X: 0 Y: 0 W: 512px H: 512px

4) Use pathfinder to punch the white square out of the black square

5) Copy the object into Photoshop as a smart object, and look what it does to the inner edge of the left and top sides.

Now, for a control, go back to your Illustrator file, undo the Punch so that you still have both squares. Now copy both squares together and paste into Photoshop as a smart object. No bleeding.

So, I think I can flat out say "something's wrong".

|

Mark as:

Photoshop General Discussion

Trying to paste from Illustrator as smart object

Aug 23, 2012 10:17 AM

More Like This

Bookmarked By (0)

Answers + Points = Status