Export projects in aperture to DVD

How do you create a DVD from Aperture projects and slide shows?

Create a slideshow project in Aperture.
Select the images you want to use in your slideshow, and use the command "File > New > Slideshow"
Pick a slideshow theme, add captions and music, and then use the "Export" button to render a video of your slideshow.
Then use third-party software to burn the video as a video DVD. Aperture does not provide burning video DVDs.
For software for burning DVDs see:
How to create a video-DVD? (Macs without iDVD): Apple Support Communities
and
Why is there no iDVD on my new Mac?: Apple Support Communities

Similar Messages

Export Project to Auto-Play DVD in CS4?

I'm trying to burn a DVD of my project. I don't want to author any menus and I just want a simple auto-play DVD of my finished timeline.
I don't see any "Export to Encore" option like in CS3. I have tried Export>Media and choosing MPEG2-DVD. However, this only loads the Media Encoder Queue and gives me no burning options.
Any thoughts?
Thanks!

I've used the version of Premiere your talking about (pre-Encore) and your right, very limited.
However, I'm refering to the fact that CS3 (utilizing the File>ExportToEncore command) would automaticaly launch the program and burn the disc for you.
Yes, I used the 2.0 feature quite a bit. For my in depth authoring, I used DVDit Pro (um, yeh, that's right, I didn't do any in depth authoring back then). Forget that it was limited (it did not even open Encore), it was very automatic. And I hear you; when I moved to CS3, I really missed having that feature for testing DVD output, and for some finals (but not many). I did not think the CS3 setting was automatic enough, but I was hooked on having even a simple menu, so I rarely used the quick CS3 option - hey, I had Encore.
But as a practical matter, what are you really losing? And don't forget the parts of CS3 that were not automatic that are now. For the kind of quick option you are doing, you must be okay with Encore's automatic transcode setting, right?
CS3 required you to set the transcode settings, name the file that would be exported, and remember to put a disk in the drive!
CS4 requires you to dynamic link to Encore, name the Encore project, (it creates the timeline and sets it as first play), and click the build tab and burn (yeh, after remembering to put a disk in the drive).
Anyway, if you're the only one that submits a feature request, Adobe is not going to think that adding this feature back is going to be worth it. If there are a bunch who do, they take more notice and look at what their "cost" is to do so.

Export Project to loop on DVD Player

Hi, Can anyone help me. I need to know a simple way to export/save a project onto DVD which will play on any standard player and loop ?
Help
Hillster

IDVD has the loop feature under the advanced tab. You can also make the DVD play on insert on the map view menu if you need that.
IDVD is about as easy as you can get.

Export project to DVD? (Spanning)

Hi all - I'm actually (believe it or not) starting to feel more comfortable about the idea of archiving Aperture projects now that I know iview can read them. The big question though - is it possible to export projects to span across several DVDs? I can't for the life of me find a way to do this - I thought maybe I could export smart albums, but no-go. Any ideas?
The best I can come up with so far is to convert the project to a folder and then have Impression (or whatever) span that project across dvds, but I'm a bit nervous that it might be tough to reimport the project if I did that.

IDVD has the loop feature under the advanced tab. You can also make the DVD play on insert on the map view menu if you need that.
IDVD is about as easy as you can get.

Exporting Matrox HD Project To MPEG-2 DVD Taking Very Long

Project: Matrox HD 1920 x 1080i. 2 hours on timeline. The files are original files taken from AG-HMC150 AVCHD camcorder in .MTS file format.
If I export the timeline to MPEG-2 DVD format with CBR, render with maximum quality option enabled, and render with maximum depth enabled, this process takes 8 hours.
If I export the timeline to MPEG-2 DVD format with VBR 2 passes, render with maximum quality option enabled, and render with maximum depth enabled, this process takes 16 hours.
I wanted to ask is this normal for exporting to take this long on my computer with Matrox MXO2 Mini w/ MAX? Is there a problem with my computer, settings, or something else? What can I do to improve export speed of MPEG-2 DVD files?
Below are the specs of my computer. Windows 7, Adobe CS5, and Matrox are updated to latest versions. MPE GPU Acceleration is hardware enabled.
Operating System
MS Windows 7 Ultimate 64-bit SP1
CPU
Intel Core i7 920 @ 2.67GHz
Bloomfield 45nm Technology
RAM
24.0 GB Triple-Channel DDR3 @ 534MHz (8-8-8-20)
Motherboard
ASUSTeK Computer INC. P6T DELUXE V2 (LGA1366)
Graphics
ASUS VH236H (1920x1080@60Hz)
2048MB GeForce GTX 460 (EVGA)

Jim-You can speed things up (and keep that quality) by ensuring you have Hardware Acceleration turned on and doing a Direct Export, instead of Queuing it up through AME
According to Adobe that is incorrect Jim. Here's a quote...
Adobe Media Encoder
Premiere Pro and other applications employ Adobe Media Encoder, a standalone encoding application. When you specify export settings in the Export Settings dialog box and click Export, Premiere Pro sends the export request to the Adobe Media Encoder.
From the Export Settings dialog box, click Queue to send Premiere Pro sequences into the standalone Adobe Media Encoder queue. From the queue, you can encode sequences into one or more formats, or take advantage of other features.
When the standalone Adobe Media Encoder is rendering and exporting in the background, you can continue to work in Premiere Pro. Adobe Media Encoder encodes the most recently saved version of each sequence in the queue.

Exporting from Aperture to DVD

I am trying to export a slideshow , created in Aperture to DVD so that it can be played back in a DVD player.
Each time I export the slideshow it exports in Quick Movie format which is not compatible.
How do I select the format to burn to a DVD that is playable via a DVD player?

Aperture doesn't have a specific setting for exporting a slideshow for import into iDVD. I've been using the AppleTV setting to keep the highest quality possible as the source for the DVD. I haven't tried iDVD but DVD Studio Pro and Compressor do a bang up job with the AppleTV sized movie.

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

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

Export project - reimport same project query

I had a project on my iMac which I had worked on and then relocated the master images to DVD. I needed to export the project to my MBP's Aperture to work on the images at the clients home so I consolidated the images and exported the project, no problem so far. After working on the project on the MBP I again exported the project and imported it back into Aperture on the iMac. I now have the original project with the referenced images marker and the re-imported project (1) with the attached master images. The (1) project has all the adjustments on which the client wanted. What do I do with the original project and do I now have to burn the "new" master images onto another DVD or can I point Aperture to the original DVD where the original masters are?

You can either burn another DVD of the masters from the new project or you can use relocate masters and then managed referenced files/reconnect to point the new project at the old dvd volume but I would not recommend it if you are not familiar with these tools.
My preference is to do away with DVD's altogether and just go with HD storage that way you can simplify your workflow to just relocate masters/consolidate masters and get rid of the old projects when you need to deal with multiple computers.
RB

Exporting project from one mac to another

Hi, I have a project in Aperture 3 with referenced images stored on an external hard drive. I want to export this project across to another Mac without the RAW files being copied across as well. I had hoped to re-reference the masters (RAW files) simply by plugging the hard -drive into the Mac and re-connecting referenced files.
Is this possible at all ?
regards

When you export as a lbrary you have the option of not including any referenced masters into the library:
Just make sure Consolidate masters into exported library is not checked.
When you get this library over to the other Mac and connect the HD with the masters on it you probaply will have to run File->Locate Referenced Files to reconect the masters. But Aperture uses UUID's to identify disks so you might get lucky and not have to do this step.
regards

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 from FCP directly into DVD studio pro?

Is it possible to export from FCP directly into DVD studio pro? If not, what is the preferred file format because my exported quicktime files come up as "incompatible format" when I try to add them into my DVD project. Any help is appreciated.

You need to encode audio as well from Compressor. You'll have 2 files - audio and video.
Here's a tutorial:
http://www.youtube.com/watch?v=wFgJpd7DEWw
Message was edited by: Eric Pautsch1

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

How to find the size (in Mb) of a project in Aperture 3?

I do not know a quick way to find the size of the originals e versions in a project in Aperture 3. Would any one know how to do this?
Tks
Pedro

Take a look in the "More Like This" section in the right-hand column for discussions about this.
The answer is: you can't. Aperture is not so simply structured that you can select a group of Images and "weigh" them.
If needed, your easiest solution is to export the Images as a new Library and include the Originals. The size of that Library is more than but close to the size of the Originals and the Versions.
HTH.

Export projects in aperture to DVD

Similar Messages

Maybe you are looking for