Aperture 3 / Export Diaporama to Modify on Other Mac

Hello everyone.
My workmate is finishing his version of an Aperture 3 diaporama on his Mac.
Is there a way we can export the whole diaporama from his machine and open it on my mac?
Our machines are quite similar, his is a 17 inch 2010 Macbookpro, and mine is the 2011 version of the same machine.
He's going have to leave town for a good while and I want to pick from where he left to finish the job on my computer. I hope my question is clear enough.
Thanks a lot!

Do you mean a slide show?
Then I'd suggest to export the slide show as a new Aperture library and to copy this library to your Mac. When he returns, he can simply reimport the library into his library.
To export the slide show:
Select the slide show in the Library Inspector panel
And in the Aperture Apllication menu select:
File -> Export -> Slideshow as New Library
Regards
Léonie

Similar Messages

  • Export parts of my library (referenced) to be used on other Mac w/ Aperture

    I need to export parts of my library (all items are referenced, none internal) to be used on other Mac with Aperture. So my images, projects and albums shall end up on the other Mac in Aperture. A simple proejct export doe snot do the job as the path to the referenced images are not available on the other Mac. Thus, I need to hand them over within the project, or how?
    How can my workflow look like to be able to do this export?

    Have you tried exporting the items as a new library?
    1) In Aperture 3 select the projects you want to export (you can command-click to select non-contiguously)
    2) Go to File>Export>Items as New Library…
    3) In the following dialog you'll have the choice of consolidating the files in the new library package: do that.
    Once this is done you should have an independent library containing all the needed files. When you've copied this new library to the other computer, you can keep the files managed or simply use Relocate Masters to put them on another referenced drive. It should work.
    Jade

  • 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 is exporting large file size e.g. original image is 18.2MB and the exported version (TFF 16 Bit) is 47.9MB, any ideas please

    Aperture is exporting large file size e.g. original image is 18.2MB and the exported version (TFF 16 Bit) is 47.9MB, any ideas please

    Raws, even if not compressed, Sould be smaller than a 24-bit Tiff, since they have only one bitplane. My T3i shoots 14 bit 18MP raws and has a raw file size of 24.5 MB*. An uncompressed Tiff should have a size of 18 MP x 3 bytes per pixel or 54 MB.
    *There must be some lossless compression going on since 18 MP times 1.75 bytes per pixel is 31.5MB for uncompressed raw.

  • Aperture to export photos either TIFF or JPEG files, highlight and shadow transition has obvious faults, this problem solved!?

    Aperture to export photos either TIFF or JPEG files, highlight and shadow transition has obvious faults, this problem solved!?

    What problem?
    You will have to be _a lot_ more specific if you'd like responsible feedback.
    I export thousands of TIFF and JPG files a week with no obvious faults.
    (Sent from my magic glass.) 

  • Aperture and Exporting and Compression (and iPhoto)

    Hello All...
    I recently imported an aperture project into iPhoto to create a book for a friend. In aperture, the the photos appears as 1536px x 1024px - i.e. perfectly big enough to create a 6" x 8" softback book. However, after the import, some pics appear as 768px x 512, and some as 1024px x 680px. Now, when I load the images into the book template, it says they are to low quality.
    Also, when I dragged an image from aperture to the desktop (one that is the mentioned bigger size in aperture) is saved to the desktop as the smaller size. How can I export from Aperture, preferably to iPhoto, in the original, or a big enough, size?!
    Thanks,
    Sam

    Sam
    Sounds like you're dragging files from the Media Viewer that shows up when you go File -> Show Aperture Library. This Media Viewer only contains the Previews generated in Aperture. Dragging to the desktop also gets a Preview. To get the full size pics you need to export from Aperture (File -> Export and choose the correct Export settings) and import to iPhoto.
    Regards
    TD

  • Aperture 3 exporting problems

    Seems that every time I try to export a file from Aperture 3, it hangs for a long time before it performs any exports - it is very slow. In Aperture 2, exporting a file that was 900x600 @ 72 dpi was instant, in Aperture 3 the same file takes 15 minutes - 4 files = 1 hour.
    Anyone know how to fix?

    Hi Photo*Gizmo;
    You stated; "I see that this issue has not been answered by Apple in over a month, so either they don't care or they are overwhelmed by bugs."
    Besides not responding to this forum, Apple doesn't even read this forum. It is a user to user forum. If you really want Apple to be aware of a problem you should use the feedback site instead of posting here.
    Allan

  • Cannot export one room mailbox but others yes.

    Gonna try to be more specific here...
    I deleted a user (meetingroom) with an associated mailbox and then restored the user through ADRestore, reconnected the Mailbox but the calendar settings (among other settings) in ECM 2010 give me an error:
    "Mailbox /o=Domain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT/cn=Configuration/cn=Servers/cn=<server>/cn=Microsoft System Attendant cannot be opened. It was running the command 'Get-CalendarProcessing -Identity 'domain.local/ou/meetingroom'
    -ReadFromDomainController"
    I've tried to export the mailbox to a pst but that fails too. Both the properties and export-cmdlet work fine on other mailboxes...
    I tried disconnecting then connecting the mailbox to a user-type and logon with that user to see if that unlocked it somehow but no luck there either. Is there any hope to restore this room mailbox with its containing calendar, appointments and so on?
    I thank you in advance

    Hi,
    Please run the following command to check whether this room mailbox is still disconnected:
    Get-MailboxDatabase | Get-MailboxStatistics | where {$_.disconnectdate –ne $null} | FL displayname,MailboxGUID,DisconnectReason,DisconnectDate
    Please disable the mailbox and reconnect the mailbox by using the following command, for example:
    Connect-Mailbox -Identity "ConfRm212" -Database "MBXResourceDB" -Room -User "Conference Room 212"
    Then check whether the issue persists.
    Regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Winnie Liang
    TechNet Community Support

  • Aperture cannot import anything from iPhoto and other bugs!!

    Aperture is buggy. Recently, I just updated Mac OS X to 10.4.5 and also updated iLife 06. Now I cannot import anything from iPhoto. I tried import images from iphoto or import iphoto library, both not working. I can import images from other directories but jut could not see anything display under iphoto library directory. Trying to use import iphoto library, click choose and then nothing happens.
    If you create a smart web gallery, all photos will be automatically duplicated.

    I used Pacifist.app to find iPhoto in the iLife '06 install package and then installed the app in the default location replacing the bundle that was there.
    the normal method gave me an install error.
    Thank you to the person who discovered this.
    I was going nuts trying. I have 6 iphoto libraries with 30,000 photos in total and some would import fine and others would not. couldn't tell the difference between them and had forgotten the update. just got a new iMac intel and wasn't paying attention. Causality

  • HT3130 trying to export a 4 minute video to desktop.  Only 1:08 seconds exports.  I've tried other clips and they all cut at 1:08.  Used different exports like Quicktime with the same results.

    trying to export a 4 minute video to desktop.  Only 1:08 seconds exports.  I've tried other clips and they all cut at 1:08.  Used different exports like Quicktime with the same results.

    Good to hear that you've had some success with the import.
    I tried 3 times to do it before I finally changed it to H.264, and it worked on the first try.  The quality of the compression was terrible with those settings compared to my standard settings, but I'm just glad it worked.
    Rather than Share>Export using QuickTime and then choosing your own settings for H.264, you may get a better result if you simply use the Share>Export Movie option. Alternatively, use the Share>Media Browser option (as I mentioned in my earlier post). You will be presented with a range of sizes to choose from. Depending on your target, it's usually best to select the highest size available, such as Large, HD 720p or HD 1080p. However, for producing a DVD it's best to not go beyond the HD 720p size, as the DVD will be downscaled during encoding to Standard Definition in the appropriate size for either PAL or NTSC.
    In my experience, both these options (Export Movie or Media Browser) produce a video file of excellent quality. The files will be in H.264 format and will have the file extension .mov or .m4v depending on the size of the export. I'm assuming that your camera records HD video in AVCHD format.
    These files work well with iDVD (or other DVD authoring programs). The export process for the presets is optimised by Apple to produce high quality video files at a reasonable file size. So, selecting a preset may give you a much better result. Choosing your own H.264 settings when using the "Export using QuickTime" method could be why "the compression was terrible". You may have selected a data (bit) rate that was too low. There is always a trade-off between quality and file size when compressing video.
    So, to summarise, try one of the Apple presets using either Share>Export Movie or Share>Media Browser.
    John

  • Error in Pages when exporting ePub with image cover: Other images dissapear

    That's it, if I insert an image in the first page, and select use first page as cover when exporting ePub, some (not all) other images inside the book will dissappear. I checked everything many times, and all the images are placed ok (not floating)...
    Any idea about this issue?
    Thanks in advance!

    Welcome to the Apple forums
    Exporting to ePub is new to Pages 4 with the 9.0.4 updaters. It appears that most Pages users don't have a need to export to ePub, so no replies. Sorry.
    For Yvan,
    The iPad Pages forum won't help in this situation. The iPad version of Pages can't export to ePub & Pages isn't involved in reading ePub files on the iPad.

  • Bought Aperture 3.3 upgrade on Mac and need to upgrade my other mac

    I purchased aperture 3.3 upgrade on my Mac and have another mac with an older version of Aperture. How can I upgrade on my other mac.
    Appreciate the help.

    ah yes that would change it a little
    copy the DMG (if you downloaded it) to your other system and install it there
    or download the demo on the other system (the one running AP2) and put the serial number in there

  • Is Aperture displaying images with a modified color temp. or gamma?

    I am brand new to Aperture and after importing some scans from black and white negatives, I notice that the same images when viewed in Preview or Photoshop appear brighter and perhaps cooler (but it is hard to tell with black and white images).
    I am just trying to discover why Aperture displays images a little differently than other applications.
    Thanks in advance.
    D

    the same images when viewed in Preview or Photoshop
    Comparison across applications is meaningful if and only if the image has the selfsame source ICC colour space profile. Begin by checking that the image has an embedded source ICC colour space profile. There are lots of ways, either run one the ColorSync AppleScript that extracts the embedded profile, or open the image in Apple Preview and check Tools > Get Info > Summary: ColorSync Profile, or open the image in the Apple ColorSync Utility, or open the image in Adobe Photoshop (which will describe an image without an embedded source ICC colour space profile as 'Untagged RGB', 'Untagged Gray' or 'Untagged CMYK'). If instead you open an image without an embedded source ICC colour space profile in a series of side-by-side application windows, these applications will assign an assumed source ICC colour space profile and the sources they assign may not be the same. In order to configure a conversion you have to have a source and a destination: no source, no colour managed conversion, so a source has sometimes to be assigned.
    Hope this helps,
    Henrik

  • [Bug] Exporting files may overwrite each other

    I think I'm seeing a bug in LR 1.3.
    If you want to export several different versions of one image and you start exporting one version while another export of the same image is already in progress, but LR didn't already create the destination file in the file system, you'll not get a warning dialogue because of a naming conflict but the second file will just overwrite the first one.
    I managed to export 6 versions of a file, i.e. have 6 exports running at one time, but in the end having just one file. Granted my computer is of the slower ones and thus it takes some time from starting the export until the destination file (jpg, psd a.s.o.) is created. But it might also happen on up-to-date systems.
    If I'm starting the second export after a file for the first one has been created, LR correctly alerts me for the name conflict and asks me what to do.
    Johannes

    > Well, don't do that!
    Of course, that's the workaround but no fix. I don't know how often one should want to do that and it was the first time for me too (though I'm not working with LR for long time).
    I'm working with a AMD Duron 1,3GHz.
    Setting that up is a manual job. Make snapshots and then select one, export, select another, export a.s.o. First I had expected to get the chance to export several snapshots at once (using the snapshotname as file name part), but that doesn't seem to be available. Then I expected to get asked if LR should create a unique file name, but it doesn't.
    It would be nice for me to start those exports and then do some other stuff until it's done. But so I've to wait each to finish until starting the next one.
    Johannes

  • How to strongly protect the step types from being modified by others?

    how to strongly protect the step types from being modified by others?

    Hi Jacky,
    You can make a property of a step uneditable by changing the property
    flags for the step.  First, you want to be able to view the hidden
    properties so that you can change the flags for these properties as
    well.  You do this by going to Configure>>Station Options
    and selecting the Preferences tab.  Check the box for Show Hidden
    Properties.  Once you have done this you can select the step type
    from the types palette.  In the window to the left, you can expand
    the tree for the type to see all the properties of that step. 
    Right click on the property that you do not want users to be able to
    edit, select Properties.  Then click the Advanced button. 
    Here you will see a list of the setable flags.  Check the box for
    PropFlag_NonEditable.  You can then do this for all the properties
    of the step that you do not want users to edit.
    Thanks,
    Caroline Tipton
    Data Management Product Manager
    National Instruments

Maybe you are looking for

  • Macbook Pro (mid 2012 - non retina) Yosemite Slowing down

    I saw in some other posts that people were helped and slow downs were solved when fellows looked at EtreCheck reports. So i have copied my report. Kindly advice what is causing the slow down and how to fix it.  EtreCheck version: 2.0.8 (95) Report ge

  • mx:States issue

    I have a problem with state changing. I have a MAIN.MXML that has <mx:States> tag. Assume there is a top navigation, from there I click on LIBRARY button then following state is called up. <mx:State name="viewResources" basedOn="MainApp"> <mx:AddChil

  • Camera LED Flash Bug/Defect

    okay so I think theres something wrong with 4.3.1 or, its just my phone. Okay so you start the camera app.(make sure its the back facing camera when opened*the one with the flash*). Then press the button to switch to the front facing camera. Now pres

  • Building with -G rh4 SunStudio 12

    When building code, we have stuck in the -G option to all builds (shared or not) so that 2 builds are not necessary to produce the .a and the .so files. With Studio 12, this option appears to fail. When this is done, the object crashes when running.

  • My macbook won't read the snow leopard disk but my macbook pro does...why?

    For better or worse I ran a clean install of the original MacBook OS for an early 2008.  It had been running Lion over the years it had never been wiped and reinstalled.  In any case, I successfully reinstalled 10.5.2 with the start up disks that cam