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:

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 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 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.

Camera Raw / smart object ?

Using CS3 / CR / Bridge
Scenario:
I've shot 500 wedding images, sorted & edited them in Bridge. Now I'll look at each one in camera raw (in Bridge) and make any needed adjustments. I use CR and adjust / sync as many similar files as I can; zipping thru the 500 images quickly and save without opening, then in Bridge > Tools > Photoshop > Image Processor, I use the image processor to process all the 500 images (while I sleep), and save as tiff or psd. I set the CR options to process as a Smart Object. But the files don't process a SO.
Question:
Is there a way to process /batch process the 500 images and have them saved so later when I open them, they open as smart objects. I only fine tune the client "Picks" as they don't order all the 500 images shot. Now if I want to alter the color balance, exposure, etc., I can double click the smart object, go back into camera raw and make any adjustments/ refinements, click OK and it updates the file. This mantain's a higher integrity of the file.
In CR I know I can check the box "open as a smart object", but that only seems to apply if I immediately open the file (or files) and then save them. It is not practical or feasible to select 500 files, open and save them at one time. If I save the Raw file(s) to open later, (as in my above workflow) then it will not open as a smart object.
Another way to ask this question:
Why can't I use the Image Processor in Bridge / CR to process my 500 CR files as Smart Objects?
When in CR I can set the options to process as a SO, but that only will process the open file(s) in CR as SO. Not practical to process 500 files.
I checked on the Adobe Exchange but did not find any scripts or actions that would facilitate this.
Does anyone know if what I'm trying to do is possible and how?
Thanks,
JeffN

In an effort to keep this question / answer current, (this question is on listed on two forums) here is an answer from Jeff Schewe from the Photoshop > Mac forum.
31. Jul 29, 2010 3:58 PM in response to: Jeff_N
Re: Camera Raw / smart object ?
Jeff_N wrote:
Jeff S
Any thoughts, suggestions, or can this not be done.
I'm pretty sure it's a bug....when recording the action in CS5, if you change the Workflow Options to open as a Smart Object, ALL the settings are hardcoded into the recorded Open action step. This is wrong...if you open an image and change the Workflow OPtions but DON'T try to open as a Smart Object, the Open action is recorded correctly–only the Workflow Options are recorded and when processed the files properly retain their individual original settings. So, the act of changing the Workflow Options to make a Smart Object is incorrectly hard coding the settings in.

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

Why are we still dependant on Camera Raw to get Smart Objects?

I've been a professional user of both Photoshop and Lightroom since they were created and feel that I'm either missing something simple or maybe just asking too much, but can someone from the engineering team please tell me why we still have to rely on Camera Raw plugins to open the file either directly or as a Smart Object into Photoshop?
It would seem to me that Lightroom should be able to handle the round-trip conversion from Lightroom files to Photoshop Smart Objects and any future edits back in Lightroom. The only reason I can honestly see for the reliance on Camera Raw is to keep us upgrading Photoshop - something I'm sure Adobe would like us to do on a regular basis but in the current economic climate is not always possible.
I want to keep updating Lightroom to ensure the best possible conversions for my clients but don't see why I have to keep upgrading Photoshop to keep Camera Raw up to date when CS5 does everything I currently does everything I currently need. Maybe I'll be proven wrong but I'm guessing this is the way we're heading with the release of Camera Raw 7 along with Lightroom 4. Please tell me if I'm wrong!

Jason Replica wrote:
Situation 2 - Current Situation
We have Photoshop and compatible versions of Camera Raw and Lightroom installed.
I can open a raw image from Lightroom into Photoshop using the "Open in Photoshop as Smart Object" option.
This works fine but when I double-click on the Smart Object it opens back in Camera Raw for editing.
I'd always presumed that Lightroom carried out the conversion rather than Camera Raw in this situation before handing off the data to Photoshop to form the Smart Object. Have I been incorrect in my presumption?
That's where your assumption was wrong...as long as LR & ACR is in lockstep, LR hands off the image to ACR. An ACR Smart Object needs to use ACR to allow editing of the SO. That is a function of ACR and Photoshop. Lightroom can't do a SO because, well, SO's are a function of Photoshop, not Lightroom.
Jason Replica wrote:
Situation 3 - Future Situation - Maybe??
We have Photoshop and Lightroom installed.
I can open a raw image from Lightroom into Photoshop using the "Open in Photoshop as Smart Object" option.
This doesn't rely on Camera Raw to hand-off the data to Photoshop and form the Smart Object as Lightroom is capable of the same type of conversion on it's own. Double-clicking on the Smart Object should then re-open the image in Lightroom (as that's where it came from originally) and allow all the editing that we've come to expect in Lightroom.
Ain't gonna happen because Lightroom can't handle the Photoshop Smart Object SDK...and since the actual rendering of ACR/LR is the same (for the same version) it's a moot point.
Jason Replica wrote:
Ignoring the economics of having to update Photoshop as I know Adobe (and probably Jeff as well ) would like us all to be running the latest version of Photoshop and payout for the updates as soon as they come around, I would think this would be a more sensible option for the future as it would allow more people to keep their existing version of Photoshop, which they've tweaked, wrote actions for and is working very nicely at the moment thankyou while exploring the benefits of the new-and-improved Lightroom.
I really don't have a dog in this hunt–obviously, I always upgrade the moment an upgrade is available...but there are technical limitations (see above) that preclude what you think you want. As far as the economics, a $99 LR upgrade and a $199 Photoshop upgrade ever two years doesn't seem to be a huge hurdle. Add up the LR & PS upgrades and you get a cost of about $12.50/month over the 24 months...yes, it's an added cost but if you want the best user experience and usability it makes sense to keep LR & Photoshop/ACR in sync. You aren't FORCED to upgrade Photoshop...LR4 will work as far back as Photoshop CS3 (not sure about CS2). But then you are locked into the LR processed approach because older versions of ACR can't process the newer versions of LR processing controls.

Liquify as a smart object filter CS6

I understand that I should be able to use Liquify as a smart object filter in CS6 however when I get a layer rendered as a smart object and attempt to use the smart filter Liquify is greyed out.
my only opiton thus far has been to stamp it down and work on the stamped down layer. Am I missing something . I'm using Adobe Photoshop Version: 13.0.6 (13.0.6 20131025.r.54 2013/10/25:21:00:00) x64

I think that is in the photoshop cs6 creative cloud verion 13.1 that the Smart object liquify was added.
(not in the perpetual license versions of photoshop cs6)
Also, it's in photoshop cc (photoshop version 14) as well

Smart objects uneditable -- bug ?

When I try to edit smart objects via right-click>>edit contents (or double-click on the smart oject layer icon for that matter) this happens:
A.) if I disable [preferences>>file handling>>prefer ACR for JPEG files], PS calculates some seconds with intense HDD activity and then nothing happens visually, no window opens-up for editing, but the history log has the usual new entry "edit contents". Repeated tries result in repeated "edit contents" logs, but no visual changes.
[[In one instance the raster grahpic encapsulated into the smart object got enlarged by 200%-300%. But again, no window opened up for editing. I hit "edit contents" 3-4 times and I could always reproduce this. But ever since that day, it never happened to me again).
B.) if I enable [preferences>>file handling>>prefer ACR for JPEG files], ACR launches and displays the raster graphic the smart object is based on. Upon closing ACR, no window opens-up for editing the smart object.
I have been working with smart objects for some months now and everything worked fine. This bug started occurring some 3 weeks ago, but as I said, sometimes it works, sometimes not. I cannot find any regularities as to what could lead to this malfunctioning. The only regularity I found so far (but could be a coincidence) is that the smart objects affected by the bug were always (at least I don't remember any other case) .jpeg files that I opened in Photoshop(CS3) with abovementioned preference set so that ACR launches upon opening a .jpeg file. In ACR I alt-clicked the open button so that it says "open objects". So the smart objects were always based on a single layer .jpeg raster graphic opened in ACR.
My best bet would be that there is something that ACR writes into the smart object that isn't 100% identical to the way Photoshop would write smart object if I:
1) open the .jpeg file in ACR
2) click open/open copy (not open object)
3) convert the raster graphic to a smart object inside Photoshop itself.
But that's only a guess. I have quite a lot of work to do currently, but I hope to be able to provide additional information quickly enough if need be.

OK, going back to the issues I was (a bit incorrectly) describing in my OP:
I’ve been monitoring CS3’s behaviour for the past couple of months and I’ve tried to summarize my observations in a table (see attachment). As you can see, jpegs handling inside smart objects is far from uniform, given the different jpeg-opening possibilities and the interference of different “prefer ACR for jpegs” settings.
I think it’s okay the way it is, but I can also imagine people finding all these combinations a bit confusing and wishing for a more consistent handling (in this regard see also footnote 5 and the bugs).
I hope the table is rather self-explaining. Basically I combined different opening methods with different “prefer ACR 4 jpegs” settings.
For example, the fifth line reads means: disable “prefer ACR 4 jpegs” ==> open a jpeg file in ACR via file>>open as>>filetype:Camera Raw ==> make adjustments in ACR ==> click on “open object” ==> open a new document ==> drag&drop the SMO there ==> transform the SMO ==> enable “prefer ACR” ==> edit contents of SMO ==> ACR opens ==> make adjustments ==> click “OK” ==> SMO is updated ==> check if one of the two bugs occurs
OK, what are these bugs now? I’m not quite sure, but I doubt that it’s by design. Concerning what I’ve called the “auto-resize-bug” (for a lack of a better word): In the second and third case presented in the table, the SMO is updated according to the ACR color modifications but also …. resized! (always downsized as far as I’ve seen).
The “transform-resize-bug” is a problem that occurs from time to time, but I haven’t found a way to reproduce it. Once a smart object is affected by the bug, you can still move it around as you wish, but once you use “edit>>free transform” it mysteriously shrinks in the same way as observed in the “auto-resize-bug”. For some users it might not be a big deal, as you can just enlarge the SMO again as you please, but it can be quite annoying if a SMO has been precisely fitted into the document and you have to redo all the fitting (the values like width/height % won’t help you, because they’ve stayed the same, for example 180%, whereas the SMO has shrinked to a quarter of its size).
If not already fixed in CS4, I guess it would be important to look into this for future releases.

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

Pasted smart objects are distorted in CS6

Any time I paste an object from AI into PS, it's getting horizontally squashed. Here's an example:
1. 12x12 pixel circle in Illustrator, aligned to pixel grid.
2. Pasted into Photoshop as a Smart Object, it's visibly distorted (12x11), but the W/H is inaccurately labeled 100%.
3. After pasted, if I select Edit > Transform > Scale, now the starting W/H are shown with the accurate distorted values.
This is driving me nuts. Can anyone suggest a fix, or is this a bug?

You could be correct that the bad AA is a Mac-only Ps problem. We need more participants to see if any Windows user is affected.
An Illustrator-saved AI or PDF placed into Ps results in the very same bad rendering as a paste. A slightly different but similarly bad AA arises when the placed file is an Illustrator-saved EPS.
The AA bug appears to be related to Photoshop's rasterizing of vector files rather than something to do with the clipboard.
There is no improvement by pasting into a new document created with clipboard dimensions. I had already tried that and I've rechecked now.
Here's an example comparing Ps CS5.1 and CS6 using the same clipboard content. The very same results happen when placing the design as a vector file in the two versions of Ps.
1. Object in Illustrator CS5.1 that's copied to clipboard.
2. The transformation opportunity of the paste into Ps CS5.1. The height is short by a pixel.
3. After correcting the height and committing. A perfect rasterization.
4. The transformation opportunity of the paste into Ps CS6. The height is correct.
5. After committing. A terrible rasterization with gray pixels which should be white.
Other examples will result in the height being initially wrong in Ps CS6 and the height being initially correct in CS5, which is the opposite of this one, and the rendering being differently bad in each version of Ps.

Can you extract higher resolutions from Smart Objects or Linked Smart Objects?

When I am designing at 1x resolution, can I extract assets from smart objects or linked smart objects for 2x or more? If so, how do they scale up?

Yes with caveats.
PSD and Illustrator smart objects are also re-rendered and smoothly scaled to the requested resolution.
Other smart objects (including those with filters) are only scaled up from the resolution they are at within the Photoshop file. If you want them to re-render, you can paste them at 100% resolution into a linked smart object and get the smooth scaling.

Enlarged Smart Objects with vectors inside them appear as resized bitmaps

In Photoshop CC for Mac I have...
Created layers of vector art
Combined them into a smart object
Enlarged the smart object (both via "Transform" and "Image Size")
Upon enlarging, the vector objects look the way an enlarged bitmap would (i.e. fuzzy, pixelated, terrible) instead of crisp and clean as a vector should look. I've double- and triple-checked to make sure all layers have remained vector after resizing and they have.
This is a terrible inconvenience for anyone that works heavily with vector smart objects and resizes them. I use this workflow on a daily basis to make adapting interface elements for various screen resolutions easier, without it I am beyond screwed.
If anyone knows a workaround (or if this requires a setting that I haven't found to be changed) please let me know.
Screenshot proof below:

Read this thread -link http://forums.adobe.com/message/3498406#3498406
you may want to read it from the beginning.
Basically while a smart object layer embedded object may contain vector graphics. Photoshop renders a composite for the embedded object and uses the resulting rendered pixels for the smart object layers pixels. When you transform a smart object layer your transforming those pixels like raster layer using your Photoshop preference interpolation preference.. If you want to resize the vector graphics contained in the embedded object you must open the embedded object into the approbate application and resize the embedded object using vector tools. After you commit the resize. Photoshop will update the embedded object and the layers pixel will be the composite rendered for the updated resized embedded object.

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.

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 objects rendering incorrectly

Similar Messages

Maybe you are looking for