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

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

Command to Export project as Final Cut Pro XML from jsx script

Hi All,
Can somebody get me the command to export the project as final cut pro xml from jsx script.
I was using the extension builder script earlier for cs6 panel development, so we were using pjct.exportFinalCutProXML("pathname");
Now I am working for panel in Premiere CC so working on HTML 5 panel and qe dom scripting(.jsx).
In some jsx examples i got there is script to export sequence as final cut pro xml but cannot get the code for project export.
project.activeSequence.exportAsFinalCutProXML(entire_out_path);
Also please let me know if there are any kind of reference available about all the functions and properties in the pe dom scripting for premiere pro cc.
I am using premiere pro cc 7.1, windows 7, Eclipse Kepler.
Thanks in advance,
Anoop NR

When you reimport the exported project XML to FCP, do you get the full project or just the single bin/sequence? If you get the full project then it sounds like you need Premiere help, not FCP help ... have you tried asking on the Adobe forums? If you only get the single bin/sequence then it seems you might have inadvertently selected those prior to creating the project export. Try making sure that your FCP Browser window is active and that you have not selected anything within that window prior to using the File > Export > XML command. If that still causes issue then you might try using an earlier FCP XML version.
Hope it helps
Andy

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

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

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

IMovie '10 consumes all RAM and I can not export projects

A few days ago I upgraded to iMovie '10, but since then consumes all memory, close the application, I can not export projects. I upgraded my Macbook Pro from 4GB to 8GB of RAM, but the problem persists. I'd like to iMovie 9.0.9 but I do not know how to do

I have this same issue also, on my MacBook Pro. When I click 'export project' nothing comes up at all.
It's very frustrating and I have tried everything also:
All files rendered
Re-installed FCPX
The only change i've made since it has started happening was upgrading to Mavericks OS X 10.9.1. So it has to be something to do with that.
I was wondering and hoping if you have since solved the problem, and can help me with a solution to amend it.
If anyone else can help it will be much appreciated, and most thankful.

How to export project(s) with GPS data

I tried to export a project with GPS metadata but when I import that project (as a library) into my Aperture on my iMac, no GPS data...
Am I missing something obvious??
Adam

Hello Adam,
First of all - shift-L does NOT bring up the lift and stamp HUD on my Aperture 3...in fact, on the menu, it has no keyboard shortcut.
That is surprising for me, perhaps in my list of questions I should also have asked for your OS and exact Aperture Version. I tried this with OS Lion 10.7.2 and Aperture 3.2.1.
But you found how to bring forward the Lift&Stamp HUD, so that is not so important right now.
It is really good to know that you see GPS data on your images. Those you should be able to export.
I apply your smart album and it's rules, that image shows up...so if I see latitude/longitude data in the metadata tab, why does your smart album pull it out??
Probably your GPS tags contain Latitude/Longitude allright, but not the GPS version.
Remove the rule '"GPS Version" is empty' from the smart album, then you will see only those images that don't even have Latitude or Longitude. Hopefully that are not too many.
I guess from my perspective, if I either assign a "place" for my pictures or import GPS info from my Garmin, shouldn't that put the right metadata in so that it could be exported properly?? If not, when I move these images to my iMac I will have to redo ALL my places...which doesn't make sense...
Sorry if I'm not getting it...
sorry, if I am not explaining properly...
I have done some experiments right now with my current Aperture version 3.2.1 and surprise, surprise! Seems I have to eat my words.
In this version 3.2.1 assigning a place to an image seems also to set the GPS EXIF data, not only the places name as IPICT. What a relieve! I used to have to assign Places data over over again, because the places information would not be recognized by my other applications. So my advice to you is to upgrade to 3.2.1 if you have not done so.
I suspect the GPS data you see without "GPS Version"-tags are those you created manually in Places, wheras any other GPS data with GPS Version Tag come from your imported Garmin tracks.
I have to make further experiments with this new behaviour before I can feel confident to give advice, and I could use a helping hand here. Anyone?
@Kirby Krieger: I see you have been looking in on this thread, could you please confirm if this new places behaviour is also true in SL, if you have time?
Sofar I tested the following with several folders and it worked beautifully: Try it.
Export the folder from Aperture as a Library: File -> Export -> Project as a library
Reimport it to Aperture on your other machine: File -> Import -> Library/Project
Regards
Léonie

Pixelated video when export projects using QUICKTIME COMPRSESION.

I'm having problems to export projects using QUICKTIME COMPRSESION. When I select either "quicktime movie" or "AVI", the result is a totally pixelated picture. I tried to do some settings in order to fix this problem but still doing the same. Make a note that only happens when I use QUICK TIME COMPRESION. It works fine when I select "quicktime movie" directly from export menu. i can use this to work onmy MAC but. it will not work with Vegas or whatsoever. SOME HELP WILL BE APRECIATED.
thanks
Juan.

I used the following settings:
compression: H.264
Quality: Best
Key frame Rate: 24
Dimensions: 720x480
Yes, vegas support Qt, The problem is exporting from FCP a pixelated video.
regards
Juan.

I cannot export projects from GB in my MacBook into GB on my iPad3; nor can I export from IPad to my MacBook. I have tried going onto Apps update on the MacBook, but there were none available. I have read that this omission is to be corrected - can you co

I cannot export projects from GB in my MacBook into GB on my iPad3; nor can I export from IPad to my MacBook. I have tried going onto Apps update on the MacBook, but there were none available. I have read that this omission is to be corrected - can you confirm this is intended to happen, or is it already in process. While awaiting for this essential development, can you please suggest any way of transferring information either way?

spicer_the_coalman wrote:
I cannot export projects from GB in my MacBook into GB on my iPad3
http://www.bulletsandbones.com/GB/GBFAQ.html#exportgbxtogbi
(Let the page FULLY load. The link to your answer is at the top of your screen)
spicer_the_coalman wrote:
nor can I export from IPad to my MacBook.
http://www.bulletsandbones.com/GB/GBFAQ.html#exportgbitogbx
(Let the page FULLY load. The link to your answer is at the top of your screen)

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

Export Project Tasks to Excel using VBA by Custom Field

Question referring to the link:
http://social.technet.microsoft.com/Forums/projectserver/en-US/9c46458c-893f-41ba-bd46-bdb59c533f4a/export-project-tasks-to-excel-using-vba-by-custom-field?forum=project2010custprog
Help needed. I have inserted my question at this address for Andrew or anybody else to reply. Hope to hear from you.
Regards,
Chuck

Thank you Andrew for getting back to me and I have found somewhere on the net the following macro that would do the job for the version 2007. Here is a copy for those that may need it.
Option Explicit
Sub CreateMenus()
Dim cbrMain As CommandBar
Dim ctlMain As CommandBarControl
Dim ctlOLExport1 As CommandBarControl
Dim ctlOLExport2 As CommandBarControl
Dim ctlOLExport3 As CommandBarControl
Set cbrMain = Application.CommandBars.ActiveMenuBar
Set ctlMain = cbrMain.Controls.Add(Type:=msoControlPopup, Temporary:=True)
ctlMain.Caption = "Export to Outlook"
Set ctlOLExport1 = ctlMain.CommandBar.Controls.Add(Type:=msoControlButton)
With ctlOLExport1
.Caption = "Selection to Outlook tasks"
.OnAction = "Macro """ & "Export_Selection_To_OL_Tasks"""
End With
Set ctlOLExport2 = ctlMain.CommandBar.Controls.Add(Type:=msoControlButton)
With ctlOLExport2
.Caption = "Selection to Outlook appointments"
.OnAction = "Macro """ & "Export_Selection_To_OL_Appointments"""
End With
Set ctlOLExport3 = ctlMain.CommandBar.Controls.Add(Type:=msoControlButton)
With ctlOLExport3
.Caption = "Selection to Outlook notes"
.OnAction = "Macro """ & "Export_Selection_To_OL_Notes"""
End With
End Sub
Cheers!
Chuck

Error in exporting project in OSB 11.1.5

Hi All,
I am facing problem while exporting my resource in OSB console.
The export failed with exception: org.apache.xmlbeans.SchemaTypeLoaderException: XML-BEANS compiled schema: Could not locate compiled schema resource schemaorg_apache_xmlbeans/system/sC32E5426CD7FE802750A77E9B68AD947/insertelement.xsb (schemaorg_apache_xmlbeans.system.sC32E5426CD7FE802750A77E9B68AD947.insertelement) - code 0
if some one have any idea please help
I am selecting Export Resources and tried both following option.
Export Projects
Export Resources
with included dependency....
Environment:
Oracle Service Bus Version: [Oracle Service Bus 11.1 ]
Oracle Weblogic Server Version: [WebLogic Server 10.3.5.0 ]
Please suggest some info.
Regards,
Abhishek
Edited by: abhishek on Sep 23, 2012 10:42 PM

i guess you are exporting both deployments and system file
you can not export system file without authorization what you need to do is that when exporting unchecked system and export rest of the files.

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?

Export project - reimport same project query

Similar Messages

Maybe you are looking for