Skip to main content
Participant
September 23, 2011
Question

Bridge CS4 not using newly installed Enhanced Image Processing Photoshop script

  • September 23, 2011
  • 1 reply
  • 1399 views

Hi all,

Hope someone can help here.  We just added this Photoshop extention:  Enhanced Image Processor by Manovi to our Photoshop CS4's Presets/Scripts folder.  Here's my problem.  The new image processor opens and runs great - in Photoshop.  But when I'm in Bridge CS4 and choose Tools>Photoshop>Image Processor it opens/uses the old script.  Does Bridge cache this kind of thing or what's going on.

How can I get Bridge to use the new image processor?  (note:  Old script was replaced by new one in Photoshop's preset/scripts folder - the old one is no longer there - although we did save a copy of it elsewhere)

Thanks

This topic has been closed for replies.

1 reply

Inspiring
September 23, 2011

I don't have CS4… but in CS5 the paths to the files in Photoshop's scripts folder are coded into the functions that call them… Bridge reads these files on request evaluates them then runs… I would suspect the file name may differ from what it's looking for… Have you tried calling it the same and placing it in the same location? If this fails you may need someone to edit the Bridge startup script (not a job for the faint hearted)… Sorry but that ain't going to be me it uses localized strings don't understand them yet… Paul R may well say he can do it I don't know… So NOT cached… but possibly NOT read either in you case…

Participant
September 23, 2011

Mark that's helpful.   I'll check into some of those things you mention.  And yes, the file name is the same so it must be something else.

Inspiring
September 23, 2011

It could be that the 2 scripts are NOT compatible at all… That's really a question for the developer… For the standard Adobe provided functions you have one Bridge script reading the Photoshop scripts and providing them as services… Im not sure why Bridge would still use the old script if moved… These scripts load at app start have you done the usual reboot stuff?