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

Similar Messages

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

Font Anti-Aliasing Issues in HTML/Ajax based Air Applications

It seems that the font-renderer in HTML/Ajax based Air Applications is using some kind of sub-pixel font renderer that is overriding and vastly inferior to the standard Windows ClearType, or any Apple based option as well. This problem is particularly noticable with light text on a dark background, and made worse the smaller the text is. I've put together an example image explaining exactly what I mean at: http://regator.com/fontRendering.png (it's a large image 1126 x 1500 px)
My example shows two fonts at four different sizes rendered in an HTML Air App vs the default Windows Cleartype, as well as using Safari to show the Font style anti-aliasing. In all cases the HTML Air App rendering is far more difficult to read, and in many cases severely distorts the color of the text in a way that other subpixel algorithms do not. As far as I can find after literally hours of googling and searching there's no way to override this in HTML based applications. Is there any solution to this, or a planned fix for the renderer? Other than this rendering issue, the HTML interface for creating Air apps is absolutely brilliant, this is just making my finished product look significantly less polished than it otherwise would if the text were more readable.
Thanks.

Dear caturner81, dear Adobe,
is there a solution to this problem? I'd really love to fix the aliasing thing in Air/HTML!

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?

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

MSI GTX 680 LIGHTNING having MSAA ANTI ALIASING ISSUE

Hey guys!
I have a question concerning my GPU. I would like to know if anyone thinks this is a faulty card or is there something I need to do to fix the issue.
MSAA Anti-Aliasing is causing a very weird blood graphic issue... Toggle it off and the blood looks fine, turn it too 2,4 or 8 and the blood is outlines in glowing yellow craziness(see image link below)!
My card is stock and has never been OC. I've re installed the game, done clean installs of GPU drivers but the error still persists(only if MSAA Anti Aliasing is enabled). Prior to installing new drivers I was getting a OPEN GL error 3 code , the new drivers seem to have fixed that.
This is zoomed in using a camera, it looks the same at all distances. The yellow trace around the blood shines like a light in game. This does not happen randomly, all blood splatter in the grass looks this way when
MSAA Anti-Aliasing is enabled.
Hope someone can help!
Thanks for reading,
cheers!

Quote from: Svet on 13-February-13, 10:31:43
list full system specifications, read >>Posting Guide<<
does the same hapends in other games?
what vga drivers you use?
Hey thanks for replying! Sorry I will post my system info below.
I just updated my drivers to 313.96 from 310.70. With the 310.70 driver I was experiencing the MSAA issue(above post) but also with the I was getting a full game crash after 20-30 mins of game play. The 313.96 resolved the crash but not the MSAA issue.
System
Board- ASUS|P8Z77-V PRO Z77
VGA- MSI 680GTX LIGHTNING
PSU -CORSAIR | AX1200I 1200W RT
CPU- INTEL|CORE I7 3770K 3.5G 8M R
MEM- 4Gx4|CORSAIR CMZ16GX3M4X1600C9
SSD -240G|INTEL SSDSC2CT240A3K5 R
HDD- 1 TB WD Black Caviar
COOLER- WATER COOLER CORSAIR| CWCH100 R
OS- WIN7 64BIT
CASE- CORSAIR OBSIDIAN 650D
Opt Drv- ASUS...
I can post a DxDiag if needed too!

Anti-Alias, Smart Objects and Photoshop

I'm using photoshop to create a poster for a client of mine. I placed vector graphics from illustrator into my photoshop document, creating smart objects. As you can see, below, it looks like an Anti-Aliasing issue, where jagged lines are EVERYWHERE. However, you can also observe that the text (created in photoshop) also appears to be fuzzy/jagged.
This issue can be seen on the print out, as well, so it doesn't appear to be anything in the preview...
The Anti-Aliasing option in the transform toolbar is greyed out for me. I've gone through all the settings and i can't seem to find anything that may do this to my file (and it only seems to be affecting this one file).
Version is as follows: 14.2.1 x64
Any and all help is greatly appreciated.

There are no jagged lines in that example - you're just rasterizing at a REALLY low resolution.

Photoshop CS6 - Pasting Smart Objects from InDesign CS6 look awful

Since upgrading from CS5 I'm having a huge problem using Smart Objects.
What:
Smart Objects pasted from InDesign into Photoshop are pixelated and corny beyond belief. Originating material placed in InDesign is hi-res (e.g. 600ppi) but when pasted in PS it looks crappy.
How:
Selecting an image in InDesign and pasting it in PS in a 72ppi file.
Typically I need to copy elements from previous art in ID and re-compose and use for web.
Why:
Can't seem to fix it. Have tried with Anti-Aliasing both on and off to no avail. None of the Image Interpolation settings affect this either.
Only solution is to scale the placed Smart Object to something like 400% where it suddenly looks nice again, rasterize and then scale it back down.
Theory:
Smart Object scaling is flawed in PS CS6.
Note: All scaled images in InDesign already look gritty and awful. Even with Display Performance: High Quality set (using default settings). Seems to me like CS6 scaling is b a d.
Anyone else seeing this?
Thanks
Image 1: Smart Object rasterized at same size as placed. (ouch. awful.)
Image 2: Smart Object Scaled to 400%, rasterized and then scaled back to original size (yum yum, like it used to be without up-rasterize-down-scaling)

That does not resolve the anti-aliasing issue in CS6 - it still looks rather bad.
The anti-aliasing sampling method applied to smart vector objects is just extremely bad looking. And it is not merely an issue in Photoshop: exporting artwork from Illustrator at web/screen resolution using the web export is absolutely abysmal looking (not other word applies here, unfortunately).
I explain more about this issue here: http://forums.adobe.com/message/6002543#6002543
The best option is to blow up the artwork, rasterize, and then scale down with bicubic or bicubic automatic, depending. But even then you will not achieve the same quality that can be attained with other tools that, for example, support catmul rom and mitchellnetravali for downsampling.
Anyway, Adobe applications are very weak when it comes to proper downsampling and file size optimization for web and screen graphics. You're better off looking someplace else.

Error: Could not edit original smart object ...

Hi - I'm getting the following error when double clicking on a Smart Object in Photoshop (CS4)
"Could not edit original smart object because the application which created the smart obejct could not be launched."
Notes
1. The SO was pasted into the psd file moments before from Illustrator.
2. Both applications are open
3. Both files sit on the same disk.
4. XP Pro.
Does anyone have an idea how to get PS to launch its sister program?
Thanks,
Sean

HI, I just had the same problem with cs5 on win7. Photoshop cs5 would not open a smart object created in AI CS4 into CS5.
Turns out I had, somehow, lost all my file associations to .ai and .eps files. When I went into properties and told win 7 to open .ai and .eps files with illy all my troubles went away.
Hope my solution helps someone else with the same prob.
jeff

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.

Bitmap smart objects and anti aliasing, Photoshop CC

Photoshop CC is doing a poor job of rendering bitmap smart objects, and I saw Chris Cox mention the checkbox to enable anti aliasing for placed smart objects. This works with vector smart objects, but this box is grayed out for bitmaps that I've converted to smart objects. The smart object bitmap renders poorly when manually rasterized too. I don't recall having this problem in previous versions of Photoshop. For now I'm going to avoid converting bitmap elements to smart objects so I get decent transforms.

There are no jagged lines in that example - you're just rasterizing at a REALLY low resolution.

CS5 bug rendering anti-aliased text in 'Save for web'

Seems like there's a bit of a bug when using 'Save for web and devices' with thin weights of type in CS5 for Mac. Although thin type looks fine while working in Illustrator, as soon as you enter the 'Save for web' dialogue, it gets badly mangled. Looks like this issue has been present at least since CS4. It does not happen in Photoshop. It looks particularly bad for light text on a dark background.
Some people may say "sure, Illustrator is not really meant for intensive bitmap work". However, with features like 'pixel preview' and 'snap to pixel', Illustrator has (generally) become a very viable tool for web design, and personally I much prefer it to Photoshop. It is also clear that Adobe intends it to be usable in this manner. So the anti-aliasing render bug is definitely a problem. Just surprised they didn't address it when CS5 was born.
I put up some example images on http://www.thesheep.co.uk/2011/06/24/illustrator-save-for-web-anti-aliasing-problems/ to illustrate the problem.
Does anyone have any clever work-arounds for this? It's a bit annoying to have to move stuff over to PS before exporting, but maybe that's what I have to do. Hopefully Adobe will address this soon.

Hi,
I am experiencing this same problem of pixelated gifs when I use the "save for web" dialog from Illustrator, but this solution has not worked for me. I have tried the trick of using type-optimized anti-aliasing, but it doesn't change the output at all. I've done this from within the "Image size" tab as well as through Effect>Rasterize>Options)Anti-aliasing: Type Optimized. My image is a logo made entirely from text, although for some of it I used "outline path", so I'm not sure if it still qualifies as text...I'm a newbie at this stuff, so the technical details are still quite opaque to me.
Does anyone know of a solution to this that does not require me to add Photoshop to my workflow?
I'm using Illustrator in CS5, version 15.0.2.
Thanks in advance
Jonathan

Opening DNG as a Smart Object into Photoshop CS5?

I am using a Windows 7 64 bit platform and CS5 64 bit. I have the most recent Camera Raw plug in for my Nikon D3100 camera. In Bridge you are supposed to be able to open a dng file in Camera Raw, make your corrections and then by holding the Shift key it should change the open file button to open it as a Smart Object. When I do that nothing opens in in Photoshop.
Any suggestions?
P

Jeff Schewe wrote:
pbfp wrote:
Can you tell me how to access the workflow settings?
Pretty simple (and the settings are sticky), open a raw image and in the center where the processing info is shown (lower center link) which acts both as an info readout AND a button to change the Workflow Options settings, click on this link...it'll give you a dlog to change the Workflow Settings.
Alter the settings and click Done (cancel doesn't work since it works as a Cancel).
Thereafter, unless you make changes, the Workflow Options should be sticky.
Thank you Jeff for the information.
Please let me know if you think the worflow settings are wrong: Here is how the workflow is currently set: Space: Adobe RGB 1998; Depth: 16bits/channel; Size 34072 x 4608 (14.2 MP); Resolution: 260 p/in.; Sharpen: None; Amount: none; The bix is checked to open in Photoshop as a Smart Object.
Now here is the thing. If I am in Bridge and double click on a dng file or right click on a selection of files and choose Open in Photoshop, it opens a Camera Raw window for the file/s and then if I click on the open objects button, it does open them in Photoshop as smart objects. The problem is that if I select, from the Bridge pop=up menu to open the selected file/s in Camera Raw, it is then that they do not get sent to Photoshop as smart objects. Nothing happens, they just don't open in Photoshop.
I am also having a very hard time sending dng files from Lightroom into Photoshop. So clearly there is something not "connected" properly. Or maybe it is not clearly, but I am supposing that there might be some general issue. Any thoughts would be greatly appreciated.
P

PS CS5.1 crashes when using file open but not with bridge or "open as smart object"

I'm using a Mac with Snow Leopard and Photoshop CS5.1 Extended
When i try to open a file largen than ~50MB with double click in finder or with file>open in PS, the program loads the psd and shows it, then 2-3 seconds later PS crashes. If the psd is under ~50MB everything is fine.
If i open it with file>open as smart object or via the mini bridge, everything is fine, and i can work with it.
How can this be fixed?

Make sure you submit your crash report as it helps us track and resolve code for crashing issues.
Submitting Crash Reports: http://adobe.ly/gNJWVY
If you post one of you crash reports here?
Location of Crash Reports:
Users/<your user name>/Library/Logs/CrashReporter

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.

Smart Object Anti-Aliasing issues in PS CS5

Similar Messages

Maybe you are looking for