Resizing a circular smart object in CS6 results in flat sides

Resizing a circular smart object in CS6 results in flat sides, whereas in CS5 the sides would remain rounded.
Both the images below were resized using Free Transform (Apple+T) and typing in a height of 88px for the dimensions of the circle. The dropshadow is a layer effect and the background is a solid colour.
This might not seem like a big deal to some people but for me it would mean I'd have to change my workflow and figure out a method of resizing to avoid the flat eges.
CS5:
CS6:
Any ideas?

I am able to replicate flat edges in both Photoshop CS5 and CS6 with the circular object occupying the full canvas, right to the edges, inside the smart object.
Photoshop CS5:
Photoshop CS6:
Here's the file if you want to look at it yourself:
http://Noel.ProDigitalSoftware.com/temp/RoundSmartObject.zip
Your workaround to getting square edges on downsized Smart Objects is always to leave a few pixels to spare around the edges of your Smart Object - i.e., don't trim it to the very edges.
-Noel

Similar Messages

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

Original filename for Smart Objects in CS6

After processing a camera raw image in ACR, I want to open the image in CS6 as a Smart Object.
Then I want to run a java script that depends on the original filename. Where in the metadata can I find the original filename?
Background: I have a script that executes very well if the file is opened in CS6 as a regular layer. However, when I open a file as a Smart Object, the script fails, complaining about an invalid filename.
The problem is associated with my favorite time-saving script and I am very keen to resolve the problem.   :-(
Thank you for your assistance.
BA

rj acton wrote:
After processing a camera raw image in ACR, I want to open the image in CS6 as a Smart Object.
Then I want to run a java script that depends on the original filename. Where in the metadata can I find the original filename?
Background: I have a script that executes very well if the file is opened in CS6 as a regular layer. However, when I open a file as a Smart Object, the script fails, complaining about an invalid filename.
I think the the only reason it works when you open them as a regular layer is because of your work-flow and habits. Try opening it twice as a normal layer an see if it works.
When you open a RAW file through ACR as a normal layer and as a smart object layer there is no backing file associated with the open document yet.   I feel you problem is you script is using something like the document name.   If you look at the title in the image floating window or tab you will see that Photoshop has assigned a name the first time you open it as a normal layer you will see something like filename.cr2 @ 25% (RGB16) the second time you will see filename-2 @ 25% (RGB16) when you open as Object you will see filename as smart object-1 (filename, RGB16). These title will change when you save the document to a image file type the title will change to the associated backing file you just saved.
I you look at Photoshop File info you can see all the image metadata and you can find the RAWFileName you want here a text file I wrote using a Photoshop script
It is enev in small jpef file saved from raw conversions if you don't strip mete data
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="Adobe XMP Core 5.3-c011 66.145661, 2012/02/06-14:56:27        ">
   <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
      <rdf:Description rdf:about=""
            xmlns:xmp="http://ns.adobe.com/xap/1.0/">
         <xmp:ModifyDate>2010-08-16T22:47:35-04:00</xmp:ModifyDate>
         <xmp:CreateDate>2009-04-25T15:20:46</xmp:CreateDate>
         <xmp:Rating>0</xmp:Rating>
         <xmp:MetadataDate>2010-08-16T22:47:35-04:00</xmp:MetadataDate>
         <xmp:CreatorTool>Adobe Photoshop CS5 Windows</xmp:CreatorTool>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:dc="http://purl.org/dc/elements/1.1/">
         <dc:format>image/jpeg</dc:format>
         <dc:creator>
            <rdf:Seq>
               <rdf:li>McAssey</rdf:li>
            </rdf:Seq>
         </dc:creator>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:aux="http://ns.adobe.com/exif/1.0/aux/">
         <aux:SerialNumber>237498</aux:SerialNumber>
         <aux:LensInfo>300/1 300/1 0/0 0/0</aux:LensInfo>
         <aux:Lens>300.0 mm</aux:Lens>
         <aux:LensID>142</aux:LensID>
         <aux:ImageNumber>48302</aux:ImageNumber>
         <aux:FlashCompensation>0/1</aux:FlashCompensation>
         <aux:OwnerName>McAssey</aux:OwnerName>
         <aux:Firmware>1.2.3</aux:Firmware>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:crs="http://ns.adobe.com/camera-raw-settings/1.0/">
         <crs:RawFileName>LO2G5037.CR2</crs:RawFileName>
         <crs:Version>6.1</crs:Version>
         <crs:ProcessVersion>5.7</crs:ProcessVersion>
         <crs:WhiteBalance>Custom</crs:WhiteBalance>
         <crs:Temperature>5350</crs:Temperature>
         <crs:Tint>-22</crs:Tint>
         <crs:Exposure>0.00</crs:Exposure>
         <crs:Shadows>5</crs:Shadows>
         <crs:Brightness>+65</crs:Brightness>
         <crs:Contrast>+25</crs:Contrast>
         <crs:Saturation>0</crs:Saturation>
         <crs:Sharpness>25</crs:Sharpness>
         <crs:LuminanceSmoothing>0</crs:LuminanceSmoothing>
         <crs:ColorNoiseReduction>0</crs:ColorNoiseReduction>
         <crs:ChromaticAberrationR>0</crs:ChromaticAberrationR>
         <crs:ChromaticAberrationB>0</crs:ChromaticAberrationB>
         <crs:VignetteAmount>0</crs:VignetteAmount>
         <crs:ShadowTint>0</crs:ShadowTint>
         <crs:RedHue>0</crs:RedHue>
         <crs:RedSaturation>0</crs:RedSaturation>
         <crs:GreenHue>0</crs:GreenHue>
         <crs:GreenSaturation>0</crs:GreenSaturation>
         <crs:BlueHue>0</crs:BlueHue>
         <crs:BlueSaturation>0</crs:BlueSaturation>
         <crs:FillLight>0</crs:FillLight>
         <crs:Vibrance>+21</crs:Vibrance>
         <crs:HighlightRecovery>0</crs:HighlightRecovery>
         <crs:Clarity>0</crs:Clarity>
         <crs:Defringe>0</crs:Defringe>
         <crs:HueAdjustmentRed>0</crs:HueAdjustmentRed>
         <crs:HueAdjustmentOrange>0</crs:HueAdjustmentOrange>
         <crs:HueAdjustmentYellow>0</crs:HueAdjustmentYellow>
         <crs:HueAdjustmentGreen>0</crs:HueAdjustmentGreen>
         <crs:HueAdjustmentAqua>0</crs:HueAdjustmentAqua>
         <crs:HueAdjustmentBlue>0</crs:HueAdjustmentBlue>
         <crs:HueAdjustmentPurple>0</crs:HueAdjustmentPurple>
         <crs:HueAdjustmentMagenta>0</crs:HueAdjustmentMagenta>
         <crs:SaturationAdjustmentRed>0</crs:SaturationAdjustmentRed>
         <crs:SaturationAdjustmentOrange>0</crs:SaturationAdjustmentOrange>
         <crs:SaturationAdjustmentYellow>0</crs:SaturationAdjustmentYellow>
         <crs:SaturationAdjustmentGreen>0</crs:SaturationAdjustmentGreen>
         <crs:SaturationAdjustmentAqua>0</crs:SaturationAdjustmentAqua>
         <crs:SaturationAdjustmentBlue>0</crs:SaturationAdjustmentBlue>
         <crs:SaturationAdjustmentPurple>0</crs:SaturationAdjustmentPurple>
         <crs:SaturationAdjustmentMagenta>0</crs:SaturationAdjustmentMagenta>
         <crs:LuminanceAdjustmentRed>0</crs:LuminanceAdjustmentRed>
         <crs:LuminanceAdjustmentOrange>0</crs:LuminanceAdjustmentOrange>
         <crs:LuminanceAdjustmentYellow>0</crs:LuminanceAdjustmentYellow>
         <crs:LuminanceAdjustmentGreen>0</crs:LuminanceAdjustmentGreen>
         <crs:LuminanceAdjustmentAqua>0</crs:LuminanceAdjustmentAqua>
         <crs:LuminanceAdjustmentBlue>0</crs:LuminanceAdjustmentBlue>
         <crs:LuminanceAdjustmentPurple>0</crs:LuminanceAdjustmentPurple>
         <crs:LuminanceAdjustmentMagenta>0</crs:LuminanceAdjustmentMagenta>
         <crs:SplitToningShadowHue>0</crs:SplitToningShadowHue>
         <crs:SplitToningShadowSaturation>0</crs:SplitToningShadowSaturation>
         <crs:SplitToningHighlightHue>0</crs:SplitToningHighlightHue>
         <crs:SplitToningHighlightSaturation>0</crs:SplitToningHighlightSaturation>
         <crs:SplitToningBalance>0</crs:SplitToningBalance>
         <crs:ParametricShadows>-25</crs:ParametricShadows>
         <crs:ParametricDarks>-13</crs:ParametricDarks>
         <crs:ParametricLights>+13</crs:ParametricLights>
         <crs:ParametricHighlights>+25</crs:ParametricHighlights>
         <crs:ParametricShadowSplit>25</crs:ParametricShadowSplit>
         <crs:ParametricMidtoneSplit>50</crs:ParametricMidtoneSplit>
         <crs:ParametricHighlightSplit>75</crs:ParametricHighlightSplit>
         <crs:SharpenRadius>+1.1</crs:SharpenRadius>
         <crs:SharpenDetail>25</crs:SharpenDetail>
         <crs:SharpenEdgeMasking>27</crs:SharpenEdgeMasking>
         <crs:PostCropVignetteAmount>0</crs:PostCropVignetteAmount>
         <crs:GrainAmount>0</crs:GrainAmount>
         <crs:LensProfileEnable>0</crs:LensProfileEnable>
         <crs:LensManualDistortionAmount>0</crs:LensManualDistortionAmount>
         <crs:PerspectiveVertical>0</crs:PerspectiveVertical>
         <crs:PerspectiveHorizontal>0</crs:PerspectiveHorizontal>
         <crs:PerspectiveRotate>0.0</crs:PerspectiveRotate>
         <crs:PerspectiveScale>100</crs:PerspectiveScale>
         <crs:ConvertToGrayscale>False</crs:ConvertToGrayscale>
         <crs:ToneCurveName>Strong Contrast</crs:ToneCurveName>
         <crs:CameraProfile>Camera Faithful</crs:CameraProfile>
         <crs:CameraProfileDigest>07AA307EAF63019A907C3A103EC361D0</crs:CameraProfileDigest>
         <crs:LensProfileSetup>LensDefaults</crs:LensProfileSetup>
         <crs:HasSettings>True</crs:HasSettings>
         <crs:HasCrop>False</crs:HasCrop>
         <crs:AlreadyApplied>True</crs:AlreadyApplied>
         <crs:ToneCurve>
            <rdf:Seq>
               <rdf:li>0, 0</rdf:li>
               <rdf:li>32, 16</rdf:li>
               <rdf:li>64, 50</rdf:li>
               <rdf:li>128, 128</rdf:li>
               <rdf:li>192, 202</rdf:li>
               <rdf:li>255, 255</rdf:li>
            </rdf:Seq>
         </crs:ToneCurve>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:photoshop="http://ns.adobe.com/photoshop/1.0/">
         <photoshop:DateCreated>2009-04-25T15:20:46</photoshop:DateCreated>
         <photoshop:LegacyIPTCDigest>C919DE8C578CC777664AB2BCEBAFE2ED</photoshop:LegacyIPTCDigest>
         <photoshop:ColorMode>3</photoshop:ColorMode>
         <photoshop:ICCProfile>sRGB IEC61966-2.1</photoshop:ICCProfile>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:xmpMM="http://ns.adobe.com/xap/1.0/mm/"
            xmlns:stEvt="http://ns.adobe.com/xap/1.0/sType/ResourceEvent#"
            xmlns:stRef="http://ns.adobe.com/xap/1.0/sType/ResourceRef#">
         <xmpMM:InstanceID>xmp.iid:53B401F530A9DF11A629E42CB0F33EB0</xmpMM:InstanceID>
         <xmpMM:DocumentID>xmp.did:E719AF78E386DF1185EABAB6DC507A64</xmpMM:DocumentID>
         <xmpMM:OriginalDocumentID>xmp.did:E719AF78E386DF1185EABAB6DC507A64</xmpMM:OriginalDocumentID>
         <xmpMM:History>
            <rdf:Seq>
               <rdf:li rdf:parseType="Resource">
                  <stEvt:action>saved</stEvt:action>
                  <stEvt:instanceID>xmp.iid:E719AF78E386DF1185EABAB6DC507A64</stEvt:instanceID>
                  <stEvt:when>2010-07-03T16:42:18-04:00</stEvt:when>
                  <stEvt:softwareAgent>Adobe Photoshop CS5 Windows</stEvt:softwareAgent>
                  <stEvt:changed>/</stEvt:changed>
               </rdf:li>
               <rdf:li rdf:parseType="Resource">
                  <stEvt:action>converted</stEvt:action>
                  <stEvt:parameters>from image/tiff to image/jpeg</stEvt:parameters>
               </rdf:li>
               <rdf:li rdf:parseType="Resource">
                  <stEvt:action>derived</stEvt:action>
                  <stEvt:parameters>converted from image/tiff to image/jpeg</stEvt:parameters>
               </rdf:li>
               <rdf:li rdf:parseType="Resource">
                  <stEvt:action>saved</stEvt:action>
                  <stEvt:instanceID>xmp.iid:E819AF78E386DF1185EABAB6DC507A64</stEvt:instanceID>
                  <stEvt:when>2010-07-03T16:42:18-04:00</stEvt:when>
                  <stEvt:softwareAgent>Adobe Photoshop CS5 Windows</stEvt:softwareAgent>
                  <stEvt:changed>/</stEvt:changed>
               </rdf:li>
               <rdf:li rdf:parseType="Resource">
                  <stEvt:action>saved</stEvt:action>
                  <stEvt:instanceID>xmp.iid:52B401F530A9DF11A629E42CB0F33EB0</stEvt:instanceID>
                  <stEvt:when>2010-08-16T22:47:35-04:00</stEvt:when>
                  <stEvt:softwareAgent>Adobe Photoshop CS5 Windows</stEvt:softwareAgent>
                  <stEvt:changed>/</stEvt:changed>
               </rdf:li>
               <rdf:li rdf:parseType="Resource">
                  <stEvt:action>saved</stEvt:action>
                  <stEvt:instanceID>xmp.iid:53B401F530A9DF11A629E42CB0F33EB0</stEvt:instanceID>
                  <stEvt:when>2010-08-16T22:47:35-04:00</stEvt:when>
                  <stEvt:softwareAgent>Adobe Photoshop CS5 Windows</stEvt:softwareAgent>
                  <stEvt:changed>/</stEvt:changed>
               </rdf:li>
            </rdf:Seq>
         </xmpMM:History>
         <xmpMM:DerivedFrom rdf:parseType="Resource">
            <stRef:instanceID>xmp.iid:E719AF78E386DF1185EABAB6DC507A64</stRef:instanceID>
            <stRef:documentID>xmp.did:E719AF78E386DF1185EABAB6DC507A64</stRef:documentID>
            <stRef:originalDocumentID>xmp.did:E719AF78E386DF1185EABAB6DC507A64</stRef:originalDocumentID>
         </xmpMM:DerivedFrom>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:tiff="http://ns.adobe.com/tiff/1.0/">
         <tiff:ImageWidth>2336</tiff:ImageWidth>
         <tiff:ImageLength>3504</tiff:ImageLength>
         <tiff:BitsPerSample>
            <rdf:Seq>
               <rdf:li>8</rdf:li>
               <rdf:li>8</rdf:li>
               <rdf:li>8</rdf:li>
            </rdf:Seq>
         </tiff:BitsPerSample>
         <tiff:PhotometricInterpretation>2</tiff:PhotometricInterpretation>
         <tiff:Orientation>1</tiff:Orientation>
         <tiff:SamplesPerPixel>3</tiff:SamplesPerPixel>
         <tiff:XResolution>2400000/10000</tiff:XResolution>
         <tiff:YResolution>2400000/10000</tiff:YResolution>
         <tiff:ResolutionUnit>2</tiff:ResolutionUnit>
         <tiff:Make>Canon</tiff:Make>
         <tiff:Model>Canon EOS-1D Mark II</tiff:Model>
      </rdf:Description>
      <rdf:Description rdf:about=""
            xmlns:exif="http://ns.adobe.com/exif/1.0/">
         <exif:ExifVersion>0221</exif:ExifVersion>
         <exif:ColorSpace>1</exif:ColorSpace>
         <exif:PixelXDimension>400</exif:PixelXDimension>
         <exif:PixelYDimension>600</exif:PixelYDimension>
         <exif:DateTimeOriginal>2009-04-25T15:20:46</exif:DateTimeOriginal>
         <exif:ExposureTime>1/1000</exif:ExposureTime>
         <exif:FNumber>56/10</exif:FNumber>
         <exif:ExposureProgram>2</exif:ExposureProgram>
         <exif:ISOSpeedRatings>
            <rdf:Seq>
               <rdf:li>800</rdf:li>
            </rdf:Seq>
         </exif:ISOSpeedRatings>
         <exif:ShutterSpeedValue>9965784/1000000</exif:ShutterSpeedValue>
         <exif:ApertureValue>4970854/1000000</exif:ApertureValue>
         <exif:ExposureBiasValue>0/1</exif:ExposureBiasValue>
         <exif:MaxApertureValue>3/1</exif:MaxApertureValue>
         <exif:MeteringMode>5</exif:MeteringMode>
         <exif:Flash rdf:parseType="Resource">
            <exif:Fired>False</exif:Fired>
            <exif:Return>0</exif:Return>
            <exif:Mode>2</exif:Mode>
            <exif:Function>False</exif:Function>
            <exif:RedEyeMode>False</exif:RedEyeMode>
         </exif:Flash>
         <exif:FocalLength>300/1</exif:FocalLength>
         <exif:FocalPlaneXResolution>3520000/1136</exif:FocalPlaneXResolution>
         <exif:FocalPlaneYResolution>2342000/756</exif:FocalPlaneYResolution>
         <exif:FocalPlaneResolutionUnit>2</exif:FocalPlaneResolutionUnit>
         <exif:CustomRendered>0</exif:CustomRendered>
         <exif:ExposureMode>0</exif:ExposureMode>
         <exif:WhiteBalance>0</exif:WhiteBalance>
         <exif:SceneCaptureType>0</exif:SceneCaptureType>
      </rdf:Description>
   </rdf:RDF>
</x:xmpmeta>

Resizing a RAW Smart Object in a PSD

So I Have a PSD file with one pixel bearing layer that is a Smart Object of a Canon 5D2 RAW file. the rest of the PSD consists of adjustment layers with masks.
I ended up resizing the image to about 2000px wide and accidently clicked the "save" button when i was exiting Photoshop CC without undoing the resize. Thus i now have a PSD file that is of lesser pixel quality than i want.
But... the RAW file in the Smart Object is still the same full size RAW file. If i where to resize the PSD back to the size of the RAW file would it resample that layer or would it just resample the Masks on the Adjustment Layers?
Id like to find a way back to before the untimely save on exit.
thanks!
-Tyler

It would just resample the masks in the adjustment layers. Your Smart Object will have no problem being sized back up.

Illustrator Application Window Resizes When Opening Smart Object from PSD

Hi All, I've taken a vector graphic created in AI CS4 and pasted it into my PSD CS4 doc as a smart object. When the original AI file was created the application window was set as I preferred it, filling my screen. When I double click the Smart Object in PSD to edit it back in Illy, the window that contains the application has been switched off of the fill screen mode and is quite a bit smaller. I know it's small but now I have to click the maximize icon in the application bar to get Illy to fill the screen again. It wouldn't be so bad once, but the application window resizes itself every time I punch back into the smart object from PSD.
Any ideas on how I can get the AI environment from switching around on its own??
Win 7, CS4, all patches current, Dual 22" montiors
thnx,
jeff

I just want to point out that when you open the smart object of course it is not the same file as the original but an embedded copy of it.
That might also have something to do with this issue and might also be a photoshop issue with the smart object and one reason might be that Photoshop is see the image as resolution and Illustrator sees it as a dimension and the teams might be able to do something about this but might not actually be aware of it unless you file a report even if it is not a bug it would then be a feature request.
They might not be able to do anything about it but then there might be a clever engineer with an idea, so it might be worth the report.

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.

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 Not Opening in Camera RAW in CS6

I've converted a JPEG to a Smart Object in CS6. When I double-click on the Smart Object icon in the Layer, it opens as a separate JPEG file. What do I need to do to get it to open in Camera RAW as Russel Brown does in this video?

R_Kelly wrote:
JJMack might have been referring to the script and video that is on the script page i linked to.
I did not know about the script. I just knew that ACR can only work on Camera RAw Files and convert the camera sensor RAW data into RGB Images and use setting other then ones set into the camera, ACR can also process Jpeg and Tiff files however Camers Sensor RAW data for thes images nolonger exists in the file. So ACR can not work on the images as well as it can when it has access to the Camera RAW data.
I was somewhat wrong about not being able to edit normal layers in ACR this script sort of makes that posible. What it does is save information about the layers transparenct and layer mask save out the layer as a temp Tiff file and place it back in as a smart object and restor the best it can any layer mask and transparency. You preferences must be set to open Tiff in ACR. While I was somewhat wrong I was bassicly right. The script turns the layer into a Temp Tiff file and places it back in the document as a smart object layer the embedded object is a Tiff file. The temp Tiff file is nolonger needed for the smart object layer has a copy of it in its embedded object.

Smart objects generate huge ( 10 GB) temp files ??

Hi folks. I think there's a bug in CS3's smart object handling. Everytime I move (not resize!) a smart object, the temp file's size increases by some 100-200 MB. I easily get over 10 GB just by moving around a single object repeatedly.
I find that quite weird, given that normal layer moving does not significantly alter the temp file's size. And PS only has to store the smart objects new X and Y coordinates as the object itself does not change. Am I missing something ? Anybody knows what's going on ?

Converting Smart objects back to embedded layers would be a very useful addition. "Return to layers" would be a good term for it.
If you are looking for real world examples where this would be useful Chris
to simplify and bring down the file size of a file that has got out of hand with smart Objects. Some sort of global command "embed all Smart objects" in the layer/smart objects menu would also be useful for this purpose.
Objects of the same res and profile could then be non-destructively edited by swapping them in and out of smart objects for direct editing within the master document.
would be particularly useful when for example you need to detach a single instance of a duplicated SO from the others.
There is sometimes a need to return layers, and adjustments back into the master document to directly modify how they interact with their surroundings in terms of color and masking - for compositing. Its useful for simplicity to have them tucked away as SO's still
Of course data loss due to resampling, bit depth and modes could be greeted with a warning, perhaps the warning could be contextual "this operation will result in data loss, will decrease file size by 75%, change its mode from LAB, and resample the embedded pixels to 120%".
What happens to the smart-filters? if they are there, a choice either to rasterise them or abandon them

LR2:DNG - PSCS3:'Smart Object' workflow question

Hello, I've just started working with DNG files exported as Smart Object from LR2 to PSCS3 and I would appreciate some feedback on my experiences thus far.
Let us assume that I've made basic corrections to _DSC1190.dng within LR2. I then want to apply a filter to a particular region of the DNG file with all of my LR2 adjustments applied.
1. Here are the steps I currently follow:
1.1. Right-click on the DNG file and select 'Edit In'->'Open as Smart Object in Photoshop...'. This results (I believe) in the DNG file with all of my LR2 changes being embedded within a smart object and the resulting temporary file being opened within PSCS3.
1.2. I perform my edits in PSCS3 and save the file as a PSD (i.e. _DSC1190.psd). As long as I was smart about things, I can now go back at any time and alter any of the changes I made in PSCS3, as well as access the DNG file within the smart object to make and ACR changes I desire.
1.3. If I want the new PSD file to be added to my LR2 catalog, I then need to navigate to where it was saved and manually add it.
1.4. If I want to make any exposure adjustments, or really, any adjustments that I'd normally make within LR2 or ACR to _DSC1190.psd, I need to open the file within PSCS3, double click on the smart object to get the ACR dialog, make my changes, and voila!, the PSD composite now reflects those changes.
1.5. If I make any changes within LR2 to the original DNG file (i.e. _DSC1190.dng), those changes are *not* reflected within the PSD file.
1.6. Questions
1.6.1. Is what I've described the expected behavior?
1.6.2. Although it might seem silly to some, and may present a technical challenge not worth the trouble, it seems it would be beneficial to have the smart object exported from within LR2 to PSCS3, contain a link to the original DNG file, and not now have two separate DNG files, one visible to the file system, and the other embedded within the smart object saved as presumably a PSD. I'm sure there are a lot of corner cases to consider, but it just seems very strange to now have two files wherein if you want to change something you would normally do through LR2 or ACR, you now have to do it in two different programs to two different files. Is this a problem Adobe has considered, i.e. any discussion about supporting this perhaps in an update to LR2 along with PSCS3/4?
Thanks much for any help/insight,
Matt

I haven't tried doing what you are in CS but do you have the embed xmp into file enabled or are you updating the xmp by saving it out of LR CTRL-s? Do you have ACR set to read the xmp data? I don't have access to LR at the moment but will have a play l8r and get back to you if no one else does.

Smart Object Aliasing

Hi everyone,
So, all of a sudden I'm having aliasing issue with my smart objects in CS6 I never had before. I've searched all over PS and these forums to try and figure out how to get rid of the jaggies, with no luck. Below is a screenshot example of a SO with the aliasing (I'm trying to reconstruct a dresser top). Can anyone help me get back to smooth edges?
Many thanks for any and all replies
Andy

Thanks for the prompt reply!
My II setting is Bilinear. And I'm not totally sure what you mean by "scaling", but if you're wondering if I created the SO from a smaller image, I did not. In this case, I simply grafted a piece of wood paneling from another piece of furniture to make the dresser top, which was slightly larger to begin with.

Problem when extracting Smart Objects

I am having a problem when extracting Smart Objects.
I work for a small pre-press company. We are working on several computers using one Job Server. Some of these computers have different versions of OS.
For one of our clients the company uses Smart Objects as a precaution for moire issues. The child file stays a certain size, while the parent file is sized down for print. Our client has started to request the larger Child size image for their use. For the volume of images requested, I have made an action out of Photoshop to open the smart object and save out a flat tif of the larger child file image. Here is the problem...
At times the smart objects child file does not retain the name of the smart object layer as its being extracted. What could be causing the lost connection between the parent file name to the child file name, and is there a way to prevent it in the future?
Thanks for your help:)
DVan

Hello,
I have noticed that. The true problem is that the child files name starts out as the parent layer name, but then somewhere down the line it turns wonkie, starting to be named things like 12.psd etc. Please see attached. Your can't re-save the name of the child file either because all that does is save out a named temp file that does not get linked back to the parent file....so what is making the name change?

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 "bleeding" colours when resized

Bit of a strange one, this. In Photoshop CS6, whenever I create a smart object with the intention of resizing it, whenever I shrink it, where one flat colour collides with another, it creates a really ugly "bleed" effect -- kind of the same effect you get when you take a small image and try to make it larger:
I've zoomed in on this particular part to show just how bad it looks. Particularly on the upper part of the forearm, see how it's got a sort of white "halo" before the black outline? It now looks like I drew a slightly darker outline around all the levels of shading, and it looks really bad, almost like a raised/chiselled effect.
Obviously it's not as noticeable when you zoom out, but it's definitely there. If it helps, I've noticed that the same thing happens when I just resize the whole image using "bicubic automatic", but when I select "bicubic / anything else", the bleed does not occur. It kind of makes the once-incredibly-useful smart object tool kind of pointless now.
This never happened with any other prior version of Photoshop which had smart objects, and I've only just got hold of CS6 a few days ago, so if there's a really obvious preference/setting or something that I'm missing, please let me know
Thanks in advance x

Smart Object resizing uses the image interpolation method that's set in Preferences > General. The default has changed from CS5 to CS6, and many people do not like the change.
CS5 is set to Bicubic by default.
CS6 is set to Bicubic Automatic by default. Automatic results in Bicubic Sharper when reducing pixel dimensions, and Bicubic Smoother when increasing pixel dimensions. Bicubic Sarper tends to oversharpen and create ugly artifacts such as the halo that's plagueing you.
Set the preference in CS6 to plain Bicubic to make it like CS5.
Also in CS6, Free Transform now has an independent control for interpolation when pixel layers are targeted. It is set to Bicubic Automatic by default, so set that to plain Bicubic, too.

Photoshop CS6: Pros and Cons of Using Smart Objects

I haven't had Photoshop CS6 for that long, and have only just got past feeling uncomfortable with using Curves, now I've learnt how to use them properly.
My concern is - I am currently learning about Smart Objects. The concept, at first, seemed like 'the best thing since sliced bread', being able to non-destructively use filters, Shadows/Highlights command, Unsharp Mask, endlessly scale using Free-Transform etc etc, without harming pixels at all.
However, the more articles I read about their use in Photoshop, the more I am afraid to start using them in my workflow.
I understand that when you convert to a Smart Object, this process is non-destructive, i.e. I can perform as many readjustments to a filter, for example, and Photoshop will always work from the embedded container file (which has had no filter adjustment made to it) to adjust the filter to your most recently adjusted settings. If you later decide you don't want to use a filter at all, and rasterize the Smart Object back into a regular layer again, is this process non-destructive as well?
Then there is this article, which I struggle to understand properly:
http://bjango.com/articles/smartobjects/
Please see the part 'Smart Objects Created in Photoshop'. It seems to say I can't scale with a Smart Object without causing interpolation and blurry edges. Please can somebody clarify what the writer of this article is trying to get across, because it is well documented that Smart Objects can be endlessly rescaled non-destructively.
Please understand I use Photoshop primarily for editing photographs.

There is much modern focus on "non-destructive" editing, but keep in mind if you don't overwrite or destroy the original file there is no destruction at the highest level. Put in layman's terms, you could always start over with the raw file.
That thought segways into my next one: Non-destructive editing makes sense if you need to use the same information for a variety of somewhat related purposes, or if the work product may need to change (e.g., to suit the whims of a fickle client).
But at another extreme, if you're editing for a particular purpose - say creating the best possible print from an exposure - sprinting right for the finish line by changing pixel values directly and being done with it can be an extremely effective approach. This requires that you get things right the first time, and that takes practice.
Some folks do their Photoshop work by building up layer after layer and using smart objects, smart filters, etc., and this can be effective but no computer has yet been built that can composite all that stuff in real time with a big image. So there IS a cost to doing it. What you might gain by being able to re-do things, you might not have needed to gain if your control responses were instantaneous and you could tweak the intermediate result at every step very easily. Note the number of posts about how slow Photoshop CS6 is/was at editing deep documents, some by people using 2012 computers.
As with most things, it's horses for courses. It's good that Photoshop gives us rich tools and choices for how to work.
Regarding your specific question, bear in mind that what's communicated to the parent document from each of its embedded Smart Objects is a flat, rasterized image. Think of the embedded smart object kind of like going off and opening another document, making the changes you want, saving the document, then flattening it and pasting the pixels into your parent document.
In the very first example in the linked article, they show how the smart-object-rasterized image of a vector circle, subsequently scaled by resampling the parent document in which the Smart Object is used, becomes fuzzy as it is scaled up. Once you understand this you realize that of course you could scale up the smart object itself, e.g., to a size equal to or larger than what's ultimately needed by the parent document, and then it could be crisp in the parent document where it's used.
Of course, having all your smart objects at a size larger than you need takes up even more resources.
-Noel

Resizing a circular smart object in CS6 results in flat sides

Similar Messages

Maybe you are looking for