In one case, I set the PS dialogs on to check the settings then cancelled NI. Or the action would record a fixed profile name. Or it would seem to work fine but actually used the last (incorrect for this image) profile.

I was often getting bogus messages that no matching profile could be found. This all adds up to unpredictable PS action behavior depending on how NI was last used. Even Auto Match Preset (Actions Menu) will default to RecentPreset if a preset matching the profile name is not found. Then in the Noise Filter Settings (Tab) you need to select a previously saved Filter Preset from the fly-out selection list. The trick was to use the Action menu to set Auto Match Profile instead of the Device Noise Profile (Tab) icons. The trick is to get the new action to record AutoMatchProfile and “MyPreset” so that batch is unaffected by other NI activities. The problem is that when you then run the action with PS automation, it will use whatever you last did with NI (for some unrelated manual tweaking) instead of what you really wanted. By default these will contain RecentProfile and RecentPreset. The action records two parameters, Profile and Preset. The frustration was with getting the action to record usable options for Neat Image. The major difficulty was with recording a new PS Action for the NI plug-in. And you should have some experience with CS2 actions. If you are attempting this, be sure to read the NI docs cover to cover first. I am very impressed with the capabilities of NI but the User’s Guide and product usability could be improved. So I would like to post some comments for the NI folks. I was able to automate Win/XP NI 5.6 Pro+ with PS CS2 but only after considerable frustration.

Photoshop cs2 actions