Hi,

Can anyone help ? I have been running Russell Brown's excellent 'Adobe Edit in ACR' script for some time now through version 1.1.5 and now 1.1.6 and for some reason it has now stopped working. I have made no changes to anything that I am aware of (running Photoshop CS6 Extended) but now when I attempt to run the script I get the following script error:

General Photoshop error occurred. This functionality may not be available in this version of Photoshop.

The object "current document' is not currently available"

The script worked 100% before (both 1.1.5 and 1.1.6) - I have uninstalled and re-installed to no avail.

When I run Adobe Edit in ACR it creates a Raw Smart Object layer and then the error message pops up - but ACR does not open. And yes - TIFF preferences within ACR have been set as per Russell's instructions.

Anyone got any clues - I e-mailed Russell himself but guess he will be too busy to respond.

Regards,

Richard

I have tried to find it and // it out with no success. I would like to have it when I "Layer Comps To Files" the it won't put the _0000_,_0001_, Etc.. in the middle of every file the comps are named acording ly so that when i do "Layer Comps To Files" i can add a bit to the front and the remainder of the comp name is enough i don't need count in the middle of the file.

I had asked in a different post how to "Load Files to Stack..." could i instead have the "Layer Comps To Files" disreguard .png or .jpg in the end of the layer comp?

SO in looking in to the script my self i know it has to be in this bit

            for ( compsIndex = 0; compsIndex < compsCount; compsIndex++ ) {                 var compRef = docRef.layerComps[ compsIndex ];                 if (exportInfo.selectionOnly && !compRef.selected) continue; // selected only                 compRef.apply();                 var duppedDocument = app.activeDocument.duplicate();                 var fileNameBody = exportInfo.fileNamePrefix;                 fileNameBody += "_" + zeroSuppress(compsIndex, 4);                 fileNameBody += "_" + compRef.name;                 if (null != compRef.comment)    fileNameBody += "_" + compRef.comment;                 fileNameBody = fileNameBody.replace(/[:\/\\*\?\"\<\>\|\\\r\\\n]/g, "_");  // '/\:*?"<>|\r\n' -> '_'                 if (fileNameBody.length > 120) fileNameBody = fileNameBody.substring(0,120);                 saveFile(duppedDocument, fileNameBody, exportInfo);                 duppedDocument.close(SaveOptions.DONOTSAVECHANGES);             }

this little bit

var fileNameBody = exportInfo.fileNamePrefix;

fileNameBody += "_" + zeroSuppress(compsIndex, 4);

fileNameBody += "_" + compRef.name;

stood out but i'm no scripter so help

It looks like Tom Ruark and Mike Shaw actually wrote the script.  I have been using this script over many versions and always rely on it.  Recently I started getting this message.  I have gone into Extension Manager and deleted the script, rebooted then reinstalled the script but that didn't resolve the issue.  Any help on this would be appreciated.

Thanks in advanceImage may be NSFW.
Clik here to view.

I have noticed in some threads that the script listener action manager code is modified.

Is there a method  to modify the script-listener/action manager code?

How ca interpret the script-listener action manager syntax?

Hi,

Can anybody help with geting XMP property from file? I need to get the date of picture shooting (exif:DateTimeOriginal). But while trying example from internet I'm stuck already on XMP file opening. Function XMPFile returns "Error 1000: XMP Exception: OpenFile returned false".

Here is a code sample:

    var imageRef = File.openDialog("Please select File","All Files:*.*;");
     loadXMPLibrary(); 
     placeFile( imageRef );  //opens image as smart object

    var myxmpFile = new XMPFile(decodeURI(imageRef), XMPConst.UNKNOWN, XMPConst.OPEN_FOR_UPDATE);
    var xmp = myxmpFile.getXMP();
    var myXmp = xmp.serialize();
    myxmpFile.closeFile(XMPConst.CLOSE_UPDATE_SAFELY);

Which file should be used as the first argument of XMPFile function? RAW format file, xmp, psd? Actually I tried to put all of them explicitly but no success.

Maybe there is another way to do my task, so here is a description of the final target.

I need to get the date of the picture that is included in PSD file as a layer. As I understood the only way to do it is to insert files as smart objects and assign this information to XMP property "userComment" of the layer.

It was an easy task to find example of SO insertion. But I can't solve the date reading problem.

PS CS6 is used if it matters.

Any help is appreciated.

Best regards,

Mike

I've seen a number of different posts on these forums about trying to do this and I never really found a complete and suitable solution. It also has really annoyed me that adobe never implemented this (and it's not possible to do with actions because the action just runs a script and you can't record the HDR toning settings, the dialog always pops up, its in the script). So I finally had some time to get my hands dirty with ExtendScript and I have created a fully featured script complete with UI that allows batch creation of HDR tonned images in photoshop.

The code I got working from various snipets of code I found around the 'net and single stepping through the MergeToHDR.jsx script that is built into photoshop.

This has only been partially tested on photoshop CC on a mac. Hopefully I made it portable enough and it will work on windows and older versions. I don't think the MergeToHDR script has changed much in the last several versions (and that is mainly what I call to do the work) so I think it should work. If you have issues please let me know.

My motivation for this script was coming up with a way to do batch HDR toning for timelapse and so this script's features lean toward using it for that end. I really didn't want to buy another separate program for doing this like photomatix, when I knew it should at least be possible to do in photoshop.

I uploaded the script to github:

https://github.com/davidmilligan/PhotoshopBatchHDR/blob/master/Batch%20HDR.jsx

How to use:

• Drop the script in the '[photoshop folder]/presets/scripts' folder and restart photoshop if it is already running.
• The script should appear as a menu item under File>Automate>Batch HDR...
• A dialog will appear where you specify all the settings for the batch
• Input Section:
  • Click browse and select the source folder that contains the images to be merged/toned
  • Specify "Number of Brackets" this is how many separate images to group into a single HDR output image (the script will group the images in the source folder in order based on this parameter). You can use a value of 1, which means each image in the source folder is separate and will be toned and output. (I find that many times when shooting RAW, 14 bits is ample to capture the full dynamic of the scene, so I do not waste storage space and shutter acutations using more than one exposure, just make sure to ETTR, also post-processing with this script will be faster)
  • If there are other files in your source folder (for example .xmp files) that you need to exclude you can specify a filte. For example: *.cr2
  • Typically for timelapse you are using a tripod and do not need to have photoshop align the images, but I provided that capability for anyone who might need it b/c it was easy to enable. Note that enabling this will make the process MUCH slower.
• Toning Section:
  • These settings are all the same as the photoshop HDR toning dialog for "Local Adaptation"
  • To preview what your toning settings will look like you can select any file(s) in your sequence by clicking "Select File(s)..." under "Preview". The file(s) you select will open and merge (if more than one file). When that's finished you can click the "Update Preview" button to apply the current toning settings and see what they will look like (I can't do the fast, automatic previews like the builtin dialog, sorry - somebody from adobe want to show me how to do this?)
  • You can see what the settings will look like at another point in your sequence by clicking the "Select File(s).." button again. (I recommend previewing a shot near the beginning, middle, and end of your sequence)
  • The dialog prevents you from using anything in photoshop while its open so I provided a zoom to allow you to zoom in on the preview
  • The tone curve you must enter as a comma separated list of points (sorry, ScriptUI is not really adequate to create the graphical histogram overlay for the curves like in the builtin dialog). The points are grouped into x,y pairs so for example: x1,y1,x2,y2,etc. Typically you will start with 0,0 and end with 255,255 (note that 255 is the max, full white). Like the curves tool, x represents the input and y represents the output
• Output Section:
  • Click browse and select a folder for the script to save the output files to
  • The rest of this section should be self explanitory. NOTE: If you select to output 32bit files, the toning will not be applied, the files will simply be merged into a 32bit HDR image and saved.
• Once you have specified the input and output folders the OK button should be enabled, when you are ready, click OK to start the process
• Go watch a movie or take a nap, this is going to take a while. The script will display a progress window showing you how far along the proces is (the photoshop progress windows may occasionally appear on top of it, I usually just move them up a little so I can see both)

Limitations:

• Only the local adaptation method is supported. It's really the only one I ever use, and I didn't really feel like implementing the other ones, but feel free to modify the script yourself to add this support
• You canot load or save presets from the builtin toning dialog. The format of the preset files is binary and would require reverse engineering of the format and it would be very difficult to read to the files in javascript anyway. If it were xml, it would be much easier, alas it is not. Feel free to grab a hex editor and do this yourself. For now you'll just have to copy all of the values of a preset by hand into the dialog if you want to use a preset. If I have more time this is something I might work on.
• Preview is slow because it has to do the actual full toning, I don't know a way to do the fast real time previews like the builtin dialog.
• I don't think the "Cancel" button on the progress window really works, once running, the script is too busy to register a click, anybody know how I might fix this?
• There may potentially be some ways to improve performance of this script in certain scenarios, IDK, but I'm just glad it works

You're welcome Adobe, you can send me a check at:

[REDACTED]

[REDACTED]

[REDACTED]

Please hit me up with comments/suggestions,

David

I'm a seasoned Photoshop/Bridge CS5 user who recently upgraded to CS6.  In Bridge I just ran my first Image Processor batch, trying to convert a set of RAW .NEF files to .PSD files with a basic editing action I created applied to them.  Photoshop CS6 opens the files from Bridge and applies the actions, but then I get the "Script alert" error message "Sorry I could not process the following files" and a list of all of the files in the batch I was trying to run the script on.  The files all remain open and are saved on my hard drive in a folder created by the Image Processor script, but do not close unless I manually close them.  I never had this problem in CS5 where the image processor would apply the desired actions to the batch of photos one at a time, then save and close.  Thoughts on how I can fix this bug?

I would like to be able to import fields from Excel into Photoshop CS4 and have the Excel information print directly onto the photo image as a line of text across the bottom and layered over the image itself.  This Excel information needs to be able to change sequentialy (eg: ascending numbers, etc)  with each new photo.  Is there a way to do that with CS4 (or do I need a later version of Photoshop) ?

Hello everyone,

I am working on a project that needs to run PhotoShop's script/action on a folder everyday. It needs to be done automatically without no user interaction.  Ideally, I would create a Window Service, because besides running PhotoShop, it needs to run other routines (record the action, enter data in tables, etc).

Does anyone know if PhotoShop can be ran like Command Line like?

Thanks

Robert J.

Hi!

I'm trying to get a script to execute each time photoshop cs6 is started. I've tried to put it in that folder ( Photoshop-CS6-Scripting-Guide.pdf page 10) C:\Program Files\Common Files\Adobe\Startup Scripts CS6\Adobe Photoshop but it doesn't start ... If I put it in there C:\Users\[USERNAME]\AppData\Roaming\Adobe\Bridge CS6\Startup Scripts it loads when I start BridgeCS6 but it fails as it's a script done for photoshop. So I try to put it in C:\Users\[USERNAME]\AppData\Roaming\Adobe\Photoshop CS6\Startup Scripts but didn't work as I was expecting ;o) .

I don' think it matters but my OS is in french but photoshop is in english.

So where is the proper place ?

cheers

Greetings!

Sorry if that title is not clear. I have a cover design template (see example). The image is a transformed Smart Object. I want to streamline my workflow.

Say I have a folder of jpgs, and need to replace the smart object of the template with the new cover jpg, then save for web as a JPG comp. Repeat.

I already have a nice "scale layer to current canvas size" script from Michael L Hale. Which would be necessary in case the jpg is larger or smaller than the Smart object's content it will replace.

Any thoughts if this could be done?

Michael's resize script is here: http://forums.adobe.com/thread/1233856

Thanks

Maxi

Image may be NSFW.
Clik here to view.

Is there a console or log for output from script events?  I tried making a function, which executes an alert correctly, but doesn't create a new document.  I can't find any way to see if this syntax is wrong or the command is just outdated. 

In the code below, for example, I see the alert message, but no new document.  I don't see anyway to see what's wrong with it and I pulled that line straight from the photoshop scripting guide. 

var createDocument = function() {

    alert("creating new doc!");

    app.documents.add(2,4);

};

I have complicated workflow in photoshop in which i often use selection of layers by ctrl+click (auto-select is unchecked and selecting layers is chosen) That works good for me. But some time i need quickly select parent group of active layer (only one level up) (it can be achived by using some keyboard shortcut)  I think the only way to do that is PS scripting.

Im new to photoshop scripting but i have a lot of expirience in other languages

As i understand its sould take just couple commands:

1) select parent folder from active object (it can be any type of layer)

2) Collapse this folder (cos it was uncollapsed before)

what syntax shoud i use for this commands? i tried to use help but couldn't find even how to select parent folder of active layer..

Any help?

I've been trying a few different approaches along the lines of:

var newLayer = activeDocument.artLayers.add(); // Create a new ArtLayer object

newLayer.name = "MyLayer"; // name it for later reference

app.activeDocument.artLayers.getByName("MyLayer").kind=LayerKind.CURVES

When I do, I get an error that I can only change the layer's kind to text or normal.  Anyone know how to create a new curves adjustment layer via script?

I am running a 3-action droplet automatically using windows task scheduler.  Here are the 3 steps:

1.    Batch file to move files from hot folder to processing folder

2.    Run IPP (dr brown's image processor pro) using preloaded settings to make several sizes copies of the files.

3.    Bat file to move the files from processing folder to archive folder.

The problem I am observing is that Step 1 works and IPP begins to run.  It only processes the first few images, and then moves on to the 3rd step where the bat file is ran to move all files from processing folder to archive folder.   The trouble is, only a few images were processes (about 10 or so), yet all of the images get moved to the archive without being processed.  Is there a way to make sure that step 2 (IPP) doesn’t begin until all files have successfully been moved from the hot folder to the processing folder?  IPP starts right away and files are still being transferred to the processing folder.

Does anyone have a script that will move files from one folder to another? 

I'm already enjoying some success at distributing an interworking set of actions and scripts. BUT there are several barriers that I'm sure others have thought about solving, and I'd like to get an idea what the possible (and best) solutions might be.

Let's start with the following assumptions, based on my sales so far:

• The target audience has Photoshop CS2 up to Photoshop CC.  (For me, so far, MOST people are CS5, CS6 or CC). An ideal solution would allow me to continue to target all of these people.
• The target audience are Photoshop "aware" but not Photoshop "Savvy".  They want tools to do a specific job and may not know all the ins and outs of Photoshop.
• In addition to supporting a wide variety of Photoshop versions, we must also support both Mac and PC users and the variety of OS's that are present in the wild.

Currently the "state of the art" as I understand it are the following:

1. Sell actions or scripts with a set of instructions about where to copy the items, being careful to describe the differences for different machines and OS's and Photoshop Versions.
   PROBLEM:
   A. This is unwieldy and requires the consumer to be more "savvy" about their OS and their Photoshop than many people are.
   B. Many versions of windows do not allow one to copy into some directories without special privileges, ditto for the Mac.
   
   
2. Package the actions or scripts for Mac separately from those for the PC and bundle each with some kind of installer.
   PROBLEMs:
   A> Multiple packages are harder to maintain 
   B> "canonical locations" for the PC are different than on the Mac 
   C> There are security problem with creating and distributing a an installer. While it may be easier to send a bundle around, it moves the burden to the user who has to know what "this app is not trusted" means and how to circumvent it.
   D> some users, especially CC users who have more than one platform may want both Mac and PC versions.
   
   
3. Figure out how to slog through the process of getting something into "Adobe Exchange"
   PROBLEMS:
   A. The process seems inscrutable to me.
   B. "Exchange" is an additional Product that someone must install (not included with Photoshop)
   C. Does no support older versions of Photoshop (before CS5, i believe)
   D. Apparently requires a different package for EACH supported Photoshop version?? True?
   E. Given that Exchange is not bundled with Photoshop the market is stacked against someone who adopts this route.
   F. Exchange itself is sometimes a pain. For example just now it told me I needed to update it *and* restart Photoshop.  It's hard to imagine a potential customer going through that much pain to try to find a package there. Besides after all that I clicked "My Stuff" and the tool sat spinning infinitely.
   G. The user must KNOW about exchange, and I, the seller have to describe how they can navigate that landscape, that is once in Exchange a user has to somehow FIND your content.
   H. There seems to be no clarity about what percentage Adobe is taking in this model, or how payment will work.
   I. Users must be willing to use an Adobe ID to make a purchase.
   J. Based on what is currently in exchange, it seems a poor vehicle to get eyes as there is very limited ability to put text and descriptions
   K. There is obviously a very low incidence of people looking in Exchange... NONE of the products I saw there had even ONE review!
   
   
4. Create something that uses Adobe Configurator (could be in addition to or a replacement for any of the above)
   PROBLEMS:
   A. Configurator is DEFINITELY Photoshop version specific. Lots of overhead building and testing for each supported PS.
   B. As near as I can tell, Configurator is a dead project that has no team and no support.
   C. Doesn't support earlier Photoshop versions.  (CS4? unlikely)
   D. Still requires that a user stall an "Administrator Required" Adobe Extension Manager tool.
   
   
5. Join the Apple Developer program so you can build, sign and distribute a package for the Mac including, possibly, via the Mac Store.
   PROBLEMS:
   A. Might work for the Mac, but doesn't help much for the PC which is 60% of the market.
   B. More $ and pain. Though perhaps worth it as the Mac store (like the App store) get's a LOT more eyes than whatever Adobe has cooked up so far.
   C. Seems like a lot of work and hassle to distribute Photoshop specific content.

As near as I can tell there is no solution for "upgrades" (distributing newer versions) or "upsells" for any of the above options. 

Is there an option 6?  Have I misstated something? Does Adobe indeed have a "Photoshop script/action bundle maker' which is platform independent, robust and EASY for anyone to use?

Using CS3. I've created an action to Crop and straighten, and I'm using it on Batch options to split hundereds of scanned images.

I managed to find two old scripts from c.pfaffenbichler (much appreciated, thanks) which I've managed to adapt a little into a single one, which save the open files. In essence it works perfectly, although it always saves it to the default location (in the original it was the desktop, I've amended it to a Folder on my images disk called Split).

I'd be grateful if someone could help by explaining why the initial save to the source directory does not work.

many thanks

Colin

// save all open documents;

// 2011, use it at your own risk;

#target photoshop;

if (app.documents.length > 0) {

var theFirst = app.activeDocument;

var theDocs = app.documents;

// psd options for unsaved files;

psdOpts = new PhotoshopSaveOptions();

psdOpts.embedColorProfile = true;

psdOpts.alphaChannels = false;

psdOpts.layers = true;

psdOpts.spotColors = true;

// go through all files;

for (var m = 0; m < theDocs.length; m++) {

     var theDoc = theDocs[m];

     app.activeDocument = theDoc;

// getting the name and location;

     var docName = theDoc.name;

// thanks to xbytor for the regexp;

     if (docName.indexOf(&quot;.&quot;) != -1) {var basename = docName.match(/(.*)\.[^\.]+$/)[1]}

     else {var basename = docName};

// getting the location, if unsaved save to desktop;

          try {

          var docPath = theDoc.path;

// jpg options;

var jpegOptions = new JPEGSaveOptions();

jpegOptions.quality = 10;

jpegOptions.embedColorProfile = false;

jpegOptions.matte = MatteType.NONE;

// save the file if unsaved;

          if (theDoc.saved == false) {theDoc.save()}

          }

// if file has not been saved yet save to E:\Split;

     catch (e) {

          var docPath = &quot;E:\Split&quot;;

          theDoc.saveAs((new File(docPath+'/'+basename+&quot;.jpg&quot;)), jpegOptions, false, Extension.LOWERCASE);

          };

     };

app.activeDocument = theFirst;

};

I'm looking to make a script that would delete all channels that are not visible.  That would include the RGB channels.  This would be my first script attempt.  So I have no idea where to start.  Any help in the right direction would be great.

Thanks,

Chris