Found out on a brand new install of Mountain Lion and Adobe Photoshop CS6 that Image processor will not save any othe images processed. Anybody else have this problem or anyone test this out for me?? Also is there a work around to this issue?
Well, you adopted Mountain Lion on the very first day it became available. Talk about early adopters!
Apple doesn't seem to get new major versions of OS X right until about the sixth dot-dot release. That's why Lion wasn't and isn't reliable even at 10.7.4.
I'm sticking to Tiger 10.4.11 on my main Power Mac and have rigged a minimal Snow Leopard 10.6.8 system just to run ACR 7.x hosted by Photoshop 13 ("CS6").
Leopard 10.5.x was awful, not just in dropping Classic Support but also in totally killing SCSI support.
The two Lions are mainly concerned with compatibility with mobile devices like the iPad and the iPhone.
The future of the desktop Mac as a serious computing platform seems doomed.
I can save out JPG, PSD, and TIFF resized images from source JPG files using Ps CS6 running on 10.8. Do you see the source images opening when you run the script and just don't have a resulting output folder? What options are you setting?
I can save out the images just fine manualy. The image processor just runs, does the action I want and it doesn't close and save the image as usual. I look in the folder in bridge where it's supposed to save in and an incomplete or corrupt file is there. Also in refence to the post before, I have another machine I can use, in case something like this happens. I think maybe it's a permissions issue, where the script running doesn't have write permissions. Guessing??
A wild guess The image process saves and switches between documents and may try to catch error and continue processing. On a Windows system there is an error in Photoshop CS6 that causes Action and Scripts that process more then on dcument to fail. If in your Photoshop preferences you have un-checked "Open Document in Tabs" edit your preferences and check the option in the interface settings and try the Image Processor Script again.
Where are your source files kept, and where are you targeting for the saved files? So far I have only tried on 1) a partion that is not the 10.8 boot, and 2) my 10.8 user's desktop 'Save in Same Location'.
Can you try running a Batch using the Production> Save as JPEG Medium action? Pick from the same source directory and save to the same destination, and check the 'Override Action "Save As" Commands'. You'll also want to turn off the 'Save' dialog in the action before running the batch script.
I tried John's suggestion and ran with Tabbed documents OFF and it didn't change anything (AFAIK, that is a Win specific bug).
The Bridge Cs5.1 crashing also isn't showing up on my 10.8 setup, but it would be wholly separate from this issue.
I tried that SG. came up with this error.
Could not save a copy as “ROD_9405 copy.jpg” because of a program error.
I saved in the same directory.
Here is the log of error.
File: "Dumbo:Seniors2013:Bridget Kazda:ROD_9402.NEF"
Error: Could not save a copy as "ROD_9402 copy.jpg" because of a program error. (-199)
Yes that seems like a permissions issue. Have you tried repairing disk permissions after the install?
Here's a video for repairing that's geared to when installers balk, but give general navigation if you haven't used Disk Utility before:
I found it works if I save local to my hard drive. I have been using a network share to process my files for years and now it doesn't work. So yes it's a permission problem, but I can save manually to my SMB share, just not throught the image processor. Solutions??
There are several reports around the web about 10.8 having problems with network volumes that worked under 10.7 (especially volumes using SMB protocol). We'll investigate and document the problem for Apple.
In the meantime, it sounds like 10.8 doesn't like working with network volumes, so the above suggestions about saving locally still apply.
So just to be perfectly clear, have you seen it work before, saving to the network device, on Mountain Lion, or not?
If not, it sure sounds like a new bug introduced in 10.8 to me. I just rescanned the thread and didn't see... What's the server you're trying to save the files to running?
I think storing files onto windows-shared volumes is broken in various ways in Photoshop on 10.8. We've discovered that third-party folrmat writers simply cannot write into such locations and a prime example of it is JPEG2000 which is shipped with Photoshop but seems to behave very much like a third-party plugin from the internal point of view. Simply try File->Save As -> JPEG2000 (into a _windows_ shared network folder)
There were some known OS bugs in 10.6 and 10.7 when saving to SMB. I suspect that Apple may have made those worse instead of better.
Using another network server protocol (AFP, or (shudder) NFS) may help, or saving locally and copying manually to the server.
Possible solution: I created the /etc/nsmb.conf file, with the contents:
It's an Apple problem, not Adobe
Good to know all problems enconted using CS6 are not Adobe problems. Network file sharing betweens OSs having problems seems to happen often when major changes are made in the operating systems, file systems and protocols.
I am experiencing this too, but I am not a techy at all. How do I create this file, and where do I save it please? I would really appreciate some help.
Also, I have lost a couple of files after I couldn't save them again on our server, they simply vanished, or at least it seems. Is there any way I can retrieve them?
Thank you for any help you can provide.
Edit: actually, I found the following in another post, which seems to be working, although saving seems very slow on the network, but that's a workaround that's easy to implement. Hopefully there will be a more suitable fix soon, but in the meantime, this seems to work.