Bad working of Smart Objects in cs5

Hello everyone, this is my first post and I hope not miss anything ... you must have a little patience because I write through the translator the google.
my problem is this: in CS4 Smart Objects are dependent on size (and quality) from the PSB file, In fact when you scale with the scale tool , it show the percentage of the original scale and in the case the Smart Objects with vector data everything works fine . In cs5 instead has disappeared the relationship with the PSB, with the result that we  use the pixels on the screen and not real ones (that is with the scale tool every time shows the percentage 100%). vector data are no longer taken into consideration ... what happened? Smart Objects were the best of cs4, why this malfunction in CS5?
Should I set me anything?
Thank you so much for the help, hello

thanks for your answer, I just felt such as you have suggested and it works only in part:
I created a vector graphics and I made a copy.
I turned the copy into a Smart Object and I have scaled with edit / transform / scale
Result:
I get the x, and the percentage remains the original of the smart object, but the smart object does not fit such as quality as it happens in CS4 ....
I hope I explained ...

Similar Messages

  • Smart Objects in CS5 behave differently than in CS4?

    I've just upgraded from CS4 to CS5, and I've noticed, what is to me, a BIG change in the way Smart Objects work.
    Imagine this simplified hypothetical scenario...
    I create a document in Illustrator, with two layers.
    On one layer would be a 800x600 solid rectangle. On another layer I'd put a small 50x50 circle.
    The import thing here is that the circle would be positioned roughly in the top-left corner in relation to the rectangle.
    I'd select both objects, go over to Photoshop, create a new 800x600 document, and paste what I've just copied into the document as a Smart Object.
    Photoshop would treat both Illustrator layers as one Smart Object of course, and they would get pasted together, and they would look exactly how they did in Illustrator - that being the circle positioned in the top left corner of the rectangle.
    Now I decide I want to hide the solid rectangle in my Smart Object, but I want to keep the circle exactly as it is now in the Photoshop document.
    So I simply double-click to edit the original Illustrator file, and then I hide the layer with the rectangle on it, save the file, close it, and go back to Photoshop.
    In CS4, the file would update to show the changes I had made, so the rectangle would disappear and only the circle would remain - and importantly, the circle would maintain its position. It would stay in the top-left corner of my Photoshop document (the rectangle still exists in the original Illustrator file, but the layer it's on is simply hidden).
    However, when I do this exact same process in CS5, when I update the Smart Object after hiding the rectangle layer in Illustrator, the Smart Object seems to ignore the rectangle that is hidden in the file, and the solitary circle that remains gets totally shifted into the centre of the 800x600 Photoshop file. So it is now no longer in the top-left corner where it was before.
    This is causing me HUGE problems, because I have painstakingly positioned many many various objects in my Illustrator files which then get shifted out of place whenever I make an adjustment!
    Is there any way to get CS5 to treat Smart Objects in the same way that CS4 did before it?

    Regards your comments above, yes I am aware of that discrepancy, but I very carefully make sure not to change the size or position of the largest object. In other words, when ALL objects on ALL layers are selected, I make sure that the OVERALL X/Y co-ordinates AND X/Y dimensions do not change between adjustments of various isolated objects.
    (I actually deliberately keep a "spare" oversized rectangle on a bottom layer to maintain overall size, and it's this layer that I normally switch off in my final Smart Object.)

  • Working with smart objects

    I've got a menu I built in Photoshop that uses smart objects to warp and give perspective to both button text as well as pictures in the menu. I built the menu at 300dpi, then resized it to 72 for working in Encore.
    That 72dpi menu then became a template for other menus in the project.
    Encore does not support smart objects, it converts them to shape layers. Since I had done additional design work on the menu in Encore/Photoshop, I saved a copy of it to be a template. I then opened my original of this file and dragged the smart objects back into it for my template, so that I could create new buttons, etc. for other menus.
    I've since discovered that if I create a NEW smart object in that template, the smart object is at 72 dpi. However, if I modify an existing smart object, it's still at 300 dpi, even though the file is 72 dpi. Am I making any sense? So when I double click one of the original smart objects to, for example, change the text to create a new button, I get a large, 300dpi file to work with. The result is that the original smart objects are creating much sharper, cleaner text, and all my new smart objects are creating soft text. I've also discovered if I open one of the new smart objects and change it's size to 300dpi before creating the text layer, I can save it that way and the text is sharper and cleaner.
    I'm not sure what my question is... I guess I'm just sharing :-), but also wondering if my workaround has a downside that I don't see.
    The logical question you might be thinking is why don't I just build all the menus in 300 and then resize, and the answer is that I did a lot more work on the template after I had resized it for Encore and don't want to go back and redo all of that on the original file.
    Julie

    I'll test it without the warping and see what I learn and let you know, but I suspect I won't see a difference and you're right that warping the text may be more dependent on resolution.
    I just created a 72 dpi file with 2 identical smart objects, except one is 72dpi and the other is 300dpi. I then put the same text with the same layer style on each. There is a difference in the appearance, with the 300dpi smart object yielding cleaner, sharper looking text. When I remove the layer style on both so they're flat, no drop shadow or bevel, there is still a very discernible difference in sharpness. Also, when I export the images to a NTSC monitor, the difference is apparent.
    So it appears if you plan to warp text in a 72dpi graphic, you'll get better results if you increase the dpi of the smart object.

  • Smart Object in CS5

    Hi,
    I want to save my time, and i know that it's possible to copy a vector object from illustrator to photoshop. Photoshop keep the relation on this object as a SMART OBJECT.
    Is it possible to copy a vector from illustrator to Indesign in the same way (Smart Object)
    OR
    What is the efficient way to reduce the time of any changes on this illustrator object. For example, I created a logo in Illustrator and photoshop document have a copy of this logo as a Smart Object. That very easy to change this logo in Photoshop.
    But, in InDesign, i never see this possibility.
    Can you help me about this.
    P.S: The best way for me, is to keep the relation on the original illustrator object and if a change this original illustrator object, the change impact all other document wich include this original illustrator object.
    Thanks !

    No. ALL objects that are PLACED (File >Place...) except for text and spreadsheet files are automatically linked to the original (you are really putting a pointer to the original file in the document, not the actual data), and you can choose to link text and spreadsheets as well. This not only keeps the file size down -- you can have hundreds, or thousands of pages in your document with hundreds or thousands of linked images -- but allows you to modify the original file and update the link inside ID at any time.
    You can embed a linked file if you choose, but there is really no advantage in most workflows, and you can paste from Illustrator if you choose. The advantage to pasting is that you can edit the individual paths locally in your ID file without affecting the original, but the disadvantage is you lose any connection to the original. Having worked both ways I've come to the conclusion that any convenience from pasting is outweighed by the lack of portability and the loss of edit-once-update-many capability for most situations.

  • Smart Object Anti-Aliasing issues in PS CS5

    I am having a heck of a time working with smart objects that contain transparency in CS5. Here is an example of what I'm experiencing:
    1,700px smart object scaled down to 156px. No transparency in SO. Good anti-aliasing.
    Same smart object, but with a layer mask or transparency in the smart object. But alas: horrible anti-aliasing, throughout the entire image.
    I frequently embed my transparency within the SOs I work with, due to the limitations of linking embedded SOs with layer masks etc. I experienced no problems in CS3. I'm thinking this is a bug? Does anyone have any insight? Thanks!
    UPDATE: after performing many tests, and noticing that having transparency in a smart object does not necessarily lead to poor anti-aliasing in the parent image, I have narrowed-down the issue. The issue will occur only if at least an antire column or row of pixels (of any height/width) along the border of the image are transparent. It does not matter if the transparency is at the top, bottom, sides, or surrounding the image, but it must take up some amount of an entire side. This is looking more and more like a bug... Is anyone able to replicate the issue? (Adobe engineers?) Thanks.

    Here is the file I'm seeing this in. Incidentally, if I drag the problematic smart object to another open image, the appearance is the same (Photoshop is, after all, the epitome of wysiwyg software). But this works both ways: I can also re-create the smart object in another document without the poor anti-aliasing, then drag it into the original image and it will still look fine. (in this file there are two side-by-side, so that you can compare the two. you can also play with the smart object on the left to see the anti-aliasing go from good to bad; just go into the SO and delete a row or column of pixels from the border and re-save).
    http://dl.dropbox.com/u/8162462/SO-aa-issue%3F.tif
    (i used Dropbox; lmk if there's a better way to post a file in this forum)
    Since I just started using CS5 (from CS3), I have suspicions that it may be a version translation issue (either in the TIFF or smart object). Either way, I'm glad that this is not a common or easily-reproduced issue. Let me know if you learn anything from the file
    Thanks,
    Cory

  • Smart Object Bug?

    When I edit Smart Objects in CS5.5 they open in their own window; meaning I only see the smart object in my new window when I chose to edit. In CS6 I am seeing the actual document I made the Smart Object from, as well as the Smart Object when I edit the Smart Object, AND it has its own rounded border that when saved out, does not appear - it is taking that from the original for no reason.
    Windows 7 Pro 64 Bit only. I did not install 32 bit.

    Hi Zeno,
    Thanks for the suggestion. Resetting the temp directory to another location is a good workaround. I was having the same problem with another program, CuteFTP, and changing the temp dir fixed its problem too. I had previously tried running in Compatibility mode, Administrator mode and both together but none of those modes helped.
    It would still be nice to know why Windows 7 denies access to its own temp directory but at least now, I can get back to work.
    Thanks,
    David Salahi

  • Smart Objects - File size issues

    Hey All,
    The Question: Not sure if this question has been answered elsewhere. But when using a nested smart object (meaning a smart object within a smart object) Photoshop CS5 doesn't display the correct file size (at bottom left) or seem to account for the nested smart object file size.  Is there a "setting" I’m missing to accurately display what the true file size is?
    The Problem: Using multiple nested smart objects that I have reduced the size of my image to be 260x200 for web export. Photoshop CS5 won't let me save a file that appears to be only 3mbs claiming it's over 2 gig's. See image below.
    Really not sure what to do about this, the company I work for makes lots of changes so using smart objects is necessary for my work flow. But also seems to be slowing me down trying to figure out issues like this and is problematic when it comes to saving all the work I have been doing.
    Thanks for the help

    FentonDesigns wrote:
    when using a nested smart object (meaning a smart object within a smart object) Photoshop CS5 doesn't display the correct file size (at bottom left) or seem to account for the nested smart object file size.  Is there a "setting" I’m missing to accurately display what the true file size is?
    One thing you might have missed is that Photoshop is not a file editor its a document editor.   The sizes Photoshop is displaying are related to how much ram it using for the documents data. How efficient ram is being used etc. File sizes vary all over the place sizes depend on the number of pixels in an image format support layers no layers compression?, transparency.   There is no way Photoshop could even guess at any file sizes.
    An other is all smart object layer are not created the same and their sizes my be far different the you may think.  
    Smart object layers have a basic format. There is an embedded object, there is a composite pixel rendering for embedded object that is used for the layer pixels and there is a transform associated for the layer rendered pixels.
    Anything Photoshop supports can be an embedded object.  These objects are copies of the original object.  For example a copy of a RAW file where ACR settings are stored in the file copy metadata. An embedded object might be a copy of a PSD file that has thousands of layers. in any case Photoshop renders pixels for the embedded objects composite view and uses these rendered pixels as the smart object layers pixels.  These pixels can not be changed within the document.
    However the embed object can be opened and worked on and changed. If the change is committed Photoshop will update the embedded object and render the updated object composit view and replace the layers pixels. 
    Smart Object Layer Pixels can only be acted on in the document not changed with paint etc. For example the Transform associated with the smart object layer sizes and positions the layer rendering over the canvas. The layer actual size may be larger then, smaller then the canvas size and have a different aspect ratio then the canvas. Example if you place in an image that is larger then the document canvas size one of Adobe Photoshop's Preferences is set by default have Place resize large images to fit within current the documents canvas size. The transform associated with that placed layer would cause the rendering of the layers pixels to fit with in the canvas. 
    Though an embedded  object may contain thousands of layers the actual object may be much smaller then you think for PSD files are compressed object may be compressed.  Also while the embedded object  may contain vector layers when a smart object layer is transformed the layer is transformed using interpolation like a raster layer for all that is being transformed is the pixels Photoshop rendered for the embedded smart object. The only way to work on the embedded smart object layers it to open the smart object and work on the object itself.j

  • Smart Object as traditional link (as in InDesign or Illustrator)

    Is there a way to link a smart object, so that updates are made to the originally placed object ....as opposed to creating a new vector file save in a temporaray folder.  Is there a way to work with smart object like traditional links in InDesign and Illustrator?
    Thanks

    Check out this Links Panel that let’s you create Linked Smart Objects to external files:
    http://www.ps-scripts.com/bb/viewtopic.php?f=27&t=3045&sid=70f368dca9bfd96f3c974ee11b798f9 7

  • How to save a file with smart object?

    I have just created a file from LR2, by choosing 'open as smart object' in PS.
    I then added a cloning layer and did my cloning.
    When I wanted to save the file, instead of PS turning it in into a PSD with the same name, I now suddenly got the 'save as' pop up screen and '-2' as the recommended name. The original folder where the file came from was not shown.
    I don't know what that's all about, but I'd prefer it would just save the file as a PSD and automatically show the file alongside the NEF in LR2, like it does when I don't use the 'open as smart object' feature. Is this typical for working with smart objects opened straight from LR2?
    Any help will be greatly appreciated.
    Marsel

    Well, like this you open the file s a smart object, so if you want to now clone on a layer but want it to be a part of the smart object then you go to the layer panel and click on the smart object's icon there to edit the smart object and you hit save (command S) and it will save with that layer to your original.
    then when you click the tab or the window that has the original opened as smart object those changes will be reflected, but you will not see your cloned layer active as that is a part of the smart object and you have to open the smart object to get to it.
    What you say! Yes that is what I say that is what a smart object is, you are using the smart object as a part of another document( that is why you are being asked to save as, as this new documents you can now make changes which will not effect the original which is the smart object unless you rasterize it which will make it no longer a smart object.
    What good is a smart object, well there are many say you are using this document or image if you wish in say five projects and the image has been retouched and it is determined it should have some more work done to it all you have to do is retouch the smart object and all five projects are updated.
    You see smart.
    And of course you can d things to all five projects that can be different from one another on other layers without ever destroying the work you have done to the smart object.

  • Smart objects uneditable -- bug ?

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

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

  • Why use smart objects

    Been away from photoshop since early days of CS6. At that time I did not use smart objects. Now I see many tutorials using smart objects and smart filters. Is the use of smart objects in the mainstream now? Reasons for and against using them.

    Smart Objects are a very good thing!
    Photoshop Help | Work with Smart Objects
    "Smart Object are layers that contain image data from raster or vector images, such as Photoshop or Illustrator files. Smart Objects preserve an image’s source content with all its original characteristics, enabling you to perform nondestructive editing to the layer."
    I can't think of reasons NOT to use them.
    Nancy O.

  • How to use data sets with smart objects?

    Hi,
    I have a psd of some mock-up boxes, and I want to apply different text to multiple versions. The solution here: http://helpx.adobe.com/photoshop/using/creating-data-driven-graphics.html is good, but doesn't seem to work with smart objects?
    The file that I have has the box label as a smart object (which opens as a psb). How could I apply a data set to that, and have it pump out multiple jpegs?
    If I apply the data set to the psb layers, then go back to the main image, I cannot export the whole complete picture anymore.
    Thanks!

    What database and connection type are you using? Are you connecting the report directly to the database, or trying to assign the datasource to object data?
    It sounds like you might be trying to use a linked list, collection or other C# construct to pass your data in. This currently isn't supported by the Crystal Reports SDK. You can use a DataSet or a DataTable, and possibly also an IDataReader depending on which version of Crystal Reports you're referencing in your project. Of course you can also connect directly to the database, even if the database isn't on the same machine as the application.
    The way to show master records with detail information is through the use of subreports and linked subreport parameters. Linked subreports take their parameter value from a record in the main report, so that only the data appropriate to that master record is displayed. The guys over in the [report design|SAP Crystal Reports; forum can help you out with this if you have questions on the specifics.

  • Smart Object Irregularity

    This is a bit of a "deep dive"...
    I'm trying to develop a retina workflow in photoshop for web projects. In doing this I found a strange irregularity in photoshop using smart objects and Photoshop CC 2014's new asset extraction.
    Essentially what is happening is that when I import an image into an already open photoshop document and make that raster image a smart object (either by importing it using the "place embedded..." option or by converting the image to a smart object after placing it) I am getting different results when I try to extract those images at 2x using the new extractor. Of course you will have to perform a transform on the image to scale it down in the photoshop document after you make them smart objects (i.e. I know that 2x of the original smart object size will still be blurry — that's not what I'm doing). The image that is converted to a smart object after it's placed saves as 2x perfectly clearly and the one that was "place embedded..." comes out blurry as if it wasn't a smart object at all.
    What should I do about this? I thought these two options were different ways of accomplishing the same thing. Honestly, I like to use the "place embedded..." option because it saves me steps, but it is the one that isn't working.
    Thanks,
    Ethan

    You may want to add your +1 and your observation on different behaviour for placed and converted SOs to  this thread.
    Photoshop generator not working with smart object & scaling.

  • Trying to paste from Illustrator as smart object

    Is there a trick to pasting a pixel-perfect vector image from Illustrator into Photoshop as a smart object, and not introduce a bunch of anti-aliasing that was not in the original file? My images are perfectly aligned with the pixel grid in Illustrator, and the pixel preview shows them correctly.
    This page is helpful for dealing with vector shape layers, but the techniques he talks about don't work for smart objects. Strangely, he says he doesn't have a problem with smart objects, but I do.
    Here is an example of what I'm talking about: a simple 13x13 pixel image in Illustrator turns to crap in Photoshop when pasted as a smart object (I know an image as simple as this could be pasted as a shape layer, but the real images I'm working with are much more complex, and cannot be pasted as simple shape layers).
    I'm using Photoshop CS4.

    Good news, everyone! With the release of Photoshop CC 2014, this is STILL broken.
    Starting with an Illustrator document that is 50x50 px:
    Then create a 50x50 square, at x=0 and y=0:
    Create a 30x30 square over top of that, inset it (x=10 and y=10):
    Use Pathfinder to punch out the front:
    Paste that into Photoshop as a smart object. 100%x100%, at exactly x=0 and y=0.
    Expected behavior:
    The first ten rows and the first ten columns of pixels should have a solid color.  The pixels in the 11th row or column should be 100% transparent, right? We punched a hole with precise coordinates, and have the Photoshop document matching the document size as well as accommodate exactly 100% of the object.
    But instead, we get this:
    Zooming in further, you can see the 11th pixel, whether looking at the rows or columns, has a slight bleed of the color and opaqueness from the pixel immediately above/left:
    It is approximately 6% of the strength of the adjacent pixel that it is inheriting from. Interestingly, the effect can compound where a pixel is receiving color from BOTH the left AND the top.  Also interesting: the effect does not occur in reverse.  That is, opaque pixels do not "inherit"  ~6% transparency from the top/left adjacent pixels:
    So, my question to Chris, if he's still employed by Adobe, if this is intended behavior, how can I accomplish transparencies with solid lines that do not bleed?  Like.. what is the workaround (that doesn't involve flattening or touching up with masks)?
    -J

  • CC 14.2 Smart Objects, Relative Path?

    Hi,
    The Linked SO's are very welcome, however as far as I can tell we're still stuck with absolute file paths. Is this right; there's no way to map to document relative paths?

    There are not two Place items in the menu File.  Place Embedded and Place Linked this had me worried because I use  the old menu FIle>Place in many of my scripts.  The good news for was my scripts still worked.   I use ScriptListener code for Place in my scripts so I went about capturing "Place Embedded" and "Place Link" compare them to the old "Place" All three do record full Path so I'm quite sure it would have to be and most likely you can not move file and expect things to work.  To me a relative path would not work for smart object layer has pixels rendered for the image file be it layers  have ACR setting if its RAW. It has to be a particular file.  The Path can not change neither Windows  and OSX have an object oriented file system.
    // ========= Place Embedded Photoshop CC 14.2 =======    // ========Place Linked Photoshop CC 14.2============  // ========Place prior Photoshop CC 14.2============================
    var idPlc = charIDToTypeID( "Plc " );                                          var idPlc = charIDToTypeID( "Plc " );                                          var idPlc = charIDToTypeID( "Plc " );
        var desc34 = new ActionDescriptor();                                           var desc37 = new ActionDescriptor();                                           var desc5 = new ActionDescriptor();
        var idnull = charIDToTypeID( "null" );                                         var idnull = charIDToTypeID( "null" );                                         var idnull = charIDToTypeID( "null" );
        desc34.putPath( idnull, new File( "Path\\Name" ) );                            desc37.putPath( idnull, new File( "Path\\Name" ) );                            desc5.putPath( idnull, new File( "Path\\Name" ) );
        var idOpAs = charIDToTypeID( "OpAs" );
            var desc35 = new ActionDescriptor();
            var idCMod = charIDToTypeID( "CMod" );
            desc35.putString( idCMod, """Canon EOS-1D Mark II""" );
            var idSett = charIDToTypeID( "Sett" );
            var idSett = charIDToTypeID( "Sett" );
            var idCst = charIDToTypeID( "Cst " );
            desc35.putEnumerated( idSett, idSett, idCst );
            var idWBal = charIDToTypeID( "WBal" );
            var idWBal = charIDToTypeID( "WBal" );
            var idAsSh = charIDToTypeID( "AsSh" );
            desc35.putEnumerated( idWBal, idWBal, idAsSh );
            var idTemp = charIDToTypeID( "Temp" );
            desc35.putInteger( idTemp, 5500 );
            var idTint = charIDToTypeID( "Tint" );
            desc35.putInteger( idTint, 6 );
            var idAWBV = charIDToTypeID( "AWBV" );
            desc35.putInteger( idAWBV, 134348800 );
            var idCtoG = charIDToTypeID( "CtoG" );
            desc35.putBoolean( idCtoG, false );
            var idStrt = charIDToTypeID( "Strt" );
            desc35.putInteger( idStrt, 0 );
            var idShrp = charIDToTypeID( "Shrp" );
            desc35.putInteger( idShrp, 25 );
            var idLNR = charIDToTypeID( "LNR " );
            desc35.putInteger( idLNR, 0 );
            var idCNR = charIDToTypeID( "CNR " );
            desc35.putInteger( idCNR, 25 );
            var idVigA = charIDToTypeID( "VigA" );
            desc35.putInteger( idVigA, 0 );
            var idBlkB = charIDToTypeID( "BlkB" );
            desc35.putInteger( idBlkB, 0 );
            var idRHue = charIDToTypeID( "RHue" );
            desc35.putInteger( idRHue, 0 );
            var idRSat = charIDToTypeID( "RSat" );
            desc35.putInteger( idRSat, 0 );
            var idGHue = charIDToTypeID( "GHue" );
            desc35.putInteger( idGHue, 0 );
            var idGSat = charIDToTypeID( "GSat" );
            desc35.putInteger( idGSat, 0 );
            var idBHue = charIDToTypeID( "BHue" );
            desc35.putInteger( idBHue, 0 );
            var idBSat = charIDToTypeID( "BSat" );
            desc35.putInteger( idBSat, 0 );
            var idVibr = charIDToTypeID( "Vibr" );
            desc35.putInteger( idVibr, 23 );
            var idHA_R = charIDToTypeID( "HA_R" );
            desc35.putInteger( idHA_R, 0 );
            var idHA_O = charIDToTypeID( "HA_O" );
            desc35.putInteger( idHA_O, 0 );
            var idHA_Y = charIDToTypeID( "HA_Y" );
            desc35.putInteger( idHA_Y, 0 );
            var idHA_G = charIDToTypeID( "HA_G" );
            desc35.putInteger( idHA_G, 0 );
            var idHA_A = charIDToTypeID( "HA_A" );
            desc35.putInteger( idHA_A, 0 );
            var idHA_B = charIDToTypeID( "HA_B" );
            desc35.putInteger( idHA_B, 0 );
            var idHA_P = charIDToTypeID( "HA_P" );
            desc35.putInteger( idHA_P, 0 );
            var idHA_M = charIDToTypeID( "HA_M" );
            desc35.putInteger( idHA_M, 0 );
            var idSA_R = charIDToTypeID( "SA_R" );
            desc35.putInteger( idSA_R, 0 );
            var idSA_O = charIDToTypeID( "SA_O" );
            desc35.putInteger( idSA_O, 0 );
            var idSA_Y = charIDToTypeID( "SA_Y" );
            desc35.putInteger( idSA_Y, 0 );
            var idSA_G = charIDToTypeID( "SA_G" );
            desc35.putInteger( idSA_G, 0 );
            var idSA_A = charIDToTypeID( "SA_A" );
            desc35.putInteger( idSA_A, 0 );
            var idSA_B = charIDToTypeID( "SA_B" );
            desc35.putInteger( idSA_B, 0 );
            var idSA_P = charIDToTypeID( "SA_P" );
            desc35.putInteger( idSA_P, 0 );
            var idSA_M = charIDToTypeID( "SA_M" );
            desc35.putInteger( idSA_M, 0 );
            var idLA_R = charIDToTypeID( "LA_R" );
            desc35.putInteger( idLA_R, 0 );
            var idLA_O = charIDToTypeID( "LA_O" );
            desc35.putInteger( idLA_O, 0 );
            var idLA_Y = charIDToTypeID( "LA_Y" );
            desc35.putInteger( idLA_Y, 0 );
            var idLA_G = charIDToTypeID( "LA_G" );
            desc35.putInteger( idLA_G, 0 );
            var idLA_A = charIDToTypeID( "LA_A" );
            desc35.putInteger( idLA_A, 0 );
            var idLA_B = charIDToTypeID( "LA_B" );
            desc35.putInteger( idLA_B, 0 );
            var idLA_P = charIDToTypeID( "LA_P" );
            desc35.putInteger( idLA_P, 0 );
            var idLA_M = charIDToTypeID( "LA_M" );
            desc35.putInteger( idLA_M, 0 );
            var idSTSH = charIDToTypeID( "STSH" );
            desc35.putInteger( idSTSH, 0 );
            var idSTSS = charIDToTypeID( "STSS" );
            desc35.putInteger( idSTSS, 0 );
            var idSTHH = charIDToTypeID( "STHH" );
            desc35.putInteger( idSTHH, 0 );
            var idSTHS = charIDToTypeID( "STHS" );
            desc35.putInteger( idSTHS, 0 );
            var idSTB = charIDToTypeID( "STB " );
            desc35.putInteger( idSTB, 0 );
            var idPC_S = charIDToTypeID( "PC_S" );
            desc35.putInteger( idPC_S, 0 );
            var idPC_D = charIDToTypeID( "PC_D" );
            desc35.putInteger( idPC_D, 0 );
            var idPC_L = charIDToTypeID( "PC_L" );
            desc35.putInteger( idPC_L, 0 );
            var idPC_H = charIDToTypeID( "PC_H" );
            desc35.putInteger( idPC_H, 0 );
            var idPC_one = charIDToTypeID( "PC_1" );
            desc35.putInteger( idPC_one, 25 );
            var idPC_two = charIDToTypeID( "PC_2" );
            desc35.putInteger( idPC_two, 50 );
            var idPC_three = charIDToTypeID( "PC_3" );
            desc35.putInteger( idPC_three, 75 );
            var idShpR = charIDToTypeID( "ShpR" );
            desc35.putDouble( idShpR, 1.000000 );
            var idShpD = charIDToTypeID( "ShpD" );
            desc35.putInteger( idShpD, 25 );
            var idShpM = charIDToTypeID( "ShpM" );
            desc35.putInteger( idShpM, 0 );
            var idPCVA = charIDToTypeID( "PCVA" );
            desc35.putInteger( idPCVA, 0 );
            var idGRNA = charIDToTypeID( "GRNA" );
            desc35.putInteger( idGRNA, 0 );
            var idCNRD = charIDToTypeID( "CNRD" );
            desc35.putInteger( idCNRD, 50 );
            var idCNRS = charIDToTypeID( "CNRS" );
            desc35.putInteger( idCNRS, 50 );
            var idLPEn = charIDToTypeID( "LPEn" );
            desc35.putInteger( idLPEn, 0 );
            var idMDis = charIDToTypeID( "MDis" );
            desc35.putInteger( idMDis, 0 );
            var idPerV = charIDToTypeID( "PerV" );
            desc35.putInteger( idPerV, 0 );
            var idPerH = charIDToTypeID( "PerH" );
            desc35.putInteger( idPerH, 0 );
            var idPerR = charIDToTypeID( "PerR" );
            desc35.putDouble( idPerR, 0.000000 );
            var idPerS = charIDToTypeID( "PerS" );
            desc35.putInteger( idPerS, 100 );
            var idPerA = charIDToTypeID( "PerA" );
            desc35.putInteger( idPerA, 0 );
            var idPerU = charIDToTypeID( "PerU" );
            desc35.putInteger( idPerU, 0 );
            var idAuCA = charIDToTypeID( "AuCA" );
            desc35.putInteger( idAuCA, 0 );
            var idExonetwo = charIDToTypeID( "Ex12" );
            desc35.putDouble( idExonetwo, 0.600000 );
            var idCronetwo = charIDToTypeID( "Cr12" );
            desc35.putInteger( idCronetwo, -10 );
            var idHionetwo = charIDToTypeID( "Hi12" );
            desc35.putInteger( idHionetwo, -19 );
            var idShonetwo = charIDToTypeID( "Sh12" );
            desc35.putInteger( idShonetwo, 19 );
            var idWhonetwo = charIDToTypeID( "Wh12" );
            desc35.putInteger( idWhonetwo, -3 );
            var idBkonetwo = charIDToTypeID( "Bk12" );
            desc35.putInteger( idBkonetwo, 28 );
            var idClonetwo = charIDToTypeID( "Cl12" );
            desc35.putInteger( idClonetwo, 19 );
            var idDfPA = charIDToTypeID( "DfPA" );
            desc35.putInteger( idDfPA, 0 );
            var idDPHL = charIDToTypeID( "DPHL" );
            desc35.putInteger( idDPHL, 30 );
            var idDPHH = charIDToTypeID( "DPHH" );
            desc35.putInteger( idDPHH, 70 );
            var idDfGA = charIDToTypeID( "DfGA" );
            desc35.putInteger( idDfGA, 0 );
            var idDPGL = charIDToTypeID( "DPGL" );
            desc35.putInteger( idDPGL, 40 );
            var idDPGH = charIDToTypeID( "DPGH" );
            desc35.putInteger( idDPGH, 60 );
            var idCrv = charIDToTypeID( "Crv " );
                var list9 = new ActionList();
                list9.putInteger( 0 );
                list9.putInteger( 0 );
                list9.putInteger( 255 );
                list9.putInteger( 255 );
            desc35.putList( idCrv, list9 );
            var idCrvR = charIDToTypeID( "CrvR" );
                var list10 = new ActionList();
                list10.putInteger( 0 );
                list10.putInteger( 0 );
                list10.putInteger( 255 );
                list10.putInteger( 255 );
            desc35.putList( idCrvR, list10 );
            var idCrvG = charIDToTypeID( "CrvG" );
                var list11 = new ActionList();
                list11.putInteger( 0 );
                list11.putInteger( 0 );
                list11.putInteger( 255 );
                list11.putInteger( 255 );
            desc35.putList( idCrvG, list11 );
            var idCrvB = charIDToTypeID( "CrvB" );
                var list12 = new ActionList();
                list12.putInteger( 0 );
                list12.putInteger( 0 );
                list12.putInteger( 255 );
                list12.putInteger( 255 );
            desc35.putList( idCrvB, list12 );
            var idCamP = charIDToTypeID( "CamP" );
            desc35.putString( idCamP, """Adobe Standard""" );
            var idCP_D = charIDToTypeID( "CP_D" );
            desc35.putString( idCP_D, """B0393704628CAFDD09F0DE7684972186""" );
            var idPrVe = charIDToTypeID( "PrVe" );
            desc35.putInteger( idPrVe, 101122048 );
            var idRtch = charIDToTypeID( "Rtch" );
            desc35.putString( idRtch, """""" );
            var idREye = charIDToTypeID( "REye" );
            desc35.putString( idREye, """""" );
            var idLCs = charIDToTypeID( "LCs " );
            desc35.putString( idLCs, """""" );
            var idUpri = charIDToTypeID( "Upri" );
            desc35.putString( idUpri, """""" );
            var idCrpT = charIDToTypeID( "CrpT" );
            desc35.putDouble( idCrpT, 0.000000 );
            var idCrpL = charIDToTypeID( "CrpL" );
            desc35.putDouble( idCrpL, 0.000000 );
            var idCrpB = charIDToTypeID( "CrpB" );
            desc35.putDouble( idCrpB, 0.000000 );
            var idCrpR = charIDToTypeID( "CrpR" );
            desc35.putDouble( idCrpR, 0.000000 );
            var idCrpA = charIDToTypeID( "CrpA" );
            desc35.putDouble( idCrpA, 0.000000 );
            var idClrS = charIDToTypeID( "ClrS" );
            var idClrS = charIDToTypeID( "ClrS" );
            var idProP = charIDToTypeID( "ProP" );
            desc35.putEnumerated( idClrS, idClrS, idProP );
            var idBtDp = charIDToTypeID( "BtDp" );
            var idBtDp = charIDToTypeID( "BtDp" );
            var idBDonesix = charIDToTypeID( "BD16" );
            desc35.putEnumerated( idBtDp, idBtDp, idBDonesix );
            var idRStF = charIDToTypeID( "RStF" );
            var idRStF = charIDToTypeID( "RStF" );
            var idRFNo = charIDToTypeID( "RFNo" );
            desc35.putEnumerated( idRStF, idRStF, idRFNo );
            var idRslt = charIDToTypeID( "Rslt" );
            desc35.putDouble( idRslt, 300.000000 );
            var idReUn = charIDToTypeID( "ReUn" );
            var idReUn = charIDToTypeID( "ReUn" );
            var idPpIn = charIDToTypeID( "PpIn" );
            desc35.putEnumerated( idReUn, idReUn, idPpIn );
            var idOSM = charIDToTypeID( "OSM " );
            var idOSM = charIDToTypeID( "OSM " );
            var idOSMN = charIDToTypeID( "OSMN" );
            desc35.putEnumerated( idOSM, idOSM, idOSMN );
            var idOrnt = charIDToTypeID( "Ornt" );
            desc35.putInteger( idOrnt, 3 );
            var idSnap = charIDToTypeID( "Snap" );
            desc35.putString( idSnap, """""" );
        var idAdobeCameraRaw = stringIDToTypeID( "Adobe Camera Raw" );
        desc34.putObject( idOpAs, idAdobeCameraRaw, desc35 );
                                                                                       var idLnkd = charIDToTypeID( "Lnkd" );
                                                                                       desc37.putBoolean( idLnkd, true );
                                                                                       var idOpAs = charIDToTypeID( "OpAs" );
                                                                                           var desc38 = new ActionDescriptor();
                                                                                       var idnull = charIDToTypeID( "null" );
                                                                                       desc37.putObject( idOpAs, idnull, desc38 );
        var idFTcs = charIDToTypeID( "FTcs" );                                         var idFTcs = charIDToTypeID( "FTcs" );                                         var idFTcs = charIDToTypeID( "FTcs" );
        var idQCSt = charIDToTypeID( "QCSt" );                                         var idQCSt = charIDToTypeID( "QCSt" );                                         var idQCSt = charIDToTypeID( "QCSt" );
        var idQcsa = charIDToTypeID( "Qcsa" );                                         var idQcsa = charIDToTypeID( "Qcsa" );                                         var idQcsa = charIDToTypeID( "Qcsa" );
        desc34.putEnumerated( idFTcs, idQCSt, idQcsa );                                desc37.putEnumerated( idFTcs, idQCSt, idQcsa );                                desc5.putEnumerated( idFTcs, idQCSt, idQcsa );
        var idOfst = charIDToTypeID( "Ofst" );                                         var idOfst = charIDToTypeID( "Ofst" );                                         var idOfst = charIDToTypeID( "Ofst" );
            var desc36 = new ActionDescriptor();                                           var desc39 = new ActionDescriptor();                                           var desc6 = new ActionDescriptor();
            var idHrzn = charIDToTypeID( "Hrzn" );                                         var idHrzn = charIDToTypeID( "Hrzn" );                                         var idHrzn = charIDToTypeID( "Hrzn" );
            var idRlt = charIDToTypeID( "#Rlt" );                                          var idRlt = charIDToTypeID( "#Rlt" );                                          var idPxl = charIDToTypeID( "#Pxl" );
            desc36.putUnitDouble( idHrzn, idRlt, 0.000000 );                               desc39.putUnitDouble( idHrzn, idRlt, 0.000000 );                               desc6.putUnitDouble( idHrzn, idPxl, 0.000000 );
            var idVrtc = charIDToTypeID( "Vrtc" );                                         var idVrtc = charIDToTypeID( "Vrtc" );                                         var idVrtc = charIDToTypeID( "Vrtc" );
            var idRlt = charIDToTypeID( "#Rlt" );                                          var idRlt = charIDToTypeID( "#Rlt" );                                          var idPxl = charIDToTypeID( "#Pxl" );
            desc36.putUnitDouble( idVrtc, idRlt, 0.000000 );                               desc39.putUnitDouble( idVrtc, idRlt, 0.000000 );                               desc6.putUnitDouble( idVrtc, idPxl, 0.000000 );
        var idOfst = charIDToTypeID( "Ofst" );                                         var idOfst = charIDToTypeID( "Ofst" );                                         var idOfst = charIDToTypeID( "Ofst" );
        desc34.putObject( idOfst, idOfst, desc36 );                                    desc37.putObject( idOfst, idOfst, desc39 );                                    desc5.putObject( idOfst, idOfst, desc6 );
    executeAction( idPlc, desc34, DialogModes.NO );                                executeAction( idPlc, desc37, DialogModes.NO );                                executeAction( idPlc, desc5, DialogModes.NO );

Maybe you are looking for