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>

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

Perspective transform for Smart object.

Hello!
I working on the Photoshop with Smart Object with link to Illustrator. How can i transform perspective for Smart Object in Photoshop? There are accessible to me only Scale Rotate and Skew, others is gray out.
Thanks all!

That's a special type of SO you've got: Vector SO. Right-click it in Layers panel and pick Convert to Smart Object. That'll put the VSO inside a SO which you can transform with perspective.

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

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

Inspector filenames for MathType6 objects

At first I was very excited about creating MathType6 objects directly in Keynote -- until I see that the filename for every equation is reported in the Metrics Inspector as "temp.pict" (even though the object's actual filename is appended with a unique identifier inside the respective document's file). It's a nightmare trying to sequence builds on a slide with five or six equation objects when they all report the same name.
Am I going to have to first assemble all my equations in an external resource folder as individual files, then drag them onto my Keynote slide as needed so the Inspector will reflect different filenames for different equation instances?

Hi,
Presence of a TMP object doesnt necessarily mean that your code wont work in the destination environment. There a number of DDIC objects created by SAP which belongs to TMP package but is present in all environments in a landscape.
Hence there is no program to check for TMP objects within a code. The only way is to transport it and see if any objects have been missed out. After you transport, try checking the program for errors in the destination system, that will give you the first instance of such missing objects. I would suggest it move it from dev box to test box for the same.
Hope this is helpful.
Thanks
Mani

Batch rename only preserved original filename for .pdf

I attempted to use the batch rename function for the first time just now. I Renamed 1200 files (.jpeg, .png, .pdf) and made sure to check the preserve original file name box. When it completed, only the .pdf files did so, and I was unable to undo this action.
I'm using CS5 Master Collection with all appropriate updates on Windows 8.1.
Is there anyway for me to retrieve these file names? I can't understand why this happened.

Did you try Ctrl+Z?
Benjamin

Ps CS6 Problem: Transform applied to Smart Object cannot be repeated on another target

Ps CS6
OS X 10.6.8
Problem: Transform applied to Smart Object cannot be repeated on another target.
"Edit > Transform > Again" fails to transform any target after a Transform is applied to a Smart Object. The following message appears:

When ever I have a problem in CS6 and I have many I always test priot releases like cs2 cs3 cs5. I nevet nitice before you posted this problem the Photoshop has different favlors of Free Transform and that free transform for CS6 has been modified. Adobe seems to be introducind new improvement matche with new bugs,
Investgating your bug using CS5 I see the following. There are two types of free transform one type seems to be for smart Object layers and the other for other layer types. In CS5 you should see a difference in the Option bar for Free transform.
The option bar for layers other then smart object looklike this:
Transform 9 anchor point icons X: field Relative icon Y: filed W: % Constrain icon H: % Angle ° H: ° V: °
The Option Bar for Smart Object layers look like this:
Transform 9 anchor point icons X: field Relative icon Y: filed W: % Constrain icon H: % Angle ° Check Box Anti Alias (grayed out)
If I use the one for other then smart object layers Transform Again is not gratey out and I can use Transform Again on layers even smart object layers However the anchor point seems to be relative always to the first transformed layer's anchor point
If I use free transform on the smart Object Layer and not have done any transform on a other then smart object layer in this Photoshop session not even in an other document the smart object layer will be tramsformed and Transform again menu item will be grayed out. If any had done a Transform on an layer other then smart object layer even in an other document Transform Again would not be grayed out and could be used on the smart object layer at hand. The transform would not be the one just done on the smart object layer rather it be the one done to the other then smart object layer. Seems a bit bazzar to me. This may be how CS6 is also working.
CS6 also added interpolation method to the other then Smart object layer transform and not the one for smart object layers. To be consuitant Adobe should have also put interpolation into the omart opject transform for Adobe transforms smart opject layer by first rendering the pixels for the smart opject then transforms them like a raster layer. Adobe did manage to record the interpolation use into an action step. However I do not know if the made it into Scripting it did not make it into the photoshop javascript user guide. I will test the scriptlistener plugin to see if it records it for the action manager....
Message was edited by: JJMack
I have now tested the Scriptlistner Plugin it does record the interpolation for transform normal layers. Still the layer resize method in the Photoshop Javascript user guide has not been change for that support. In the past what I have done is scripting was to save the users default interpolation Photoshop prenerenvr changed the preference to what I wanted to use do the layer transform resize then restored the users interpolation preferance. Adobe broke that in CS6 if the users defalt preference is what Adobe's defalt is "Bicubic Automatic" an internal Photoshop error occurs. Adobe did not add "Bicubic Autoimatic" to scripting when I try to save the preference scriping has the internal error. There is also no way to set the preference back to "Bicubic Automatic. I'm also transform smart object layers so I would still have to use the save preference, change preference, transform, restore preferance method. This works if the users preference is set to some preference other the "Bicubic Automatic"
Message was edited by: JJMack
So to me it look like CS5 and CS6 transform work basiclly the same. There seems to have been some behavior changes made to CS6 I can not seem to put my finger on as well as the addition of the interpolation method in the option bar. I can't put my finger on it so it may be the same in CS5 and CS6.
It may have to do with the bazar behavior of Free Transform and Transform Again not being available on smart object layers if no free transform to a normal layer has been done in this Photoshop session but are available if one was done in any doument. And thet you can start to do a transform on the smart object layer and see the Transform handle but then start using transform Again shortcut Ctrl+Shift+T and watch the old transform being done perhaps rotating some virtual anchor point and not around the acnchor point bing displayed in the Transform bounding box and control points.
Message was edited by: JJMack
Over in the Adobe Feedback site several issues were posted with CS6 Transform one was marked "Not a problem" by Adobe. One was marked "Solved" by Adobe and the others have no Adobe markings the may on not be a problem
So I beleive there is a bug but I do not think it originated in CS6 the bazar things I see happing also seem to be in CS5.

Vector smart objects still looking for older version of Illustrator

When we try to open smart objects from withing Photoshop CC, they're looking for Illustrator CS6. On machines where Illustrator CS6 is uninstalled we get errors. All the file associations in Bridge are correctly set. Is there a way to change the file associations for smart objects?
Thanks,
-Onur

Editing smart objectrs uses the system wide associations, not the ones from Bridge, so you need to adjust that for the *.ai file type.
Mylenium

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.

Mass change original system for objects

Is there a way to change the original systems for multiple objects at once?
So instead of changing them one by one, can the original system for objects be changed for multiple objects at once?
Kind regards,
Ben

I've checked with the Basis team, but they couldn't help me further.
For the moment we'll leave the objects like they are and Overwrite the originals when transporting.
Kind regards and thanks,
Ben

Does Extract for PSD support smart objects?

I have spent some time exploring Extract for PSD and so far it it fantastic. I can really see this being useful when passing on my PSDs to my developers.
One feature that I would love to see would be support for smart objects. I use smart objects a ton in my web designs. For example when I create the footer I will make it a smart object so that it stays consistent throughout all my layer comps. currently in Extract for PSD all smart objects seem to be flattened. It would be great if my devs could click into the smart objects and access the content within.

You are right that we don't expose this right now. We do have plans to do this in the future soon!

Open as "Smart Object" from ACR to PS questions.

I have 2 questions associated with opening from ACR as a Smart Object in Photoshop. I'm using CS4.
1. Is there a way to retrieve the original filename (complete with path) using a script or a setting somewhere to do this? I'm currently using Bridge Talk to ask Bridge what the active folder is then adding that to the document's .name property and taking off the " as Smart Object-1" part. Then I add a .psd extension to it and then I have to save it to retain that name unless there's an answer to #2 below.
2. Is there a way to change the Document's name as described above from "Filename as Smart Object-1" to "Filename.psd" without actually saving it?
It seems to me there would be a simple way that I might be overlooking here.
Thanks
Mike

Sorry, I guess I need to explain better.
I wrote a script to do this, but here is this portion of the workflow:
1. Open CR2 file in ACR and make adjustments.
2. Open as Smart Object in PS.
3. Script Events Manager activates this script on Document Open, checks to see if it was opened as a Smart Object. We'll assume it did.
4. The script asks me if I want to make another layer. I pick yes. The script copies the SO layer, sets an inverted mask, and opens to edit settings in ACR again.
5. I adjust the settings for that layer in ACR and click OK.
The script will keep looping between 4 and 5 as long as I pick YES.
This gives me more local control of areas. If I want to bring out eyes a bit, I can up contrast, saturation, sharpness, brightness, exposure, or whatever looks best for the eyes in ACR, then unmask the eyes as much as I want on that layer in Photoshop. There is more data to pull from in the RAW file vs trying to do the same thing within Photoshop.
Opening as a regular image file then converting to a SO doesn't give me the same control. I would have to reopen the file separately, make the adjustments in ACR, open to PS then copy that document and paste as a new layer in the original.
Duplicating the document might work also, but I can also just save as .psd at that point since I'd have to know the path name by then anyway. I'll give that a try, though, and see if it might work better. The only catch with the save part is it slows me down waiting for it to write the file and if I have 5+ SO layers, it takes awhile. Once I unmask where I want, I flatten to a rasterized layer and continue.
Thanks

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.

Original filename for Smart Objects in CS6

Similar Messages

Maybe you are looking for