As far as I can remember, there is no way to specify a desired file size for SFW via any JS API. The best you can do is perform multiple saves changing the quality each time until you reach your desired file size. It's not very fast, but it does work. There may actually be code for this posted in a thread over on ps-scripts.com. -X ... View more

Would this be the best way to proceed? Record an action that does the watermark creation process for a single image. Don't use a template. Open one of the EPS files, create the watermark on that document, save as a jpg. Once you have the action, you can batch it. -X ... View more

I highly recommend reading the JS Ref Guide sections for ArtLayer and Document in detail. Every entry. The method you are looking for, in this case, is probably ArtLayer.translate(). -X ... View more

I've never seen this error and I've been working on both platforms for years. The only time I would expect to see this kind of error message is if you recorded an action in one version of PS and tried to load it in an earlier version. The only serious compatibility problem I've run into is with paths (Mac vs XP) or when trying to read actions from PS6. -X ... View more

exif:DataTimeOriginal is probably the one you want. Try exiftool -XMP filename.jpg -b | grep Date to get a full list of date property names and values and work from there. -X ... View more

What's the original mode and bit depth of the document? Can you convert it manually? ... View more

If you are converting to RGB, there is no second object to pass. I have no idea how to express that in C#. In JS, you either don't put anything or you pass undefined which is almost the same as null. -X ... View more

You shold only need the second argument to changeMode if you are converting to bitmapped or indexed color images. -X ... View more

But how do I get access to the positional data (XY coordinates/location of each and every pixel in the selection)? You don't need to know about each pixel, just the bounds of the selection. E.g. var doc = app.activeDocument; alert(doc.selection.bounds); There are pdf docs that come with PS on scripting (in general) and a (mostly) complete JS API reference. ps-scripts.com has a lot of stuff as well. ... View more

Hmm.. I'm a bit confused.  I thought that when you convert a selection to a path, the new path follows the exact location of the selection. (Therefore conversion from the selection bounds to the path should be pixel exact) Nope. Wand some part of a photograph and zoom in to %1600. Then make the selection a workpath with various tolerance levels. At 0.5 you get a very good approximation, but converting between bitmap graphics and vector graphics will never be pixel perfect. What I don't know how to do (if it's even possible) is program Photoshop using scripts to alter each and every pixel on the path using an algorithm similar to what you described. You can use the Path APIs in PS to describe as many points on a path as you need. BTW, when you ".. skip it and check the next point on the path" what path are we talking about (we just rejected a test point on the current path because it was out of alignment).  The new path hasn't even been defined yet.  Even if you used the next point on a tangent to the previous two points as the new path, what's to say that that tangent will meet up with the correct portion of the path? A better way of looking at the this is that you traverse the path. If the next point is way out of whack, delete it and check the next point. If the border defects aren't too large, you eventually find a point that is near enough that you can discard/delete the intermediate points, though you do end up with a small flat part on the circle. NetGeek888, has an interesting idea (see my commet to his post) If you are going to have a user tweaking the selection, I'd take the bounds of the initial wand selection, as he suggests, create a circle in those bounds, and let the user adjust the circle's size and location. You probably need to start coding some of these ideas up and see what's reasonable for your workflow. ... View more

The best I could do with the "Islands" is to use "Smooth" after the magic wand with "Contiguous" checked.  (Unchecked, it grabbs areas out side the circle.  No good) Expanding and contracting the selection may also be useful. Maybe you would have to turn the selection into a path, then apply this "stiffness" to the path, then convert back to a selection? This would work. One problem, though, is getting a good/precise conversion from the selection bounds to the path. After you've seen a point on the path that is too far out of alignment with the previous two points, skip it and check the next point on the path. ... View more

The first one got whacked on the email side. The second came through fine. ... View more

There is probably a way to remove the isolated islands. Depending on how you are wanding, it may be a simple case of making sure that the 'Contiguous' box is checked. A technique for removing the shavings on the edge, however, is not quite as simple. I'll let you know if I think of something. ... View more

It's just about impossible to say with any certainty whether it can be done with scripting in PS without a set of test images available. Some of us have written scripts that do something similar, but whether or not they would have the precision that you apparently require is difficult to tell. ... View more

MarkWalsh wrote: A fairly easy way, you can add your script to the 'Scripts' menu, then create an action that calls this script (use 'Insert Menu Item' to add to your action) and call this action through a batch in Bridge. One issue with this, though, is that it does require creating an action to specifically call the script, I don't know if you can call the script directly from Bridge. I haven't scripted Bridge at all myself, but I believe you should also be able to rewrite your script to get the selection in Bridge, and process those files in Photoshop. If your script is set up to process one file at a time, the Bridge/Batch technique is the simplest way to do it. If your script needs to know what all of the files are before it can begin processing, you have to add a Menu element in Bridge and have it call your action/script in Photoshop. A bit more complicated, but there are a lot of examples of this at ps-scripts.com. -X ... View more

Should be: activeDocument.close( SaveOptions.DONOTSAVECHANGES ); ... View more

Can't this be done by recording an Action to handle one image in the sequence then Batch the Action over the entire folder of images? ... View more

That would work around the problem you are seeing. I never double-click to open files in Bridge, so this didn't occur to me. I always explicitly open into ACR or Photoshop. ... View more

#1 doesn't generate an entry in the Script Listener log which means there is nothing you can do about it. This is likely not the only place that Open events don't get generated. For instance, I suspect the files opened during Batch processing or via scripts (like Image Processor) fail to generate Open events. So, you are out of luck with #1. ... View more

In #2, Photoshop is opening the file via ACR, so an Open event is generated. In #3, Bridge calls Photoshop which results in #2. In #1, the ACR plugin (in Bridge) calls Photoshop to process a rendered version of the (raw) file. There is no real PS Open event for this kind of thing since it was ACR (running in Bridge) that actually opened the raw file, not PS or ACR in PS. ... View more

Here's a script for you: var count = 4;           // number of characters to remove var appendStr = '1500';  // string to append function main() {   if (app.documents.length == 0) {     return;   }   var doc = app.activeDocument;   var nm = doc.name;   var base = nm;   var ext = '';   var m = nm.match(/(.*)(\.[^\.]+)/);   if (m) {     base = m[1];     ext = m[2];   }   if (base.length > count) {     base = base.substring(0, base.length - count);   }   var newName = base + appendStr + ext;   doc.duplicate(newName); }; main(); Save this to a file called "1500Dupe.jsx" or whatever. At the end of your first action, call this script. It will create a duplicate of the current document with last 4 characters replaced with '1500'. You will also need additional step in the action to save this to a file and close the duplicate document. It's simpler to do this in the action than it is in the script. You will need to create new jsx files for each of the other substitutions that you want to make. Just change the 'count' and 'appendStr' values as needed and save to new files. -X ... View more

<Photoshop App Folder>/Presets/Scripts/Stack Scripts Only There are actually a group of files in there that you will probably need. Check for it after the reinstall. -X ... View more

http://www.atncentral.com/ is a good site for actions. And they also have The Mother of All Tutorials. http://www.atncentral.com/zip/PhotoshopActions_ver1.1Btoc.zip I am by no means a master of actions. ... View more

But when i did it in batch, it did not work? Add a final step into the action to close the image after it is saved. You may have to fine tune Batch settings a bit to get this all working correctly. Can you tell me how to set cs4 so when i open a photos they float in their own window Turning off this setting should do the trick: Preferences->Interface->Open Documents as Tabs -X Message was edited by: xbytor2 damn jive UI ... View more

You can do this with an action. First, open your logo. Then start recording the action. Open an image from the folder. Switch to the logo, select all, copy. Switch to the image. Paste and do whatever resizing or arrangment you need to do. Save the image. Stop the recording. Now that you have an action, you can use Batch to run it over a folder of images. This only really works if all of the images are the same size. ... View more

I just checked with an nef from my D90. Load an image into PS (via ACR). Go to the Advanced (or RawData() tab in the File Info dialog. It does not appear that Adobe is passing that through. If you need that data, you may have to call exiftool to get at it. And it may take a bit of work to make sense out of what exiftool reports back. -X ... View more

Descriptors are like dictionaries. Lists are lists (obviously) of identically typed things. References are like linked lists. You can repeatedly add stuff to a reference (of the types permitted) and retrieve them back in the same order. Trying to think of them as anything else just gave me headaches. The arguments the the various 'put' methods are the same. It's just that with Descriptors, the key is explicit. With Lists, the key is the next index. With References, there really is no key, just the next slot. Actions are (in essence) an ActionDescriptor full of data and an EventID (like 'Dspl') which indicates what to do with that data. The parallel I'm most familiar with is when using CORBA without IDL. That may or may not be helpful There are no real docs beyond what is in the pdfs provided by Adobe. There is a lot of information at ps-scripts.com and in the xtools code. I've implemented code there that can read and write .atn files which means that all of the gorey details for handling ActionDescriptor/List/Reference objects are there. For me, the magic moment was when I finally realized that steps in an action are defined as ActionDescriptors. Once I got confirmation of this from someone at Adobe (probably Chris Cox) my mental model for all of this quickly fell into place. Working out all of the file formats, etc... has just be filling in the details. ... View more