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?

Similar Messages

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

Projects and Referenced Images

Hi - I have been using APerture 1.5.6 for a while but am suddenly confused and have several questions:
1)Most of my images are Referenced and exist on my hard drive in various folders with various titles. If I get rid of the Aperture Library, my referenced files will still be on my hard drive untouched including all the versions I have made - is this correct?
2) If I get rid of the Aperture library (delete it) all that will be lost is the names of my projects - is this correct?
3) Which brings to me to this question. The projects in Aperture do not match the names of my folders under Pictures on my hard drive. For example - on the hard drive I have a 2009 Folder and within this folder have Winter 2009, Fall 2009 and so on. In Aperture I have a 2009 Folder with many projects with names (like Sam's Birthday) which do not match the folders on my hard drive. Sam's Birthday project for example is in the 2009 Fall Folder. How do I reconcile this so all my projects are created as folders in the the right Parent folder in my hard drive. If I export the project is just duplicates the photos and I don't want this. Thanks so much

pavillion wrote:
1)Most of my images are Referenced and exist on my hard drive in various folders with various titles. If I get rid of the Aperture Library, my referenced files will still be on my hard drive untouched including all the versions I have made - is this correct? 2) If I get rid of the Aperture library (delete it) all that will be lost is the names of my projects - is this correct?
No. "Referenced" means the Masters images reside where you left them, not in the Aperture Library. But versions only live in the Library so deleting the Library would delete all edits and versions.
3) The projects in Aperture do not match the names of my folders under Pictures on my hard drive. For example - on the hard drive I have a 2009 Folder and within this folder have Winter 2009, Fall 2009 and so on. In Aperture I have a 2009 Folder with many projects with names (like Sam's Birthday) which do not match the folders on my hard drive. Sam's Birthday project for example is in the 2009 Fall Folder. How do I reconcile this so all my projects are created as folders in the the right Parent folder in my hard drive. If I export the project is just duplicates the photos and I don't want this. ...I don't want to ditch Aperture. I want my hard drive to reflect the same organization as the projects/catalogue in Aperture.
Personally I recommend trying to avoid what I call "folder-think," or thinking about digital image files the way we thought about film originals. Of course digitally we still have file folders, but any given folder is not necessarily relevant to the location of an image file (unlike with film, where only one folder has all the film in it). Dozens of folders in Aperture can all "point" to the same image version.
Apply keywords as needed in Aperture to allow you to easily correlate the image files that you renamed when you imported into Aperture with the folders outside of Aperture. In the future you may want to do what I do. After a shoot copy images from CF to a named folder on the hard drive like 20090314-SJoneswedmstr. Then when that folder is imported into Aperture name the Aperture folder 20090314-SJones_wed. Also include 20090314-SJones_wed as a batch keyword during import along with other important keywords like Jones, wed, etc.
2) So if I want to save the image modifications I have done on Aperture, I have to export the version of each modified image to my hard drive? ...I assume I need to do all this MANUALLY.
I don't really understand the question. The Aperture Referenced-Masters Library automatically saves all the edits/versions and links to Masters. Masters do need to be separately backed up from the Library, but that to me is natural anyway because IMO Masters should be fully redundantly on/off site backed up before ever importing into Aperture.
4) One more question. I am trying out photomechanic and what I really want to do is use Aperture in conjunction with Photomechanic as I am told Photomechanic is a better organizational tool.
I don't know who told you that but I disagree and unless you already have long experience with Photo Mechanic I would just stick to Aperture. One learning curve at a time is plenty!
HTH
-Allen Wicks

Managing Events and/or Projects With Disk Images

I came across this method of managing Events and Projects a while ago. I finally got around to giving it a try. Personally, I really like this method.
It's simple.
It keeps things very well organized.
It's easy to open only the project or events that you want.
It's easy to consolidate and back up once you're done.
It takes some workload off FCP X by not having to always open up all your Events and Projects.
So, I thought I would share this for those of you who were not already aware of it.
This is my workflow: (based on the link below)
I create a Disk Image (named for the Event/Project).
(Note: There are two places to create the name, I use both, keep them the same)
I open up FCP X.
I typically put only one Event on this Disk Image.
I then reference whatever Media I need in this Event.
I usually don't bother to copy the media. (except when I'm done and I archive it)
You can create multiple Events, if you feel the need for additional organization.
Then I create however many Projects I need.
(since Projects equates to Sequences from prior FCP versions)
I have a unique Disk Image for each Event/Project that I work on.
To use them ...
First, always make sure FCP X is not running.
Locate the Disk Image in finder.
Double click on the Disk Image and it will Mount on your desktop.
(assuming it's not already mounted on your desktop)
Open up FCP X and it will load the Event(s)/Project(s) in the Disk Image.
If you don't want to work on an Event/Project in FCP X (make sure FCP X is not open), in Finder, simply Eject the Disk Image.
Now when you open FCP X, it won't be there.
Its not gone, but since it's not mounted on the desktop, FCP X simply doesn't see it.
To get it back (obviously quit FCP X first) simply double click the Disk Image in Finder and it remounts.
Open FCP X and you can see it's back.
You can open (double click to mount) as many Event/Project Disk Images as you want.
Just make sure you mount and un-mount disk images when FCP X is not running.
If find this to be a great workflow.
Many thanks to Steve Martin of Riple Training for posting this method.
http://www.kenstone.net/fcp_homepage/fcp_x_managing_disk_image_martin.html

Re the final commercial spot. What I am getting at is if all my media is optimized and therefore in ProRes, and I export in ProRes using the current settings, then shouldn't the media needed to rebuild the project be the same or close to what an exported Quicktime would have been?
Perhaps the notion of "used clips only" is not what it says then. I took that to be the "media managed" feature otherwise why is that wording there. I guess "used" actually refers to all of the media for the project and associated events rather than just for the project. This is misleading because the DUPLICATE operation and menu prompt only appears as a result of requesting an action on the project item.
There are aliases in my original event folder, but before I started this process tried to get FCPX to consolidate media for the project and it already was according the app. Truth is, some of the media is outside of the FCPX required folders. So it's strange that it says it's consolditated, but it's not and yet in duplicating the project it moves the references to the new volume only to point back to the old volume.
So my next question would be: Is there no feature to back up only what's needed to rebuild the final project (edit) reliably. Moving the project moves everything. According to the FCP manual, it seems using the Duplicate feature is the way I should be archiving. However if by "used clips only" FCP X means all media and refrerenced events, then I guess there's nothing for me in here. However then, whey would there be an option (after choosing duplicate project) an option to Duplicate Project and referenced events. If "used clips only" means all media, then there's no difference between the 2nd and 3rd Duplicate Project options.
Thanks Tom.

Vault restoration with referenced images - SEEKING HELP

Long story short: I have, had, a library that contained both managed and referenced images. 2 vaults set up for managed images, RAID system set up for referenced images.
Rebuilt library the other day because Aperture was moving kinda slowly. Followed the typical protocol of backing up first then rebuilding and to later back up again. In the middle of rebuilding, Aperture froze (Activity Monitor said Aperture was using only .50% of resources) and hung there for over 8 hours. Force quite wouldn't work. Had to hard restart.
Problems surface with the primary library. Decide to restore from recently backed up vault. Worked for only 13 projects but hung/froze again on the 14th project for another 8 hours.
Freaking out that my redundant back up system completely doesn't work, I put the managed projects back together in a new library by going into "show contents" of the vault and importing projects individually. This took another day of work. Managed projects are working just fine now and are backed up once again.
Referenced projects will not import at all. I can not reconnect them to their referenced images in any reasonable manor. The only way I've figured out how to do this is by hand, placing the referenced master image file into the "show package" content file of the said image. This is a daunting task for the 7 weddings of 700-1000 image each. Even if I do this, there is no guarantee that the project will import with out issue.
Anyone know how to do this? Does anyone know what happened here? Any thoughts would be greatly helpful.
Thanks in advance,
cd
Mac Pro 2x2.66GHz, 4 GB RAM, duel HD displays Mac OS X (10.4.10) MacBook Pro 17" 2.33 GHz 3 GB RAM

Andreas Yankopolus wrote:
Dudley,
I'm experiencing the same problem on my MacBook Pro: Aperture will periodically show all of my reference masters as being disconnected. They're on the laptop's internal HD, which is the only one connected to it. Quitting and restarting Aperture usually reconnects them temporarily.
My main piece of advice is to not install Leopard. It's been nothing but trouble for me, my wife, and a friend that's done so. If there was an easy way to drop back to 10.4.11, I'd do so in a heartbeat.
Hi, Andreas
I think there is something else going on. (would like to know what it is). We've been on Leopard/Aperture combo since day one and running without any hickups on PPC, Intels and Laptops.
Is there anything that seems to trigger this disconnect?
victor

Exporting form with referenced objects

Hi!
Is there any way a (pdf-based) form can be exported with referenced resources (e.g images referenced via URL) included? For example when using Live Cycle Designer ES outside SAP a form can be exported to an LCA archive which contains all images and other referencesd objects.
Regards,
Christian

Thanks for the answer!
Do you know if there is any standard SAP way of exporting the XFA template (xdb file) from SAP - in order to re-use it externally?
Regards,
Christian

Watch Folder to Overwrite Sequence Files? – Templated Project with Custom Images

So I want users to be able to upload an image to my server, have it added to a video, and rendered out and served to them. Simple right? Maybe my workflow needs adjustment:
I have a project saved with an image sequence render queued, and a subsequent movie file render (of the image sequence) queued and collected. (the image sequence is to utilize multi-machine rendering because of intense effects, etc.) When a user uploads an image, the server duplicates this template-project collected folder. The project has a placeholder image that is replaced by the user's uploaded image (into the footage folder). The server then drops it all in a watch folder for multi-machine rendering. The sequence renders and the movie renders just fine! All good.
The only PROBLEM is that when the second instance comes along, "skip existing files" is checked (by necessity to use the multi-machine function) and therefore just keeps the existing image sequence without overwriting. Every instance of the project is just a duplicate, and so has the same target path for the image sequence. So the subsequent movie file comes out the same as the first.
So how can I either:
1) force overwriting the image sequence
2) automate unique directories for each image sequence render – without physically opening the project to specify a different target path
-or- 3) move/delete the image sequence folder AFTER movie render, but BEFORE another watch folder render (considering multiple queued projects in the watch folder at once).
An ideas?? Thanks!!!

> So is there a way to automate importing the image sequence through aerender and tell it to render a movie?
Are you familiar with post-render actions? They exist to do this kind of thing.
Here's a relevant excerpt from After Effects Help:
http://helpx.adobe.com/after-effects/using/basics-rendering-exporting.html#post_render_act ions
"Use the Import & Replace Usage option to create a chain of dependent render items. For example, you can set one render item to use a watch folder and multiple computers to create a still-image sequence, and then the next render item can render a single movie file from that still-image sequence"

Error "Failed to Export PDF" with big image on CS6 (32) and CC (64)

Hi everyone,
I'm on indesign CS6 (v8.0.2) and when I try to export pdf with a very big image ( *.tiff, 25000*35000 pixels, ) , the action failed with this message :" Failed to export a PDF".
To be sure that there is no any corrupted elements, I made a very simple layout (one page , and just one element for my image,I turnoff prefilgth and all ressource intensive options, and export with no downsampling or resampling) and try to export with different size image:with 20000*30000 -or smaller -image the export works, always failed with image .The export failed to in scripting mode.
If I diveded my image in four , the export works but this solution is not convenient (I actually made tests for a fully automatised process, and we want to be sure that the indesign component is enough "safe")
I try the same action with an evaluation version of indesign CC 64 bits (v9.2) and have the same behavior.
I can imagine that there is a memory issue there, but my config seems to be strong ( windows server 64 with 16GB ram, DD with more than 100GB free). I don't undersant why-in a "full" 64 bit environnement- it is not possible to manipulate and export very large image ?
I'm wonder If the background task is a part of the problem, and if it 's possible to disable it in CS6 or CC as in cs5 ( creates an “DisableAsyncExports.txt” file in Adobe InDesign executable directoty don't seems to disable it in CC or CS6).
Thank you for your help and good ideas..
DC.

this is a .tif (not a "big"tiff) compressed in LZW or ZIP.
I just tried with another format (png), the error is the same...

Export Problem with Color Image Washing Out

I did an export of an image from DNG to JPG in LR4. Funny thing is, the JPG suddenly appears with a washed out look. It looks the same in Develop and Print modules also.
It gets even funnier, because when I use Finder to check the photo, the preview of the image is fine. I also opened the image from Finder in Photoshop CS5 and it is fine there. I also opened the image in PSCS5 from LR4 with "Edit In" and again the image in Photoshop is fine. So this appears to be a view issue in LR4. I did not print out the washed out photo but I suspect it would print out as it appears in LR4.
I've done some other image exports from DNG to JPG with other images and they do not have this problem but those were black&white converted images. However, I did check doing an export of another color image with the same result as the problem image. Here are screen captures of the DNG and the exported JPG (I was going to upload the exported JPG, but like I said it appears fine in Finder):

My monitor calibration is just fine. I was saying that because similar
problems are almost always due to bad monitor profiles. If you calibrate
regularly using hardware calibration then you're probably fine. Many people
use canned profiles from monitor manufacturers however and lightroom is
highly sensitive to those and shows messed up color depending on the
source. In this case however, since the restart fixed it it was likely a
bad preview image. I have seen before that LR sometimes is lazy in
refreshing those and can show you strange results that only get cleared up
by forcing a preview refresh.
Last your top screenshot DOES show that you are pushing the red in that
dress out of the monitor gamut. You can check this in the soft proof in LR
4 by turning on the monitor gamut warning. If you blow the color out of the
monitor gamut the preview is no going to be accurate no matter how good
your calibration. Just a cautionary warning.
Sent from my iPhone

Problem with Referenced Images

Hi all,
I have some documents that all follow the same structure.
doc1\doc1.book
\*.fm
\images\A.jpg
doc2\doc2.book
\*.fm
\images\A.jpg
In both documents, I have an imported image file that I want to be "images\A.jpg".
my doc2 directory would have been created by copying and renaming doc1 (because they all follow the same document template/format). But in doc2's .fm file, my referenced image file's path is "..\doc1\images\A.jpg", referencing to the original file.
I've tried renaming doc1\images\A.jpg to doc1\images\B.jpg, and opening the doc2 .fm, which then says it can't find "..\doc1\images\A.jpg" and asks me to replace it with another file. So, I use "images\A.jpg" (which is in the doc2 directory). That seems to work. But this seems to also change the link in the doc1 .fm file to point to "..\doc2\images\A.jpg".
So, the problem seems like both .fm files will always point to the same image file. I don't know how to disconnect these, so that they can work independently from each other. i.e. each doc directory (doc1 and doc2) is self-sufficient.
Any ideas?
Thanks in advance.
Kevin

Kevin,
If I understand you correctly, you have created the doc1 folder, inside is the doc1.book, *.fm files, and an images folder. One of the *.fm files references the A.jpg image in the images folder.
Create the doc2 folder, then copy all the files and folders inside doc1 to inside doc2. Do this in Windows Explorer, NOT FrameMaker.
Rename the doc1.book inside the doc2 folder to doc2.book. Everything should be as you want it to be.
NOTE that if you open doc1/*.fm in FrameMaker and then save it as doc2/*.fm, then FrameMaker recalculates the path to A.jpg to point to the file doc1/images/A.jpg, because FrameMaker assumes you want to retain your links to the original image files. The difference from the procedure above is that you are doing the copying within FrameMaker, not within the Windows file system.
Van

Unsuported Image Format error with referenced images

Hi,
importing referenced images does not work for me: when selecting "store images in their current location" (i.e., referencing them), the preview is visible for a moment and then becomes gray; the large preview says "Unsupported Image Format" (if AP doesn't crash at all).
When moving the same images into the library, it works fine. This applies to Nikon RAW (NEF) files (from a D70 and D2H) as well as plain JPEGs.
I'm using Aperture 1.5.2 / OSX 10.4.8 on a Mac Pro; DigitalCameraRAWUniv200601.dmg is installed.
Thanks in advance for any hints,
Bernhard
Mac Pro 2.66 Mac OS X (10.4.8)

Just if anyone cares (somehow this seems to be a rare issue), using referenced images seems to work if I choose a specific location ("Pictures") in the import dialog. The images get copied to a project-specific subfolder of ~/Pictures/ from where they are referenced, seems to work ok.
BB

Export project with Transparent Background

I need to export a Motion project with no solid color background and then import the .MOV into FCP to layer on top of preexisting footage. In project properties I have the transparent checked, but it still exports with a black background. Anyone know of a solution for this?

I cannot get a choice to set the background as transparent. I click edit>project properties and then the background color only offers colors, transparent is never a choice. I have set the color to black and then moved the slider and I have exported it on 100% and 0% and I still get the same results. I am exporting as an lossless+alpha and under the options I have selected a quicktime movie as the Kind and Animation as the Compressor. I have tried every possible combination and cannot get the project to export with a transparent background and like I said when I go into project properties there is no option for a transparent background, only colors.

How to export project with dual monaural instead of stereo?

I have a very large project with many audio tracks and they are all adjusted right now so they sound right on a balanced stereo system, but I want to make sure the final sound isn't corrupted by someone having their channels adjusted unevenly, so I've decided to sacrifice any stereo effect and output dual identical monaural channels...but I'm not sure the easiest way to do it. Is using Quicktime Conversion and checking "monaural" a way? Or is there someway to do it inside the program...but not irreversibly?
I appreciate any help anybody can give me.

I was over at a friends yesterday I had given him a copy of my dvd and he had said the sound was horrible..that in many places the bkgd music totally overpowered the dialogue and in other places in the program it was just the opposite. Sure enough, he was right. It wa horrible. And I easily discovered the reason. He has a large screen HD TV and his teenagers have the audio from the dvd player hooked to a stereo and had the levels and the equalization set totally different for each of the two tracks.
And I think some other people at one time or another do indeed disturb the balance of their stereo without even realizing it.
Stereo is 2 channels, Left & Right. What could any
user do to 'corrupt the sound' other than change the
Left-Right balance control on their amp, which most
people never touch.

Problems with exporting project incorporating still images

I'm using iMovie 11 with Snow Leopard in my iMac. I've made a movie incorporating nonHD footage and requiring 4:3 aspect ratio.The project also includes still pictures that introduce the old movie footage itself. I find I can get better overall quality exporting the completed project as a QuickTime movie rather than sending it directly to iDVD or using the "Export movie..." option. However, when I export as a Quick Time movie, although the old movie footage itself shows up exactly the way it should, the aspect ratio of the still pictures preceding the old movie footage has changed. When I use the "Find Info" option I notice the dimensions for the Quick Time movie are shown as 480 x 720 while the dimensions for the version I shared using "Export movie..." option are 480 x 640. I'm imagining this has something to do with the changed aspect ratio of the still photographs, although I should say that the movie that follows the introduction using the still pictures appears identical in both options. I would like to retain the quality of the "Export as Quick Time movie..." option while retaining the proper aspect ratio of the still pictures. When I run the project in the project browser, the still imagery looks fine; it's only when it's exported as a Quick Time movie that the aspect ration changes. Thank you.

What you might want to try is to set the cropping attribute in iMovie for those pictures to the 'Fit' option. To do that on a single image, click on the gear icon in the Project Browser for that picture and choose 'Cropping, Ken Burns and Rotation'. In the Preview window there's 3 buttons that allow you to set how the pictures are displayed. Fit|Crop|Ken Burns. in order to maintain the aspect ratio of the videos versus the pictures set the button to 'Fit' and see if it looks different in the final output to QuickTime. Fit will add black bars to the sides or top of the image to match the aspect ratio of the whole video. The other option, Crop, will cut off the sides or tops as needed to fill the whole video frame with the picture (no black spacer bars necessary).
Double-check your iMovie Project settings under the File Menu > Project Properties and make sure your aspect ratio is reflected there properly. Also make sure your QuickTime export settings indicate a frame size that is in the 4:3 ratio (as opposed to the 720x480 closer to 3:2).

!!!!HELP!!!! Exporting project with clips still referencing from memory card - Final Cut Pro X

I was working on a project recently (music video) where I had about 75 clips to cut up and edit, but my HD was too full to import all of the clips.
The clips still added to an event and I was still able to drag them into the project and cut them up like any regularly imported clip, but now that the clips are all lined up and edited where I need them to be, Final Cut won't let me export the project to youtube or a master file because the clips are still "referencing" off of my memory card.
Is there any way to bypass this or maybe import them and be able to not lose my edits or cuts?
Thanks.
- John

FOUND THE SOLUTION!!!!!!!!
In the event window, all of the clips that have the little camera icon on them, I highlighted and went to File >> Import >> Reimport from Camera/Archive. I had to do each clip individually which was annoying, but it worked.
And most importantly, none of the clips were taken out of their place.
Thanks for your input guys.
- John

Exporting projects with referenced images

Similar Messages

Maybe you are looking for