Which cameras save autofocus EXIF metadata

When I try and use the Show Focus Points overlay, it appears that Aperture does not have that information.  I find nothing in the manuals for my Sony Cameras about saving this EXIF data, and I was wondering if it is not saved, or if Aperture just does not understand it.

"Yes" seems to be safe answer.  But I want to emphasize that we still don't know whether the information
- is not recorded, or
- is recorded but not recognized by Aperture. 
You could fire up the app Sony includes with their cameras and see if displays the focus area used by the AF system.  You might be able to extract this and store it in Aperture as a custom metadata field (just as values -- you'll never get these to show as an overlay in Aperture).
My guess is the information is recorded in the "maker notes" section of the EXIF.  Aperture rarely (perhaps never) uses the maker notes.

Similar Messages

  • IPhoto geotags not save in EXIF metadata

    Why if I geotag a picture using iPhoto, that geotag won't be saved into the EXIF metadata? Exporting for example that picture in, say, Adobe Lightroom, or uploading it to Flickr won't show the location I picked in iPhoto, simply because that information is not stored in the EXIF metadata.
    Is it this behaviour what iPhoto is supposed to do? Or is it a bug? Conversely, if I geotag a picture in Lightroom, that geotag will be saved in the EXIF metadata, and correctly read by any other application

    iPhoto stores the location data in the edited version and does not write it into the original image file. To create a geocoded image file, export the edited version with the location data included:

  • How do i remove the exif metadata from my jpg file produced with a digital camera photo?

    How do i remove the exif metadata from my jpg file produced with a digital camera photo?

    The excellent and free utility Irfanview has the option to remove the EXIF data.
    Simply open and the file and do a Save, or Save As with the original name.
    Surprisingly, the default is to not keep the original EXIF data.

  • Lens Exif metadata worked for KM but no more for Sony cams

    Playing with the metadata panel in Aperture 2.1, I was surprised to see the information for the lens manufacturer/model for some shots I did with my old Konica-Minolta 5D DSLR.
    Sony took over the Konica-Minolta DSLR system about 2 years ago and as many others I have since moved to a Sony A100 body and recently to an A700 body.
    Using the very same lenses, that give me detailed lens Exif metadata with the old Konica-Minolta 5D, the metadata field is empty with Sony A100 and A700 files.
    A bit annoying, that the 4 years old Konica-Minolta 5D is supported in Aperture, while the follow up models from Sony are not.
    Hope this will be fixed in the next update.
    Peter

    Steve,
    you are probably right, that Sony is encoding the lens data in a somewhat non standard way.
    But as far as I know, in the EXIF of the Konica-Minolta files, this was done as well in a non standard way, by storing a binary lens code (at least I don't find any plaintext lens data in the image file, when I peek into it with a low level file-editor like Hexedit). As the lens information is displayed in clear text for the Konica-Minolta files within Aperture, Apple must have already integrated a lens database holding data for Konica-Minolta and Sony lenses. Interestingly even new Sony lenses like the Carl-Zeiss 16-80 lens show up, when used on an old Konica-Minolta DSLR.
    For me it looks like Sony might store the same lens-code now in a different proprietary EXIF field but Aperture is still looking into the old Konica-Minolta EXIF field, which is non existent or empty.
    So yes, Sony probably broke it, but there was enough time for Apple to fix it, especially as they have updated the lens database all the time. It is weired to add all recent Sony lenses to Aperture's lens database, but make the data only available, if you use the lenses on a 5 years old Konica-Minolta body.
    So I repeat my request for Apple to fix this in Aperture soon.
    Peter

  • Metering Mode - EXIF metadata

    Is there any correlation between the Metering Mode (a number) in the EXIF metadata and the actual mode used on cameras ?
    Not mentioned in forums, the manual, or an Aperture book i have...which means it must be obvious and every but me knows it...!
    I expect it may differ between manufacturers and possibly cameras. Does the camera drop a number into this field when the image is taken ? Looking for details on Canon EOS series (rebelxt, 20d & 5).
    eg for EOS 5
    1=CW
    2=spot
    3=evaluative....

    On my D60 the info is..
    3= Evaluative
    4= Partial
    5= CW
    Aperture doesn't read the EXIF as well as iView MP, I seem to loose a bit, flash fire/no fire, exposure comp, mode etc. iView manages to get it all.
    I love the ap though - it saves me hours, and keeps me organised!

  • How to synchronise metadata between Lightroom catalogue and exif metadata (e.g. Orientation and rating)?

    Hi there,
    i have some third-party tools that also read my original photos that I use in my workflow. That is especially my private synology cloud, from which I can watch my images in the browser and in mobile devices like my iPhone/iPad.
    i Ido not want to export a second copy of the pictures from Lightroom to be used by the other tools and still want to be able to synchronise the two most important values between these tools and Lightroom: orientation and rating.
    is there any way to store orientation and rating from lightroom in the original photo's exif data? vice versa is there a way to synchronise these values back from the exif metadata to Lightroom? Especially orientation is an issue, because I have older cameras that do not set the orientation tag and I have to orient them in Lightroom.
    rationale: I'd like to use web or mobile devices to rate pictures with my friends and family and do not to have everybody gather around my Lightroom PC.
    I don't want to be trapped in the adobe product family. Buying Lightroom-mobile is not an option as I don't accept public clouds and the pricing of it.
    Any hints?
    cheers,
    Meike

    Use the Metadata > Save Metadata To File command to write orientation and rating from the LR catalog back to the photo's metadata.  Or set the option Catalog Settings > Metadata > Automatically Write Changes Into XMP.
    If an external tool changes a photo's metadata, LR will display an indicator in the upper-right corner of its thumbnail in Library grid mode:
    You can tell LR to reread all the metadata from the file by doing Metadata > Read Metadata From File (this will replace all the metadata in the LR catalog, so beware).
    You can find all photos that have changed metadata in the file by using the Metadata Status column in Metadata browser of the Library Filter bar.

  • Lightroom Import: How to load Exif metadata description

    Exif schema contains a description tag, which I would like to populate as part of the process of importing images from camera. Would you please show me how that can be done. I cannot locate rhe correct property in the import dialog.

    Are you referring to the EXIF:ImageDescription field or the EXIF:UserComment field?  When LR imports an image, those fields get automatically imported into the LR catalog.  They appear in the Metadata panel on the right.   EXIF:ImageDescription will be displayed as "Caption" under the Default metadata set, and EXIF:UserComment will be displayed as "User Comment" under the EXIF metadata set.

  • Photoshop Bug? GPS exif metadata stripped out

    We recently discovered that ANY changes made in Photoshop CS4 stripped out our GPS exif metadata.  We also tried it in CS3 - same thing!  And by changes, this includes anything - changing IPTC, adjusting levels, etc.  It even happened when just opening, re- saving and closing the file in Photoshop.
    FYI:  We tested it with images exported from both Adobe Camera RAW (Canon files) and Phocus(Hasselblad), and the problem occurred with both.  We've also tried it with files from different cameras, which used different GPS brands altogether, therefore we can rule out:  the GPS units, camera (Canon 1Ds Mark II, Hasselblad H3D-39), and software used to convert RAWS (Phocus, Adobe Camera RAW, Lightroom).  We also tried different computers to make sure no preferences were corrupt on an individual machine, to rule that out.
    To make things even more complicated, we just discovered that even though we can no longer see the GPS info in Photoshop CS4, Adobe Bridge DOES see the GPS info!  But - none of our other softwares which normally recognize GPS can see the info (iView, Cumulus).
    Very, very frustrating.......HELP!
    Mac OS 10.5.6, PowerMac 2 x 2.66 GHz Dual-Core Intel Xenon, Photoshop CS4, Files exported to Prophoto RGB 16-bit TIFF) using both Lightroom and Phocus

    Addendum: Does anyone know how to add EXIF back into a file?  
    I assume this would be difficult, as EXIF is hard to remove, much less put back.
    Many of these files have already been worked on extensively, and re-importing and re-working is not a good option.
    We have already tried the following (did NOT work):
    1)  Exporting the XMP from the file BEFORE any changes are made (with GPS info still intact), and importing XMP to finished file (tried all 3 option settings)
    2)  Copy and pasting the finished file on top of the original (GPS intact file) and flattening, so that the finished file would take on the properties of the old, un-retouched file.  What's odd about this is that after flattening the file, saving, and looking at File Info - it appeared it had WORKED.  But when you close the file, and re-open, the GPS is gone again.

  • Updating EXIF metadata

    My new imports into Aperture 2 show some metadata which was not present in in 1.5. Specifically, the new version identifies lenses specifically and records camera serial numbers.
    I would like to get my imported library to show these metadata items too. The info must be in the raw file, but doesn't show in the Aperture 2 metadata. I assume this means that the metadata is parsed at import and then not touched again.
    Does anyone know a way of forcing Aperture to update the metadata from raw files to take advantage of software improvements?

    I am disappointed to see that a bunch of EXIF metadata is still not imported correctly from my EOS 1D Mk 3 - ie metering mode, exposure mode and white balance are still only represented by numbers and not their actual selection title.
    Is this my error are there any other EOS1D Mk3 users out there experiencing the same issue?
    Dingah

  • Quickly retrieve Exif metadata

    I've got a script for Photoshop CC 2014 that makes some exposure value (EV) calculations based on Exif metadata in camera raw files and then adjusts the image exposure to the target EV.  I know that this information is quickly available in Bridge, but when I try to get the metadata in Photoshop, I have to use the Document.open() command, and that opens the file (which takes a long time) instead of just grabbing the Exif metadata.  I can get it quickly in a Bridge script, but I'm having a hard time embedding that stuff in a Photoshop-targeted script (the BridgeTalk stuff is a bit confusing to me, or it isn't working on my computer).
    I've also attempted to use "bridge.executeScript()", but the bridge object apparently is not available to scripts targeting Photoshop (or else something is messed up with my installation).  Bridge is available in bridge-targeted scripts only.
    Here's how it's working in Photoshop scripting (I include only the relevant part).
    for (var nfile = nstart; nfile < nstop; nfile++){
    var Name = File(testListing[nfile]).name.replace(/\.[^\.]+$/, '');
    var file = File(testListing[nfile].path + "/" + Name + ".JPG");
    if (file.exists){
    app.open(file);
    else{
    app.open(testListing[nfile]);
    var DocInfo = app.activeDocument.info;
    var docRef = app.activeDocument
    EV[nfile] = CalcEV (DocInfo, BaseISO);
    app.activeDocument.close(SaveOptions.DONOTSAVECHANGES);
    (FYI, I use the jpeg file if it's there because Photoshop reads the exif from that file more quickly than it does from the raw file)
    Here's how it's working in Bridge scripting:
    firstfile = '7A7A5842.CR2';
    lastfile = '7A7A5843.CR2';
    var ExifProperty = 'exif:DateTimeOriginal';
    var ExifNamespace = 'http://ns.adobe.com/exif/1.0/';
    app.document.deselectAll();
    app.document.selectAll();
    var myThumbs = app.document.getSelection("cr2");
    var fstart = -999;
    var fend = -999;
    for (var n = 0; n < myThumbs.length; n++){
        if (myThumbs[n].name == firstfile) fstart = n;
        if (myThumbs[n].name == lastfile) fend = n;
    var NumFiles = myThumbs.length;
    var fileThumbs = myThumbs.slice(fstart,fend);
    flen = fend-fstart+1;
    var EVarray = new Array(flen);
    for (var n = 0; n < fileThumbs.length; n++){
        var md = fileThumbs[n].metadata;
        ISO = md.read(ExifNamespace,'exif:ISOSpeedRatings');
        SS_string = md.read(ExifNamespace,'exif:ExposureTime');
        var test = SS_string.split("/");
        ShutterSpeed = test[0]/test[1];
        var Aperture_string = md.read(ExifNamespace,'exif:FNumber');
        if (Aperture_string == '') {
            var Aperture = Number(1.4); // assume Samyang set at f1.4
        else {
            var test = Aperture_string.split("/");
            Aperture = test[0]/test[1];
        var ISOadjust = Number(1.);
        EVarray[n] = Math.log(Math.pow(Aperture,2)/(ShutterSpeed*ISOadjust))/Math.LN2;
        $.writeln('ISO ',ISO,' SS ',SS,' Av ',Aperture, ' EV=',EVarray[n]);
    app.document.deselectAll();
    "Done...";

    Hi Bob, if Bridge was closed then no info would be returned, so make sure Bridge is running.
    Here is the script with slight modifications showing how to process the data in the main function.
    #target photoshop;
    main();
    function main(){
    var bt = new BridgeTalk();
    cameraRawData = new Object();
    bt.target = "bridge";
    bt.body = "var ftn = " + getInfoFromBridge.toSource() + "; ftn();";
    bt.onResult = function( returnedData ) {  cameraRawData = eval( returnedData.body );}
    bt.onError = function( sumatWentWrong ) {  alert(sumatWentWrong.body);}
    bt.send(10);
    //If you get here all should be well and you can process the data
    for(var a = 0; a< cameraRawData.Name.length; a++){
    $.writeln(cameraRawData.Name[a] + " - " + cameraRawData.FNumber[a]);
    function getInfoFromBridge(){
    /* all comments in this function must be in this format ! */
    Info = {}; /* new Object, can be written as var Info = new Object(); */
    /* create new arrays within the object */
    Info.Name = new Array();
    Info.FNumber = new Array();
    /* change folder to */
    app.document.thumbnail = Folder("~/desktop/test");
    app.document.deselectAll();
    /*get  a list of all cr2 documents */
    var thumbs = app.document.getSelection("cr2");
    for(var a in thumbs){
    var t = new Thumbnail(thumbs[a]);   
    var md = t.synchronousMetadata;
    /*populate the arrays */
    Info.Name.push(thumbs[a].name);
    Info.FNumber.push(md.read( "http://ns.adobe.com/exif/1.0/","exif:FNumber"));
    return Info.toSource();

  • Problem with EXIF metadata reading

    Hi everyone
    I'm trying to read EXIF metadata information. Here is my code snippet:
    uchar* exifData;
    Handle exifDataHandle = filterRecord->handleProcs->newProc(100);
    propSuite->getPropertyProc('8BIM', propEXIFData, 0, nil, &exifDataHandle);
    exifData = (uchar*)(*exifDataHandle);
    filterRecord->handleProcs->disposeProc(exifDataHandle);
    After this code executed I have exifData size only 4 bytes, but as I now minimum valid EXIF data should be 6 bytes. Maybe I did something wrong?
    Thanks for help.
    Regards

    Dennis Knutson wrote:
    The old serpdrv was eliminated with 7.0 unless you manually copied the VIs and driver from an older version.
    Well perhaps it was I who converted in labview 5.1. I remember that the old system was quite clumsy written. It was very slow. But with a few trick it could be speeded up. Just by using refnums like in files and a simple C program for baud rate setting. I could use stable 115200 tranfer rates back in labview 3.1 
    Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
    (Sorry no Labview "brag list" so far)

  • Can I change exif metadata with AIR?

    Hi.
    I am autor of a simple application that changes exif information in scanned images. I am looking for a way of re-implementing the application in a more cross platform way than it is today and found AIR interresting.
    However, I can not find any API for accessing image metadata in the documentation..
    Is altering the exif metadata possible with AIR (without having to implement all the "libexif-like" suff myself?)
    Thanks
    /sverrir

    There is nothing built in to AIR - but you may wish to look at
    http://code.google.com/p/as3corelib/
    which is an opensource AS3 library which includes some image metadata manipulation routines.
    You may also wish to make a feature request here
    http://ideas.adobe.com/air
    so that we will consider this addition in a future addition of the AIR runtime.
    Hope that helps.
    Chris Thilgen
    AIR Engineering

  • Canon EOS-1D X vs. EOS-5D MK III - Which camera do you prefer ?

    Canon has two excellent full frame cameras occupying their higher end of the DSLR market. They are the EOS-1D X and the EOS-5D MK III. I have been using Canon equipment for about 25 years now and started with the EOS-1 series when it first came out in 1989 and the EOS-5 series when it first appeared on the market in 2005.
    I am a Wildlife and Travel photographer and have used both cameras extensively out in the field. The two questions I get asked the most are, which is a better camera and which one do you prefer? My answers are always the same two questions, what type of photography are you shooting and how much do you want to spend? This analysis will not have photos, charts and graphs and assumes the reader is already familiar with Canon equipment. It will get straight to the point on my opinion of the two cameras from the viewpoint of a photographer out on photo shoots.
    First, let us compare the major specs of the two cameras, EOS-1D X vs. EOS-5D MK III :
    Sensor Resolution :  18.1 MP  vs.  22.3 MP
    ISO Sensitivity :  100 - 204800  vs. 100 - 102400
    Processors :  Dual DIGIC 5+ and 1 DIGIC 4  vs.  One DIGIC 5+
    Recording Media :  Two CF slots  vs.  One CF and One SD slot
    Viewfinder :  0.76X  vs.  0.71X
    Burst Rate :  14 fps  vs.  6 fps
    Autofocus :  61-AF points  vs.  61-AF points
    Cycle Count :  400,000  vs.  150,000
    DxOMark Sensor Score :  Overall - 82  vs.  81
    Low Light Performance :  2786 ISO  vs.  2293 ISO
    Weight and Dimension :  6.2 x 6.4 x 3.3 @ 3.37 lbs  vs.  6.0 x 4.6 x 3.0 @ 2.1 lbs.
    List price :  $6,799  vs.  $3,499
    Both cameras are excellent performers out in the field. The 1D X is completely weather sealed and can stand up to most conditions. AF is lighting fast and high ISO performance are superb and as you can see from the specifications above, they are almost evenly matched in performance but the EOS-1D X edges out the EOS-5D MK III in Sensor Score, Low Light Performance, burst rate and cycle count, while the 5D MK III has an edge in pixel count. So, going back to the original questions posed to me :
    Q : Which is a better camera ?
    A : They are both great cameras in their own right. If you are primarily a Wildlife photographer, the obvious choice is the EOS-1D X. It comes through for me under extreme conditions with little fuss and stands up to harsh use but if you are into Portrait and Landscape photography, the higher megapixel count in the 5D MK III will allow a slightly more robust cropping and lends itself to very big photo prints.
    Q : Which camera do you prefer ?
    A : If I were strictly a Landscape or Portrait photographer, I will pick the EOS-5D MK III. A photographer shooting both Wildlife and Landscape/Travel will do better with the EOS-1D X.
    Q : Which camera is the better value (price dependent) ?
    A : Without a doubt, I have picked the EOS-5D MK III as the best value in full frame DSLR camera on the market today.
    Q : Which is a better camera, overall ?
    A : Without another doubt, the EOS-1D X excels in all categories but at a price some may not want to, or cannot afford. Good, used ones will appear on the market eventually.
    Q : Which camera would you buy (price dependent) ?
    A : The Canon EOS-1D X represents the pinnacle of Canon's camera technology. There is really no substitute to shoot with the latest 1D. The performance, feel and ruggedness of the camera exudes confidence. I have not bought the EOS-5D MK III because I still own the original 5D and I have the EOS-1Ds MK III as well. So, there is little room in my equipment bag for another full frame camera but the price of the 5D MK III is now down to $2,600 on eBay (limited quantity) and is tempting me by the day.
    For full details on each camera's specifications, visit the Canon USA website. For a detailed analysis on the EOS-1D X, visit this page. You can visit MichaelDanielHo.com to see photos taken with all the cameras.

    I went through the same drill - came down to $3300 extra for 14 vs 6 fps.  I bought the 5DIII.

  • Why is there missing EXIF metadata after merging aperture libraries?

    I had an old library and a new library. All metadata and files were fine in the respective libraries.
    After importing one into the other, I am missing all EXIF metadata like Camera, Lens, ISO, Aperture, Focal Length.
    Anyone experience this problem or have any ideas?

    FIXED!
    I waited this long for a simple fix:
    Select all the photos, control-click on a photo and select Update from Original.

  • EXIF metadata SubjectDistance bug

    Hi.
    I've just discovered that Lightromm 3.3 RC1 and earlier wrongly displays SubjectDistance EXIF tag if camera focus distance was set to infinity.
    According to EXIF specification SubjectDistance tag is stored using two numbers - nominator and denominator.
    And if numerator is zero - subject distance should be reported as unknown and if it is set to 0xFFFFFFFF - subject distance is infinity.
    But instead of displaying infinity - lightroom shown numeric value.
    For example in my photo I have nominator equal to 0xFFFFFFFF and denominator equal to 1000.
    Lightroom reports distance of 4.29 Mm (million of meters 0xFFFFFFFF/1000 = 4294967295/1000 = 4.29*10^6), which is numerically right, but should be reported as infinity.

    Still not fixed in LR 3.4
    Lightroom reports infinity only if the resulting value of SubjectDistance is 0xFFFFFFFF (numerator is 0xFFFFFFFF and denominator is 1).
    With any other denominator value it reports numerical value, which is wrong.
    EXIF 2.2 specification says:
    SubjectDistance
    The distance to the subject, given in meters. Note that if the numerator of the recorded value is FFFFFFFF.H,Infinity shall be indicated; and if the numerator is 0, Distance unknown shall be indicated.
    So infinity SHOULD be reported with any denominator value, if numerator is 0xFFFFFFFF, but Lightroom reports that SubjectDistance is infinity only if denominator is equal to 1.

Maybe you are looking for

  • How to use create_sort_rule? Please help!

    Hi Experts,           I want to craete a sort rule for a field. There is a method called create_sort_rule in IF_SALV_WD_SORT interface. It has following parameters: inputs: SORT_ORDER : LIKE IF_SALV_WD_C_SORT=>SORT_ORDER  DEFAULT  IF_SALV_WD_C_SORT=>

  • Selecting line in Illustrator

    Is there a way to open a file and select every line in it at the same time no matter what the line weight or color is?

  • Photoshop cs6 has detected problem with gpu

    my photoshop says it detected a problem with the GPU..However, my card seems to be working perfectly with other software and games..Should i be worried or jus ignored the message? thank you in advance

  • Creating Issue against Reservation

    Dear SAP Gurus, While creating Goods Issue against the reservation the system through the message M7 181 only O Quantity availble. But if i see the actual quantity through MMBE the system shows the actual quantity which is there in PRD server. Can an

  • Can't Sync after IOS5 Upgrade - Device driver software was not successfully installed

    I upgraded to OS5 and now can't sync. I have tried uninstalling and reinstalling iTunes and rebooting and still get an error saying Apple Mobile Device USB Driver was not successfully installed. This is on Windows7 64bit Anyone else had this problem?