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

Similar Messages

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

Photoshop CS6 (mac) - Why is Liquify disabled for smart object?

I've sent over an image from LR5 into PS CS6 as a smart object.
I'm wanting to run the liquify filter, but it isn't open to me as an option. Can someone give me some ideas on what the problem is here?
I checked with Help on PS..and it says my copy is up to date and no new updates available.
I thought CS6 would work liquify on smart objects as a smart filter.
I'm a bit of a noob here, so I may have something set wrong, so, please be patient talk slowly when using big words with me.
Thank you in advance,
chilecayenne

john worthington wrote:
Liquify Smart Object support was added in a update/dot release to CS6. I don't remember which one. Also we are currently investigating a possible bug where Liquify Smart Objects from older Photoshop psd files may not be recognized correctly in the latest version of Photoshop.
Can you find out for sure on which version? Seems strange, that CS6, no matter where it came from, wouldn't be sync'ed as far as version. I understand features coming out for PHotoshop CC, that would go forward and not be in CS6, but it seems that CS6 should be CS6 and be sync'd for features and version numbers no matter where you got it from.
If you got CS6 from CC....and you quit CC....does that version of CS6 quit functioning or does it work still going forward if you stop paying the CC monthly rent?
Thanks in advance,
C

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>

Link Smart-Object Filter mask to transformation of Smart object

Often it would be very nice, if you could link the filtermask of a smart object to the smart object itself. So that when you transform the SM (rotate, scale etc) the filtermask of the smartfilter is transformed, too.

It would seem if a linked layer mask can be transformed with the smart object the filter mask could be linked as well.
I didn't mean the workaround to be vote against the request. But it does have an added benefit. When you transform a smart object with almost any smart filter the appearance of the filter changes. Blurs become more or less blurred depending on the transform. Same with sharpen. If you want the effect of the filter to appear the same after the transform you need to embed it into a new smart object.

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

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

Kelby shows CS 6 converting to smart object before using Liquify

In Kelby's "Hidden Gems" of CS6, he converts the image to a smart object using the filter menu "convert for smart objects" before he uses the Liquify filter, thus adding a Liquify mask and the ability to go back and edit Liqify. When I open a Raw file and convert to smart object, it greys out the Liquify filter. Liquify is only available before adding the smart filter. What's wrong with this? I'm on a Mac 10.8.2

Only the Creative Cloud Photoshop CS6 v13.1 has Smart Filter enabled Liquify and Blur Gallery. (However, apparently, 13.1 has an additional payload of bugs and broken functionality.)

Ps CS6 Problem: Transform applied to Smart Object fails to transform an attached Smart Filters Mask

Ps CS6
OSX 10.6.8
Problem: Transform applied to Smart Object fails to transform an attached Smart Filters Mask.
I mean a Transform, including Free Transform, as found in the Edit menu. A simple move by the Move Tool is OK.
A workaround until this bug is squashed is to encapsulate the Smart Object + Smart Filters + Filter Mask inside another Smart Object and transform that.
However, that will not be a satisfactory solution in some cases. If a filter has size parameter(s), e.g. Gaussian Blur radius, a scaling or warping/distorting transform applied after the filter will obviously differ from the filter applied after the transform.
In any case, the workaround is inconvenient to subsequent editing and experimenting with filters and masks.

R_Kelly wrote:
I don't think that's a bug since the implementation seems to be purposely done.
It's been that way since photoshop cs3.
If its been like that since CS3 then I think it's a bug which remains because nobody (or not enough people) has complained before.

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

Raw file settings missing from smart objects in tiff files after upgrade to CS6

Yesterday I was using Photoshop CS5 and RAW 6.4 (?) in a Windows environment.
When editing photographs, I generally open the photo in Camera Raw, make development changes (ie exposure, contrast, etc) and then open the developed image as Smart Object in Photoshop. I then clone, add layers, masks, etc. and then save the final image as a tiff.
Yesterday, I upgraded to Photoshop CS6 and RAW 7.0. Now, when I open my tiff files and Smart Objects in the RAW editor, my exposure, contrast, and black settings are missing (reset to zero). My graduated filter settings are also missing.
It seems to me that the embedded sidecar data in the tiff / Smart Object is not being read correctly.
How can I update my old tiff / Smart Objects? Re-developing thousands of photos is impractical.
NOTE: As a side note, I opened a RAW file with xmp data (not stored as a tiff/Smart Object) and had no problems.
Many thanks.

You need to set the ACR engine to the 2010 version in the prefs.
Mylenium

Documents with Smart Objects - Very slow to open and Save - CS6 Photoshop

When opening and saving documents with smart objects photoshop freezes the adobe PS loader (circle dots) is replaced and the system loader (multi colored wheel of death) spins for 30 seconds or more.
What I've tried so far based off looking at various posts.
Photoshop Preferenes
Save in Background off
Maximise PSD and PSB file compatability never
Cache Tile Size: 128k
Advanced Graphic Processor Settings: Basic & Normal
Layer Panel options: No Thumbnail
Observations and workthroughs to date
The file size and amount of smart objects effects the file expotentially i.e. The more smart objects you have the worse it gets
These files worked perfectly in PS CS5
It also happens on files natively created in PS CS6
The CPU is maxing out at 100% while PS loads
Closing or opening suitcase has no effect.
System:
iMac 27-inch, Mid 2011
Processor 3.4 GHz Intel Core i7
Memory 16 GB 1333 MHz DDR3
Graphics AMD Radeon HD 6970M 1024 MB
Mac OS X Lion 10.7.5 (11G63)
Suitcase 4
Anyone got any ideas? This is making me go nuts!

A solution!
It turns out the problem in my case was in fact Suitcase. Previously, I'd tried turning it off, but that didn't fix the problem, so this time, I uninstalled it completely and the problem disappeared. I then began re-adding it (installed 15.0.1, upgraded it, etc.) and the problem resurfaced with the addition of the Photoshop-specific plugin. Deleting that plugin solved the problem. So it seems that "disabling" Suitcase by stopping the TypeCore doesn't seem to actually disable all of the tentacles it sticks into your system.
You can find the plugin here: Applications / Adobe Photoshop CS6 / Plug-ins / Automate / ExtensisFontManagementPSCS6.plugin
(After a restart, I also had to delete the font cache, as described here http://helpx.adobe.com/photoshop/kb/troubleshoot-fonts-photoshop-cs5.html but your mileage may vary.)
Alternately, if you don't want to delete the plugin, disabling it from within Photoshop seems to work as well. To do that, go to File > Automate > Extensis, click Preferences..., then deselect Enable Suitcase Fusion 4 Auto-Activation.
Fortunately, the plugin doesn't seem necessary at all to use the the core functionality of Suitcase (enabling and disabling fonts) in Photoshop. I didn't even know what these app-specific plugins did until researching this problem, and I still don't quite understand the point of them. I guess they allow you to let the apps for which they're installed do a little bit more of their own management (enable a font via Suitcase that isn't enabled system-wide), but that seems like more control than I need--if I'm enabling a font, I want all my software to be able to use it.
Anyway, the problem seems to be completely solved on my system now, though I just did all this, so more testing over the next few days is required. I'll post here if any issues crop up. I'm interested in hearing if this solves it for anyone else as well.

Why can't I open the filter gallery in Photoshop CC 2014? I've converted the photo layer into a smart object, but the filter gallery selection is still grayed out.

Why can't I open the filter gallery in Photoshop CC 2014? I've converted the photo layer into a smart object, but the filter gallery selection is still grayed out. How do I make it active?

Please go to Help, System Info and Copy then paste here.
Benjamin

Liquify as a smart object filter CS6

Similar Messages

Maybe you are looking for