1) Export projects to disk using preset or preferred QT compression format?

i don't understand this i'M A VIDEOGRAPHER NOT AN EDITER BUT THANX

i don't understand this i'M A VIDEOGRAPHER NOT AN EDITER
It means that once you finish working on your project in iMovie '08, you will have to export it in order to use it. Exports are normally targeted for a specific use. I believe all presets are in H.264/AAC. However, you have the option of exporting your project using QuickTime which means you can perform custom exports for your own special use.

Similar Messages

How can I use QuickTime SDK to get Compress format of Video stream?

I can get uncompress video stream like this:
QDerr = NewGWorldFromPtr( &m_hGWorld, k32BGRAPixelFormat, &rcMac,
NULL, NULL, 0, (char*)m_pVideoBuffer,
m_sAVFileInfo.sResInfo.ulWidth*4);
then the m_pVideoBuffer is uncompress video stream. How can I use QuickTime SDK to get Compress format of Video stream? I could change "k32BGRAPixelFormat" to other format,use other API or something?
Could someone have the method? Best Wishes!

Firefox, I would make sure you update your Desktop to Firefox 14.0.1, as the version you are running is quite old and out of date.
Then, do you have your Sync Recovery key, username and password? If you do, you can re-add Firefox Sync to your computer.

I'm going to save my old Hi8 tapes on a hard disk using final cut pro x, to save it for the future. But how shall I export it, and in what will be the best quality to save it in?

I'm going to save my old Hi8 tapes on a hard disk using final cut pro x, to save it for the future. But how shall I export it, and in what will be the best quality to save it in?

Hi Carsten...good luck with your project.. I had just about as many Video8 & Hi8 tapes as
you that I digitized and eventually brought into FCPX..took me many months not weeks
to do so,BTW, as each tape was 60-90 minutes in lenght...and many hundreds of
gigab ytes of storage ( uncompressed AVI files)..it's tedious work unless you plan to farm
it out to a processing house...also regarding eventual storage format...remember
Hi8 is 400 lines or about 540X480 in todays resoultion metrics..you can't make hi-def out
of source that starts out as 400 lines...in my case I rewrapped the avi files into .mov
containers and imported the mov files into FCPX where I got rid of the hundreds of
minutes of Colorado mountain landscapes to get to that one minute shot of the kids
on horseback ( late 80's for most of my archives)..so its a job..scouring thru 30X90 min
of source to not miss those precious memories takes diligence and hard work but its worth
it; eventually I encode the uncompressed video I want to save in H.264 format Staandard
Def not HiDef

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

Indesign export pdf used preset include comment

Is there a way including the summary of the used preset as comment within the exported pdf? Within Acrobat Distiller you have an option called "save adobe pdf settings inside pdf file", is there also such an option available in Indesign?
As a receiver of pdf files, then you have the possibility detecting which preset is used.
Regards,

There is no such option.
Instead, you should use Acrobat Pro's Preflight tools to check for issues like image resolution or colors spaces which are important to your workflow.

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.

"Export Song to Disk" will not create file

So, I've been trying to bounce my GarageBand song for a few days now using the Share>Export Song to Disk option and nothing ever comes out. I uncheck "Compress" and I save it to my desktop, it completes the mixdown and normalizes the track and completes but when I check my desktop, there is nothing there. The project itself is 71.8 MB in size. I have already deleted the com.apple.garageband.plist file from my library but it did not help. Any ideas?

Make sure the file name isn't too long. There's a known glitch where project names longer than around 28 or so characters won't export to disk. That's the only thing I can think of.
Also it won't be on your desktop unless you choose that location when exporting.
Message was edited by: poflynn

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

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

Bug with exporting project to java source

Hi,
This is in TopLink 9.0.4.2 (Build 040311).
We're in the process of trying to determine if we should upgrade our TopLink from 2.5 to 9.0.4, and have not yet purchased a support contract because we haven't made the final decision yet, so I'm posting this bug here in hopes that someone can submit the bug.
In one of our projects, we have an AggregateObjectMapping (AOM) for a Measurement object that is owned by 2 different objects, each with 2 to 4 instances of this Measurement class. I set up the instances of the AOM in the workbench just fine, and looking at the XML descriptors that are written out, it appears fine. Exporting the project session XML file works fine as well. However, when it is exported to a Java file, the instances of the AOM are exported incorrectly as described below.
Here is the abbreviated mapping of the attributes of the Measurement class:
<mappings>
<mapping>
<inherited>false</inherited>
<instance-variable-name>mPrecision</instance-variable-name>
<default-field-names>
<default-field-name>direct field=yPrecision</default-field-name>
</default-field-names>
<uses-method-accessing>false</uses-method-accessing>
<read-only>false</read-only>
<mapping-class>MWDirectToFieldMapping</mapping-class>
</mapping>
<mapping>
<inherited>false</inherited>
<instance-variable-name>mQuantity</instance-variable-name>
<default-field-names>
<default-field-name>direct field=y</default-field-name>
</default-field-names>
<uses-method-accessing>false</uses-method-accessing>
<read-only>false</read-only>
<mapping-class>MWDirectToFieldMapping</mapping-class>
</mapping>
<mapping>
<inherited>false</inherited>
<instance-variable-name>mUnit</instance-variable-name>
<uses-method-accessing>false</uses-method-accessing>
<read-only>false</read-only>
<reference-descriptor>com.cimsoft.lws.units.Unit.ClassDescriptor</reference-descriptor>
<private-owned>false</private-owned>
<uses-batch-reading>false</uses-batch-reading>
<table-reference-mapping-reference-handle>
<reference-handle>
<reference-table>csrSlotGenericValue</reference-table>
<reference-name>csrSlotGenericValue_csdUnit</reference-name>
</reference-handle>
</table-reference-mapping-reference-handle>
<uses-joining>false</uses-joining>
<one-to-one-mapping-indirection-policy>
<indirection-policy>
<uses-indirection>false</uses-indirection>
</indirection-policy>
</one-to-one-mapping-indirection-policy>
<mapping-class>MWOneToOneMapping</mapping-class>
</mapping>
<mapping>
<inherited>false</inherited>
<instance-variable-name>UNDEFINED_MEASUREMENT</instance-variable-name>
<mapping-class>MWUnmappedMapping</mapping-class>
</mapping>
</mappings>
Notice that there are two direct to field mappings (mPrecision and mQuantity) and one OneToOneMapping (mUnit). The exported sessions XML file has the correct XML for instances of this object. Here is an example from a class that has 3 instances of this Measurement object mapped:
<database-mapping>
<attribute-name>mAlarmSize</attribute-name>
<read-only>false</read-only>
<reference-class>com.cimsoft.lws.units.Measurement</reference-class>
<is-null-allowed>true</is-null-allowed>
<aggregate-to-source-field-name-associations>
<association>
<association-key>unitId</association-key>
<association-value>csrStock.alarmSizeUnitId</association-value>
</association>
<association>
<association-key>y</association-key>
<association-value>csrStock.alarmSize</association-value>
</association>
<association>
<association-key>yPrecision</association-key>
<association-value>csrStock.alarmSizePrecision</association-value>
</association>
</aggregate-to-source-field-name-associations>
<type>oracle.toplink.mappings.AggregateObjectMapping</type>
</database-mapping>
<database-mapping>
<attribute-name>mCurrentSize</attribute-name>
<read-only>false</read-only>
<reference-class>com.cimsoft.lws.units.Measurement</reference-class>
<is-null-allowed>true</is-null-allowed>
<aggregate-to-source-field-name-associations>
<association>
<association-key>unitId</association-key>
<association-value>csrStock.currentSizeUnitId</association-value>
</association>
<association>
<association-key>y</association-key>
<association-value>csrStock.currentSize</association-value>
</association>
<association>
<association-key>yPrecision</association-key>
<association-value>csrStock.currentSizePrecision</association-value>
</association>
</aggregate-to-source-field-name-associations>
<type>oracle.toplink.mappings.AggregateObjectMapping</type>
</database-mapping>
<database-mapping>
<attribute-name>mLotSize</attribute-name>
<read-only>false</read-only>
<reference-class>com.cimsoft.lws.units.Measurement</reference-class>
<is-null-allowed>true</is-null-allowed>
<aggregate-to-source-field-name-associations>
<association>
<association-key>unitId</association-key>
<association-value>csrStock.lotSizeUnitId</association-value>
</association>
<association>
<association-key>y</association-key>
<association-value>csrStock.lotSize</association-value>
</association>
<association>
<association-key>yPrecision</association-key>
<association-value>csrStock.lotSizePrecision</association-value>
</association>
</aggregate-to-source-field-name-associations>
<type>oracle.toplink.mappings.AggregateObjectMapping</type>
</database-mapping>
However, here are the corresponding mappings in the exported Java file (with what it really should be manually inserted by me in comments):
     AggregateObjectMapping mAlarmSizeMapping = new AggregateObjectMapping();
     mAlarmSizeMapping.setAttributeName("mAlarmSize");
     mAlarmSizeMapping.setReferenceClass(com.cimsoft.lws.units.Measurement.class);
     mAlarmSizeMapping.setIsNullAllowed(true);
     mAlarmSizeMapping.addFieldNameTranslation("csrStock.alarmSizeUnitId", "unitId");
     mAlarmSizeMapping.addFieldNameTranslation("csrStock.alarmSize", "y");
     mAlarmSizeMapping.addFieldNameTranslation("csrStock.alarmSizePrecision", "yPrecision");
     descriptor.addMapping(mAlarmSizeMapping);
     AggregateObjectMapping mCurrentSizeMapping = new AggregateObjectMapping();
     mCurrentSizeMapping.setAttributeName("mCurrentSize");
     mCurrentSizeMapping.setReferenceClass(com.cimsoft.lws.units.Measurement.class);
     mCurrentSizeMapping.setIsNullAllowed(true);
     mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSize", "alarmSize");
     mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSizeUnitId", "unitId");
     mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSizePrecision", "alarmSizePrecision");
     // should be: mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSize", "y");
     // should be: mCurrentSizeMapping.addFieldNameTranslation("csrStock.currentSizePrecision", "yPrecision");
     descriptor.addMapping(mCurrentSizeMapping);
     AggregateObjectMapping mLotSizeMapping = new AggregateObjectMapping();
     mLotSizeMapping.setAttributeName("mLotSize");
     mLotSizeMapping.setReferenceClass(com.cimsoft.lws.units.Measurement.class);
     mLotSizeMapping.setIsNullAllowed(true);
     mLotSizeMapping.addFieldNameTranslation("csrStock.lotSizeUnitId", "unitId");
     mLotSizeMapping.addFieldNameTranslation("csrStock.lotSize", "currentSize");
     mLotSizeMapping.addFieldNameTranslation("csrStock.lotSizePrecision", "currentSizePrecision");
     // should be: mLotSizeMapping.addFieldNameTranslation("csrStock.lotSize", "y");
     // should be: mLotSizeMapping.addFieldNameTranslation("csrStock.lotSizePrecision", "yPrecision");
     descriptor.addMapping(mLotSizeMapping);
It appears that the actual Measurement descriptor is being modified accidentally as it's being exported, as you'll notice that the first mapping (for mAlarmSize) correctly maps the default "y" to "alarmSize", and then the next mapping (for mCurrentSize) instead of mapping "y" to "currentSize" maps "alarmSize" to "currentSize", and the next AOM maps "currentSize" to "lotSize" instead of "y" to "lotSize".
Thanks,
Greg

No one ever responded, so I'm commenting to bring it up again. It turns out that the error happens not just exporting to Java, but anytime the command-line project generation is used. If the Workbench is used to export either to XML or to a Java file, the file is generated correctly. It is not generated correctly if you try to do it from the commandline (e.g. from a build environment).
This has happened with 9.0.4.2 through the current 9.0.4.5.
Here are different ways I've tried doing it from the commandline, and they all generate the erroneous XML and Java files:
java oracle.toplink.workbench.external.api.JavaSourceGenerator inputMWP outputJava.java
and
java oracle.toplink.workbench.external.api.DeploymentXMLGenerator inputMWP outputXML.xml
which are recommended by the documentation. Also recommended by the documentation:
JavaSourceGenerator.generate( inputFile, outputFile )
and
DeploymentXMLGenerator.generate( inputFile, outputFile ).
From decompiling the management workbench to see what it was doing differently:
MWProject project = WorkbenchSession.instance().openProject( inputFile );
if ( doXML )
project.setProjectDeploymentXmlDirectory( directory );
project.setProjectDeploymentXmlFileName( filename );
project.exportDeploymentXml();
else
project.setProjectSourceRootDirectory( directory );
project.setProjectClassName( classname );
project.exportJavaSource( outputFile );
//Also tried plain old project.exportJavaSource(); which appears to actually do something different.
Any ideas? It looks like a bug to me, particularly that different java or XML deployment files are generated when run from the commandline versus run from the UI. Obviously, the commandline is very important because it is what the build system needs.
Thanks,
Greg

Ps touch exporting projects?

So I have a samsung galaxy note 10.1 and cannot seem to be able to share or export my finished projects? Can anyone help?

What's the desired format and destination?
You should be able to export using the 5th icon from the upper right back out in the project selection user interface. How you will share/export will depend on file format used and destination. (e.g., You can save locally to Gallery/Photos (Android) or Camera Roll (iOS) when saving as JPEG of PNG. You can save to Facebook or Twitter using the "share" command in those formats provided you have those apps installed.)

Problem when exporting a virtual disk backend twice

I have a t5140 server, with two 146G disks.
I have created 2 guest domains ,and want to install solaris for them.
Followed by the Logical Domains (LDoms) 1.0.3 Administration Guide , using the following command to export the second disk as a virtual disk backend multiple times:
ldm add-vdsdev /dev/dsk/c1t1d0s2 vdisk1@priamry-vds0
ldm add-vdsdev /dev/dsk/c1t1d0s2 vdisk2@primary-vds0
but it said:
Device /dev/dsk/c1t1d0s2 already used by another server in guest primary!

I have a t5140 server, with two 146G disks.
I have created 2 guest domains ,and want to install solaris for them.
Followed by the Logical Domains (LDoms) 1.0.3 Administration Guide , using the following command to export the second disk as a virtual disk backend multiple times:
ldm add-vdsdev /dev/dsk/c1t1d0s2 vdisk1@priamry-vds0
ldm add-vdsdev /dev/dsk/c1t1d0s2 vdisk2@primary-vds0
but it said:
Device /dev/dsk/c1t1d0s2 already used by another server in guest primary!

Please help. When exporting a 720p video using Quicktime Conversion in FCP it saves some extra temporary files to my computer. The file is called ICMMultiPassStorage. This file gets so large that eventually the program and exporting process crashes.

Please help. When exporting a 720p video using Quicktime Conversion in FCP it saves some extra temporary files to my computer. The temporary file it saves is called ICMMultiPassStorage. This file gets so large that eventually the program and exporting process crashes. I have been able to locate the file using GrandPerspective and close out of FCP to delete it. But when I try exporting the movie again it creates the ICMMultiPassStorage file again. I have made sure my scratch disks are set to my external hard drive so I know that isn't the issue. How do I fix this problem so these temporary files are not being stored on my internal hard drive instead of my external?Thanks!

Try exporting the timeline "using current settings" via Make QuickTime Movie, then submit that clip to Compressor for the transcode. This should be faster and less painful.

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

1) Export projects to disk using preset or preferred QT compression format?

Similar Messages

Maybe you are looking for