Rotate in CS2 from Bridge (OS 10.3.9)

It would be much more useful if rotating an image in Bridge would also rotate the original file - as it stands rotating in Bridge is a waste of time as this has to be repeated in Photoshop.

[email protected] wrote in news:[email protected]:
> Even with a fast computer rotating a scanned iamge file of 55 MB is
> not that quick
Repeating: Bridge only rotates the preview.
I guarantee you do not have a preview 55MB in size.
If the rotate in Bridge for any single image lasts more than a fraction of
a second, your problem lies elsewhere.
Actually, if rotating a 55 meg bitmap in photoshop takes more than about
three seconds, either you really haven't got a very fast computer, or your
fast computer has problems.

Similar Messages

  • Copying from Bridge CS2

    I cannot seem to be able to copy files from Bridge when I am viewing them. I am using Windows Vista. Why can't I highlight a photo, then copy and paste it to another location?

    Because what you see is just a thumbnail with a link to the file. To get around this I added "copy to" and "move to" to the right menu.
    Have to change the resistry, but on-line instructions are pretty easy. Believe Google - copy to vista.

  • Image processor from Bridge problem

    ONe of most annoying things with Bridge is that often, image processor wont open from Bridge -- unless you quit out and relaunch Bridge -- quite a hassle.

    You are absolutely correct. In order to pass selected images in bridge over to photoshop, you need to invoke IP from within Bridge. I didn't make that connection from your earlier post.
    So your original request makes sense. Personally, I would rather see an improvement in Image Processor (as well as the Batch dialog) that allowed one to specify the source as "Bridge".
    In photoshop 7, in the batch dialog, you could specify the source of the files to be batched as "Open Files", "folder", or "File Browser". If you choose File Browser, the batch action will be performed on files selected within FB.
    In CS2, in the batch dialog, you can see Bridge as an option, but it's grayed out. You can only invoke the Batch operation on files selected in Bridge from within Bridge - a serious shortcoming.
    The same theme holds true for Image Processor, and indeed, it looks like most of the scripts behave that way.
    So rather than have a shortcut, I would like, as I say, the ability to specify bridge as a source in the dialog boxes for the image processor and batch dialogs.

  • CS3: Favorites from Bridge dont show up in Adobe Dialog

    Favorites from Bridge don't show up in the Adobe dialogs of ID, AI and PS.
    This issue was already reported here: http://www.adobeforums.com/webx/.3bc3e4b8/12
    with no solutions or workarounds to the problem. This function was very useful in CS2. I can help myself on a Mac but file handling is very annoying if you have to work with Windows (XP).
    Anyone with a solution out there?
    regards
    dirk

    It works differently in CS3 than CS2. From the file open dialog, browse
    to where you need to be. Right click the folder and choose add to favorites.
    Bob

  • Tiff previously edited in ACR will not open in Camera RAW from Bridge

    Yes, I have googled this and found instances going back to 2010 with no satisfactory answer. I have Photoshop 5.1 and the latest ACR and Bridge that work with it. 2011 MAC Mini 10.8.2.
    I scanned a landscape oriented printed email image at 800 spi as a portrait orientation and saved it as a tiff. I opened this tiff in Preview and decided it needed more than minor tweaks so I opened it in ACR from Bridge, made a few adjustments and saved it. I thought I could see what I was doing better if it was in landscape orientation again so I opened it in Preview and rotated 90 deg CCW, saved it as a tiff. Going to Bridge I found Open in Camera Raw greyed out. I went back to Preview to see if I could get what I needed in its Tools while viewing it in landscape. Adjustments took forever this time, so I gave up and took a look at the image characteristics. Rotating in Preview had changed the image size to 3.3333...... times larger at 240 ppi still aRGB, still a tiff. This has never happened before, including slow adjustments
    I duplicated the rotated file and changed it back to 800 ppi and normal size, went to Bridge, Camera Raw still greyed out. Original unrotated image
    that had been edited in ACR and saved will still open in ACR.
    All kinds of strange things have happened since updating to 10.8.2, but I don't think this is one of them because of the complaints I have seen that date back to 2010. I did a full maintenance routine, i e cleared RAM, reboot in single user with fsck -fy, repaired permissions, back up with SuperDuper which repairs permissions again. Then I tried Bridge again, original will open, rotated won't.
    Anyone know the answe?

    The answer is that making edits in ACR and saving it creates layers in the tiff and Bridge will then not open it again in ACR unless you flatten it. I still don't know why Preview increased the image size by 3.333.....x or why ACR increased the tiff file size by 2.6x and why the flattened tiff is 2x the file size of the original scan but the image dimensions are the same. This stuff apparently is above the pay grade of anyone in google, too.

  • Can't Open jpeg files from Bridge CS3 to PhotoShop CS3

    This is really weird. I had a trial version of CS3 and bridge worked fine. That ran out, so I tried CS2 to see if I could get by with the older version. CS2's bridge worked just fine.
    Then I installed a full version copy of CS3 and removed CS2 (to free up space) and for some bizarre reason, I cannot open any files from bridge into Photoshop. It's the CS3 bridge because I clicked on the Help, About Bridge and it showed CS3.
    When I just click "open" under file, it tries to open with Illustrator. When I click, "open with" I get this list: Adobe Illustrator CS3 (default), Firefox 2.0, Internet Explorer 6.00, and Paint 5.1.
    I can't figure out a way to change the default to CS3, and it worked fine with the trials.
    Please advise.

    It was a nice thought. I just did it, and associated all .jpg type files with photoshop, but no such luck in solving issue. I did figure out a way around it that kinda works, but not nearly as convenient. I drag select a group, then hold-click on the group and toggle into Photoshop, then let go. It pastes the group there. However, if I control click to select a group (or deselect within a group), I can't hold-click. So I have to do smaller groups at a time if I want to bypass certain pictures that get grabbed in a bigger group--does that make any sense at all?

  • CS3 Extended - Can't get images from Bridge to open in Photoshop

    I am wondering if I have this CS3 installed incorrectly.  I had CS2 before and after my hard drive failed I ordered CS3.  Before the new CS3 arrived I downloaded Picasa from Google and that was my image viewer in the interim. I also installed a trial CS2 on my computer from finding it on the internet.  When I downloaded CS3, my RAW images were opening up in Picasa which I didn't like.  So, I went to Picasa's software and clicked no to opening RAW images in it.  That fixed that problem and I also uninstalled the CS2 trial.  But now my CS3 Adobe Bridge doesn't recognize that there is CS3 Adobe Photoshop when I want to open TIFF or JPEG images.  It opens them in Windows viewer.  Even when I right click on an image in Bridge to Open with, it only offers me two browsers, Firefox and IE.  Where do I go to reset the Bridge images to open in Photoshop?  Right now I have to switch back to Photoshop from Bridge and go to File-Open. 

    In Bridge, go to Edit->Preferences->File Type Associations

  • Initiating Photoshop CS4 batch from Bridge sometimes ignores RAW xmp settings

    This happens a lot using both my work PC (XP 64) and home PC (Vista 64), but not always...and I have not been able to track down exactly how to fix this.
    What happens is I try to launch a batch process for RAW photos taken with my Canon EOS 5D Mark II (develop settings already set in xmp files using Adobe Camera RAW from Bridge). The actions in the batch process execute correctly, but the resulting files appear to have completely ignored my ACR develop settings. This happens if I launch the batch process in either version of Photoshop CS4 (64 or 32 bit).
    My only solution is to carefully watch Photoshop as files get loaded by the batch process and abort the batch if one opens without the correct develop settings (not always easy to discern...sometimes I have to wait for the process to save the file so I can toggle back and forth between the images in Bridge). I then restart Bridge and/or Photoshop until I can start a batch process that opens the image correctly. Once a single file has opened with the correct settings, subsequent files open as expected...so the rest of the batch process will complete.
    Has anyone else seen this phenomenon? This is really annoying as it never happened to me in CS or CS2.

    This happens a lot using both my work PC (XP 64) and home PC (Vista 64), but not always...and I have not been able to track down exactly how to fix this.
    What happens is I try to launch a batch process for RAW photos taken with my Canon EOS 5D Mark II (develop settings already set in xmp files using Adobe Camera RAW from Bridge). The actions in the batch process execute correctly, but the resulting files appear to have completely ignored my ACR develop settings. This happens if I launch the batch process in either version of Photoshop CS4 (64 or 32 bit).
    My only solution is to carefully watch Photoshop as files get loaded by the batch process and abort the batch if one opens without the correct develop settings (not always easy to discern...sometimes I have to wait for the process to save the file so I can toggle back and forth between the images in Bridge). I then restart Bridge and/or Photoshop until I can start a batch process that opens the image correctly. Once a single file has opened with the correct settings, subsequent files open as expected...so the rest of the batch process will complete.
    Has anyone else seen this phenomenon? This is really annoying as it never happened to me in CS or CS2.

  • Opening a Script in PS from Bridge

    The following script was (severely) hacked from Bob's OpenClose_PS.jsx. It is called from Bridge and runs the target script in Photoshop. It seems to work even with complex scripts that go from Photoshop back to Bridge to do more things in Bridge.
    #target bridge
    function getScript ( ) {
    var scp = "remoteScript = " + remoteScript + "\n";
    scp += "remoteScript();";
    return scp;
    function remoteScript ( ) {
    var f = new File ('/c/Program Files/Adobe/Adobe Photoshop CS2/Presets/Scripts/ah-rawprocessor1.js');
    if (f.open('r')) {
    var sStr = f.read();
    else throw('failed to open script'+f.fsName);
    eval(sStr);
    function runScript ( ) {
    var bt = new BridgeTalk ();
    var theScript = getScript();
    bt.target = "photoshop";
    bt.body = theScript;
    bt.send();
    runScript();
    BUT I do not understand what is going on in the first line of the getScript function - or perhaps in the whole of that function. I would like to understand it better and as part of that find a way to specify the target script path within the runscript() call ie runScript(targetScript);
    Andrew

    Just to make sure - you're creating a script (in Bridge) from a PS script in PS' presets/scripts folder, that will eventually be sent to PS - correct?
    Send 2 BT messages.
    The first one gets the script path. Put the result of that into your script before you actually send it to PS.
    You'll get the result in the onResult handler.
    var bt = new BridgeTalk();
    bt.target = "photoshop";
    bt.body = "app.path;"
    bt.onResult = continueOp; // function that continues the process
    continueOp = function( msg ) {
    var path = msg.body;
    // do the rest
    You have to be careful - there's a bug in BT that causes a queued message (waiting for an app to launch) to un-bind from it's onResult handler. The result is that if you launch PS with a BT message that expects an onResult handler to fire, it won't. Once PS is launched and ready, this isn't a problem.
    There's a function - startTargetApplication( target );
    that will start the target app and wait until it's ready. You can use that, but it locks bridge up until the target app is fully launched.
    Another way is to use this new beastie I've been working on:
    AppLauncher = {};
    AppLauncher.array = new Array();
    AppLauncher.processID = null;
    AppLauncher.running = false;
    AppLauncher.pause = false;
    AppLauncher.id = 0;
    AppLauncher.launchTimeout = 2 * 60 * 1000; // 2 minutes
    AppLauncher.launchCycle = 3000; // launch and check launch status every 3 seconds
    AppLauncher.purge = function() {
    AppLauncher.array = new Array();
    try {
    app.cancelTask( AppLauncher.processId );
    } catch ( e ) {
    AppLauncher.running = false;
    AppLauncher.pause = false;
    AppLauncher.launch = function( target, callback, context ) {
    if ( !BridgeTalk.isRunning( target ) ) {
    var launcher = new AppLauncher.Launcher( target, callback, context );
    AppLauncher.array.push( launcher );
    if ( !AppLauncher.running ) {
    AppLauncher.running = true;
    AppLauncher.processId = app.scheduleTask( "AppLauncher._$launch();", AppLauncher.launchCycle, true );
    } else {
    if ( context ) {
    callback.call( context, true, target );
    } else {
    callback( true, target );
    AppLauncher._$launch = function() {
    // $.writeln( "launching" );
    if ( !AppLauncher.pause ) {
    for ( var i = 0; i < AppLauncher.array.length; i++ ) {
    AppLauncher.array[ i ].launch();
    if ( AppLauncher.array.length == 0 ) {
    if ( AppLauncher.processId != null ) {
    app.cancelTask( AppLauncher.processId );
    AppLauncher.running = false;
    AppLauncher.pause = false;
    AppLauncher.Launcher = function( target, callback, context ) {
    this.id = AppLauncher.id++;
    this.target = target;
    this.callback = callback;
    this.context = context;
    this.calledback = false;
    this.launched = false;
    this.t1 = new Date();
    AppLauncher.Launcher.prototype.timedOut = function() {
    return ( ( new Date() - this.t1 ) > AppLauncher.launchTimeout );
    AppLauncher.Launcher.prototype.resultHandler = function() {
    if ( this.context ) {
    this.callback.call( this.context, true, this.target );
    } else {
    this.callback( true, this.target );
    AppLauncher.Launcher.prototype.kill = function() {
    AppLauncher.pause = true;
    var array = new Array();
    for ( var i = 0; i < AppLauncher.array.length; i++ ) {
    if ( AppLauncher.array[ i ].id != this.id ) {
    array.push( AppLauncher.array[ i ] );
    AppLauncher.array = array;
    AppLauncher.pause = false;
    AppLauncher.Launcher.prototype.launch = function() {
    if ( this.timedOut() ) {
    this.kill();
    if ( this.context ) {
    this.callback.call( this.context, false, this.target );
    } else {
    this.callback( false, this.target );
    } else {
    if ( !this.launched ) {
    BridgeTalk.launch( this.target );
    this.launched = true;
    if ( BridgeTalk.isRunning( this.target ) && ( !this.calledback ) ) {
    this.calledback = true;
    if ( this.context ) {
    this.callback.call( this.context, true, this.target );
    } else {
    this.callback( true, this.target );
    this.kill();
    The usage is:
    AppLauncher.launch( target, onLaunchedHandler, context );
    target is the target app
    onLaunchedHandler is a callback to execute when the app has been lauched.
    context - is a context object - used ONLY if your onLaunchedHandler is a method of an instance of an object. IF THAT IS THE CASE - include the object as the context. If it is NOT the case, leave as undefined.
    onLaunchedHandler = function( success, target ) {
    success - boolean -true if app launched and responded
    target - target app that launched.
    Example:
    var ns = {};
    ns.continue = function( success, target ) {
    // make and execute script
    AppLauncher.launch( "photoshop", ns.continue );
    fred = fuction( target, script ) {
    this.target = target;
    this.script = script;
    fred.prototype.continue = function( success, target ) {
    // make and execute script
    var bt = new BridgeTalk();
    bt.target = this.target;
    bt.body = this.message;
    bt.send();
    fred.prototype.send = function() {
    AppLauncher.launch( this.target, this.continue, this ); // note the context object here because the onLaunchHandler is attached to an instance object
    var f = new fred( "photoshop", "app.path;" );
    f.send();
    This on will not freeze bridge while waiting for launch.
    Bob
    Adobe WAS Scripting

  • ACR missing from Bridge CS3 on Mac

    I am working on a MacBook Pro with Adobe CS3.
    When I originially installed CS3 running OSX 10.4 the "Camera Raw Preferences" under the file menu was missing. I also could not "Develop Settings" or any other ACR functions from Bridge. I was able to open files in Photoshop and use ACR that way, but that seriously hindered my workflow.
    In order to solve the issue I: 1) Updated CS3 (did not fix) 2) Rebuilt Permissions (did not fix) 3) Un-installed CS3, Re-installed CS3 (DID FIX! Camera Raw back in Bridge!)
    I Recently upgraded to Mac OSX 10.5 (Leopard) and now I am right back where I started: no ACR in Bridge.
    So, again I tried to fix by: 1) Un-installing & Re-installing CS3 (did not fix) 2) Re-installing Mac OSX 10.5 & CS3 (did not fix, but was a major hassle)
    I am hoping their is a known fix to this, or if there is a scheduled update to either CS3 or Mac OSX 10.5 addressing such issues with Bridge. I would rather not revert to 10.4 having bought 10.5.

    Assuming you have installed the RAW plug in at the correct location??
    from the FAQ;
    Q: How do I know that Adobe Camera Raw is installed correctly?
    A: For Photoshop CS2 and CS3 customers the most efficient way to ensure that you have the latest Camera Raw update installed correctly is to choose the �Updates�� option from the help menu. For Photoshop Elements customers the best way to verify that the Camera Raw plug-in is installed correctly is to make sure it appears (only once) in the "About Plug-in" menu (see: Photoshop menu on a Mac or Help menu on a PC). The correct version is displayed when you pick its name and see its about box. If "Camera Raw" is not in this list, you have not installed it correctly.
    Q: I am trying to replace ACR 3.0 by 3.1 (or higher) I cannot find ACR in my Photoshop/Plug-in/File Formats folder, where is it located now?
    A: As explained in the "Readme", which can be found on the ACR download page, the new correct location is:
    Photoshop CS2
    Mac: /Library/Application Support/Adobe/Plug-ins/CS2/File Formats/�
    Win: \Program Files\Common Files\Adobe\Plug-ins\CS2\File Formats\�
    Photoshop CS3
    Mac: /Library/Application Support/Adobe/Plug-ins/CS3/File Formats/�
    Win: \Program Files\Common Files\Adobe\Plug-ins\CS3\File Formats\�

  • Kernal Panics with CS2 and Bridge?

    I have had the Mac Pro for two weeks.
    This AM I sent it back to Apple for a new one.
    From the day I took it out of the box I experienced
    K.Panics. More so while in CS2 / Bridge.
    Did an erase and install to no avail - ie. ruled
    out software.
    Anyone else having these types of issues with
    CS2 and Bridge? On another note - while doing
    nothing the machine is reallllly quiet, however,
    once I start working on it the drive make a
    sound like a subtle static, frying rice, etc.
    Is this normal?
    Many thanks.
    Mac Pro   Mac OS X (10.4.7)  

    Have installed 3rd party RAM or any other internal devices?
    As for your drive noises… this is normal.

  • I an getting an error with photo merge in PS cc . It gives me a code tmp00000001 using from photoshop and if I try from bridge it tell me that I need to select more than one image. It is not recognizing the photos I am selecting in bridge. please help. my

    A new problem with CS5 forced me to download PScc but the problem is still there.  I am getting tmp00000001 in photo merge when importing multiple files from inside PS and if trying from bridge I am getting a pop up box telling me I need to select more than 1 file. Photoshop potomerge is not recognizing my selections from bridge..!! please help.. my knowledge of computers is a 3 on a scale of 1-10

    if i run this particular code
    ( SELECT
    AccountDetails.CUSTOMERNUMBER, AccountDetails.ACCOUNTNUMBER, CUSTOMERDETAILS.CDTITLE, CUSTOMERDETAILS.CDFIRSTNAME, CUSTOMERDETAILS.CDLASTNAME, AccountDetails.ACCOUNTTYPE,
    AccountDetails.ORIGINALCONTRACTENDDATE, AccountDetails.CONTRACTTERM, AccountDetails.CONTRACTENDDATE, AccountDetails.BRANCHAREA, AccountDetails.PRODUCTTYPE,
    AccountDetails.HOUSEBANKACCOUNT, AccountDetails.CARMODEL, AccountDetails.CARLICENCE, AccountDetails.ARREARSBALANCE, AccountDetails.CODEBTOR, AccountDetails.GUARANTORNUMBER
    FROM AccountDetails
    JOIN CUSTOMERDETAILS ON AccountDetails.CUSTOMERNUMBER = CUSTOMERDETAILS.CUSTOMERS1
    WHERE EXISTS
    ( SELECT *
    FROM Dcaaccountallocation
    JOIN DebtEpisodes ON DebtEpisodes.ACCOUNTID = Dcaaccountallocation.ACCOUNTID
    WHERE Dcaaccountallocation.dcaid = 41
    AND Dcaaccountallocation.status = 2
    AND DebtEpisodes.DCASentDate IS NULL
    AND Dcaaccountallocation.ACCOUNTID = AccountDetails.ACCOUNTNUMBER
    AND DebtEpisodes.DCAORLAWYER = 'DCA'
    This returns 1 row of data
    However if i run a small part of the above code...
    SELECT *
    FROM Dcaaccountallocation
    JOIN DebtEpisodes ON DebtEpisodes.ACCOUNTID = Dcaaccountallocation.ACCOUNTID
    WHERE Dcaaccountallocation.dcaid = 41
    AND Dcaaccountallocation.status = 2
    It returns a lot of rows with a status of 2
    Now i presume what I am going to do is to ensure that all the fields provide satisfactory requirements, with regards to the above code. Although I have many records in all the stated tables already.
    :(

  • Problem using Image Processor from Bridge

    I have been using the Image Processor to process photos from Bridge for quite some time. However, I recently received an error message when I try to initiate Image Processor from Bridge and I have not been able to find any help topics that address my problem: I select images in Bridge to process, then click "Tools>Photoshop>Image Processor". Photoshop opens and the familiar Image Processor dialog box opens. Item 1 in the dialog box says "Process files from Bridge only" and has the number of files I have selected in parenteses. I select the file type and other settings in #3, and preferences in #4. When I click "Run", I get an error message window that says: "Script Alert. There were no source files that could be opened by Photoshop". The Image Processor works if I open the files in Photoshop first, then run it by selecting "File>Scripts>Image Processor" and tell it to process all open files.
    Would someone be able to help me with this problem?
    Thanks, Larry

    Usually when it worked before and not now, and you have added no new software or hardware I recommend resetting the preferences.  Hold down the Ctrl key and click on the Bridge icon to start.  You should get a reset window with 3 options.

  • I can't get Dr Browns Image Processor Pro to work from Bridge with Photoshop CC 2014

    We use the wonderful DR Browns Image Processor Pro script a lot, but cannot get it to work from Bridge with PS CC 2014. When I select files in Bridge CC and then go to Tools> Dr Browns Services 2.3.1 > Image Processor Pro it just pops up an error message that says ReferenceError: photoshop is undefined.
    The actual script works fine if I launch it from Photoshop CC 2014 - just not if I load it from Bridge CC.
    I have unistalled it and re installed a few times, both manually and through the Extension Manager CC.
    I am using a Win 7 64bit computer.
    I assume there is some change in the scripting part that loads Photoshop from bridge but not sure. It worked fine in CC. Just not CC 2014.
    I opened the Dr Browns Services .jsx file but don't see anything obvious. This is the section related to the Image Processor Pro part:
      // This routine takes an array of files. If called by Photoshop,
      // it will invoke Dr. Brown's Process 1-2-3 with the files. If called by
      // any other app, it will send a BridgeTalk message to Photoshop
      // to invoke this routine with the same arguments.
    drbrownserv.process123 = function (files) {
    // Bring Photoshop to the foreground.
      BridgeTalk.bringToFront ("photoshop");
      // Create a new BridgeTalk message for Photoshop to invoke
      // Image Processor with the selected files
      var btMessage = new BridgeTalk;
    btMessage.target = "photoshop";
      btMessage.body = "drbrownserv.process123 (" + files.toSource () + ");";
      btMessage.send ();
      } else {
    photoshop.runActionCommand ('611736f0-9c46-11e0-aa82-0800200c9a66', files);
      catch (error) {
      if (error.number != 8007) // Don't report user cancelled errors.
      drbrownserv.alert (error);

    I copied that .jsx file to a new name "Xbytor Image Processor Pro.jsx" edit that file changed the string Dr Browns services to "Xbytor Image Processor Pro" then commented out all the code that added tools menu items but "Image Processor Pro" and I put that file into
    "C:\Program Files (x86)\Common Files\Adobe\Startup Scripts CC\Adobe Bridge" even though Bridge CC is 64Bit seems to use theat location.
    Bridge CC was updated by the creative clouds update and opens Photoshop CC 2014 now

  • Exporting to Flickr from Bridge CS6 Fail

    I'm trying to export photos from Bridge CS6 to my Flickr.com account for the first time in several months, and getting an error message from Bridge that it cannot "authenticate with Flickr".  I've used presets that were successful in the past, as well as going through the usual routine to get new authentication codes from Flickr.com. I recently updated my iMac to OSX 10.x, but visiting Flickr's community site suggests that they adopted a new API that was sent to developers like Adobe and that Adobe has not updated their export protocol. Other contributors to the site suggest that Adobe's position is that Flickr needs to do something.  Are others experiencing this problem? Does Adobe offer no solutions to this problem?
    Any advice would be appreciated.

    I had to rebuild the file from scratch in order to export the pdf, and the hotspots line up accurately to their originally location drawn on fireworks.
    This may have occurred because I began the document with a canvas size of portrait letter, but changed the canvas size later to landscape letter, and although everything looked well and fine, the export was still triggering the old referential data in the file.

Maybe you are looking for