Smart Object Rendering Issue

I have an issue has been plaguing me since PS5, I've currently working in PS6 but I've seen this issue in PSCC. When I scale (and in this case, skew) a smart object with a shadow behind it (or any high contrast layer) I get an odd pixillation between the image and its shadow. I've created a couple work-arounds, but I thought I'd post here to see if anyone has any suggestions. It's annoying! Thanks in advance for any help. I'm attaching some images so you can see what I mean:

Hmm, that definitely seems to be the issue. Any idea why it would be happening on brand new layers? And is there any hope of fixing it without having to go through and resize every single object manually by half a pixel? Either way, thanks.
Edit: My concern is these are all at 100% x 100%, so while resizing them does "fix" the problem, the objects are now being resized in some way.
Double edit: Moving the object with the transform tool fixes things without having to resize anything. In my book this is still a bug.

Similar Messages

Smart Objects rendered incorrectly in CS6

Here is a logo, pasted as a smart object from Illustrator into Photoshop CS5.1 :
Here is the same logo pasted as a smart object from Illustrator to Photoshop CS6:
Note the gaps in the orange gradient at the top of the graphic, and the transparent areas in the border of the shield. This discrepancy appears (to me) to be a result of using a "sharper" antialiasing mode in CS6 which is leaving 1 pixel wide gaps between objects that are actually completely aligned to the same points in Illustrator. Scaling the object will result in the gaps showing up in different areas of the graphic. This is incorrect behavior on the part of Photoshop CS6. Will there be a fix forthcoming? I'll have to keep working in Photoshop CS5.1 for the time being until issues like this are resolved.

I think the discussion got sidetracked here on talking about anti-aliasing of "raster" smart objects. THIS IS NOT WHAT THIS COMPLAINT IS ABOUT.
The original complaint, which still stands, is that vector artwork is now rendering with 1 pixel wide gaps between elements that are, in Illustrator, exactly aligned. If you go back and look at my original two examples, the logo in the second screen shot has gaps in the orange banner in the logo, and is missing elements in the border around the shield. These are gaps or holes in the logo caused by a change in the way vector objects are rendered in Photoshop CS6. This can NOT be corrected by changing the antialiasing style - there is no choice of rendering method used. You get the new one, that is broken.
In this particular example, I opened up an old CS5.5 Photoshop file in CS6, and edited it. During that process I resized the logo a little bit, and didn't notice the gaps and lines that now appeared in the logo. I ended up sending out artwork that was affected by this bug. Luckily I did finally notice and in the nick of time was able to fix it by using the .PNG export work-around.
I was going to post a very simple example where I had a grid of filled boxes in Illustrator that were exactly adjacent to each other, which should result in a single larger solid box in Photoshop, but instead results in 1 pixel wide gaps between the elements. You can do this experiment for yourself. The reason I have not posted such an example is that, to my dismay, this example also now exhibits the same thin gaps in Adobe Illustrator CS6. So the rendering of vector images is broken there, as well.
Dragging and dropping elements out of InDesign into Photoshop is also a workflow that I have developed when creating web pages from previously produced print designs. This bug also affects this workflow. Every seperate vector shape in a logo or other compound artwork is now being rendered in such a way that small gaps might appear between elements that should be touching. I imagine that they are being pixel aligned or otherwise sharply antiased so that two shapes that are touching in the vector artwork are now being drawn not-touching. In the original example, if I resize the logo to a different size, the places the gaps happen change - some places that are gapped now touch, others that didn't have gaps now do.
THIS IS A BUG which will affect legacy artwork, and will affect workflows. This has degraded the usability of the Creative Suite as a whole, and should be corrected as soon as possible.

Smart objects rendering incorrectly

Whenever I paste an object from illustrator as a smart object the edges become jagged and the vector loses it's sharpness. It works fine in CS6 but this hads just started happening in Photoshop CC. I've updated to the current version but it hasn't changed.
Screen shots are below, taken at 100% - you can see that the vectors aren't very sharp

Yeah, all the documents are the same resolution. To highlight the issue I've set up 2 identical documents, one in CC and one in CS6 and pasted in a new vector. You can see this difference between the versions below:

Smart Object Display Issue CS5 - Anyone else?

I created a new PS document (CS5 Mac latest version) I have a few layers I grouped and made a smart object for ease of updating and reuse. Problem is my smart object just randomly disappear or even sppear to be "erased" by other layters if i move them around. They are still there and through some random acts I can them to reappear.
I am not even sure if I can explain it right as it is just odd...
Anyone else having dusplay issues with Smrt Objects in CS5?
I am running on a new iMac in 64bit mode.
Thanks!

Try turning Open GL off and relaunching the document. This is most likely something to do with your Graphics card not being able to keep up with Photoshops stringent requirements.

Smart object rendering badly in pdf

Hi everyone,
I've copied a logo from illustrator into photoshop and pasted it as a smart object. When I save the .psd file as a pdf and view it, the logo is really bad quality, ie. it hasn't retained the vector data from illustrator. The rest of the .psd is fine though.
If I copy the same logo and paste as paths or a shape object, it looks great in the exported pdf. I thought a smart object would have been ok since it came from Illustrator.
Can anyone tell me why this is happening?
Appreciate any help.

While Vector Smart Objects retain the original data and can be edited in Illlustrator, within the Photoshop-document they are present as pixel-data.
Adobe never made claims to the contrary as far as I can tell.
But your work-around of pasting paths and using those as Vector Masks is a good one.

Smart Objects - File size issues

Hey All,
The Question: Not sure if this question has been answered elsewhere. But when using a nested smart object (meaning a smart object within a smart object) Photoshop CS5 doesn't display the correct file size (at bottom left) or seem to account for the nested smart object file size. Is there a "setting" I’m missing to accurately display what the true file size is?
The Problem: Using multiple nested smart objects that I have reduced the size of my image to be 260x200 for web export. Photoshop CS5 won't let me save a file that appears to be only 3mbs claiming it's over 2 gig's. See image below.
Really not sure what to do about this, the company I work for makes lots of changes so using smart objects is necessary for my work flow. But also seems to be slowing me down trying to figure out issues like this and is problematic when it comes to saving all the work I have been doing.
Thanks for the help

FentonDesigns wrote:
when using a nested smart object (meaning a smart object within a smart object) Photoshop CS5 doesn't display the correct file size (at bottom left) or seem to account for the nested smart object file size. Is there a "setting" I’m missing to accurately display what the true file size is?
One thing you might have missed is that Photoshop is not a file editor its a document editor. The sizes Photoshop is displaying are related to how much ram it using for the documents data. How efficient ram is being used etc. File sizes vary all over the place sizes depend on the number of pixels in an image format support layers no layers compression?, transparency. There is no way Photoshop could even guess at any file sizes.
An other is all smart object layer are not created the same and their sizes my be far different the you may think.
Smart object layers have a basic format. There is an embedded object, there is a composite pixel rendering for embedded object that is used for the layer pixels and there is a transform associated for the layer rendered pixels.
Anything Photoshop supports can be an embedded object. These objects are copies of the original object. For example a copy of a RAW file where ACR settings are stored in the file copy metadata. An embedded object might be a copy of a PSD file that has thousands of layers. in any case Photoshop renders pixels for the embedded objects composite view and uses these rendered pixels as the smart object layers pixels. These pixels can not be changed within the document.
However the embed object can be opened and worked on and changed. If the change is committed Photoshop will update the embedded object and render the updated object composit view and replace the layers pixels.
Smart Object Layer Pixels can only be acted on in the document not changed with paint etc. For example the Transform associated with the smart object layer sizes and positions the layer rendering over the canvas. The layer actual size may be larger then, smaller then the canvas size and have a different aspect ratio then the canvas. Example if you place in an image that is larger then the document canvas size one of Adobe Photoshop's Preferences is set by default have Place resize large images to fit within current the documents canvas size. The transform associated with that placed layer would cause the rendering of the layers pixels to fit with in the canvas.
Though an embedded object may contain thousands of layers the actual object may be much smaller then you think for PSD files are compressed object may be compressed. Also while the embedded object may contain vector layers when a smart object layer is transformed the layer is transformed using interpolation like a raster layer for all that is being transformed is the pixels Photoshop rendered for the embedded smart object. The only way to work on the embedded smart object layers it to open the smart object and work on the object itself.j

Photoshop CS6 Scaling issues: Vector/Raster smart objects

My team and I have noticed some strange issues when affecting the overall interpolation of a .psd via scaling, cropping, or canvas resize.
Test:
Original .psd is even x even overall pixel dimensions.
Original vector and raster smart object assets are all proportionally scaled with width x height percentages equal.
Preferences: "Snap vector tools and transforms to pixel grid" is turned off
Resize .psd via Image > Image Size palette.
Scale styles, constrain proportions selected.
Every interpolation style tested.
Resize the .psd to 50%
Result: All smart objects (both types) no longer are proportionately scaled. Usually off by a minor amount under 1/10th of a percent.
Some objects' center point shift a half pixel to the right or left.
This also occurs if we use the crop tool or resize the canvas.
Is this a known bug and if so, is there:
1) any setting to truly lock proportions?
2) any resolution being pursued currently?
Though the shift and the disproproptions seem minor, the overall quality of items such as icons, hairlines, and other things that should be more crisp become far more degraded in CS6 vs CS5.
We have over 100 users and need to evaluate if we should drop back down to CS5, where we weren't having any of these issues, as our work demands a lot of precision, so you can see why this is worrisome.
Thanks!

I'm not going to say anything about the abysmal rendering of Vector Smart Objects in CS6 because it'll be beating a dead horse but I can explain the issues you see with measurements after scaling.
The slightly disproportionate scaling and half-pixel shift of the centre is unavoidable when it happens because the resulting Smart Object/Vector Smart Object must measure an integer number of pixels in height and width and be perfectly aligned to the document pixel grid. That's true in CS5 and CS6.
Say a SO/VSO originally measures 102 x 103 pixels and you scale it by 50%. The Options bar may say the result is 51 x 51.5 px but the result will really be 51 x 52 px, and therefore the new height will really be 50.49% of the old height.
The original SO/VSO is an even number of pixels wide and an odd number of pixels high, therefore its centre will be halfway down a pixel. The 50%-scaled SO/VSO is an odd number of pixels wide and an even number of pixels high, therefore its centre will be halfway across a pixel.

PS Smart Object Import Render issues from AI

I have scoured these forums for a while to find anything regarding these circumstances. I apologize if this has been mentioned before but I'm trying to find some way to mitigate this issue.
When importing a vector smart object into Photoshop from Illsutrator I end up with text rendering issues. The fonts render as if they were assigned the sharp AA setting, despite having the crisp AA setting on the AI source.
The pixel previewed AI opened vector smart object looks clean and crisp.
Any ideas on how to fix the text rendering issues?

I have scoured these forums for a while to find anything regarding these circumstances. I apologize if this has been mentioned before but I'm trying to find some way to mitigate this issue.
When importing a vector smart object into Photoshop from Illsutrator I end up with text rendering issues. The fonts render as if they were assigned the sharp AA setting, despite having the crisp AA setting on the AI source.
The pixel previewed AI opened vector smart object looks clean and crisp.
Any ideas on how to fix the text rendering issues?

Vector smart object is rendering poorly.

Has anyone run across an issue when pasting complex Vector Smart Objects into Photoshop CC?
I created a shape in Illustrator CC, added an Extrude and Bevel effect to it, and then pasted it as a smart object in Photoshop CC. The first example what it looks like in Illustrator CC, the second is what it pastes as in Photoshop CC.
As you can see, it is rendering it very poorly and totally unusable as a Smart Object.
I've recently updated to CC, and this never happened in CS5. Is there a new preference in CC that helps render vector objects? maybe something I turned off by accident?
Thanks,
Mike

Thanks for the helpful tips.
The screens were taken at 100%, cropped for space and unfortunately optimized as jpegs. But you can see that the after image has lines and jagged edges instead of a smoother gradient and softer edges.
Unfortunately my computer can no longer support 3D since Photoshop CC requires a video card with 512mb of vram. I only have 256mb.
I've tried a few different performance changes in preferences, but nothing stood out as the cause.
The only work around I found was to export from illustrator as a png but that negates the usefullness of smart objects.
Thanks again,
Mike

Smart Object Anti-Aliasing issues in PS CS5

I am having a heck of a time working with smart objects that contain transparency in CS5. Here is an example of what I'm experiencing:
1,700px smart object scaled down to 156px. No transparency in SO. Good anti-aliasing.
Same smart object, but with a layer mask or transparency in the smart object. But alas: horrible anti-aliasing, throughout the entire image.
I frequently embed my transparency within the SOs I work with, due to the limitations of linking embedded SOs with layer masks etc. I experienced no problems in CS3. I'm thinking this is a bug? Does anyone have any insight? Thanks!
UPDATE: after performing many tests, and noticing that having transparency in a smart object does not necessarily lead to poor anti-aliasing in the parent image, I have narrowed-down the issue. The issue will occur only if at least an antire column or row of pixels (of any height/width) along the border of the image are transparent. It does not matter if the transparency is at the top, bottom, sides, or surrounding the image, but it must take up some amount of an entire side. This is looking more and more like a bug... Is anyone able to replicate the issue? (Adobe engineers?) Thanks.

Here is the file I'm seeing this in. Incidentally, if I drag the problematic smart object to another open image, the appearance is the same (Photoshop is, after all, the epitome of wysiwyg software). But this works both ways: I can also re-create the smart object in another document without the poor anti-aliasing, then drag it into the original image and it will still look fine. (in this file there are two side-by-side, so that you can compare the two. you can also play with the smart object on the left to see the anti-aliasing go from good to bad; just go into the SO and delete a row or column of pixels from the border and re-save).
http://dl.dropbox.com/u/8162462/SO-aa-issue%3F.tif
(i used Dropbox; lmk if there's a better way to post a file in this forum)
Since I just started using CS5 (from CS3), I have suspicions that it may be a version translation issue (either in the TIFF or smart object). Either way, I'm glad that this is not a common or easily-reproduced issue. Let me know if you learn anything from the file
Thanks,
Cory

Smart Object and blend mode issue

I have an object that I moved from another image and needed to resize. The object is an image of a bottle and glass, with both the bottle and glass having reflections from their base. They both also have some layer masks with the reflections. I grouped the glass and bottle and created a smat object before the move to the new file). Anyway everything worked fine, except the reflections are much stonger in the new file (they are sitting over the same colored backgrond as in the original. If I open up the smart object and put a background behind the images and the reflections (background is transparent)everthing looks as they should. The reflections have a blend mode of multiply).
So why does the smart object not render the reflections properly (without lowering the opacity more within the smart object group) they appear almost at 100% in the new file. Any suggestions?
Can't post the files as this happened at work.
Thanks
Jeff

Anything to do with soft proofing? Does the new document have the same colour space as the original?

Photoshop, smart objects and dynamic filters performance issues

Hello,
I am quite new to Photoshop, after several years with Capture NX 2 to process thousands of NEF and RW2 files (RAW from Nikon and Panasonic).
I use Photoshop to read RAW pictures, convert them to a smart object, then apply several dynamic filters, mainly from the Nik Collection (Dfine, Color Efex Pro, Sharperner Pro), sometimes Topaz Denoise. I do that with actions, so I can batch process many pictures.
But sometimes I have to manually adjust some settings, and this where I do not really understand the way Photoshop works. If I have to adjust let say the last filter on the stack, Photoshop reprocesses all the filters below, which can be very tedious as this takes lot of time.
Is there a way to tell Photoshop to keep all intermediate data in memory, so if you have to adjust one of the last filters the process starts immediately?
Any help would be greatly appreciate.
Frederic.

Thank you Chris.
I am surprised, as for years there has been a lot of discussions about Capture NX2 which was supposed to be slow. In fact, when using the same filters (+ Nik Color Efex), NX2 is much much faster than Photoshop, and when you have to make an adjustment in any of the setttings, you can do that immediateley.
Of course, Photoshop is completely opened and NX2 totally closed (and now not supported anymore).
But, I really don't know how to adapt my workflow, except buying the most powerful PC possible (I already have 2 which are quite powerful), and this will still be far from being comfortable. I am used to tune manually many many pictures (adjust noise reduction, sharpening, light, colors ...), and this was quite fast with NX2.
I am probably not on the correct forum for this, and I will try to investigate elsewhere.
Anyhow, thank you for your answer.
Frédéric

Why do vector shapes in scaled smart objects blur?

This remains a point of frustration.
Why does converting a vector shape to a smart object in Photoshop mean that it's then treated as a bitmap and blurs when scaled up?
If i paste the same vector shape into Illustrator and then back into Photoshop as a smart object it then behaves correctly, and remains sharp.
See the image for example of what i mean. Left is the master shape, centre is it converted into a smart object in Photoshop, right pasted to and from Illustrator. These were then scaled 300% resulting in the centre one blurring.
I don't really want to have to invovle Illustrator in this way and keep all my vector work in Photoshop now it has the tools to do so, but this issue creates me a lot of extra work.
Or am i doing something wrong?
Rob

Smart Object layers are transform to other sizes through interpolating the pixels rendered for the embedded object not be using vector graphics on the embedded object.. If your resize resizes the pixel count way un the image will become soft. Yoy can try seting your Photoshop Default interpolation setting to other setting then Adobe default Bicubic Automatic to something like plain bicubic which IMO is a better general purpose option then Bicubic Automatic.
You can also open the embedded object by double clicking the smart layers smart object icon in the layers palette. Once opened in Photoshop resize the vector graphic using Image size and save the embedded vector object larger. Photoshop will update the smart object layers content then.

RAW as Smart Objects - Lock Edge Pixel Opacity During Resize

I'm a professional fine art printer. I prepare images for large format printing, often starting from the original RAW files. Since the feature to open RAW files as Smart Objects in Camera Raw was introduced, I've been doing that, as it allows me to go back into the Raw file at anytime and re-tweak as I layer. I love this option and it is totally indispensable to my workflow.
HOWEVER, I find a serious flaw when resizing the image for final print, or even when resizing for web-output. If I do any interpolation (pixel resizing) up or down, the edge pixels are not locked in place, and treated as if they are a floating object, therefore the edge pixels usually show up at a lower opacity, (see attached image). This KILLS my workflow! It means I have to completely flatten my work and then resize, loosing all my groovy layers and the ability to go back into Camera Raw and make final tweaks while I make test prints and final decisions with the client by my side.
Even worse, when I apply the final print sharpening and flatten the file to send out, the edge transparency issue is compounded, and the sharpening adds an ugly halo around the whole image, BLAH!
What I need is a way for Smart Objects with the exact same pixel dimensions as the file to lock their edge pixels at the current opacity when resizing. In other words, I need Photoshop to treat the Smart Object as a true Background Layer for certain purposes, while still being able to go back into Camera Raw as I like. I notice the ability to lock transparency is gone on Smart Objects, which I'm sure is necessary for compositing, but not for what I'm doing at all.
Is there anyway this can be done in the current CS5 or 5.5 (haven't upgraded yet) that I'm simply missing? Can anyone from Adobe confirm that this is something you'll look into for me?
Thanks so much, absolutely loving Adobe products these days, you guys rock!
Best,
-B

I'm not going to say anything about the abysmal rendering of Vector Smart Objects in CS6 because it'll be beating a dead horse but I can explain the issues you see with measurements after scaling.
The slightly disproportionate scaling and half-pixel shift of the centre is unavoidable when it happens because the resulting Smart Object/Vector Smart Object must measure an integer number of pixels in height and width and be perfectly aligned to the document pixel grid. That's true in CS5 and CS6.
Say a SO/VSO originally measures 102 x 103 pixels and you scale it by 50%. The Options bar may say the result is 51 x 51.5 px but the result will really be 51 x 52 px, and therefore the new height will really be 50.49% of the old height.
The original SO/VSO is an even number of pixels wide and an odd number of pixels high, therefore its centre will be halfway down a pixel. The 50%-scaled SO/VSO is an odd number of pixels wide and an even number of pixels high, therefore its centre will be halfway across a pixel.

Smart Object import from Illustrator to Photoshop ( CS5 )

Hello !
Here's the thing:
I have an icon in Illustrator and I'm designing a website in Photoshop so I copy and paste that icon as a Smart Object in Photoshop and everything is perfect but when I resize that Smart Object is not perfect anymore.
*The document is 200 %
-The first icon is the original file I import from Illustrator and It's 100%
-I resize the second icon to 70%
Now look at those gray light lines around the second icon. Why is that happening ? How can I fix it ?
Thanks !
PS: Sorry for my English I just speak a little bit.

Hi, again, Sunniess.
Now look at those gray light lines around the second icon. Why is that happening ? How can I fix it ?
You may be sorry you asked. I didn't have time to bore you with the answer to that earlier.
The gray lines are being generated in Ps, so this should be of interest to anyone who works with small images in Ps.
When you export from Illy using the clipboard, Illy rounds to the nearest whole pixel. A rounded rectangle is created in Illy measuring 73x30 pixels. If you scale the rectangle 70% in Illy, the new rectangle measures 51.1 x 21 pixels. But it pastes into Ps as 51x21 pixels.
If you import the 73x30 pixel image into Ps and scale 70% , instead of 51x21 pixels, you will get either 52x21, 53x21, 52x23 or 53x23 pixels, depending on where the Reference point locator (highlighted below) is set in the Transform Toolbar. The gray lines are the extra pixels.
Why the extra pixels? The extra pixels are a form of dithering. When you scale the 73x30 imported image 70% in Ps, you get 51.1 x 21 pixels, same as in Illy. But Ps doesn't round to the nearest pixel. It creates fractional pixels. In the screenshot below, the rectangle is rendered 52x21. The lines at top and bottom are sharp because the pixel height is a whole integer, 21. But the width is 51.1. There's a decimal fraction. The gray vertical bar at right is how Ps represents fractional pixels. The .1 of 51.1. Ps can't actually make .1 of a pixel black. So instead it makes 1 pixel .1 black by assigning 10% opacity.
If the Reference point locater is set as below, you get a different result. Now the rectangle renders at 53x23 pixels. You now have gray rows of pixels at top and bottom, as well as both sides. The height is still really 21 pixels, but since it is transforming from the center and it's an odd number, Ps splits a pixel, assigning .5 black pixels at the top, and .5 black pixels at the bottom, which it represents with 2 rows of pixels at 50% opacity. Similar thing with the ends, except they are lower opacity because they represent smaller fractions of a pixel. This pretty much reproduces what your icon looks like.
Below is a closeup of the above rectangle over a blue background. The rows of pixels aren't actually gray. They are semi transparent black.
The point is, how the Reference point locator is set can have unexpected influence on the results, particularly when downsizing small images. And will be most noticable on straight vertical or horizontal edges.
As if that weren't enough, there are options in your General Preferences that affect the results of resizing images.
I copied and pasted your icon into Ps, then scaled it 70% at two different settings.
The top is Bicubic, the botttom is Nearest Neighbor.
A significant difference. And this interacts with the Transform Locator setting to further confuse the issue. But if you resize in Illy you avoid all this.
If you resize in Ps, it's good to be aware of this stuff. This all happens in Ps. It really has nothing to do with Illy. If you must scale in Ps and get noticable rows of fractional pixels, it's easy enough to select the rows and just delete them. Or fill them. That's essentially what Illy does when it copies to the clipboard.
Your English is fine. I hope mine makes as much sense.
Peace,
Lee

Smart Object Rendering Issue

Similar Messages

Maybe you are looking for