I haven’t experienced that problem. But a related annoying problem with batch actions in CS4 is that if I minimize Photoshop while a batch action is running, the program interface minimizes, but the images open and close on the desktop still. In prior versions of PS, I could minimize the program and the batch action would go on in the background, invisible to me, while I could do other tasks. But now, when I run a batch to convert over 1000 files, each one pops open on the desktop, in front of any other open app’s windows. It then closes and the next one opens, etc. Which means my computer is unusableduring any batch command.
Very annoying! How could the QA and beta testers have not noticed this?
Hi David,
There is a workaround for you:
On Mac, you can select Windows > Application Frame, then run batch, the application can be minimized
On my Windows, the whole application can be minimized.
I’m using Windows on a PC. I actually reported this as a bug, and one of the engineers confirmed it as a bug. So apparently they were able to reproduce the problem. I’m waiting with baited breath for a fix, since I run batch conversions frequently on thousands of files at a time.
David, which bug did you report to Adobe? Was it the bug that the thread was started for or your bug?
Its confusing when a thread specific to one very particular problem is taken over by another issue entirely. If you are going to tell people that Adobe is aware of the problem and it is not the problem that the thread was started about and titled, you should either start your own thread or reiterate the specific bug when talk about it.
Thank you.
Sorry, Mike. I reported to Adobe the bug I discovered. My apologies if I somehow hijacked your thread. But it seems to me that the problem I experience is rather similar to yours, even if it isn’t identical. Just like the very very long threads on this forum about performance issues related to OGL. Not everyone experiences the identical symptoms, but all seem (at this point) to have common cause. I suggest you make an official bug report. Clearly there have been some changes to batch actions in PS, and possibly our two problems are two sides of the same coin.
