Keywords in Bridge & Lightroom

Does anyone know if there is a limit on the number of keywords that can be used in Bridge/Lightroom?   Bridge seems to just keeps adding the keywords and keeps all of them together, whereas Lightroom only has the keywords associated with a catalogue.
I have a feeling I might be approaching a maximum and this is causing my problems with the corrupt files in the Cache.
It may also be I had let the Cache become too large.
Thanks

Bridge seems to just keeps adding the keywords and keeps all of them together, whereas Lightroom only has the keywords associated with a catalogue.
Keywords created in Bridge are stored in an xml file (on my Mac the path is: user/ library/ application support/ Adobe/ Bridge CS6 / Adobe Bridge Keywords.xml
But you can also use the tiny menu icon top right of metadata panel to use the option to export as a text file for back up purpose (and import also).
Can't imagine that there is a limit on the amount of keywords other then the storage space on your computer. but having said that, you already would have an endless list to exceed the space of an ancient floppy disk
Don't know how LR handles these list but can't image they store it in the cache.
Bridge Cache contains only the cache for thumbnails in different sizes, I dump this on a somewhat regular base if it has grown to large.
Applied keywords are stored in the files itself (including a DNG file) or in case of Raw (and having set the option to save metadata in an xmp side car file) in this side car file.
The central database is not the same as the central cache so dumping cache only needs an action to recache the thumbnails.

Similar Messages

  • Will the Keywords transfer from Lightroom to Bridge?

    Will the Keywords transfer from Lightroom to Bridge

    In LR once you add a keyword, have that thunbnail highlighted and (if on a Mac) hit the Command Key + the S key and it will send the info so it will be readable in Bridge. Or go to Metadata and click to send metadata to file. (I don't know the shortcut for a PC)  I haven't done it with PSCC yet, but in CS6 I quite often had to close out Bridge and re-start it and the keywords showed up.
    Sue

  • Delete Keywords in Bridge? Re-import into Lightroom?

    When I started trying Lightroom three weeks ago, I imported a few folders to learn with and created a keyword hierarchy.
    Then when I imported all my photos, the keywords assigned in Bridge came along for the ride, giving me something to do with my time straighten it back to the structure I had created.
    I use Bridge for renaming. Renaming my photos with the date first is a priority right now to help straighten out a mess of scanned photos not organized by date. It's been a slow process but necessary and I find it much easier to do in Bridge.
    So now I know renaming files outside of Lightroom creates a problem. What will happen if I get rid of my Lightroom catalog; delete all keywords in Bridge (not a problem since I'm right now working in folders for renaming and can easily delete all keywords in the folder); then import all the renamed files into a new catalog in Lightroom.
    Will the files keep the keywords written to them before in Lightroom even though I deleted keywords in Bridge? Or will I be deleting all keywords and have to start assigning them all over?
    Hope this makes sense, I'm afraid to do anything right now!
    Peggy

    Peggy,
    I think that if you are creating a new Ligtroom catalog, and importing your photos, that they will reflect what you have done in Bridge.
    But, to confirm that, I would suggest that you do a small test first:
    Start Lightroom, create a new catalog, import say 5 photos and see what Lighroom shows as keywords. Select a photo in Lightroom, change its keywords, save the changes and see if Bridge shows the change. Do the same then in Bridge, and Lightroom should show an icon at the top right of the frame in Grid view. Right-Click on it and "read metadata from file". The keywords should show the Bridge changes.
    I think you will see that Keywords operate fairly well between both programs. (If I had the time now I would have experimented for you, but I thought that suggesting something would be faster and work better).
    I think that when you have finished all your keywording in Bridge, you can safely create Lighroom catalog and import all you photos, and the new Bridge keywords will be there. (None of the old Lightroom catalog keywords should show up).
    p.s I am not atall sure of the syntax in Bridge for entering Parent-Child keywords, but Lightroom's syntax is Child>Parent. I had to think about the Lightroom syntax, because I always think the > is the "greater than" symbol in maths etc, but now I look at as a branching from Parent to Child. Amazing how the little things become " gotchas".

  • Duplicate Italic Keywords in Bridge

    You asked....
    In the keyword panel,I have the same keyword in several places in the hierarchy. I think some came in as legacy keywords, and others, I inadvertently created the same keyword twice. These duplicates appear in different parts of the whole keyword list. Now so I don't have all those confusing duplicates, and so I can find stuff, I would like to delete the extra keywords. The duplicates appear in italics. I can make them persistent, but I can't get rid of them. I've tried all sorts of things like finding all the files with the keyword in question, manually deleting the words and then re entering. I can delete the words, but they will magically reappear. What I want to do is consolidate multiple, duplicate kewords. Is that possible? Any ideas?Thanks
    Here is the summary of details and how to fix this.
    When you create keywords in Bridge, the metadata is stored in the xmp file in unicode 8 format.
    While that sounds like software techno babble, a point emerges.
    When Bridge reads the xmp file it reports on keywords that already exist within your own keyword library and this is indicated by a floating italic keyword.
    While this does not harm anything, it is a mess to read and organize.
    Here is the fix.
    You must follow these steps EXACTLY or you may create the need to re-keword files.
    1. Create a new UNIQUE keyword. I suggest capital "AAAA" (no quotes) since this places the keyword at the very top of your keywords.
    2. Do a Find with the keyword of interest. (typically one of the italic keywords that appear but choose the keyword in your Keyword Library and Not the italic keyword)
    3. Once the files are found, check the keyword in the Filter panel ON THE LEFT side of the Bridge screen where the keyword lists appear. (your Keyword Library is the panel on the right of the screen)
    4. Select ALL in the browser window.
    5. On the right side of the screen in the Keyword Library apply "AAAA" (or unique keyword of your choice) to the selected files. (no quotes) WAIT!.... for Bridge to COMPLETELY finish writing the metadata. (thousands of files can take some time, just watch the lower left progress indicator carefully!!!! and if you have tens of thousands consider using this technique to individual folders rather than entire root directories BE WISE!.... too many files can run Bridge out of memory and create a new problem)
    6. On the left side of the screen in the Filter keyword lists panel, check AAAA.
    7. On the right side of the screen in the keywords library panel navigate to where you would prefer to have the duplicate keyword located just so you know where it is.... Do NOT apply.
    8. On the right side of the screen where the italic duplicate keyword appears (alphabetically as it works out) uncheck the duplicate italic keyword and WAIT for bridge to COMPLETELY finish erasing the italic keyword.
    Here's the trick.
    What you have done is made a unique selection based a unique find and applied the unique keyword AAAA and have instructed Bridge to show all files within the unique search that NOW have the keyword AAAA and have erased the keyword that you used to do a Find, ie, the duplicate. (you will see that the unique word you used to do the Find will now be italic and "0" in the Filter keywords lists on the left side of the screen.
    All the photos will remain selected because they are now identified by AAAA.
    Now for the next step.
    9. In the Keyword Library on the right side of the screen, Navigate to the place where you wish the duplicate keyword to be located in step 7.
    10. Check the keyword and apply the keyword from the place where you want it (step 7) and WAIT for Bridge to COMPLETELY finish writing the metadata keyword. (the keyword lists on the left will no longer be italic and will be the exact number of files you selected)
    11. IMPORTANT!!!!!...... now uncheck AAAA in the keyword library to remove AAAA from the Filter keyword lists on the left. YOU MUST DO THIS AND NOT FORGET.
    (verify that AAAA is now italic and has "0" files)
    Believe it or not, you are done!
    You have now removed the italic keyword on the right permanently.
    Oddly enough, you won't see the italic keyword on the right go away, why is that you ask?
    The italic duplicate keyword you see is in Ram and will not go away until you Quit and ReLaunch Bridge.
    Like magic, the duplicate italic keyword has vanished.
    You must repeat this technique for EVERY file that has a duplicate keyword whether you created it or not otherwise the duplicate italic keyword will once again reappear.
    I VERY STRONGLY SUGGEST.... that you repeat these steps For ONE duplicate keyword Find at a time, in fact I cannot suggest this strongly enough. One Keyword At A Time.
    While you can use this technique for more than one keyword at a time, you will only cause more work as you go through this process.
    Sound complicated?..... its not..... do this once or twice and see that it is easier done than said.
    PS
    I have more than a million files keyworded and had to use this technique myself. (I devised this technique out of pure necessity and if followed and understood.... it works perfectly)

    Workflow...  A couple weeks ago I decided it was time to reload from scratch, so I re-installed Windows 7.  Which meant re-installing Photoshop and all that stuff.  Which meant it did all the updates.
    I've been doing other stuff, so I'm not sure I've been in Bridge where I'd have noticed the problem in the last week or so, which is about how long I've had all the new installs up and running... 
    So, it's a brute force "fix", but I opened Bridge and dithe "reset your preferences" thing.  Then immediately un-installed all the Photoshop stuff and re-installed all the Photoshop stuff.  When I restarted Bridge I pointed the cache at a different partition......
    I have NO idea WHICH thing fixed it, but no more phantom folders...  Curt, your idea about workflow finally got me thinking WHY was I only seeing recent folders as phantoms rather than ALL the ones I'd fiddled with...  And the ones I WAS seeing were all recent - in the last week or so.  So WHY it'd make any difference I don't know, but it appears to be happy again.  I'll try fiddling with stuff in Lightroom, make sure no new phantom folders show up, then if it's good I"ll point things back to the "cache" partition...
    Thanks for your help...

  • Import Keywords from Bridge ?

    I have a lot of keywords in Bridge and I'd love to bring them in LR (no way I'm going to retype them all). Is there any way to do that ?
    Thanks !
    Matt

    It is a bit fiddly, but essentially you need a tabbed text file. Create a few in Lightroom as an example then Export the Keywords, that will give you the structure.
    Places
    USA
    New York
    Washington
    United Kingdom
    London
    Birmingham
    Events
    etc
    Bridge's are in XML so you need to clear the code out
    It was a pity that they are not both in XML, but maybe version 2.0
    Richard Earney
    http://inside-lightroom.com

  • Is it possible to embed keywords assigned in Lightroom 4 into DNG files?

    Keywords I assign to photos in Lightroom do not show up as "tags" when I view the photo's properties in Windows Live Photo Gallery. Is it possible to embed keywords assigned in Lightroom to the properties of the photo file?

    Thanks very much for your response. Ctrl-S saved the keywords to the DNG file properties. However, my original question was wrong. I should have asked how to save the keywords assigned in Lightroom to the properties of a TIFF file. Ctrl-S in Lightroom does not seem to embed keywords assigned to a TIFF file. When I check the properties of a TIFF file in Windows Live Photo Gallery after I have assigned keywords in Lightroom, the keywords assigned in Lightroom do not appear as "tags." Do you have any additional suggestions?

  • Tags / Keywords PSE6 -- Bridge CS3 how???

    Hello,
    sorry to cause inconvenience to you but i can´t find an answer to my question here in the forum.
    I read a lot of similar threads, but no one answerd my problem BridgeCS3 <-> PSE6.
    What i have:
    Bridge CS3 / Photoshop CS3 / Photoshop Elements 6.0
    What i want to do:
    At this time i organize all my photos with the Organizer of PSE6 and put keywords
    with the Tags-function from PSE6 to my photos.
    Now i want to change to the bridge to organize my photos.
    What i need:
    Now i need a functionality to import all my keywords/tags from PSE6 into the bridge.
    What i have done until now:
    In PSE6-Organizer i export all my keywords to a file. The automatic generated file
    from PSE6 is named: stichwort.xml . I can´t change the format or name in PSE6 to write the Tags
    to a file.
    In the bridge i tried to import the "stichwort.xml"-File, but that doesnt work.. There are no structures
    and useable Keywords coming into the bridge.
    So... is it general possible to import the Tags/Structure form PSE6 into the BridgeCS3 ??
    And when... what´s my fault? Can you give me a hint?
    Thanks for help.
    Bye

    There was a post some time ago that I will try to recall - hopefully not too inaccurately. I have never used PSE so don't really know what you are trying to do.
    The way I remember it PSE uses some sort of a table for the keywords. Bridge does not, but embeds the information as metadata to each file. Apparently this is more of a standardized format for the data and can be used by other applications.
    For a clearer explanation on how the information is handled go to Bridge Help and type in metadata. It does say something about ability to export metadata so maybe that would work for you.
    Before you go to all that effort you might investigate how PSE Organizer may handle the data in the future. Can never tell - the next upgrade may change that feature also. Perhaps PSE forum?

  • Sharing PSE7 Organizer keywords with Bridge?

    I want to share my existing PSE7 Organizer keywords with Bridge. I searched the forums and found an some answers to use PSE7's "File/Write Keyword Tag and Properties Info to Photo" menu option. I did some tests with that option, and it appears to only do what I'll refer to as "additive writes," meaning it will add keywords in PSE7 Organizer for a particular photo, but it will not remove any keywords which are presently in the photo file but not in Organizer's informaton for the same photo file.
    I'm guessing this is the case because PSE7 Organizer cannot assume the keyboard already in the file originally came from Organizer itself, or that the user (regardless of where an existing keyword came from) wants to remove a keyword if it's not in Organizer for the same file. It would be nice if there were a preferences option which one could select such as "Replace all keywords when writing to file" so that a user like myself could make Organizer's keywords the main keywords.
    Does anyone happen to know if I understand this correctly, or is there a way to remove a PSE7 Organizer-written keyword from a file (based on its non-existence in PSE7 Organizer for the same file)?
    If there is no way around this, I'm wondering if it may be better to do things the Bridge-way (which seems more like the general standard) since it seems to always keep the current info in the file, so the state is always with the file itself. Even if some features are missing, it may be better than dealing with this sort of PSE7-only feature. Any comments on this would be great to hear.
    Thanks for any insight on this,
    Tom

    Okay, that makes sense on the Albums. I wasn't aware that Albums were ordered.
    I was using Bridge some more after my post yesterday, and I was seeing that with PSE7, both Albums and Keyword items seem more readily accessible regardless of location of the items (photo files) because there isn't an extensive file system search required since the DB provides a quick search (assuming first-searches and no pre-existing caching in Bridge).
    I started testing Collections with Bridge, and realized that it was sort-of doing that. This is another aspect of Bridge which is sort of a "db" aspect of Bridge in that it requires the browser to persist data seperate from the photo file. .
    What can be a little frustrating about any browser-persisted informaton (such as that for Collections) is to not find anything in the docs about how to ensure one gets a good backup of that info. PSE7 does a great job of providing a feature to do just that. Recall this is one thing I really liked about PSE7 when I was unaware of the benefits of Bridge's "minimalist db" approach (where a "db" in Bridge is anything persisted by itself such as Collections).
    The "how to" backup app-persisted information (aside from docs a user saves, where the user knows the location) is a must for any pro-am or pro person, if not an end user. People don't want information that is key to something they're building over time to be persisted in some mysterious unknown location. I couldn't find what I wanted in Bridge docs, so I did my own hunting, and found Bridge Collection information hiding in "%APPDATA%\Adobe\Bridge CS4\Collections" (i.e., c:\Users\<user_name>\Roaming\Adobe\Bridge CS4\Collections" on my laptop) in files named "<collection_name>.filelist". But even with that info, I, as a user, would still have to test to ensure I could get a backup good enough for disaster recovery / restoration. I'm a relatively technical user so I cannot imagine what "Dad" or "Mom" would do. This sort of thing is bothersome only because it's remedied with at least a small paragraph in the docs. What would it take to say "Backing Up Bridge Information: If you have a backup program which backs up the "%APPDATA%\Adobe\Bridge CS4" you will have all necessary data to restore the information that Bridge maintains. You must ensure you backup your photo files..." etc. etc. Without that, I have to do a bunch of hunting and testing. 
    All that said, I see how Collections, maintained by Bridge, offer some of that PSE7 power where you don't have to search for files in various locations to find what is already noted in a central Bridge file or "db" such as a Collection for which Bridge has a list of files in the Collection itself. (If Collections could contain other Collections, that would be a nice touch. I didn't see that ability.)
    What I still like about Bridge's approach is that while Albums don't exist, and while Collections are hierarchical, there's a feeling that Bridge is not taking things over where you are forced to use that app. It persists some items relating to its organizational features, but keeps the rest of the info right in the photo file. Still a nice balance. Another nice thing about this minimalist approach is that there's no importing per se. Everything is browseable/maintainable since the file system is the photo db.
    All that said, I can see where PSE7 does things for the non-power user such that they can just use, say, an Album, which has a familiar name, and behaves like an Album with ordering and whatnot. A user like me doesn't need that since I can use tools to create an Album like effect, so the Bridge approach wins since I can fend for myself in areas were I don't see PSE7 to hand hold.

  • Tired of color desat when opening in Bridge/Lightroom. HELP!

    I am going insane in my attempt to keep consistent color management through all areas. Everything was fine, color was great, prints were matched to calbration, monitor calibrated, and then....I rebooted the computer since I hadn't done so for a week, and when I restarted Bridge, and Lightroom (yields same results), the color immediately drains from the photos. Similar to the screenshot, however when I initially created this screenshot, Bridge was still accepting the color. Now, the desaturation exists in all Adobe programs. (PS CS5, camera raw, bridge , lightroom 3.  I feel like I'm going in circles here. I have no clue what could have changed with the reboot. One thing I have noticed is that in Window before a photo image is generated in a folder is shows as a paint pallette. And, when asked in Windows Color Management of the program I would like to use to install a profile, I am give Microsoft Color Management System (which to my understanding is designed for Vista or XP). Tried to delete the program but was denied. Not sure if that has anything to do with it either.
    If you have any insight and can help me stop the madness I would be so greatly appreciative!!
    Thanks!
    Windows7
    U2410 Dell Ultra Sharp Monitor
    Photoshop CS5 64-bit
    Adobe Lightroom 3
    Camera RAW
    Adobe Bridge
    NIVIDIA FX 580

    Hi Connie,
    Let me resume:
    Non  colormanaged applications (like windows explorer) shows your images  right, managed apps like LR and Bridge, which have different  cache folders, shows them desaturated, even the previewed NEF.
    Putting this  together, it can't a problem with the cache, harddisk, CF card. I mean, a  cache is a cache, and might needed to be updated from time to time, f.e.  when changing the monitor- or image profile. But I expect you always have done this.
    That's it - most of the rest (the tests done) provides unreliable information, sorry. I'm aware that to most of them you were forced by others, so don't take my following statements to personal.
    Nevertheless I believe what we see partitial is right: some of your images  are untagged (at least the PSD we see in one of the screenshots in here)
    Untagged images should look the same  in IE and Firefox unless you set Gfx.color management.mode to 1 and assign the monitor profile to FF. Per default CM in FF is enabled for tagged images only and by this acts like IE <V9 on untagged images
    Untagged sRGB should look oversaturated on wide-gamut monitors and browsers on which you can't apply a profile. Believe that is what you get.
    You asked me
    I'm confused which photos you viewed of mine that you found to be untagged?
    all the images you presented in threads in here are untagged ;-)
    Some might think different about that, but IMHO images always should have an embedded profile, even sRGB JPEGs used for web. You already get some hints on that in the other thread and the links to Ballard - even when his webdesign is a bit odd, its worth reading.
    I believe your issue is a combination of untagged images, a faulty monitor profile and maybe false handling.
    As implied above, personaly I can't trust any of the tests here, because they are (including the browser test I mentioned) not consistant done - I will tell you why.
    What you see next are three of the images you provided here, but stacked:
    #1 (RGB/8*)*
    here the second * indicates, that the image was altered (either bei assigning a colorspace or bei normal editing) after it was loaded and in a colorspace which is different from Photoshops working colorspace, which is indicated by the first *
    #2 (RGB/8*)
    indicates images colorspace is different from Photoshops working colorspace - that's fine when the working space is aRGB and the image f.e. sRGB
    #3 (RGB/8)
    no *, no # in here indicates it is in Photoshops working colorspace.
    (RGB/8#) at the top would mean it is untagged, but when when colormanagement was OFF in that moment, it also would read as (RGB/8) or (RGB/16) (without an # or *) at the top, but "untagged" in the info panel at the bottom, even when the image has an embedded profile...
    On the otherhand - and this is the important part - the Photoshop (import) settings you provided here, tells that your PS is at "preserve embedded profiles" BUT "ask when opening" at profile mismatches. By this you will be asked whenever an image profile mismatches the working colorspace.
    The latter should be unchecked, anyway.
    So what have you been doing, when you were asked for image #1 and #2? With this settings and since their colorprofiles are different from PS working space, you must have been asked and have assigned a profile different from working space or you haven't been asked (because images colorspace and the working space was the same) and you assigned a different profile initially later.
    Or you have changed settings again and again when taking those screenshots....
    When you say you see images as untagged in Bridge but in Photoshops info panel as "Adobe RGB (1998)" this can be, when a profile was added (assigned) after the image was imported to PS. Bridge will not know about that until you save the image.
    Will say: those of us trying to help, never know exactly what they are here looking at (maybe without realizing)
    Do we see a sRGB under an aRGB working space (RGB/8*) for #2? And #3, is this an aRGB image under an aRGB working space or a sRGB image under sRGB, (both would appear as RGB/8)? Or was the image untagged and colormanagement was off?
    Seems a bit chaotic, sorry.
    At least this is nothing on which I'ld be able to tell for sure what is going on.
    Next: the monitor  profile you sent to me, turns my U2410 dark and too much purple/reddish.
    Of  course there should be a differences (different monitor, different  environment light and my old eyes), but this is far to much - it hurt my eyes
    As  far I know, LR internal uses the Melissa color space (which is larger  than aRGB)  - I wonder what happens when RAW were processed via Meliassa  to aRGB with a too reddish monitor profile and are saved as untagged  aRGB....?
    I also wonder how LR can be configured to export to PSD without  they being tagged...?   Nevertheless, I was able to reproduce this once. For one of my PSDs the profile was removed, but at the moment I don't know how to reproduce that again.
    As said just make sure you images are tagged. But don't just apply a profile to those images already processed, when you don't know what really happend to them - it might get worse.
    Anyway.
    To solve your prob, you should forget about LR for  now and remove the monitor profile made with the Spyder, set the DELL  profile which comes with the CD and process images from scratch.
    Means  straight from NEF in one colorspace only -> via Photoshops ACR (output as aRGB and make sure aRGB is your  working space in PS), save them as PSD or TIFF and make sure they get tagged as aRGB. See if it makes a difference (color shift or not), when viewed  in Bridge.
    If there is no shift, start over with calibrating your monitor. Calibrating means setting the hardware right, by making sure the monitor was set to aRGB and brightness and contrast was adjusted, before you profilling it with the Spyder.
    If the problem still exists with this new profile and with images, which were processed by the above workflow and by the new conditions (make sure of that, the already processed images might be messed up) again let some one with an U2410 check the new profile.
    If its still have a huge red shift on another U2410, it might point to a hardware fault (either Monitor or Spyder)
    @MJOrts
    I notice that "Use Windows display calibration" is checked on in your
    screenshot. 
    AFAIK this setting means, that Windows is loading the LUT and not a third-party LUT-Loader, coming with the profiling device.
    Message was edited by: ablichter
    #1 (RGB/8*)*
    was edited - wasn't able to mark the wrong part by formating it <s>"striked"</s>, so I removed and corrected it

  • Raw File from Bridge, Lightroom, CS5 not show on Window 8.1 OS

    I recently bought a new computer with Window-8.1 OS.  Then I loaded CS5, Bridge & Lightroom on. 
    However, non of the program reads raw file.  Please advise what to do.  Thank you.
    James

    If photoshop, bridge or lightroom are old enough, it may not support your camera. A search on adobe's web site will give you a list a supported cameras for that version of software.
    If they are not supported, you have basically 2 options
    1)Upgrade your software
    2)download the free dng converter and convert your raw files to dng which can be opened by photoshop, camera raw, or lightroom.
    Another possiblity is the file it self is corrupted. Hopefully that is not the case.

  • Export and import "keywords" in bridge

    Is it possible to "move keywords and comments" from one collection of images (directory) to another on a different computer?
    We have a collection of images (about 1000 RAW files - about 50 GB) where a client have enclosed comments and keywords in Bridge on their copy of the collection. Is there som way to "transport" these comments and keywords form their "collection" to ours (without copying the collection once more)? The two "collections" are supposed to be identical except for these comments. Any ideas?

    What you could do it save the fields to a csv file, see..
    http://www.ps-scripts.com/bb/viewtopic.php?f=19&t=2365&sid=aacde2d6b388724ce1cb0ff447795f5 d
    Then input the data on your other machine, see...
    http://www.ps-scripts.com/bb/viewtopic.php?f=19&t=3463&sid=aacde2d6b388724ce1cb0ff447795f5 d

  • Keywords in Bridge CS5 on Mac OSX network issue?

    Is there any way for multiple workstations using OSX 10.6.3 to enter keywords using Bridge CS5 to photos residing on a server?  It appears that only one user may make changes or add keywords... the others are relegated to a read only status and cannot add or modify keywords.  If the file is duplicated on the server by another user, the original user is then denied access.  This is a huge issue for our office and our IT person has no clue.  Help please.

    This is a huge issue for our office and our IT person has no clue.  Help
    please.
    Look at this thread and the solution from the Image Archivist:
    http://forums.adobe.com/message/2571008#2571008
    And also see his blogspot:
    http://imagearchivist.blogspot.com/
    And his blog using Bridge to share images across a network from the archive
    in july 2009.
    Maybe this will help your IT person on the right path?

  • Keywords in Bridge CS5 & CS6 beta

    After I installed Photoshop CS6 beta and opened Bridge CS6 I noted that it had imported a copy of my keywords from Bridge CS5. 
    However when a new keyword is added in Bridge CS5 it is not added to Bridge CS6….  and new keywords added in Bridge CS6 are not added into Bridge CS5. 
    Is there a way to sync my keywords in the two versions of Bridge? 
    Also need to know what will happen when I install the final release version of Photoshop CS6.  Will it import the keywords from my Bridge CS5 or the beta CS6?

    Beleive CS5 and CS6 use different cache.  So you will probably have to trash the cache and let it rebuild to so new additons.
    Can use Tools/cache/purge cache for xxx folder

  • Any way to create a keyboard shortcut for keywords in Bridge CC?

    Just curious if there's any way to create a keyboard shortcut for "new keyword" and "new sub keyword" in Bridge CC?
    If not, that would be a welcome addition in any future Bridge update - being able to customize keyboard shortcuts or add your own the way you can in Premiere Pro CC.

    Steve,
    Not, as far as I know, directly, but the problem is with Aperture, not Keyboard Maestro.  Aperture has no command (afaik) for selecting the caption field of the Info Inspector.  Without a command, you will have to find another way to access it, or another way to accomplish what you want.
    You can specify the spot clicked by screen coordinates, so you cold use the Inspector HUD and the coordinates of the Caption field, as long as the Inspector HUD always pops up in the same location.
    Many dialog boxes allow the user to advance through the fields with the Tab key.  Unfortunately, the number of times you have to type "{Tab}" in order to get to a particular field depends on other interface elements (if the Control Bar is showing, add 2).  I don't know of a way to determine if the Control Bar is showing.
    You might find a work-around using a Metadata Preset and the Batch Change command.  Keyboard Maestro can easily pop up a dialog with a text field in which you can type what you want to go into Aperture's Caption field.
    The best thing to do is download the trial version and see if it meets your needs.  Keyboard Maestro is adept at creating macros based on keyboard input.  If the program does not provide keyboard equivalents, writing an effective macro becomes difficult.
    http://www.keyboardmaestro.com/main/
    The author provides exemplary documentation:
    http://wiki.keyboardmaestro.com/About_Keyboard_Maestro
    Lastly, for the use you cite, I simply show the Inspector if it's not showing (by typing "i"), change to the Info tab if it is not currently activated (by clicking, but note that opening the Inspector with the Info tab selected can be done with one command "View➞Inspector➞Info"), and then clicking in the Caption field, which is part of all of the Metadata Views I regularly use.
    HTH.  Perhaps one of our programming mavens will suggest something better.
    --Kirby.

  • Can I restore deleted keywords in Bridge CS5?

    I accidentally deleted a long string of keywords in Bridge and I don't even remember what they all were. Any way to get them back?

    Not that I know of.  HOWEVER, if you did not delete the keywords on the photos, when you visit a folder with those deleted keywords it will write them back to the list.  If they are itacalized, they are temporary, or right click on them and choose persistent.
    The filter tab should show you what keywords are the current folder.

Maybe you are looking for