1. I haven’t encountered this.
2. There is no guarantee that actions will work identically in different versions. You needed to debug those actions and modify them as necessary to work under Ps CS3. The same goes for the scripts that you apparently run under your actions. There were significant differences between CS and CS2 for scripts; the same is true with respect to CS3. You acknowledge in #4 that the API may change. You need to modify the scripts for CS3.
3. I haven’t encountered this.
4. Obviously something has changed, and you need to modify the scripts. Have you tried using the tools available?
Hi Michael.
1. Other people have encountered this and it’s mentioned on the Bridge forum. This really isn’t a show-stopper, though.
2. Let me state this again – it’s not a certain action – it’s due to a set of concurrent steps of ANY actions. For example, try creating a color-boosting action, and create another action that calls this color-boosting action 10 times or so. Then, go to bridge, select image processor, and select this ‘master action’ to run on your images. You should be to see what I am talking about because the same error that I see should occur. Now, in reality, you wouldn’t run the same action that many times, but it’s a quick and easy way to replicate my problem and I would prefer to not release my own recipe for color-boosting to the public.
3. I have the latest’n’greatest intel processor, 4gb’s of memory and 1 TB of disk space – I shouldn’t have any problems with memory, but bridge does crash often, and it does it randomly.
4. I don’t know what tools are available. Can you educate me on this?
thanks
4gb’s of memory and 1 TB of disk space – I shouldn’t have any problems with memory,
I think I can see where you might have a problem – but I would prefer to not release my own recipe for solving this to the public.
What the heck – here goes. 😉
With that much disk space I would guess you might be working/opening/saving across a network. If so try keeping all "work in hand" on the local computer.
Also, unless you are running on a 64bit OS, 1770MB is all your application can use (3GB with XP Pro’s 3GB switch). Try dropping the amount of memory allocated to Photoshop. Bridge runs outside of this alocation and can be starved of resources if it’s set too high.
I would prefer to not release my own recipe for color-boosting to the public.
This is a "User to User" forum with a two-way flow of information. 99.99% of us come here to share.
Keep such things to yourself by all means – but announcing it like that might make some people think: "why should I bother helping you then?"
Point taken?
Hi, the actions that I use are purchased from other photographers, and I don’t think they would appreciate me posting their actions and what they contain on an open forum. It defeats the purpose of selling them. Besides, you don’t really need my exact color recipe to replicate the error message. It’s not that I don’t want to share, but I want to respect the integrity of the actions that I purchased, too.
I’m not on a network – all on 1 PC. Again, I never had any of these problems with CS2. I am using the 3G switch, too. I allocated 70% of my resources to CS3 through the preferences.
I’m not really looking for user’s help, because I don’t think any user can help me (or maybe they can). Instead, I know that Adobe reads these boards, and I believe that Adobe needs to address this. I don’t know of any way to tell Adobe about my problems without paying them $40/hour. So, I’m saving the money and voicing my opinion here. If someone knows of another way I can talk to Adobe and address these issues, then that would be greatly appreciated.
Thanks!
"I’m not really looking for user’s help, because I don’t think any user can help me (or maybe they can)."
Don’t be so sure about that, and you might want to be careful with potentially insulting people here who might very well be able to help you get your problem sussed.
"Instead, I know that Adobe reads these boards, and I believe that Adobe needs to address this."
Sometimes PS engineer Chris Cox will pop in, and other Adobe employeeseven less frequently.
"I don’t know of any way to tell Adobe about my problems without paying them $40/hour."
Can’t have it both ways. Either you do your own research and interact with others on-forum (here and elsewhere), or you pay Adobe. With all but the most esoteric problems, you’re as likely to get help here as you are by calling Adobe.
Faster, and for free.
I know that Adobe reads these boards
Not true. Sometimes Adobe employees read the boards. Not always and at certain times, not often.
Faster, and for free
And we don’t close for weekends and Holidays.
wrote in message
Hi Michael.
2. Let me state this again – it’s not a certain action – it’s due to a set of concurrent steps of ANY actions.
For example, try creating a color-boosting action, and create another action that calls this color-boosting action 10 times or so. Then, go to bridge, select image processor, and select this ‘master action’ to run on your images. You should be to see what I am talking about because the same error that I see should occur. Now, in reality, you wouldn’t run the same action that many times, but it’s a quick and easy way to replicate my problem and I would prefer to not release my own recipe for color-boosting to the public.
Are you creating this "color boosting" action in PS CS2 and then running in Bridge CS3? Or are you in this example creating the "color boosting" Action in PS CS3 and running in Bridge CS3? I do not want you to have to post your actions since they have value but if you could provide me very specific generic steps to repro your issues. I will see if I can repro locally (Adobe). Thanks, and Adobe is listening/reading these forums.
Dave @ Adobe
thanks
With that much disk space I would guess you might be working/opening/saving across a network. If so try keeping all "work in hand" on the local computer.
Making assumptions is rarely a good idea, always better to confirm/ask. I have 1.4T of disk space in my workstation computer. No networked storage, though I do have another 2.9T of external HDs space.
Thanks Dave, it is comforting to know that Adobe is monitoring these posts…I am still reluctant to install CS3, but as I learn about these problems (challenges) with others that have installed, I may be able to avoid a faulty install and avoid the frustrations that I have read regarding others…anyway, just wanted to say thanks from this consumer that you are reading and trying to help
Cecil
Michael, to test your hypothesis, I created an action, Test1, with three steps: Hue/Sat (Sat +33); Duplicate layer; Set layer blending mode to Darker Color. I created an action, Test2, consisting of twelve iterations of playing action Test1. Next, I selected an image in Bridge and ran the action from Tools > Photoshop > Batch. It worked fine. I tried it again, with 4 images selected in Bridge. It worked fine. It bogged down a bit starting with the second image, probably because there was some paging going on. These were all flattened TIFFs 77-92 MB.
This is using PsCS3 on an AMD 64X2 4600+ with 4GB RAM, XP Pro with /3GB switch, with PsCS3 set to use 70% of RAM.
Hi Michael,
Dave had asked me to look into the problem you are facing. I was finally able to reproduce it at my end. It turned out to be a little tricky one. If you copy the same action more than 20 times in a set, will show this error.
I have reported the issue and it will get resolved in the future. For the time being I can suggest you following workarounds for the same:
1. Try reducing the number of actions to less than 20.
2. Running the actions from Action palette works fine.
3. Try creating an additional action to save the file in your desired file format and then using Batch you should be able to run action as well as save them in any file format.
Hope this helps!
– Rakesh Lal @ Adobe
Thanks Rakesh. Wow, I’m so glad that these forums work. Katrin Eismann was right when she told me that you guys monitor these forums. Now, I just have to work on figuring out why the mods that I made to Russell Brown’s 1-2-3 script no longer work. I’ll hopefully get to that next week (I’m bogged down this week with customers).
Thanks so much Adobe.
No response, though, on the "printer settings not being remembered".
Glad to hear you got some action on your issue.
Rick
