Exporting Projects/Library

This may be a simple one to answer but here goes. I have an iMac which is my main machine but occasionally I need to export a project to my MacBook Pro to show a client. I usually export the project to the iMac desktop then drag it over to the MBP which leaves a copy on the iMac desktop and the MBP desktop. Can the project that is left on the desktop of the iMac be trashed pending the arrival of the previously exported project back from the MBP after any changes have been made? Following that I assume that the project on the MBP can be trashed after sending it back to the iMac.

Unless you make changes while working with the client, there's no need to bring it back. Just trash it from the laptop. If you do make changes, you have to bring it back, get rid of the original project in the desktop library and reimport it.
DLS

Similar Messages

  • Export project library to iPhoto

    I have created a rough montage in iMovie using only still photos. I need to hand the files and the running order over to a third party to finish the job. He may or may not be using iMovie. Is there a way to print a list of the images in the order that they appear in my movie? I was wondering if it is possible to export the files back to iPhoto and print a contact sheet there. The contact sheet that iMovie prints is too small for someone else to see. Please help!
    Thanks.

    My recommendation would be to change your workflow slightly.
    First, create an iPhoto Album. Then drag your pictures for your montage into your album, in the order you want them.
    Then, you can drag the album into iMovie from the iMovie photo browser and the order will be preserved. You can add transitions, music, titles, etc.
    In iPhoto, you can select the photos in the album and do a FILE/EXPORT as jpegs to provide the files to the third party.
    Since you have already created the movie, I would suggest just creating an iPhoto album to match your movie.

  • How to hide the file name (the bizarre number assigned by the camera) when exporting an image version in aperture from an album. Pl understand I want to keep the file name in the project library version.

    how to hide the file name (the bizarre number assigned by the camera) when exporting an image version in aperture from an album. Pl understand I want to keep the file name in the project library version.

    Within Aperture you have Images, which are constructed on-the-fly from two files (the Master and the Version).  You get an image-format file _only_ when you export an Image.  You select the file name (usually a scheme) when you create an image-format file (that is, when you export).  Look under "Aperture→Presets→File Naming" for built-in Presets.  You can, of course, create your own or customize any provided.
    The Preset is applied to only the file newly created by your "export" command.  It is not applied to the Image in Aperture (unless you rename your Versions or your Masters).

  • 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

  • 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

  • Exporting projects that reference images in other projects

    Hello, all. I'm wondering if anyone out there has had luck exporting projects that reference images in another project. I've just given this a try, and I get empty images (dotted gray outlines that can't be multi-selected and can't be "managed" as referenced files, even though it knows where the original file should be).
    Here's how I have things set up:
    1. main project with referenced images
    2. secondary project with an album that references images in the main project (secondary project shows 0 images, but album in secondary project shows N images)
    I export the secondary project, and import it into another Aperture instance. All images show up as dotted outlines.
    Furthermore, if I go into list view, the Activity Monitor does something bizarre. It shows the # thumbnails remaining as a moving target. See the video below for an example.
    Any help would be greatly appreciated. Thank you!
    Screen captures:
    Missing images as dotted outlines:
    http://echeng.com/temp/aperture-missing-images.png
    Small video of thumbnail creating bug:
    http://echeng.com/temp/aperture-thumbnail-bug.mov

    I do this sort of thing constantly and things a whole lot more complicated. It works fine on all three of my laptops and my macpro. I actually just tried to simulate the exact conditions you describe and I will tell you what happened.
    1)Create new empty project in library A called "export"
    2)Create new empty album in that project.
    3)Dragged multiple images from different projects (all referenced) into that new album.
    4)Used file->export project with the consolidate images checked. Imported that project into a new/different library.
    All of the images showed up and they all showed up as managed masters as expected. So I then relocated the masters from that project and did the same thing in reverse, back to the old library. I ended up with another project called "export (1)" with all of the images referenced and having nothing to do with the original project or the original referenced masters - as expected.
    I did the testing not to figure it out but to validate that nothing had changed or broken since the last update.
    You are either not doing what you think you are doing or your library/library is forked - you may want to try a rebuild or just create a brand new set of libraries and try to validate that it will work with a brand new set of libraries to try to isolate the issue to 1 - your existing libraries or 2 - your installation.
    RB

  • Export Project puzzle

    There's something about Export Project I obviously don't understand. I have two small JPG-based projects, one (57 images) referenced, the other (77 images) managed in the Aperture library. On Export Project, for either one, I can check or uncheck "Consolidate images". These are the file sizes I get:
    proj with 57 referenced images, no consolidate 65.2 MB
    proj with 57 referenced images, consolidate 224.9 MB
    proj with 77 managed images, no consolidate 159.8 MB
    proj with 77 managed images, consolidate 159.8 MB
    Is it just me, or is this puzzling?
    Am I right in guessing that both exports of the managed project DO contain the masters? If so, why so much smaller than the referenced project? But if not, why so much bigger than the referenced project, far out of proportion to the number of images?

    Seems like you might have Previews on for the referenced project, and off for the managed project.
    So, for the referenced project if you export with no consolidate, you're only exporting the previews, metadata, version info, etc., but the masters remain outside the library. If you export with consolidate, the masters join and increase the size. For the managed project, there is no difference becase the masters are in the exported project either way. Does that help?
    Mark

  • Exporting projects with referenced images

    I want to import referenced images from an external hard drive, edit them and then export the project in order to archive it. Is this something that I can do now? Will I end up with a bunch of referenced previews in my library and an exported project that can link back up to the master images that are on a separate hard drive?
    Antonio

    No, this only exports a "copy" of your projects and does not remove the master image. It is still in the Aperture Library. I am also trying to find an easy way to move the entire project outside of the library and still maintain a reference link to wherever I move the images to. Any thoughts?

  • When exporting projects in AP2.....

    what does "consolidate images into exported projects" mean? Is it best to leave the box unchecked or to check it? Does it make any difference when importing these projects back into AP2 or AP3 if they are or are not consolidated?

    If you want the project to be full importable exactly as it is in the source library when it is imported into a completely different library you will probably need to check consolidate masters - it does two things - first if any of the masters are referenced it includes them in the exported project the second think is that it includes image masters that may exist in other projects that happen to show up in albums for the exported project.
    Hope that clears things up.
    Easy enough to experiment on your own.
    RB

  • 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.

  • Export project and all events as backup

    There is an issue with my MBP 17 and the service centre has asked me to format and re-install snow leopard.
    Before I do that there is an iMovie Project (several actually) that are really close to my heart and I want to export the project, all events (videos, photos imported). I switched to Mac from PC recently and really scared how to do it.
    I have been using Time Machine to backup but have a feeling it would restore the entire hard disk to the STATE it was when backup was taken and in effect nullifying the use of reinstalling OS X altogether.
    Could someone please help me.
    Sorry if its a basic question.

    You need an external drive that is formatted as Mac OS Extended (journaled).
    In iMovie click View/Events By Volume.
    In iMovie go to the Project Library view.
    First drag the project to the external drive in the project library list.
    Then Use the File/ Consolidate command.
    It will move all events, photos, music to the external drive.
    Be sure to read about this command in iMovie help before proceeding so you understand the nuances.

  • Import back into Project Library?

    I exported a project out of iMovie, now it's gone from my project library, does anyone know if I can get that back into "Project Library" so I can edit it?
    Thank you!

    Hello, thank you for your quick response. 
    I exported the movie by doing the following:
    Share > Export Movie > Saved as "Medium size" to my Desktop > clicked "Export"
    The file was saved as a "m4v" file.
    I was unable to drag that file back into iMovie
    Thank you!

  • Exporting a library with its folders and albums

    I scanned over 1700 slides into my aperture library.  AFter spending a considerable amount of time putting them into folders and albums, I would like to export the project so my husband can put it into his aperture library.  I exported the whole project onto my desktop so I could put it in dropbox to enable him to put it into his computer.  However, when I exported the library, It came across as just one big library of photos, with no structure.  I don't care to reorganize the photos into folders and albums again, as it would be very time consuming.  Is there any way to export the library and keep its structure?
    Thanks in advance
    Nancy

    Nancy,
    what is your Aperture version, and how did you export?
    In the current Aperture version 3.4.5 all projects and albums should be preserved, when you export a library with "File > Export > Projects/Albums/Items as new library"
    For example, I selected two albums in the library Inspector simultaniously, made sure, that I only selected the albums in the panel, but not single images within the albums, and then used the command "File > Export > Albums as new library".
    The exported library had the two albums, as well as all projects and folders necessary to fill he albums.
    Did you perhaps only select one big project of scanned images? Then try again by selecting the albums you want to export. My two albums exported like this: You see, the exported library has quite a few folders with projects inside, as well as my two albums:
    Regards
    Léonie

  • 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

  • Project library - audio

    What does the little icon (next to all of my projects) in the project library window mean? It has what looks like an audio symbol and an exclamation mark in a small triangle.

    It's a very, very cool new feature.  Aperture users are very familiar with this.  It's a "publish" icon.  It means you've exported that project.  The excamation point means the resulting output file no longer exists where it was originally written to.
    Highlight a Project in the library.  Open the Inspector, go to the Sharing section.  You'll see a list of every single output you performed for that Project.  If the output file is still in it's original location (no exclamation point), you can click on the magnafying glass icon, a Finder window will open, taking you directly to that file.

Maybe you are looking for