Image Processor script won't close windows

I'm testing a client's favorite method for converting folders of, say, 1000 images from RAW to large JPEG. He now uses Photoshop in CS3: He opens File Menu > Scripts > Image Processor, designates a huge folder of RAW files, sets the right parameters, and saves to a different folder. Works perfectly (but slowly) on a Mac G5.
Now I am testing it on a Mac Pro in PS-CS4, the setup he wants to buy, using exactly the same parameters. Trouble is, the window that opens on each document isn't closed, and so they accumulate! Doesn't matter whether Tabs is enabled or not. Starts eating up scratch space and has the potential to open 1000 tabs or windows. Something is wrong.
Same operation works perfectly in PS-CS3 on this Mac Pro.
If the Close Window is missing from this repeating script, then it should be added back -- or a checkbox should be added: "Close each window." I haven't been able to create an Action that will close each window without confusing the Save/Save As mechanism in the script.
How can I report this apparent bug? Or can someone please tell me what I'm missing.
(I know there are other ways to accomplish this task. But this one should work!)

From Kathy: "I still can not find out your issues here. You may try report this to adobe through this link.
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform"
Thank you, Kathy! This was the tip I needed. I thought that Adobe may, indeed, be monitoring this forum. Many manufacturers monitor and post in their own forums, e.g. Apple.
"Also one simple workaround for you, could be create a close action and run this action in Image Processor."
I really did try this. Trouble is, you run into unresolvable interactions with a Save As dialog. I.e. the Close Action seems to interfere with the saving of the converted JPEG. At least I couldn't get it to work -- but it should not be necessary.
There are workarounds, such as selecting multiple items in Bridge, opening them all into ACR, and then selecting them all and clicking Save File. Doesn't open any windows at all! But the bug still needs to be reported.
From Ramon: "Before your frustration causes you to become overly argumentative, you may want to consider that your interlocutor may actually know a bit more than you seem to think she does. Kathy may even be part of the Adobe team, for all you know."
You are reading way too much into what I said. Argumentative? I meant what I said literally. The behavior of the Image Processor script should not have any dependencies, and the documentation (such as it is) indicates none whatever. Further, the script, when run identically in CS3, runs perfectly.

Similar Messages

  • Image processor script

    Hi everyone,
    I just tried using Photoshop's image processor script to convert a folder of .ai files into .tiff files. When it finished running though, I noticed that the physical file size of each image was really tiny, ie. not the same as the original .ai file. For example I had an A4 sized .ai file and it ended up being only about 2cm in width after being converted to a .tif.
    I'm not sure what I'm doing wrong.
    Any advice appreciated.

    It is a long-ish Script, but at a glance it does not seem to be intended for use on ai-files.
    There are a couple of other Image Processor-style Scripts available, but I’m not sure they make provisions for that case.
    Maybe you should ask over at
    Photoshop Scripting
    or
    http://www.ps-scripts.com/

  • Image Processor Pro won't run in PS6 using Window 7 OS.

    Trying to run IPP on a Windows 7 OS in PS6.  I select my images in bridge and run the script IPP. Photoshop pops up and a blank white screen appears and nothing else happens.

    Scripting was an extra down for PS7 and the first version of Photoshop to have scripting support PS6 has no scripting support.  The Image Processor Pro script uses newer scripting features like Plug-in support that was added in CS3 and I think Image Processor Pro needs newer then that like it may only works with CS5, CS6 and CC. I use it with CS6 and CC... I do not usr the installer I extract the zxp file and install manually. There are a couple of minor issues the X is working on Alpha Channels in PSD files and some TGA and BMP support... Adobe has pull Russell Brown off of Photoshop  and X is feed up with Adobe.. Make sure you have the latest version of the script... I use Windows 7 Pro OS...
    CS5/CS6 Script:
    Dr. Brown’s Services 2.3.1
    Dr. Brown’s Services is a collection of time-saving utilities for designers and photographers. Use the new CS6 Extension Manager to install both the Mac and PC versions. If the Extension Manager does not work on your system, use the manual installation process instead. Installation will require that you be in the ADMINISTRATOR mode on a PC.
    This installation includes:
    Image Processor Pro
    Stack-A-Matic
    Place-A-Matic 8-bit
    Place-A-Matic 16-bit
    Trouble Shooting
    Having trouble with any of my scripts? Then be sure and try my "JUST FIX IT" http://www.russellbrown.com/scripts.html#Fix_Itscript that will remove all the damaged preference files. This could to the trick to solve your issues.
    IMAGE PROCESSOR PRO
    STACK-A-MATIC
    PLACE-A-MATIC
    Adobe Photoshop CS6 Installer
    Adobe Photoshop CS5 Installer

  • Image processor script and image interpolation setting (cs3)

    Hi all,
    I'm using Bridge & Photoshop CS3 (mac) to process batches of photographs. I've discovered that the script "Image Processor" does not take into account the "image interpolation" setting of my General Preferences in Photoshop.
    It's very painful, because I cannot use "Image Processor" any longer, as it produces soft images where I need sharp ones (my default for "image interpolation" is "bicubic sharper".
    Any idea/workaround?
    thanks
    Patrick

    This is the change I made in CS5 fit image
        // resize the image using a good conversion method while keeping the pixel resolution
        // and the aspect ratio the same
        //app.activeDocument.resizeImage(newWidth, newHeight, resolution, ResampleMethod.BICUBIC); Commented out JJMACK
        if ( newWidth > app.activeDocument.width || newHeight > app.activeDocument.height ) {
            if (!limit) {app.activeDocument.resizeImage(newWidth, newHeight, resolution, ResampleMethod.BICUBICSMOOTHER);}
        else { app.activeDocument.resizeImage(newWidth, newHeight, resolution, ResampleMethod.BICUBICSHARPER); }
    Note: Adobe choice to use BICUBIC is probally the best choice for users in general. For I find an images has been sharpened before its downsizes, downsizimg it using BICUBICSHARPER  is not the best choice then.

  • Safari won't close windows

    I work in a music technology lab and on 3 of G4 Imacs, Safari can not close its windows. What I mean is that when you click on the red circle or use command W, the windows won't close. The Imacs are using 10.4.2 and have 512megs of ram. The windows do close when you quit the program. I have deleted the preferences but that did not solve the problem.
    Anyone have any ideas?

    Aaron,
    Try Resolving Disk, Permission, and Cache Corruption, by Dr. Smoke.
    If that is not successful, download and install the most recent version of OS X using the Mac OS X 10.4.6 Combo for PPC, and Security Update 2006-003 Mac OS X 10.4.6 Client (PPC).
    ;~)

  • Pages won't close windows when I quit it since I upgraded to lion.

    Ever since I upgraded to lion, whenever I open pages all the previous pages i was working on opened. It won't allow me to close them before quitting out of it, whenever I try to close them the system just ignores it.
    Also the mouse cursor has been disappearing on pages.
    I don't have this problem with numbers

    Ever since I upgraded to lion, whenever I open pages all the previous pages i was working on opened.
    The Resume feature in Lion opens the documents left open when an app was last quit. You can turn this feature off in System Preferences. See the General pane and its "Restore windows..." checkbox.
    It won't allow me to close them before quitting out of it, whenever I try to close them the system just ignores it.
    Does anything at all happen when you close a window in Pages using either the mouse or the File > Close menu command? eg a beep, a box appears, etc. It reads like you cannot close any Pages window, ever.

  • Adobe photoshop cc 2014 won't close window with unsaved file

    Recently installed update to Photoshop via creative cloud. Photoshop works great but for some reason I am unable to close a window with an unsaved project. Pressing command-w or going to file close doesn't do anything. As soon as I save the file I can close the window or quit photoshop. Is this in the preferences? Please advice.
    thanks

    I'm having this same issue.  Can't close an unsaved file that has been opened, even if it is completely unedited.  When an unsaved file is present, I can't quit Photoshop, either.
    I'm on OSX 10.7.5  (yes, I know...it's aged), Photoshop CC.  Plenty of memory and disk space, so that's not the issue.
    Any ideas?  Thanks!

  • Preview won't close windows

    I have mac book pro 10.7.4 . I opened a few PDF files. Now preview wont close the windows. I tried:
         1- turning off restore window feature on system preferences
         2- using command + option + Q
         3- deleting com.apple.preview file
    Nothing seems to work. Please help

    I was having the same problem, with a large file that was causing my Preview to open it everytime and slow it down, and it wouldn't close the **** file/window. The fact is that it was opening the file even if it was deleted. But it was opening a temporary file somewhere, somehow.
    I don't know if that's available in previous version os macOS, but I'm using Lion. Here's what I did:
    1. Right-click on the icon by the side of the title of the window/document you wish to close
    2. You can see now the path of that file - click on the folder right beneath the file name
    3. That will take you the where the file is - delete the file.
    4. Go back to preview and close the window.
    To me this worked instantly. It wasn't closing before and now it did because the file really didn't exist anymore.
    Cheers
    Guz

  • Exit button won't close window when course is completed. tried javaScipt

    I tried a short test (without JavaScript) and set the Project End preference to Stop Project. It didn't work when viewing locally but when it was published to our web server the exit button worked.
    Has this issue been resolved?  I find threads from 2011 with many people frustrated over the exit button not working; haven't found the resolution.
    Message was edited by: MN Jean

    Can you close Firefox via Firefox/File > Exit?
    That is usually a better way to close Firefox.

  • Script Alert: "Sorry I could not process the following files" (Error Message using Image Processor)

    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?

    Hey Jeff--
    No specific action steps to make the image safe - no flattening, etc. Had problems narrowing down the specific action step causing the problem. So I ran the Image Processor script in the ExtendScript ToolKit and debugged in. (I'm using the version that shipped with CS4.)
    Turns out what was happening is that the app.activeDocument.close() command on line 1490 was never getting called, because the this.SaveFile() above it was throwing an exception. More debugging got me to the problem - SaveFile() tries to restore the history state after making a doc safe for saving as a JPEG. This causes an exception. So I commented out line 1571:
    // app.activeDocument.ativeHistoryState = historyState;
    The script runs just fine after this. I commented out the close to see what history states got added to the doc, but no new states are recorded, so commenting out the restore line should not cause any problems.
    Of course, my solution does not solve the problem and I may need to comment out all the saveFile() lines that does this. Not sure why some actions have this problem and others don't. The actions I am running have about 25 steps. Perhaps PS is not catching up quick enough. I added a $.sleep(2500) after the restore history but that didn't help.
    So, not sure where this gets us. I will check about posting an action set with just one of the actions that cause the problem. But I may also have our customer comment out that line of the Image Processor script.
    Hope this helps. May post more next week.

  • File Scripts Image Processor unable to execute

    Attempting to process several files, simply converting from .TIFF to.jpg and reduce size, yields a "Sorry, could not process the following files:". Other automated scripts are working -- picture package, contact sheet II, PDF presentation, photomerge, et. al. -- but not the Image Processor script. What gives? I repaired permissions, trashed the 'com.adobe.Photoshop.plist' file, and restarted, all to no avail. What gives? Can't find similar topic in forum.
    Screenshot: http://www.artbythor.com/gfx/imageProcessor.png
    |> OS X 10.5.2, PS CS3 10.0.1, MacPro Intel <|

    Can Photoshop open the files in question?
    Do the files have odd names or the path to the files odd?
    The IP has troubles with some characters. The IP has some troubles with files off of servers or attached media.

  • Image Processor.jsx bug (CS3, 10.0.1): fail to restore history item sometimes

    I have very limited history depth (5 items) to conserve my RAM.
    When I run "Image Processor" script, which calls some complex Action, "Image Processor" fails to restore history item (because it was dropped already) in this lines (tere is same line for every save file type):
    app.activeDocument.activeHistoryState = historyState;
    This line(s) throw exception (file was saved, really!), and file remains open and after processing 10-15 files computer starts to thrash.
    I've surrounded all these lines with try { ... } catch(e) {} and it works for me.
    IMHO, it here are two bad ideas in this script:
    (1) Consider every and any exception as error. In this case, history is not a thing I care about
    (2) Don't close files in case of error. It can fill up RAM & scratch disk very quickly.

    Update Server
    Try:
    - Powering off and then back on your router.
    - iTunes for Windows: iTunes cannot contact the iPhone, iPad, or iPod software update server
    - Change the DNS to either Google's or Open DNS servers
    Public DNS — Google Developers
    OpenDNS IP Addresses
    - For one user uninstalling/reinstalling iTunes resolved the problem
    - Try on another computer/network
    - Wait if it is an Apple problem

  • Problem with image processor - photoshop cs6

    Hi there .
    I am trying to automate - image processor. From open files i am just trying to save theese pdf's as jpg's. Should be straight forward but I get this error...
    "There were no source files that could be opened by Photoshop."
    Anyone know why? I saw one google someone suggesting to reset the preferences or someting but I so not know how to do this or if it will help...
    thanks.

    It look like both the Image Processor script and the Image Processor Pro script will not process open document that have no associated backing file.  When you open a PDF file and use options for Photoshop to use opening the PDF the documents that open are new document the source PDF files have been processes into a new documents that have not been saved so the open document has no associated backing file.
    I mad a simple test. Opened a PDF. Tried the two scripts they failed. Then I saved the open document and the ran the Image processor on the still open document that had been saved as a tif.  The image processor worked and saved a jpg.
    It may be possible to write a small script to save open Document as jpeg files and close the open documents or loop around the open document ring and just save document that have no backing file.
    You could also try using Paul Riggott PDF Processor script to do it all....

  • Image Processor Pro xml issue:

    When I download the script Image Processor Pro.xml to my window 7 computer with CS6,  the File Type reads "Safari Document"  When I select my images in bridge and try to run IPP the only thing that happens is a blank white window opens and sometime PS will crash.
    I just upgraded from XP with CS5 to Win7 with CS6.  I had no problems running IPP in XP/CS5

    Thank you very much, xbytor2. 

  • Buglet in Image Processor.jsx

    I'm not sure how to report this, but there's a bug in the Image Processor script that was driving me nuts so I figured out how to patch it. This may be a Windows-only bug (I'm not sure).
    The problem is that the when you bring up either of the directory pickers for changing the directories in the Image Processor dialog, they both default to the Windows desktop rather than the path that the dialog shows. Since the Windows desktop is a long ways away from where I keep my images, tihs is a lot of mouse clicks to set this directory everytime I want to use it. There is an attempt to pass the directory picker a starting directory, but that code is just wrong. This occurs in two places in the Image Processor. To fix it, I replace this line:
    var selFolder = Folder.selectDialog( strPickDest, this.parent.parent.destLongText );
    with this line:
    var selFolder = Folder.selectDialog( strPickDest, d.destLongText);
    and now the directory picker starts out where it's supposed to and it's a lot quicker to set it to what I want.
    If this has been bugging you, you can patch your own Image Processor.jsx file. Just find the two lines that look like the first line and replace them with the second line.
    And Robert, do you have any idea how to get the real one fixed at Adobe?
    I wonder if this actually works on the Mac. On windows, it takes a chain of 5 parents up (this.parent.parent.parent.parent.parent.destLongText) to make the original way work, but I could imagine that this would be difference on Windows/Mac. Since the real parent has already been resolved with FindWindow right in this same function, I found a safer way to accomplish the goal.
    --John

    >>>I'm not sure how to report this, but there's a bug in the Image Processor script that was driving me nuts so I figured out how to patch it. This may be a Windows-only bug (I'm not sure).
    var selFolder = Folder.selectDialog( strPickDest, this.parent.parent.destLongText );
    with this line:
    var selFolder = Folder.selectDialog( strPickDest, d.destLongText); <<<<br />
    John I did your bugfix, but it did not work in my CS2. I'm still taken to the Desktop. Have you done any further work on this "bug"?
    Thanks,
    Dennis Jacobsen

Maybe you are looking for