-
All replies
-
Helpful answers
-
Jun 25, 2012 8:55 AM in response to dfoersterby William Lloyd,This has always worked for me (and I've done it often). I just checked on 3.3 and it works fine as well.
The specific setting you need to select when doing export as a project is "Copy originals into exported library." Do you have that checked?
-
Jun 25, 2012 9:21 AM in response to dfoersterby dfoerster,This is getting weird. Exporting to the local disk works fine (masters included). When I export to my external harddrive (ntfs formatted) with exactly the same settings the masters are not included in the export. This is also reflected in the filesize of the collection as displayed in the finder.
William, thanks for the hint. The setting doesn't make any difference for me, probably because I am using a managed collection.
-
Jun 25, 2012 9:27 AM in response to dfoersterby William Lloyd,★HelpfulNTFS formatted? Hmmm. Given OS X doesn't support writing to NTFS, perhaps there's an issue with MacFUSE or something? I wouldn't recommend doing that ;-)
-
Jun 25, 2012 9:33 AM in response to William Lloydby dfoerster,I am using the Paragon drivers for NTFS. The previews are written to the disk just fine so I don't see why the filesystem would be any issue.
-
Jun 25, 2012 9:48 AM in response to dfoersterby Frank Caggiano,★HelpfulWhile Aperture may work with non OS X formatted volumes the behavior is unpredictable. Could work for a while then stop working, parts of libraries mat seem ok while other parts aren't etc.
See Aperture: Use locally mounted Mac OS X Extended volumes for your Aperture library
-
Jun 26, 2012 2:29 AM in response to Frank Caggianoby dfoerster,Frank, thank you for posting that link. I am storing my entire collection on an NTFS formatted drive and wasn't aware of that limitation.
On the other hand that's pretty disappointing. I don't see why Aperture would require any special filesystem features. Apple really needs to work on interopability!