dennisfox
Level 1 (0 points)

Q: Aperture doesn't generate xml file

Aperture 3.5.1 is supposed to generate an ApertureDatabase.xml file to use images in third-party software. I have the Preference set to generate this file whenever Aperture closes, but my main Aperture library does not generate this file. I tried setting the Preference to Always and that also doesn't work.

 

My smaller, newer Aperture libraries do generate the xml file as they're supposed to. Only the older, much larger Aperture library does not generate it. This same problem exists on my iMac as well as on a copy of the library on my MacBook Air.

 

I created a new Aperture library that did generate the xml file. Then I imported the older library into it (took forever) but this library no longer generated the xml file.

 

Can I get Aperture to do what it's supposed to do?

iMac (21.5-inch Mid 2011), OS X Mavericks (10.9.2)

Posted on May 23, 2014 3:59 PM

Close
dennisfox

Q: Aperture doesn't generate xml file

  • All replies
  • Helpful answers

  • by William Lloyd,

    William Lloyd William Lloyd May 24, 2014 1:59 PM in response to dennisfox
    Level 7 (21,148 points)
    May 24, 2014 1:59 PM in response to dennisfox

    This behavior changed with Aperture 3.5:

     

    http://support.apple.com/kb/HT200060

  • by dennisfox,

    dennisfox dennisfox May 24, 2014 2:47 PM in response to William Lloyd
    Level 1 (0 points)
    May 24, 2014 2:47 PM in response to William Lloyd

    Yes, but according to the link you provided you can still set Aperture to generate the xml file when needed for third-party software. I'm using FotoMagico, which needs that xml file to locate the Aperture library.

     

    As noted, my newer/smaller Aperture libraries do generate the xml file but my larger library does not. That's the one I need to get working right.

  • by dennisfox,

    dennisfox dennisfox May 27, 2014 8:58 AM in response to dennisfox
    Level 1 (0 points)
    May 27, 2014 8:58 AM in response to dennisfox

    Has anyone else had this problem or am I on my own?

  • by j!e!t!s!,

    j!e!t!s! j!e!t!s! May 29, 2014 12:08 PM in response to dennisfox
    Level 1 (15 points)
    May 29, 2014 12:08 PM in response to dennisfox

    I am having the same problem; regardless of the Aperture preferences setting, no .XML file is created! I am trying to use Hazel to automatically import photos into Aperture, and Hazel needs this nonexistent file...

  • by Frank Caggiano,

    Frank Caggiano Frank Caggiano May 29, 2014 12:14 PM in response to dennisfox
    Level 7 (25,782 points)
    May 29, 2014 12:14 PM in response to dennisfox

    What is the setting for Share XML with other applications in both the library that is generating the XML file and the one that is not.

     

    Note Share XML with other applications is one of the few settings in the Preference file that is set on a per library basis. Most settings in the Preference file apply to all libraries.

  • by j!e!t!s!,

    j!e!t!s! j!e!t!s! May 29, 2014 12:37 PM in response to Frank Caggiano
    Level 1 (15 points)
    May 29, 2014 12:37 PM in response to Frank Caggiano

    That setting is (and has been) set to "Always.' (I am not sure whether you were asking me or dennisfox.)

  • by dennisfox,

    dennisfox dennisfox May 29, 2014 12:41 PM in response to j!e!t!s!
    Level 1 (0 points)
    May 29, 2014 12:41 PM in response to j!e!t!s!

    I've tried both Always and When Closing Aperture - it made no difference.

     

    However, I've now fixed the problem. I exported my large, old Aperture library as a new Aperture library. This took about 7 hours. But when I opened the new library, made some adjustments, and closed it again, it now created the xml file. So my particular problem is solved. Maybe there's a particular problem with older libraries, so starting from scratch could be the solution.

  • by Frank Caggiano,

    Frank Caggiano Frank Caggiano May 29, 2014 12:47 PM in response to j!e!t!s!
    Level 7 (25,782 points)
    May 29, 2014 12:47 PM in response to j!e!t!s!

    I was asking the OP, it is usually best to start your own thread becuse, as this case shows, posting to another's thread can cause confusion.

     

    You are looking at the preferences when the library in question is opened, correct? As I wrote this  is one (if not the only) preference that is set on a per library basis. If you look at it while a different library is opened you might not be seeing the correct setting.

     

    You could try the steps shown in Aperture 3: Troubleshooting Basics, that is always a good place to start.

     

    Having said that, and while not having the XML file can be a problem, I don;t understand why Hazel would need the XML file to import into Aperture. Aperture is responsible for writing the XML file and it does that to reflect the state of the library.

     

    If you are looking for a simple way to import into Aperture you should look at Automator. A simple one or two action workflow does it.

     

    regards

  • by Frank Caggiano,

    Frank Caggiano Frank Caggiano May 29, 2014 12:50 PM in response to dennisfox
    Level 7 (25,782 points)
    May 29, 2014 12:50 PM in response to dennisfox

    All my older libraries started out with the share xml preference set to never when I upgraded them. But setting it to either of the two sharing positions caused Aperture to begin generating the XML file.

     

    Did you try a library repair before you did  the export of the library? It would be interesting to know if that would have worked.

     

    Anyway glad you found a workaround.

     

    regards

  • by dennisfox,

    dennisfox dennisfox May 29, 2014 12:52 PM in response to Frank Caggiano
    Level 1 (0 points)
    May 29, 2014 12:52 PM in response to Frank Caggiano

    I don't know how Hazel works, but my problem was with FotoMagico. FM uses the Aperture xml file to figure out which Aperture library to open up. Since my library had no xml FM couldn't see the images. I've now fixed that problem. Along the way I did do a bunch of the basic troubleshooting steps but they made no difference. Only exporting the library worked.

  • by dennisfox,

    dennisfox dennisfox May 29, 2014 1:29 PM in response to Frank Caggiano
    Level 1 (0 points)
    May 29, 2014 1:29 PM in response to Frank Caggiano

    I think I did try that earlier on and it made no difference. I kinda lost track along the way....

     

    Thanks for responding~