Smart Object rendering problem

  • 1
  • Problem
  • Updated 6 years ago
  • Not a Problem
  • (Edited)
Windows 7 x64
Photoshop 13.0.1 x64

___________________________

I've always been able to produce buggy activity in smart objects, since their implementation. Many of us have. Here, I'm finally taking the time to reporting one.

Smart objects are an invaluable tool. They provide very important functionality to PS users. Love 'em. But . . .

Errors sometimes surface, such as this one:



DOWNLOAD CS6 PSD FILE:
https://www.transferbigfiles.com/bc01...

What explains the blurred semi-circle? It's as if part of the contents of the smart object are tiling.
Photo of mathias

mathias

  • 140 Posts
  • 13 Reply Likes
  • processing mountains of product images having to compensate for the shortcomings of our "photographer" salesman who brags about his $5000 camera equipment yet still produces cruddy blurred photos despite shooting in a controlled environment.

Posted 6 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 813 Reply Likes
Um, Smart Objects have had a few bugs, but not many, and they get fixed pretty quickly.

You're going to laugh when you see this, but look at the contents of your layer mask. The file is rendering correctly, given your layer mask contents.
Photo of mathias

mathias

  • 140 Posts
  • 13 Reply Likes
You're right, I did laugh . . . in pain.

Ok ok, you got me. That's pretty retarded of me! Chalk one up for the ubiquitous Chris Cox.

BUT!

NOW!

Now, I give you exhibit B, sir: (!!!)

Erronous SO cropping! A debilitating and heinously buggy SO behavior sure to doom us all!

Behold: (as I attempt to save face . . .)



Enter the "__________CUSTOMER HELPER" layer (sorry for the lack of context in this example. What you're opening here is a copy of a web design doc, all stripped out except for the offending layers.)
My workaround isn't too bad. A single pixel in the "---smart object fixer---" layer does the trick. Quick and easy. But you gotta remember to do it.

DOWNLOAD THE TERRIBLE CS6 PSD:
https://www.transferbigfiles.com/73bd...

And you're right - SO's haven't been that bad. WELL worth the minimal buggy troubles when compared to the gains they've brought to PS. Exhibit B though, has been a "bug" since the first implementation of SO's (if I recall correctly).

Your move, Cox!
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 811 Reply Likes
The example you posted has no smart objects, so I can't tell what your original looks like, or the scaling, or your fixer, etc.

One thing to check when smart objects don't scale as expected: the default interpolation method in preferences.

Also, you should pick up the 13.0.3 update to get all the latest bug fixes.
Photo of mathias

mathias

  • 140 Posts
  • 13 Reply Likes
omg . . . wrong PSD. Batting 1000, tonight.

Right PSD:
https://www.transferbigfiles.com/616a...
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 806 Reply Likes
Hmm, if I do a free transform and move the layer in the parent file - the outline appears, and won't go away again.

Ah, because of the snap transforms to pixel boundary preference.
The original SO was placed with that preference off, or in an older version of Photooshop, so it landed on a half pixel coordinate and resampling couldn't preserve the single pixel edge from the child document.
Free Transform and look a the coordinates of the top left edge -- notice both are half pixel values? Change them to whole pixel values.
Photo of mathias

mathias

  • 140 Posts
  • 13 Reply Likes
Hey, good detective work! That's good to know. I guess that makes sense, even though with smoothing interpolation turned on, I'd at least expect to see a fuzzy anti-aliased line.

And yes, the PSD was initially created with CS5 if not mistaken.

So, now with "Snap Vector Tools and Transforms to Pixel Grid", we'll see less of this issue I bet.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 806 Reply Likes
Yep, that's part of what the feature was designed to do.
Photo of mathias

mathias

  • 140 Posts
  • 13 Reply Likes
Can't believe I didn't think of that. It was just a coords snapping problem the whole time. Just like when pasting vector from Illustrator. Just like what ruins your text anti-aliasing in Flash. Gotta be on whole number coords. Geeze . . . well now I finally know. Course, the issue has pretty much been solved for me by software updates hehe.
Thanks for your time!
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 806 Reply Likes
You're welcome!