Aperture 3 Exporting Projects / Individual Library Files?

So my typical backup procedure in Ap2 and below was to export project files and back those up on two external hard drives. I do not use reference files, but rather let everything import into the aperture library file.
so. . .
Now in Aperture 3 I go to backup a project and there's no option anymore to export projects, only "Libraries". I've always considered a "Library" to be the entirety of the files stored in Aperture, but this is something new. . . Is exporting these smaller Library files from Ap3 the same as exporting project files from Ap2? The file size of the exported "library" file seems consistent with the size of the project.
I haven't tried re-importing any of these new exported library files, but should I assume that these things will behave the same way as projects did in previous versions? i.e., is this still a viable backup methodology?
If not I'd hate to have to just export masters and lose all the metadata/adjustments I rely on aperture for.
Thanks,
msg

The line between libraries and projects has just been blurred a little giving the user more flexibility. Now you can open the exported project as a stand alone library or import it to another library as a project. (note that the "Import Project" command is now "Import Project/Library") IMHO your back up plan just got better.
DLS

Similar Messages

  • "Project or Library file is corrupt" when trying to open XControl

    This is not a question, this is an account of my learning experience that I hope saves you from throwing your monitor through the wall.
    When trying to open an XControl, I received the following error: "Project or Library file is corrupt"
    Knowing Projects/Classes/XControls are all XML files, I opened the XControl using Notepad++ to see what was going on. The file structure is somewhat intuitive, and you'll be able to recognize many components of your library.
    I used a binary search approach to find the offending XML by deleting all of the virtual folders, then seeing if the XControl would open. It did, meaning the headers of the XML were fine. Then I took the original file again, and deleted half the virtual folders to see if it would open, and it did not, meaning the offending XML was in a virtual folder I had not deleted that round. I took the original file, and deleted the other half of virtual folders, and it opened. I took the original file, and deleted only one virtual folder, and it opened. Aha! that virtual folder had only 5 items, and I knew one of the items must be the culprit.
    Anyway, it only took about 10 minutes to narrow it down to an item that had a duplicate entry, two lines that were exactly the same:
    After I deleted the duplicate item, the XControl opened up just fine! No data loss, no corruption.
    How did the item get duplicated? Beats me. Could have been the product of a crash, some of my notorious renaming shenanigans, who knows.
    Lessons learned:
    Version Control (Source Code Control) is a hero, as usual.
    Try poking around with the XML if you get corrupt libraries - it may be an easy fix, but your mileage may vary.
    Don't even think about #2 unless you have #1 "under control"
    Action Item for Applications Engineer: could you point this error to the Owning Developer? I would suggest this type of an error fail more gracefully, or at least with more information. Possibly, this type of error could self-correct silently since it's so easy to diagnose? Watching the library tank due to a benign issue nearly cost me a monitor and a monitor-sized area worth of sheetrock damage.  (  )
    a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

    I cannot find the result about this topic.
    So I recreate a new project file
    Hope there is better solution for this problem
    thank you all
    QIA
    http://www.vitst.com
    Virry Test & Control
    LabVIEW Certified Developer

  • How to fix "Project or Library file is corrupt"

    Last Time I close the my project, then I want to reopen it, but popup a window "Project or Library file is corrupt"
    Can this corrupt project file can be fix?
    Because It contain too much information of this project.
    By the way, the project file size is 1.4M
    and I use LabVIEW 8.2.1 and WinXP SP3
    Hope somebody can give the answer, and thank you very much.
    Qia
    http://www.vitst.com
    Virry Test & Control
    LabVIEW Certified Developer

    I cannot find the result about this topic.
    So I recreate a new project file
    Hope there is better solution for this problem
    thank you all
    QIA
    http://www.vitst.com
    Virry Test & Control
    LabVIEW Certified Developer

  • Swapped hard drives, but now Aperture does not recognize library file

    I just swapped out my MBP hard drive for a larger one. I used SuperDuper to restore the small HD to the new, larger one from a third Firewire disk.
    Everything else is working fine, except that Aperture says that "The selected master image is either offline or not found. Please reconnect it and try again." every time I try to do anything meaningful with any file in my library.
    I have:
    -Repaired permissions on the new HD with Disk Utility
    -Tried several times moving the library file around to various places, telling Aperture where to find it each time, and restarting Aperture. Aperture finds the images okay, but I can't really do anything with them, as I get the above error message.
    -Renamed my new HD, going through the Aperture Prefs, and re-specifying where the library lives, and then repeating the process with the HD named yet again.
    Nothing seems to work for me. What else can I try?

    1. Are you using referenced or managed Masters?
    2. If using referenced Masters, have you tried reconnecting them via File>Manage Referenced Files...? What happens if you right-click on a thumbnails and pick 'Show in Finder'?
    3. If using managed Masters, have you done a Spotlight search inside the Library package (right-click on it in the Finder and choose 'Show Package Contents') to see if the master files are still in there?
    Moving the Library and/or renaming drives isn't going to help without finding out exactly where Aperture thinks the files should be.
    Ian

  • Need help exporting multiple individual PDF files out of Indesign CC

    I work for a monthly publication and we send our files to the press at the end of the month. There are around 190+ pages that need to be exported as individual PDF's and each PDF needs to be labled as their correct page number. Since we often are backed up against the wall at our deadline, we really need a way to export all these files at one time. Is there a way to export multiple PDF files at one time in Indesign CC?

    You could script InDesign to export each page as individual PDF with specific export presets and labeled with correct page number.
    But you could also use Acrobat Pro for this task (sorry for the certainly wrong translation of the Acrobat UI – I use a german version ...):
    Export the whole publication as 1 PDF file (pp. 1-190).
    Open it in Acrobat Pro and choose »Tools › Extract Pages«.
    Type 1 to 190 and check the box »extract pages as single pages«, choose the location where to extract to and acrobat automatically numbers your new PDFs sequentially from 1 to x. (Caution: it doesn’t take the correct page number, but numbers sequentially, so it is important to have a PDF from pp. 1-190 in the correct order.)
    So with this (as mentioned – sorry for German ):
    You’ll get this:
    Tobias

  • QT Pro 7.6 image sequencing aperture exports - only reads first file

    I'm exporting versions (jpg) of files that are originally Nikon raw (NEF) format.
    I'm testing with a bunch of images that were grabbed using the camera's continuous mode - want to make sure the system works before doing any real playing with time lapse.
    I have a folder with the images - all named image01.jpg, image02.jpg etc etc. No other files in the folder.
    Open QT Pro 7.6 - choose Open Image Sequence and select the first image.
    It asks for the frames per second.
    Whatever i pick - it creates a single frame movie with the first image in the set.
    I've tested with two different exports - same issue.
    Any hints?

    OK - tried this.
    For a short test - I have 22 files.
    -rw-r--r-- 1 chris staff 4428188 May 1 23:58 1.jpg
    -rw-r--r-- 1 chris staff 4634772 May 1 23:58 2.jpg
    -rw-r--r-- 1 chris staff 4451476 May 1 23:58 3.jpg
    -rw-r--r-- 1 chris staff 4564699 May 1 23:59 4.jpg
    -rw-r--r-- 1 chris staff 4450224 May 1 23:59 5.jpg
    -rw-r--r-- 1 chris staff 4344569 May 1 23:59 6.jpg
    -rw-r--r-- 1 chris staff 4637089 May 1 23:59 7.jpg
    -rw-r--r-- 1 chris staff 4143277 May 1 23:59 8.jpg
    -rw-r--r-- 1 chris staff 4144009 May 2 00:00 9.jpg
    -rw-r--r-- 1 chris staff 4311011 May 2 00:00 10.jpg
    -rw-r--r-- 1 chris staff 4054440 May 2 00:01 11.jpg
    -rw-r--r-- 1 chris staff 4020426 May 2 00:01 12.jpg
    -rw-r--r-- 1 chris staff 4382219 May 2 00:01 13.jpg
    -rw-r--r-- 1 chris staff 4315001 May 2 00:02 14.jpg
    -rw-r--r-- 1 chris staff 4084161 May 2 00:02 15.jpg
    -rw-r--r-- 1 chris staff 3772054 May 2 00:02 16.jpg
    -rw-r--r-- 1 chris staff 3363054 May 2 00:03 17.jpg
    -rw-r--r-- 1 chris staff 3392872 May 2 00:03 18.jpg
    -rw-r--r-- 1 chris staff 2956213 May 2 00:03 19.jpg
    -rw-r--r-- 1 chris staff 3063359 May 2 00:03 20.jpg
    -rw-r--r-- 1 chris staff 2728311 May 2 00:04 21.jpg
    -rw-r--r-- 1 chris staff 2877868 May 2 00:04 22.jpg
    Now - when they were called image01, image02 etc I got a 1sec movie with only the first image.
    Now - with these names - I get a movie of the correct duration (so - for example - 2 frames a sec yields an 11 sec movie) but with only the first shot shown (in other words I get to see the first jpg for 11 secs in the 2/s example.
    The file command tells me that they are "JPEG image data, JFIF standard 1.01"

  • Where to download individual library files?

    Recently, I installed the UT99 dedicated server package on my Arch system. Everything went smoothly up until the point of actually launching the server. Seems the server needed a couple of library files that aren't on my system. The missing files were libX11.so.6 and libXext.so.6; a web search confirmed these are X11 files, and I don't use X on my system (headless file server & local game server).
    My solution was to fire up Knoppix, mount my hard drive, and copy Knoppix's libX11 and libXext files into the proper location. That solved my problem, and everything's fine with UT.
    I just wanted to know if this was a silly way to obtain the two files? I searched for a download on google to no avail. Is there some central source for these types of files that I can use in the future if a similar problem crops up?
    Thanks in advance.

    I had a small feeling it's about Unreal Tournament, but I've never seen 99, only UT2004. Oh, 99 is the version before 2004... never thought of that.. although on the computer I'm on right now, not even UT99 works.
    MEfreak wrote:
    IceRAM wrote:Assuming you are missing some libraries, the best thing to do is find the package they belong, make a PKGBUILD for it, compile it, and install using pacman.
    Do you mean make a PKGBUILD to install only the missing libraries, or the entire program which owns the libraries? Sorry, I'm not yet familiar with PKGBUILD's in Arch  :oops:
    Well, I wasn't aware you didn't have any kind of X installed (xorg/Xfree). I did a brief check before and indeed they belong to xorg (my system).
    # locate libX11.so.6
    /usr/X11R6/lib/libX11.so.6
    /usr/X11R6/lib/libX11.so.6.2
    # pacman -Qo /usr/X11R6/lib/libX11.so.6
    /usr/X11R6/lib/libX11.so.6 is owned by xorg 11R6.8.0-3
    Same for the other one.
    About your question about the PKGBUILD: no, I wouldn't recommend splitting a package and building only 2 files out of it. It's better to (build &) install the full package, or you'll mess up your entire system (mostly because of the dependencies).
    In your case, maybe it would have been better to
    # pacman -Sy xorg
    to get the latest libraries. They're the latest version (or almost the latest since 6.8.1 has just been released) and they are i686 (+optimizations) compiled (as the rest of your ArchLinux system). It might offer you better performance & stability.
    (if you run that now, with your manually installed libs, you'll end up with 2 conflicts. Instead of the previous command, run pacman -Syf xorg).

  • Exporting project as audio file (wav)?

    This may sound like a stupid question but i'm new to logic. I'm trying to export the project as an audio wav file to post on the net but am a little confused how its done. The project contains apple loops - can these be exported with the rest of the project?
    Thanks

    Look up "Bounce"...
    This will create a stereo mix of your song, in any format you choose, be it .wav, AIFF, AAC,, mp3, etc...

  • Problem with Export Project as New Library

    Getting some behavior from Aperture that I do not understand.
    I am running Aperture 3.5.1 on OSX 10.9.1 on both a MacPro and a MacBookPro(Retina). 
    Both machines are believed to be completely up-to-date software-wise (no indication in App store that software updates are available.  i don't know how else to look.).
    I imported (Nikon D800) raw images from an SD card to MacBookPro Aperture Library (which contains few images), performed adjustments (and "shared" some with my SmugMug account).
    Then I selected the Project that contained my images, chose File, Export, Project as New Library (in order to move the adjusted images to my MacPro, where my "real" Aperture Library resides).  (first time i have attempted such a workflow).  I selected all 3 options (Copy originals . . ., Copy previews . . ., Show alert) and clicked Export Library.
    I copied the resulting file to my MacPro.  After choosing File, Import, Library (in Aperture on the MacPro), I see it "Merging", and then the project in question appears in the Library on the MacPro.
    The problem is that each image has a message at the top of the Adjustments pane:  "This photo was adjusted using an earlier version of Apple's RAW processing", and they all come into the receiving library with no adjustments, and no previews - not even the built-in preview that a raw file should carry (the images show in the viewer as _really_ flat, gray - very strange, i have never seen this appearance before, though I routeinely use raw format).
    Trying to troubleshoot, I went back to the MacBookPro and closed Aperture, then double-clicked the Library on the desktop that had resulted from the export process (containing only one project).
    Same situation.  All of the images think they were processed on older raw processor (even though this library is being opened on the same computer that did the processing).
    Any ideas?  Is this a bug, or have I misunderstood the point of exporting Projects?

    There have been two problems, reported, when exporting projects as library:
    In earlier versions of Aperture the exported library did not include all images, if images had been imported from Photo Stream. I cannot reproduce this bug any longer with Aperture 3.5.1.
    The export could go wrong, if the aperture library needed repairing.
    Have you tried the Aperture Library First Aid Tools,to fix a possible library curruption?
    See this link:  Aperture 3 User Manual: Repairing and Rebuilding Your Aperture Library
    Before trying to rebuild, make sure, your backup of your Aperture library is current and in a working condition.
    I see a progress bar and the .exporting library is created in the desired location.
    Finally I decided to watch a project closely as it was being exported as a library and I noticed that the file size jumps up an down. I'm not an expert on how export works, but it would appear that each exported photo is overwriting the previous one.
    What is the desired location? Are you exporting to your internal system drive or to an external drive? If external, how is the drive formatted?  Such overwriting of files could be caused by incompatible filesystems creating conflicting pathnames. Make sure, the destination is a filesystem formatted MacOS X Extended (Journaled).
    -- Léonie

  • Export Project

    Exported projects have all pictures under original Name. If I need exported project with " Version Name" - how to set-up export? Thank you !

    Ian
    I do export Project with renamed pictures according my scheme of Library. Exported Project into library of Laptop, create previews and than delete Masters - so my "Portable Library" contain just previews.
    Exporting projects due to a fact that this way I have saved also Ratings, given in Main Library.
    (before I exported just Versions, but this was without Rating).
    My "Portable Library" is just to work on road - once some publishers need an offer, or working on reports, articles with options to select Pictures. My Library is over 50.000 pictures, so no way to hold all
    in Laptop.

  • When I use Export Project to New Library in Aperture does it create a copy of the images in the new Library?

    I am going through my only library now and trying to better organize everything.  I am grouping my images into projects by year then cleaning up each year.  As I finish a year I use the Export to New Library option to create a library for each year.  My question is when I do this and I tell it to Consolidate Masters into exported library does it create copies of the images in the new library as well as leaving a copy in the original library?  My goal once I get this completed is to delete the original library but I certainly don't want to lose any of my images.  Just looking at file sizes for the libraries I can see that the main library never gets smaller and the new libraries don't really seem large enough to contain everything.
    Thanks.

    To be honest a 6 year old machine with 4gb of memory and 300gb of disk running Lion and Aperture  is not going to give you the greatest performance no matter how you split the library.
    You're going to need more disk, What's your backup procedure now? The best performance will be had by getting an external disk putting the masters on it as referenced and having the library on the internal drive.
    More memory would be nice but a 6 year old iMac, I think, is maxed out at 4. You'll need to keep other programs running to a minimum when you're working with Aperture.
    How much free space is on the internal drive? That will be an issue also. If even with the masters relocated to an external drive cause the internal drive to fill up you'll need to move the library off the internal. If you do that you'll want to go with a FW drive. As long as only the masters are on the external you can get by with a USB but once the library goes out there you're really want to look at FW.
    Hope this helps, post back if you have more questions
    regards

  • Aperture cannot export multiple projects for original files

    i want to export projects (original files) to time capsule folder for sharing
    i can only go into the individual projects, select all, then export to my desire location
    but i cannot select multiple projects and do it at once, as i have 100+ projects
    it will be a nightmare if i go projects by projects

    Tks for the reply , the reason I wrote (original) means I want each project name will be a directory name
    That is what the Export settings in my screenshot should give you, if you select the images from several projects at once and export using "File > Export > Originals".
    Only you have to select the images inside the projects, not the projects in "Projects" view. Move the projects to a containing folder and select all images in the folder, or select all photos in the "Photos" view.

  • Import / Export Projects - Consolidating Two Separate Aperture Libraries

    Question
    How do I export projects that contain ONLY the referenced images from other projects? So as to avoid importing duplicate versions of the original raw file.
    For example on hard dive 1 I have projects called
    1. Project Summer (contain raw images)
    2. Project Winter (contain raw images)
    3. Project Best Shots - Contains images that are moved from both Summer & Winter ...
    Issue
    • When I export project Best shots...it exports raw images...
    • Exporting and importing referenced images is causing me to have duplicate triplicates, etc...etc... of the original image from project 1 summer when I import to a new project
    What I want?
    • I only want it to export the referrenced images....so Im not getting duplicate images
    Background
    • All Images are all imported into Aperture (I am not using referenced files)
    • I am currently using Aperture 2.1.2 and have two 500 GB hard drives with two completely separate projects.
    What I am trying to do
    I would like to consolidate the two separate Aperture files onto one larger hard drive and keep all my organization and sub organization.

    read this:
    http://www.bagelturf.com/aparticles/library/libmergelib/index.php

  • Exporting project- folder structure to other Non-Aperture  applications

    Hello,
    I'm about to lay the foundation for a new Aperture installation. As far as organizational structure goes, this what I have in mind:
    1 Project / year
    1 Album / event
    Example:
    Project 1993
    Derek's Birthday album
    Linda's wedding album
    Project 1994
    Robert Birthday album
    Bob wedding album
    At some point, I will want to export the whole structure or some projects to family and friends who would like to view these images on their PC (not everyone is converted to MAC, yet).
    I understand the Export>Projects command generates a file that can only be understood by Aperture, so useless for sharing with non-aperture users. What I'd like to do is:
    1) Translate the project-album structure to a folder-subfolder structure in order to share images with other PC users.
    2) At the same time export images versions as opposed to masters.
    3) At the same time export all added Metadata.
    I have the feeling Aperture is not ready to do all of the above with one command only. How can I maintain the project structure in order to share with other PC users? I guess only a script will be able to do this...
    Thanks for your feedback.

    fbellay wrote:
    At some point, I will want to export the whole structure or some projects to family and friends who would like to view these images on their PC (not everyone is converted to MAC, yet).
    1) Translate the project-album structure to a folder-subfolder structure in order to share images with other PC users.
    Albums simply don't translate sensibly into Finder folders, in the same way that iTunes playlists don't. Any one Version can exist in any number of Albums, so you'd either end up having to choose one place for the exported file to be and remove it from all the other folders representing Albums, or end up with multiple duplicate copies of the same file.
    Projects, on the other hand, can be mapped directly to Finder folders. So you might be better off using Blue Folders and Projects rather than Projects and Albums.
    2) At the same time export images versions as opposed to masters.
    3) At the same time export all added Metadata.
    Exported Versions will automatically include IPTC & EXIF metadata, assuming you chose an export preset with metadata included.
    I have the feeling Aperture is not ready to do all of the above with one command only.
    There are some AppleScripts that will replicate the structure within Aperture when exporting (or Aperture Assistant* to do it without any scripting knowledge), but as I mentioned already, you will end up with multiple duplicate files.
    Also, you would have to do this again every time that you alter a Version, import files or move Versions around.
    Basically, the virtual nature of both images and organisation in Aperture mean that it won't really work in the way that you wish, and LightRoom wouldn't be much better even though it has closer ties to the folder structure.
    Why not simply export a Projects-worth of images in this way rather than your whole Library?
    Ian
    * http://aperture-assistant.com/docs/how-do-i-copy-apertures-organisational-struct ure-when-exporting
    “I may receive some form of compensation, financial or otherwise, from my recommendation or link.”

  • Aperture 2 - Project Export shows wrong filenames.

    Help!!! I have a big Problem. I have about 2000 Pictures in 3 Projects, which I like to transfer from my MacBook to my IMAC. The pictures are saved as seperates files and are not included in the project. When I imported the pictures from the camera in my MacBook, I choosed wrong filenames "NAME1 Date Counter". I changed those in Aperture on my Macbook in "NAME2 Date Counter". The Counternumber isn't the same like in the NAME1-Filenames.
    After that I did like everytime:
    - Copy the files to the IMAC
    - Export the projects to an external disk
    - Import the projects on me IMAC
    Normally, after that, I can connect the workcopys to the files on my IMAC. Has worked every time before.
    This time, I have the problem, that in the imported project, I have for each workcopy on my MacBook 2 workcopy's. One with NAME1 and one with NAME2, witch is the right one with all my work done. If I try to connect the NAME2-workcopy's to the files, the show'n filename in the workcopy is NAME1, which I can't connect with the NAME2-file on my disk. Sound's crazy, I know. On my MacBook all the filenames and the workcopys are OK. The problem only exists in the exported and imported projects.

    Yes it's a double back-up but there are some differences.
    The vault is easier as you don't have to think. Masters, versions and everything else are backed up.
    However to restore from the vault you have to restore your ENTIRE library you cannot restore projects.
    The vault does not back up referenced Masters. You have to do that yourself though it will back up any versions, book, web galleries etc that you make from those Masters.
    Export project will back up referenced Masters IF you select the consolidate Masters option.
    Personally I use the vault for back-up and the export project feature for moving from machine to machine.
    Hope this helps.
    M.

Maybe you are looking for