Metadata into Master Image??

Hi,
I wonder if it is possible to save the keywords, metadata etc. back into the Master?
We have to send our Masters away quite often, but they all have to be keyworded etc.
Is this possible to apply that Information to the Master?
thanks

Hi,
I wonder if it is possible to save the keywords,
metadata etc. back into the Master?
We have to send our Masters away quite often, but
they all have to be keyworded etc.
Is this possible to apply that Information to the
Master?
thanks
Aperture's philosophy is that it never touches the master, ever - not even on export.
As a workaround you could use a utility to copy IPTC data from an exported version into the exported master. You can do that in batch so it would not take forever...

Similar Messages

  • Import image metadata into Indesign CS5 automatically

    Hi,
    I've been looking all over for this and I have found various bits and pieces of information, but nothing comprehensive enough for a beginner. Perhaps I am researching it wrong. Could you please point me to a complete and easy to understand source, or give me some tips and details regarding the process?
    I don't know if this makes a difference, but I am trying to export my pictures (there's quite a bit of them, so working in batches is preferable) into a sort of catalogue, and I'd like Indesign to pick up the metadata that was edited in Bridge.
    Thank you in advance.

    Metadata is still pretty arcane.  The form that Adobe uses, XMP, is designed for automated software manipulation, but the software hasn't reached the point-and-shoot stage.
    Now that forum-searching seems to have been fixed, searching for "metadata captions indesign" may turn up useful threads, such as this one for CS4, mentioning a script that can pull metadata from an image for use as a caption in an ID file.
    On a more arcane level, when exporting to PDF InDesign does pick up and pass on "object-level metadata" for continuous-tone images: selecting an object with Acrobat 9 Pro's Touch-up Object and then right-clicking will let you choose Show Metadata for the object: the individualized metadata survives, though seeing it takes some doing.
    Good luck!
    David

  • GPS Metadata for Managed Images Bug

    Alright this is really dumb. Aperture strips the GPS metadata for managed images on a version export, but does not for referenced files.
    It just took me 4 hours to figure that out, ug. Metadata is sacred! Always preserve it.

    My Aperture library uses managed masters.
    I too discovered that if I performed *version exports* of geotagged masters the exported images did not retain the GPS data. The problem was the same regardless of whether the masters were .jpgs or RAW files. (Geotagging was performed with Maperture and Maperture Pro; the bug symptoms are the same regardless of which tool was used.)
    Additionally, I discovered that if I performed *master exports*, then not only were the geotags retained in the exported files, but that +reimporting those same exports resulted in new masters whose versions would subsequently retain their geotags on version export+.
    synonym wrote:
    If you Relocate Masters... BEFORE you add GPS metadata using Maperture you don't lose any IPTC metadata. If you then Consolidate Masters... you can then apply GPS metadata to these images within your Aperture library and you will not lose IPTC or the GPS data on exporting the versions.
    If I'm reading this correctly it sounds like you can "scrub" your library of the problem by relocating masters and then consolidating them again, and that subsequently applied geotags (and by inference IPTC metadata) will be retained on new version exports. Did I get that right?
    However if you already have loads of images in your Aperture library that you have added GPS data to with Maperture and you also have loads of IPTC metadata on them and adjustments what do you do?
    I did a backup of the library at this point to a vault. I then restored the vault and GPS data and IPTC metadata was all retained and was also all retained on exporting versions!
    And if I'm reading the last sentence of your post correctly, it seems like the consistent behavior between our two situations is that if *images are brought into the library with geotags already in them* - in your case by library restoration and in my case by re-importation of previously geotagged masters - *then the geotags will be retained on subsequent master and version exports*.
    Is that a valid conclusion to draw? If so, it sounds like I could workaround the problem of geotags missing from my version exports by either A) relocating and then consolidating my masters, or B) by the three-step process of:
    1) geotagging my images,
    2) updating the vault, and then
    3) restoring my library from the vault.

  • Adding metadata to master

    I'm having difficulty adding metadata to my master files.  I'm currently using referenced images.
    In Aperture I will add keywords, a caption and geo data to an image and then select Metadata > Write IPTC Metadata to Master...
    I look at the master via finder and it shows that the file has been modified.  When I open the picture in Picasa or iphoto, the caption is updated, but there are no keywords and the geo data is missing.  If I export a version of the file, and then open it in Picasa, the caption and geo data are correct, but there are still no keywords added.
    Any suggestions on where I'm going wrong?
    Thanks

    You can set a whole batch of files to "TV Show," but bring them into iTunes first. This is as easy to selecting the batch and running any kind of plug-in on them.
    Videos all go to the Movies category by default, but that's only temporary. Right after you drop them into your library, find them under Recently Added or Movies. Select them all, and press Ctrl-I to Get Info. Change the video kind to "TV Show." Now all of these files will appear in the TV library, but of course you'll have to fill in the series name and season. Those can also be filled in as a batch.

  • How can i NOT include top level keyword in the metadata of an image?

    Hello,
    I want to know how can i NOT include top level keyword in the metadata of an image. I know there is an option for not applying a keyword to an exported image, but is there an option for not applying the top level keyword to the actual image?
    I have organized my geographical (by location) keywords like this:
    Places
    USA
    New York
    Miami
    Spain.
    If i add geographical keywords to all my images, all my images will have the keyword "Places", i dont think that it have any sence to have all your images with one keyword. How can i fix this? Any sugestion? i will appreciate it a lot any help or information that you could give me.
    Excuse my english, i know it is not good. I hope that you could understand me.
    Thanks,
    Marcelo :)

    Explicitly excluding a keyword only applies when "exporting". Unfortunately, there's currently no way to stop the keyword being written to the file when "Save Metadata to File" command is used. The natural reaction of users to this difference is to suggest that it is stupid. Nevertheless, there are good reasons why the difference exists:
    1. "Export" creates a new file whereas "Save Metadata to File" writes the metadata back into the existing file.
    2. There are very good reasons why certain keywords should not be written to file, and the example given in the OP is one. Saving metadata to file is more often used as means of backing up important image related metadata, independently of the catalog or allowing the metadata to be visible in other aplications. It would be rare that such a file would be shared with a third party, so the reason for not including certain keywords is less obvious. Actually, not including it can result in no end of confusion and grief. For example, if the top level (or any keyword) was excluded during the save metadata process then the other keywords would be orphaned when image is imported back into the catalog (e.g. buiding a new catalog).
    The development team are aware of the need, in some circumstances, to exclude certain keywords when save metadata command is used. How and when the issue is resolved, without adding even more confusion/complexity, is some way off.

  • Can I automate the writing of XMP metadata into JPEG and TIFF files?

    I have written an ASP.NET 3.5 website application on behalf of an annual international photographic competition. Entrants will be uploading digital photos in either JPEG or TIFF format. Ideally, I would write entrant identity and image title information into the XMP metadata for each image immediately after upload - but so far, I have failed to find any way to do this in ASP.NET.
    Thousands of images are involved, so I need to find a way to automate the metadata insertion, perhaps with some sort of script that uses a text file (extracted from the SQL Server database on my website) as the source of the metadata for a batch of images. Is this the sort of task that can be done by writing a script for Bridge CS3? Are there any scripts already in existence that I could use? I am a total beginner in this area.
    I use a Win XP PC, though I have a colleague who, I think, has CS3 on his Mac (running under the Leopard OS), so scripts for either platform might be usable.
    David

    You are the man X!
    Ok here is another version with a check for the dll.
    #target bridge 
       if( BridgeTalk.appName == "bridge" ) {
    addInfo = new MenuElement("command", "Update Entry Details", "at the end of Thumbnail");
    addInfo .onSelect = function () {
         main();
    function main(){
    var csv = File.openDialog("Please select CSV file.","CSV File:*.csv");
    if(csv != null){
    loadXMPScript();
    csv.open("r");
    while(!csv.eof){ 
       strInputLine = csv.readln();
       if (strInputLine.length > 3) {
          strInputLine = strInputLine.replace(/\\/g,'/');
       inputArray  = strInputLine.split(",");
       var csvFile = new File(inputArray[0]);
       var title = inputArray[1];
       var author = inputArray[2];
    if(!csvFile.exists) {
    alert(csvFile + " Does not exist"); //////////Check if file exists
    return;
    if(csvFile.exists){
    var file = new Thumbnail(csvFile);
    try{
    var xmpFile = new XMPFile(file.path, XMPConst.UNKNOWN,XMPConst.OPEN_FOR_UPDATE);
    }catch(e){
          alert("Problem opening xmp for update:-\r" + file.path +"\r" +e.message);
          return;
    try{
    var xmp = xmpFile.getXMP();
    }catch(e){
          alert("Problem opening xmp data:-\r"  + e.message);
          return;
    xmp.deleteProperty(XMPConst.NS_DC, "creator");
    xmp.deleteProperty(XMPConst.NS_DC, "title");
    try{
    xmp.appendArrayItem(XMPConst.NS_DC, "creator", author, 0,XMPConst.ARRAY_IS_ORDERED);
    xmp.appendArrayItem(XMPConst.NS_DC, "title", title, 0,XMPConst.ARRAY_IS_ORDERED);
    }catch(e){
          alert("Problem writing xmp data:-\r"  + e.message);
          return;
    if (xmpFile.canPutXMP(xmp)) {
    xmpFile.putXMP(xmp);
    }else{
    alert("Can not write new metadata to " + csvFile.spec); 
    xmpFile.closeFile(XMPConst.CLOSE_UPDATE_SAFELY);
    unloadXMPScript();
    function loadXMPScript()
       var results = new XMPLibMsg("XMPScript Library already loaded", 0, false);
       if (!ExternalObject.AdobeXMPScript)
          try
             ExternalObject.AdobeXMPScript = new ExternalObject('lib:AdobeXMPScript');    
             results.message = "XMPScript Library loaded";
          catch (e)
             alert("Could not load AdobeXMPScript \r" + e.message);
             results.message = "ERROR Loading AdobeXMPScript: " + e;
             results.line = e.line;
             results.error = true;
       return results;
    function unloadXMPScript()
       var results = new XMPLibMsg("XMPScript Library not loaded", 0, false);
       if( ExternalObject.AdobeXMPScript )
          try
             ExternalObject.AdobeXMPScript.unload();
             ExternalObject.AdobeXMPScript = undefined;
             results.message = "XMPScript Library successfully unloaded";
          catch (e)
             results.message = "ERROR unloading AdobeXMPScript: " + e;
             results.line = e.line;
             results.error = true;
       return results;
    function XMPLibMsg (inMessage, inLine, inError)
       this.message = inMessage;
       this.line = inLine;
       this.error = inError;

  • How do you embed/inject xmp metadata into a mpeg 2 video file?

    Im looking to add keywords and descriptions to original file (raw MPEG-2) and have the metadata stick when i go to the transcoding process and batch convert the orginal file to either a wmv and flash file. how can i achive this? what tools are available ? and or is this a custom job? any info and or programmers looking to test this im open to all the help i can get.

    Yeah I kind of figured that. I've been trying various ways of trying to batch inject metadata into video files and thought I would start with the master file but because of the limitations the raw digitized mpg 2 video file has. In that case I have yet to find a transcoding program that will batch out various formats and read a xmp side car file to inject the metadata into the outputted file (does anyone know if Adobe media encoder 4 can accomplish this where a xmp sidecar file is created then transcoding into a wmv and or flash file , curious if the metadata will stick and be read in the outputted file) In anycase  I may have find an alternative way and use my current Rhozet carbon coder transcoder program to try to inject an xml file during the batch transcoding process. If anyone has successfully accomplished this with injecting xmp metadata in a batch transcoding program please let me know. I've been exhausted searching for the solution this problem for a long time and I don’t want to wait till a mpeg 7 solution comes out.

  • Export Bridge Assets including metadata into searchable web gallery

    Hi,
    We have several thousand images that we have tagged with metadata in Adobe Bridge. We want to be able to export these images and their associated metadata into a searchable web gallery so that customers can search keywords or at the very least pick attributes in order to narrow down the image selection process.
    What software has the ability to do this?
    Thank you!
    -Mike

    Apologies.. my advice may have been wrong.. it is a while since I figured it out.. trying to remember what it was I did..you do have to shorten that file name.. but it may not be the caption you need to change. I suspect I may have selected all the images.. then gone to meta data batch change and done something under the custom button which then applied to all images.
    In my case I needed to get the web address for the gallery created from:
    http://homepage.mac.com/farish/Smartbins™%20Chewing%20Gum%20Bin%20and%20Cigarett e%20Bin%20Image%20Gallery/
    down to:
    http://homepage.mac.com/farish/Chewing%20Gum%20Bin%20Cigarette%20Bin/
    I did manage it but can't quite remember how I did it.
    I will keep playing and when I figure out what I did that worked will post again.
    The web gallery name you choose affects how Google sees the site as when you publish the web gallery - the web gallery name can pop up in Google
    It's quite difficult to figure out exactly what to do. If anyone else knows a definitive answer please advise!
    Rgds

  • How to import XMP-MP metadata into organizer

    I have a fairly large number of photos with face tag metadata.  Since Adobe is part of the working group that developed the XMP metadata standard, imagine my surprise to find out that Photoshop Elements 11 doesn't use it!
    Is there any external program you guys know about to import face tag metadata into the organizer?  I used Windows Photo Gallery to do the face tagging and it properly writes the metadata to the XMP fields.  Problem is the photoshop organizer doesn't read the XMP fields!  It's using it's own standard(?)
    We are talking thousands of photos here so re-tagging is just not an option.  Is there a way to get photoshop to import the tags and regions?
    Struggling User

    I think most of us who deal with large amounts of photos usually have a multi-application approach to things.  No one application does it all.  I crossed the 10,000 image point some time back and the thought of face tagging all that again makes me more than a little queasy!
    I looked at PSE 11's organizer and realized it was very close to what I want.  I'm going to use PSE for pixel editing anyway so it looks like an ideal one-size-fits-all application.  However, of course I now know PSE doesn't use tags in the same way as others.  So it's just a deal breaker plain and simple.
    Right now I use:
    Photo Gallery (formerly Window Live Photo Gallery) for organization and face tagging and subject tagging
    GeoSetter for location tagging by the way it recognizes the Microsoft face tag data so I can use the people tags to sort in that app too
    ExifTool for metadata manipulation where needed (camera data or other interesting info)Also note the ExifToolGUI (no longer maintained also recognizes the Microsoft face tag metadata)
    Photoshop Elements for pixel editing
    I use the face tags as keyword tags so you get a double benifit.  The big deal of course however is the face region tag.  Having a picture of many people and a separate list of keywords isn't helpful.  You only know that John Smith is in the photo somewhere but you don't know which person he is!  Like you said however, it's not important to everyone.
    I will keep researching this.  I'm betting someone has written an app to extract one set of data and make it available to another app.

  • Import Bridge CS4 metadata into LR3?

    Is it possible to import metadata into LR3 that I've created in Bridge CS4?
    Another thread here said it's possible, but there was no explanation on how to proceed.

    Yes it is possible.
    The "metadata shuttle" between Bridge and Lr is the XMP-file.
    ( As an aside: Strictly speaking LR writes metadata to xmp-file (side-car file) only in the case of Raw images, whereas in the case of JPGs, TIFFs, PSDs the metadata is written into the header of the file. I suspect that this is the same in Bridge. But in >Catalog Settings >Metadata tab the term "XMP" is used indiscriminately.)
    To import the metadata that was created in Bridge in Lr, do a <Read metadata from file> via >Metadata >Read Metadata from file (in the Library Module), or >Photo >Read metadata from file (in the Develop Module).
    Please be aware that by < read metadata from file> the complete set of metadata will be imported, including any develop steps you might have done in Bridge, and this will overwrite all metadata already done in Lr (including develop edits which are also metadata). I believe this will even be so in case you have done no develop steps in Bridge, i.e. any develop steps done in Lr will be overwritten with "0". <Read metadata from file> cannot be undone, and there will be a warning to that effect. A selective reading of metadata (for instance keywords only) is not possible.
    So you have to import the metadata from Bridge as a first step right after importing the photo in Lr, and before you do anything in Lr.
    The "metadata shuttle" works also from Lr to Bridge if you <Write metadata to file>.
    Color labels will be imported correctly only if the textual descriptions for the individual labels are identical in Bridge and in Lr.

  • Use Referenced Masters To Avoid Accidentally Deleting A Master Image File

    If you use Managed images it is possible to delete the master file accidentally.  If you delete versions of an image using File -> Delete Version and the version you are deleting is the last remaining version for that image, Aperture 3 will delete both the version and the master image.  If you subsequently empty Aperture Trash and then System Trash that master image file is gone forever.  In Aperture 3 there is no warning that you are about to delete a master image. 
    A workaround (although a weak workaround) is to use Referenced Image Masters.  Then when you delete the last version which includes the master image from Aperture, you can uncheck the box "Move referenced file to system trash." and no master image file will be deleted.  The downside to this workaround is that when you really want to delete a master image file, it must be done via Finder.
    The best solution would be for Apple to fix this bug so that when you select "Delete Version" it only deletes the version image and reverts to the master image.  That way the master image can only be delete via the command "Delete Master Image and All Versions."

    There is no bug there.
    I had some trouble wrapping my mind around the file-Master-Version-Image-(Preview) complex that flows, sand-like, through the entire working of Aperture.  (I like a thing to be represented by itself and itself alone, and to exist in one place and one place alone.  I was comfortable with the seeming precision of the location-based "file+path" metaphor for the existence of these virtual things.  Aperture quite cleverly moves beyond that.)  Two things helped me move forward:
    - understanding the difference between Projects and Albums, and
    - separating my Library into a storage area and an output area.
    Projects are, for me, storage containers.  (I have said elsewhere that the mis-naming of "Projects" is the single worst interface decision made in Aperture.)  They have a privileged relationship with your Images:  every Image must "live" in a Project, and "lives" in only one Project.  It may help you to think of "Image+Project{Path}" as functionaly equivalent, within the Aperture Library, to the file directory "file+path" mentioned above.
    Albums are, for me, output containers.  I create Albums every time I know I will output a set of Images.
    In practice, I work on Images in each.  In general, I develop my digital captures in the Project that holds them (and I rigorously stick to "One Project = One shoot"), I create Versions and add them to Albums as needed for output (they are automatically made the Album Pick), and I tweak them for output and then output them from Albums.
    You may be wondering (if you've read this far) -- "What has this got to do with deleting Masters?"  A lot.  Note the difference in the context-menu between a Version in a Project and a Version in an Album.  The menu for the Album contains two delete commands: "Delete Version", and "Remove from Album".  The Versions live in Projects, and only visit Albums.  As Terence correctly points out, if you delete the last Version, your expectation should be that you are deleting that Image from your Library.  My suggestion is that you adopt something similar to what I've set up, and delete Versions from ONLY Projects (never from Albums).  This way you will never unknowingly delete the last Version (because Images can be in only one Project, and if you delete the last Version from that Project you know you are expunging that Image from your Library).

  • Where Are My Missing Master Images?

    I keep my Aperture Library as a "managed" library rather than "referenced, so every master image is kept inside the Aperture Library icon.
    Today I decided to look inside my Aperture Library (by selecting Show Package Contents), and I can only find master images from the past five years. The "Master" folder contains folders for projects I've titled 2012, 2011, and back to 2008. None of the earlier images that I keep in Aperture, 2007 through 2003, appear in the "Master" folder in the Aperture Library, and there are no folders for 2007 and earlier.
    That is, if I look in Aperture Library -> Master -> I see folders for 2012, 2011, 2010, 2009 and 2008. But that's it!
    There are also no folders inside Preview for those earlier years, or inside Thumbnails.
    And yet...
    And yet when I'm in the Aperture application, I can Export any of the images, all the way back to 2003. So the master images are obviously available to Aperture somewhere. They exist. And I checked -- those earlier missing images not Referenced, they're Managed, just like the whole library.
    So where are they??
    I dug through other folders inside the Aperture Library package but didn't find a thing.
    Help!

    But I'm digging around inside the package and still puzzled -- images inside the folder Aperture Library.aplibrary -> Masters -> 2009 -> 06 -> 14 -> 20090614-214439/ were indeed shot on June 14, 2009. So it appears that those various level folder names reflect image creation date, not the import date.
    Joe,
    these various level folder names reflect what Aperture thinks are the import dates.
    The "Import Session" is one of the Aperture specific Metadata tags. You can display it in the Info/Metadata pane of the Inspector Panel, if you add it to one of the presets, and then you'll know, where to search, if you absolutely must to sleep well .
    You can also use this tag to search or to define a smart album. For example, the image below has been captured in 2003, but was imported in 2010, and will be found in a 2010 folder.
    Regards
    Léonie

  • Project management and multiple master images

    Anyone here making use of 2 or more projects with the same master image in each project?
    scenario is:
    project 1 "blah shoot" <-- contains all images from shoot
    project 2 "portfolio" <-- will contain some of the images from the shoot
    The problem im having at the moment is when i drag any master image from project 1 into project 2, it removes the master file from project 1
    Surely i can have multiple images in multiple projects?

    You can copy the master image to your portfolio by
    clicking and dragging with the option key held down.
    I don't know of a way to link these images so that
    changes in one are carried over to the other though.
    If someone does know, please let me know, it'd make
    my life easier...
    If you drag an image from one project into an album under another project, it will not move the master - it puts only that version in the album, linked back to changes made in the original project.
    if you export that project, the master that version is based on will be copied at that time and pushed out into the exported project. So if you export a project and then re-import you will no longer have a link but a copied master. To get around that you can manually copy the project with the album holding links out of the Aperture library to elsewhere to make backups or move a set of projects together,

  • Unavailable Master Images are present

    Trying to relocate masters to an external drive using Aperture 2.1. Project with many albums which I am relocating to folders with the same name as the album on an external drive. Most of the albums I was able to relocate. There are 4 where I get the "unavailable master images cannot be relocated" message. When I select and image to show in finder, it shows its location on my internal drive. I have rebuilt the library and still get the same message. I have gone to Manage referenced files and located all the images in the bottom window then click reconnect all. Still get the same message about unavailable masters. What am I missing?

    I am having the same problem. I had all my master images stored in one folder on an external 300gb hard drive. However, I noticed that in aperture, it said I had only 15,000 images while in the folder showed ~17,000 masters. What were these extra 2,000 images? I decided to try to separate these "unconnected" images from the real masters by relocating all my master images into another folder. All went well until I got the following warning:
    "Unavailable master images cannot be relocated. The selected master image is either offline or not found. Please reconnect it and try again."
    I was able to move most of the masters, but Aperture says I still have 3,009 masters in the original folder (which if I navigate to in the finder contains ~5,000 images). The strange thing is that if I right click on one of these images in aperture and select "show in finder" it finds them with no problem. It can't find them thought when trying to relocate.
    I have tried rebuilding the aperture library, manually moving the images into another folder and then attempting to relocate, and copying the masters to another hard disk and linking aperture to those masters. All with the same result.
    I am using Aperture 2.1.
    Any help here would be great.

  • View metadata near his image in a html file?

    Hi
    I am new to this board,
    I wanted to ask if there is a way to publish the metadata of an image, (or filtered metadata), into a html file, (for expample near the image).
    It want to publish photos with some of the metadata of it made readable on an easy way...
    Thank you in advance for looking at my problem
    Erwin

    Within Bridge you can select a batch of images and convert them to a Photoshop Web Photo Gallery.
    You can customize the page templates that Photoshop uses. I've not seen any documentation for metadata but some of the templates display caption, copyright, etc. Try searching or asking on the Photoshop forum.

Maybe you are looking for