Aperture Image metadata

Hi I am looking for assistance with the following.
1. In aperture 2, I was able to notate the name of the image that I was working on, the fstop, shutter speed, ISO etc underneath the filmstrip. I could set that in Aperture preferences. In aperture 3, that feature has disappeared.
How do I set it? As it stands right now, in film strip view, I just see the image with no name or meta data associated.
2. When i mousover an image, I would like to see the aforementioned metadata.
Hope I am making sense.
Thanks.

1. In aperture 2, I was able to notate the name of the image that I was working on, the fstop, shutter speed, ISO etc underneath the filmstrip. I could set that in Aperture preferences. In aperture 3, that feature has disappeared. How do I set it? As it stands right now, in film strip view, I just see the image with no name or meta data associated.
Just like in Ap v2. Use the U/Y shortcuts to turn the metadata display on or off, depending on which area of the screen you're interested in. (U for the browser/filmstrip, Y for the viewer.)
2. When i mousover an image, I would like to see the aforementioned metadata.
This time it's T that you use. I don't recall if that was also in Ap v2.
You really want to take a quick read of the [Displaying Metadata with Your Images|http://documentation.apple.com/en/aperture/usermanual/chapter11_section2.html] section of the user manual. That will give you the full story.
Regards,
Gary

Similar Messages

  • Muse image metadata and global caption styling

    When will Muse be able to import image metadata and perform global caption styling with accurate positioning for lightboxes and slideshows?

    I've done some testing.
    if images are uploaded to the Facebook Wall, the Comments field that Aperture presents before uploading the image becomes the Description field on Facebook.
    however, if the images are uploaded to a known Facebook Album, the Version Name becomes the Description.
    both of these situations are not logical. in the case of uploading to the Wall, 'Comments' should probably be 'Description'. I'll report them to Apple's bugreport.
    images seem to be scaled down to fit within 2048x2048 pixels.

  • Aperture looses metadata

    I just noticed that after running an image through dnoise, Aperture looses almost all the metadata. Should this be happening? Is there a way to stop it?

    Hi Tony. DNoise is a plug-in, no? Aperture creates copies of images (file format is set in Prefs), and sends them to the plug-in, which then sends them back after changing the file. In essence the plug-in is a completely different application than Aperture. Aperture has many metadata which are not supported by other applications, and some applications don't support the full range of standard image metadata.
    One work-around is to copy all the metadata of the original and paste it into the image after it is returned from DNoise. There are no complete solutions for a workflow based on Aperture which includes plug-ins, afaik.

  • Weird behavior in opening Aperture images in Photoshop

    I have found a lot of really weird behavior when opening Aperture images in an external editor (in my case, Photoshop, so I'll use PS to refer to it):
    1) If the master image is opened in PS, a new version is created when the file is opened, not saved. So quitting PS without saving leaves you with a new version of the file, regardless of whether you actually saved any changes or not.
    2) If a version (not the master) is opened in PS, a new version is not created, either on open, or on save. So in other words, changes to that version in PS when saved overwrite that version, and the previous condition of that version is lost (with respect to versioning).
    3) If multiple versions of the same image are opened simultaneously in PS, there doesn't seem to be a way to tell the difference between them in PS, except for visually (possibly meta-data, but I haven't checked that, nor would I want to be forced to). The file names of all versions are exactly the same.
    I'm looking for feedback from anyone out there who can explain why this isn't completely quacky version control. I've been using version control almost my entire career (as a software programmer) and here's how I have seen almost invariably version control work:
    1) New versions of files are always created upon commit, i.e. saving of the file, not on opening a file. (Do not confuse this with working copies, think about what is present in the repository).
    2) Opening / editing any file version is never destructive. Any change to that file version that is saved (committed) results in a new version, not an overwrite to the same version.
    Aperture's interface basically has combined what traditional version management has represented separately, that being the client and repository views of a project. They are showing all versions of a file simultaneously. This is fine, but I'm really not liking the fact that some changes create new versions, other changes overwrite versions, and one case, merely opening the file creates a new version, whether there are any changes saved or not. In addition, when working with multiple versions in the editor, the file name and/or interface doesn't give any indication of what version you are working with. Easy to say that's the fault of the external editor, but I disagree -- all external editors are going to work with filenames, so Aperture should produce a unique namespace for any file version so that any external tool will be able to distinguish (visually) one file from another.
    Is this completely wacky version management, or is it just me?
    Brad
    Powerbook G4-1.33GHz-17" / Powermac G4-1.4GHz   Mac OS X (10.4.2)   PB: 1GB RAM, Radeon 9600-64MB / PM: 1.25GB RAM, Radeon 9000Pro-128MB

    Hi Bradley,
    Due to the way I personally use Photoshop, I want Aperture to behave as it does.
    That's because, with Photoshop, I use layers extensively. Any edits I do (levels, curves, saturation, sharpening) I do on layers. I can delete the layers at any time (or select to show or hide them). Because of this, I actually WANT Aperture to behave the way it does. Once I've done a bunch of edits in Photoshop, if I select again to edit that file in the external editor, I want to work on that specific file (to add another layer, or change one). I don't want another duplicate. I tinkered with this over the weekend, and it worked very nicely for me.
    Perhaps you work differently from within Photoshop? Do you ever use layers? If I were to have a bunch of Photoshop "versions," each with 5 layers, I'd have like 5 GB of "versions" for my original 8 MB RAW file, due to the size of PSD files. Yuck

  • Update image metadata programatically

    Hi
    I developed a plugin, which changes exif information of the image (using a third party program). Is there a way to inform Lightroom programatically to refresh image metadata? Right now I have to right-click on the folder and choose "Synchronize Folder...".

    There's at least one ODBC driver for SQLLite http://www.ch-werner.de/sqliteodbc/, and maybe command line access to the database too
    But there's nothing directly through Lightroom, and you won't be able to code Lightroom to refresh EXIF data. There is no coding mechanism to write to EXIF fields or to refresh the image (ie sadly you can't automate Metadata > Read Metadata).
    If you write directly to the SQL while LR is open, the best you can expect is that the EXIF will use updated data from the database when you next click on that image in Library. However, you are likely to encounter database locking problems  and stand a good chance of corrupting the database. Abandon all hope, ye who enter here?

  • Reading Image Metadata..

    Hi,
    I am converting some PHP pages to JSP. There is an image gallery page where images are being displayed and also the comment and Author names is displayed under that image.Those things are set as image metadata.
    The code for doing this in PHP looks like....
    $exif = exif_read_data($full_file_path, 0, true);
    foreach ($exif as $key => $section)
                                            foreach ($section as $name => $val)
    echo $section['Comments'];
    echo $section['Author'];
    How can I achieve this in java i.e. how can I read author and comment metadata fields using java....
    Thanks & Regards
    Shailesh

    http://www.drewnoakes.com/code/exif/

  • Retreiving image metadata

    Can anyone point me on how to retreive image metadata from an image... I was looking into the possibility of using JAI but could not find a clear answer.... If some one could post a link or point me in the correct direction...
    Thanks in advance....
    Sharad R.

    What type of meta data, what type of files?
    You might want to look at:
    http://groups.google.com/groups?q=IIOImage+bufferedimage&hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=2e027e56.0301172122.12504427%40posting.google.com&rnum=3
    - K

  • Image metadata is not retained(stripped) in lightbox slideshow widget

    How is this corrected

    Can someone at Adobe please confirm that there is no reading of the image metadata.  I thought it was limiting that it was only the caption field available.  I am stunned if this is the case that no metadata is being read.  I am working on a photo web site and got to the point of importing photos with the 'captions' checked.  Huge surprise.  It is hard to believe that something as fundamental as basic metadata fields (caption, title, filename, copyright) isn't pulled with the image and available as needed.  C'mon, you are the company that has Photoshop and Lightroom.  Do you guys talk to the other teams?
    I was looking at Muse galleries as an alternative to the LR web module for 2 reasons:  one is flexibility in layout, and the other is speed, since the LR gallery export cranks along at a glacial pace to the point of being almost unusable.  And this is the LR4 upgrade; much slower than LR3.  See the LR threads on this if you're interested.  Still waiting for that fix.
    The thought of manually entering caption info to a dozen galleries, each with 20 or 30 images, is nonsense.  This makes Muse a non-starter for photo galleries.  This is basic capability.  Adobe should be embarrassed that LR4 doesn't do what it should in this regard, and that the feature needed don't even exist in Muse.  Everyone expects a few bugs in the early days of a new software, but not missing essential, fundamental features to make web galleries useful. 
    Rant now over and I will happily apologize if the metada fields are, indeed, available.  Please explain how.  Thanks.

  • Image Metadata Editor

    I have been looking for inserting descriptions into my pictures. Unfortunately, there isn't any option to edit Metadata in File Explorers (I tried Thunar and Nautilus). I wouldn't like to have a photo gallery software just to do that, and, by the way, I couldn't find any of those that allows me to edit metadata in a straight-forward way. I have to navigate through a lot of menus in order to do that.
    Basically, I was looking for a plugin or other software that enhanced the "Image" tab on Thunar, so I could see and edit all file metadata there. Honestly, I don't know how do you guys keep your photo albums organized without this feature.

    I've found Shotwell pretty straightforward to edit tags. However, I personally also use feh + dmenu + a script I found somewhere to view and edit metadata. The latter method I find quite speedy when I've imported a bunch of photos. The script is
    image-metadata.sh:
    #!/bin/bash
    if [ $# -lt 2 ]
    then
    echo -e usage: "$0 <action> <filename>\n actions: edit-comment, edit-tags"
    exit -1
    fi
    action=$1
    file=$2
    if [ "$action" == "edit-comment" ]
    then
    commentText=$(echo | dmenu -t "$(exiv2 -Pt -g Exif.Photo.UserComment $file)")
    if [ $? -ne 1 ] # not aborted
    then
    if [ -z "$commentText" ]
    then
    exiv2 -M"del Exif.Photo.UserComment" $file
    else
    exiv2 -M"set Exif.Photo.UserComment $commentText" $file
    fi
    fi
    fi
    if [ "$action" == "edit-tags" ]
    then
    exiv2 -Pt -g Iptc.Application2.Keywords $file > /tmp/._image_keywords.txt
    selection=$(exiv2 -Pt -g Iptc.Application2.Keywords $file | dmenu -sb "#000" -nf "#aaa" -nb "#222" -sf "#509ba6" -fn 'Deja Vu Sans Mono-14:bold' -l 10)
    if [ -n "$selection" ]
    then
    exiv2 -M "del Iptc.Application2.Keywords" $file
    while read keyword
    do
    if [ "$selection" != "$keyword" ]
    then
    exiv2 -M "add Iptc.Application2.Keywords String $keyword" $file
    else
    deleted=true
    fi
    done < /tmp/._image_keywords.txt
    if [ -z $deleted ]
    then
    exiv2 -M "add Iptc.Application2.Keywords String $selection" $file
    fi
    fi
    rm /tmp/._image_keywords.txt
    fi
    if [ "$action" == "show" ]
    then
    comment=$(exiv2 -Pt -g Exif.Photo.UserComment $file)
    exiv2 -Pt -g Iptc.Application2.Keywords $file > /tmp/._image_keywords.txt
    echo -n Comment: $comment, "Keywords: "
    first=true
    while read keyword
    do
    if [ $first == "false" ]
    then
    echo -n ", "
    fi
    echo -n $keyword
    first="false"
    done < /tmp/._image_keywords.txt
    echo
    rm /tmp/._image_keywords.txt
    fi
    It requires exiv2, iptc, and dmenu. (Also ttf-dejavu, but you can edit out that font choice ) The script is not mine; unfortunately, I cannot remember where I found it.
    Then in .config/feh/themes, put
    tag --action2 ";/path/to/image-metadata.sh edit-comment %f" --action1 ";/path/to/image-metadata.sh edit-tags %f" --info "/path/to/image-metadata.sh show %f"
    Browse pictures with "feh -Ttag *.jpg" for instance, then press 1 to edit tags, press 2 to edit comments.

  • How do I edit image metadata?

    What I would like to be able to do is something like:
      tell application "Image Events"
      tell pic
        make new metadata tag with properties {name:"creation", value:cr}
      end tell
      end tell
    Only, sips/Image Events doesn't support setting most image metadata. Any suggestions as to how to approach this problem?

    Thanks. Lightroom 2.4, unfortunately, isn't very scriptable. This is ironic, since the program itself relies on Lua for its interface functionality. I will probably, eventually, manage to compile Exempi and the Python XMP Toolkit and do the job that way.
    Refs:
      [Exempi|http://libopenraw.freedesktop.org/wiki/Exempi]
      [Python XMP Toolkit|http://www.spacetelescope.org/projects/python-xmp-toolkit/docs/index.ht ml]

  • Aperture images with iLife

    I know you can access Aperture images in iLife, but it doesn't let you access the versions that are so carefully edited. Does anyone know if this is possible without exporting versions as JPEGs and then reimporting? Along the same lines, sometimes I just want the images I rate 5 stars to show up in iLife, but it always displays all the images in the project. Am I missing something?

    but it doesn't let you access the versions that are so carefully edited.
    Yes it does. You just need to make sure you've created previews of the edited versions. I've turned off automatic preview generation and just use a hotkey for the Generate Previews option.
    sometimes I just want the images I rate 5 stars to show up in iLife, but it always displays all the images in the project. Am I missing something?
    you can't filter out images from the Media Browser (iLife) but you can create a smart album in Aperture that only shows five star images, then use that to browse only those images in iLife apps.
    hope this helps!

  • Aperture image to external editor is SLOW

    Wondering if anyone else is having an issue with opening their images up using their "external editor" option in Aperture.
    Mine is set to Photoshop, which I'm sure many of you have. But it takes upwards of a minute for the Aperture image to duplicate itself and then open up in PS. It triples the time of my workflow -- which is a pain when I need to edit dozens of images in PS.
    Anyone have any suggestions? My computer is brand-new and quite fast. But perhaps there's a logical answer that I have yet to discover.
    Thanks.

    How much RAM do you have? You'll want 2 GB to do what you want.
    There are a few things going on here:
    1) Photoshop is a large application... it takes a while to load on any hardware
    2) Photoshop is not yet a universal application. It runs in Rosetta, which is an emulation layer. This makes it slower (probably 2-3x slower than on a PowerPC; so your MacBook running Photoshop at current is probably about as fast as an 800 MHz PowerBook).
    3) Rosetta uses lots of RAM as well. So Photoshop in Rosetta while you're using Aperture will really tax the machine.
    I'd recommend you run nothing else on the machine at all but Aperture and Photoshop. Quit mail, quit safari, quit anything but those two applications. Your life will get better when Photoshop CS3 comes out (March/April) and is universal. Until then, yeah, it's going to be a little on the slow side.

  • Aperture image-control compared with Photoshop?

    I'm looking to get Aperture 2. I've been using iPhoto as a library, and Photoshop to control\doctor images. How does the Aperture image-control compare with Photoshop's? I'm not thinking so much here about fancy plug-ins, just basic, but subtle, color, contrast, cropping controls ... especially dealing with the highlights and shadows.
    Any info from a user would be most appreciated,
    Thanks,
    Ben

    Same problem here...
    It started recently so I think some update create the problem.

  • Aperture Images on External Drive/Screensaver Can't Find

    Hi all,
    I've searched the discussions and haven't been able to find threads addressing my specific question.  I can't get my MacBook Pro (running OS x10.6/Snow Leopard) to use my Aperture Library for my screensaver.  My entire Aperture library (currently about 50,000 images) is on an external hard drive - am wondering if this is the issue.  When I try to add the file to the screensaver picture options, I find my external HD, but the Aperture Library is greyed out.
    I have already tried the proposed remedies around weeding out weird dates and removing the timestamp file/setting the iLife folder to "read only."  I'm not interested in exporting projects or files, in part because I don't want two sets of things hanging around taking up space - I just want it to randomly choose Aperture images to display on the screen.  Another suggested work around was importing the images into iPhoto - but, again, I do not want multiple sets of these images.  Can it really be the case that I can't point the screensaver to images housed on an external drive??
    I'm new to Macs in the last 6 months and mostly thrilled with the change - but this process particular was WAY easier on my PC.
    Thanks for any advice.

    Hi,
    iTunes is trying to find your tracks on your hard drive, not those in the cloud.
    I would suggest that you create a second blank iTunes library on your computer. Sign into iTunes &amp; match, run match and when completed your music in the cloud will be shown and you will be able to stream the music to your computer.
    Jim

  • Can Time Capsule host an Aperture image library efficiently?

    In our household, we have several MacBook Pros with SSD drives, which don't have a lot of storage space. Since we take a lot of high-resolution pictures in .RAW format (app. ~25 MB per file), it would be nice if we could store all of our pictures remotely on the Time Capsule, and access the image library from our laptops, without needing to copy the files to our local harddrives.
    So, is it possible to use Time Capsule as the only storage device for our Aperture image library, in a way that we can open and work with the library remotely (wirelessly) through Aperture on several Macs?
    I am guessing that this is possibly by simply sharing the files, but there are a few things that I am concerned about, such as:
    Will my images files/Aperture library get corrupted/damaged when a computer looses connection to the Time Capstule in the midst of editing?
    What will happen if several users attempt to access/modify several images on the Time Capsule at the same time?
    Will you get good performance from Aperture with a very large, remote image library?
    I have also considered getting an Mac mini with OS X Lion Server to do the same job, but setting it up a bit differently. Possibly setting up a Git repository for the images, but I would much prefer a simpler solution, which is why I'm thinking about doing this with a Time Capsule (using it as a "NAS" of sorts).
    Thanks in advance for any help, advice and suggestions.

    Of course I found this right after posting my questions...
    Also, it is strongly recommended that the Aperture library be stored on a locally mounted hard drive. Storing the Aperture library on a network share can also lead to poor performance, data corruption, or data loss.
    So I guess using the Time Capsule is out of the question, but I would still be interested in hearing from you guys if you have any good suggestions on how to work with a large image library in Aperture remotely through the network, if at all possible.

Maybe you are looking for