Export custom book as new library

I'm trying to move the book I'm working on from a stationary to a portable for presentation.
I'm exporting the custom book layout as new library.
On the portable some of the pages came with a white background where it is black on the original and the background is not editable on the exported version.
The Background button does not contain the original choices and aren't editable at all.
Any bright heads with a solution? Perhaps some prefs should be taken from the stationary but can't find them.

You have the same version of Aperture on both machines? Did you change the size of the book as a medium book will have fewer themes than large. A different theme may offer fewer background choices. I'm not sure if having iLife '11 offers more theme choices like it does for slideshows, but see if you have that on both machines...
Can't really think of anything else. Maybe others have some ideas.

Similar Messages

Export Custom Book Settings?

I created a Custom Book with custom page layouts in Aperture 2. How can I transfer this book layout and page layouts to my other iMac? I don't want to have to create everything all over again.
Kevin

From page 610 of the manual:
You can share your custom themes with other Aperture systems. By default, Aperture saves custom themes in the following location in the Finder:
/Users/username/Library/Application Support/Aperture2/Book Themes/
To share custom themes with another Aperture system:
Copy the themes you wish to share from the Book Themes folder on the first Aperture system to the same location on the other Aperture system.
The custom themes appear in the Themes dialog when you choose Custom from the
Book Type pop-up menu.

How can I export aperture pictures to a new library?

How can I export aperture pictures to a new library? I wan to create a new aperture library at an exernal drive so that I can reduce the size of the current library in the internal drive. Thank you for letting me know.

"File➞Export➞ ... as new Library " will create a new Library from the selection.
The preferred method for making the Library on your system drive smaller is to change some of the Image's Originals from Managed (= stored inside the Library) to Referenced (= stored outside the Library, often on external drives). There are so many advantages to this that it can be recommended without question. Unless you have specific reasons for splitting your Library into two Libraries (security concerns are one of the very few reasons), you should keep your Library on your system drive with some Image's Originals Managed, and the rest Referenced to an external drive.
Read up about these options in the User Manual (scroll down).

How to preserver Face data in Aperture 3.5.1 export to new library ?

In an Aperture 3.5.1 library I add some face names and export smart albums to a new Aperture 3.5.1 library. However, in the new library, when I create a smart album of Faces that include a name I had added in the old library, the album is empty. The face name is a valid name and photos with that name can be seen in the Faces view. How do I properly export albums to a new library so that the new library will allow me to create smart albums based on Face info?
Is this an Aperture 3.5.1 bug ?
Thanks

In an Aperture 3.5.1 library I add some face names and export smart albums to a new Aperture 3.5.1 library.
How did you export the albums to a new library? Like this?
Select the album in Aperture and use the command "File > Export > Album as new library"
Open the exported library in Aperture and all Faces were there with the correct name.
However, in the new library, when I create a smart album of Faces that include a name I had added in the old library, the album is empty. The face name is a valid name and photos with that name can be seen in the Faces view.
Same here. At first, the smart album was empty. I tried all variants of smart rules "Face is", Face includes" etc., and the smart album stayed empty.
Then I simply edited the name label in the Faces stack and reentered the name, exactly as it has been. Also, I clicked the -button and edited the full name again, and that sufficed, for the smart album to populate again.
It looks like Aperture would need to reindex the Faces names.
This looks indeed like a bug.

How do I duplicate the exact playlists from my iphone 4th gen to my new ipod 4th gen 64gb? So far I've created a new library for it, duplicated all the apps, books

I'v been using an iphone 4 (16gb) for a year now, and have just got an ipod touch 4gen, 64gb. I created a new library for this, and most of what I have managed to transfer everything onto the ipod touch. However, although all my music has transferred, the playlists have not. Do I have to transfer them manually? That is, creating every playlist again, which would be a nuisance since I have 48 playlists and almost 250 pieces. All the music have been bought from itunes.
What I plan to use the ipod for is mainly for books, magazines and itunes U podcasts. Most other apps and music will be the same on both iphone and ipod. Both are under my same apple id. Please help, 'cos I've been searching for an answer on the internet and can't really find one. Everything else has transferred expect the playlists.

- Go to settings>Store and sign out and sign into your account.
- Apps are locked to the account that purchased them.
- To update apps you have to sign into the account that purchased the apps. If you have apps that need updating purchased from more than one account you have to update them one at a time until the remaining apps were purchased from one account.

Trying to split large library, I exported a folder of 3000 images to a new library. The new library was created with these images, but it still remained in the original library. How can I remove it from the original library while keeping it in the new l

Splitting a library does not remove the folder I moved from the original library. I exported a folder of 3000 images from the original library to a new library. The new libraryb was created alright, but the folder and the 3000 images remain in the original library. Why? And how do I safely remove them?

The new libraryb was created alright, but the folder and the 3000 images remain in the original library. Why? And how do I safely remove them?
Exporting a library will create a duplicate of the exported library items. Usually you do this to work on a partial library on another computer and later merge the changed images back. Splitting the library is not the primary purpose of exporting.
If you want to remove the library items that you exported, select them in the source list of the library inspector and delete them (File > Delete Original Images and all Versions). Then empty the Aperture Trash, after checking that you did not trash more than you wanted.
But check, if the backup of your Aperture library is in working condition, and check the exported library carefully, before you do such a massive delete.
Regards
Léonie

Iphoto hangs (20 hours) when upgrading from 6 to 11 when writing new library data (Lion 10.7.4) - Can't rebuild because I need to print a finished book - can anyone help?

I startet by having iphoto 6, and the library update did not finish up.
Tried to uninstall iphoto 6 and then install '11 again.
I have back up my library on external.
I have tried to download the tool for preparing an old iphoto library, to see if that helped but no. It is also for version 5 and earlier.
When I try to open 11, it says it needs to upgrade library - I click upgrade - it checks the old library files, creates the new, and I can now see my old album names and so on, but then it hangs (I tried to let it hang for 20 hours now, because it does not say that the program don't answer, it is as if it is still working.
I believe I have around 6-7.000 pictures, but cleaned it recently, emptied the trash (and has also emptied the general trash and downloaded the latest version of Lion, 10.7.4 - even if I had it anyways)
I just bought '11 because I had trouble printing a book I just finished for my weeding in 2 weeks, so I am really keen on getting my library back in full style asap, even if I have to get an older version of iphoto..

Try this: launch iPhoto with the Option key held down and create a new, test library. Import some photos and check to see if the same problem persists. If you can create and run a new library then your current library is the culprit.
In that case make a temporary, backup copy (select the library and type Command+D) and apply the two fixes below in order as needed:
Fix #1
Launch iPhoto with the Command+Option keys held down and rebuild the library.
Since only one option can be run at a time start with Option #1, followed by #3 and then #4.
Fix #2
Using iPhoto Library Manager to Rebuild Your iPhoto Library
Download iPhoto Library Manager and launch.
Click on the Add Library button, navigate to your Home/Pictures folder and select your iPhoto Library folder.
Now that the library is listed in the left hand pane of iPLM, click on your library and go to the File ➙ Rebuild Library menu option
In the next window name the new library and select the location you want it to be placed.
Click on the Create button.
Note: This creates a new library based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments but not books, calendars or slideshows. The original library will be left untouched for further attempts at fixing the problem or in case the rebuilt library is not satisfactory.
OT

Custom book export resolution problem in PDF - only 150DPI!?

I've been using the custom book option and when it came to exporting my PDF I have run into a problem involving the undocumented output resolution of a PDF at a given size. The custom book dialog allows you to create a book with a certain size in inches, but this really has no real meaning since the resolution of that output cannot also be specified in either the layout option or the print dialog. For example is it 150dpi or 300dpi? From some investigation it appears to be locked at 150DPI.
Now I would have thought that Aperture was intelligent enough to just treat the album layout (this is my assumption) as some kind of smart object, where the layout is resolution independent and the final output resolution can be determined when printing to a printer or PDF. In that case the dialog for the setup of the custom size is correct. However, there is no option that I can see in the print dialog to actually specify the output resolution; Aperture is left to its own devices to specify an output resolution, which is undocumented.
I use a printer that accepts JPG or TIF files and I need 300dpi for an album size of 10x13 inches. This equates to 3900x3000 pixels per page. I am able to export to PDF in the print dialog and then used an automator action to export each page of the PDF as JPG and reimported back into Aperture 2 in the same action. In the PDF>JPG conversion option there is the ability to set the DPI to 300. That works fine and the resulting JPG images show as 300dpi (3900x3000px). When looking at the images though they look a little soft, which leads me to believe that my action was simply interpolating a 150dpi image in the PDF into 300dpi.
So to test this, I noticed that if I exported just one page of the album as a PDF and opened the PDF in Preview it does indeed tell you that it is 13x10 inches (no mention of the pixel resolution though). So, you can actually reimport a single page PDF into Aperture and if you do this it appears that the actual resolution is 1950x1500 and that equates to 150dpi for a 13x10 inch layout.
So there are two things that could possibly be going on here:
1. The actual layout of the album is locked at 150DPI and the save to PDF simply takes that and exports a PDF at that resolution.
2. The layout of the album is resolution independent, the size of the album (in the custom dialog) simply controls the aspect of the page layout, and the print dialog (save to PDF) is exporting as 150DPI as default. When I run my automator action (these are the Leopard PDF actions), the save each page to JPG action is up-res'ing the image to 300dpi.
This is where I need help. Is 1 or 2 (or something else?) happening. Also, does the PDF save as JPG12? That too is undocumented.
If number 1 is happening I may have to set my album size to 26x20inches to get a 10x13 inch page at 300dpi.
If number 2 is happening I need to find a PDF/TIFF/JPEG print driver to enable me to export at 300dpi as the print dialog in not standard (and we don't get the nice 'save as' drop down where we could do other things. So far my search has led me to CUPS-PDF, but that still doesn't allow for resolution to be set: http://www.codepoetry.net/projects/cups-pdf-for-mosx
Why can't Apple just figure this thing out correctly and allow the resolution to be specified by the user - what an oversight given all of the feedback requests for the custom album tool. We need 300dpi as a minimum as we can always down-res if we want.
Any ideas? I've got albums to send to clients! Help!
Thanks

When you import any PDF into Aperture, I think it rasterizes any PDF you import to a 150dpi flat image on import, even if it was a high res PDF to begin with. But theres the thing, PDFs don't have dpi (as such). Any shapes or text is a vector so don't have a DPI as they'll scale when printed. The images use their DPI when they were imported from the program that created the PDF.
So I did a quick test and put a page I made from Aperture in to Acrobat and ran a preflight check on all images to check the resolution. It came back at 349.956 ppi, so this example was over 350dpi.
I've attached the screenshot
Jason

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

Trying to export to new library WITHOUT consolidating masters

I am trying to export a project as a new library and I DO NOT want the masters to be included.
But when I export->project as new library and then UNCHECK "consolidate masters into new library" the raw files are still copied over, making the new library very large so I am unable to put it in Dropbox.
The original library is managed. This seems like a bug, since exporting with or without the consolidate option checked makes a library of the same size with the raw files in both.
Is there something I'm doing wrong?

So, the controlling issue here is 'referenced' vs 'managed' Masters. From the manual:
"If your project contains referenced images and you want the master files available to the new Aperture system: Select the “Consolidate masters into exported project” checkbox to copy the original master image files into the new library file."
It doesn't say explicitly, but implies, that unchecking that checkbox allows you to make a new library file without copying the original image files into the new library file. This is in fact how it works in my testing.
Notice it only mentions referenced images. What it doesn't say, but is in fact the case, is that if the images are 'managed' i.e., contained in the library package file, then selecting "Consolidate master into exported project" makes no difference. The original master image files get copied into the new library file whether you want them to or not. This is what happens when I test.
I've confirmed the difference between the two scenarios by selecting my project, going to File, "relocate masters for project...." and moving my master RAW's out of the library and into a folder elsewhere. After doing this, I again select the project, choose "export -> Project as New Library" and it works as expected: I can deselect the "Consolidate..." option and a library is made WITHOUT the Master Raws.
So apparently this behavior when masters are 'managed' is not a bug, it's designed to be that way. This makes no sense whatsoever.
1. Why have the checkbox for consolidating if it doesn't do anything?
2. Why NOT let you create a new library file WITHOUT copying the original master image files, JUST AS YOU ARE ALLOWED TO DO WHEN YOUR MASTER FILES ARE REFERENCED outside the original library?
So the solution is: Do not ever use Managed files. I would have thought that there would be some benefit to having the files stored in the aperture library, but apparently there are actually LESS features available. (All my RAWs are in their own file structure on my RAID in my tower and therefore referenced, but I assumed that it would be easier to just have them be managed on my laptop.)
Always use referenced files on every system and I am then able to transfer projects back and forth between systems without being forced to include the large RAWs.
Thanks for all the input, and if anyone has any insight into whether my conclusions are correct or why this might be so, I'd be grateful to hear it.

When I use Export Project to New Library in Aperture does it create a copy of the images in the new Library?

I am going through my only library now and trying to better organize everything. I am grouping my images into projects by year then cleaning up each year. As I finish a year I use the Export to New Library option to create a library for each year. My question is when I do this and I tell it to Consolidate Masters into exported library does it create copies of the images in the new library as well as leaving a copy in the original library? My goal once I get this completed is to delete the original library but I certainly don't want to lose any of my images. Just looking at file sizes for the libraries I can see that the main library never gets smaller and the new libraries don't really seem large enough to contain everything.
Thanks.

To be honest a 6 year old machine with 4gb of memory and 300gb of disk running Lion and Aperture is not going to give you the greatest performance no matter how you split the library.
You're going to need more disk, What's your backup procedure now? The best performance will be had by getting an external disk putting the masters on it as referenced and having the library on the internal drive.
More memory would be nice but a 6 year old iMac, I think, is maxed out at 4. You'll need to keep other programs running to a minimum when you're working with Aperture.
How much free space is on the internal drive? That will be an issue also. If even with the masters relocated to an external drive cause the internal drive to fill up you'll need to move the library off the internal. If you do that you'll want to go with a FW drive. As long as only the masters are on the external you can get by with a USB but once the library goes out there you're really want to look at FW.
Hope this helps, post back if you have more questions
regards

Export playlist to new Library

I can't seem to find a simple way to export a Christmas Playlist with about 2000 songs to a new Library I created just for Christmas Music. I tried all the import export options, but nothing seemed to work. I could put them in a folder on the desktop and then drag them into the new Library, but is there an easier way??

Here's how I ended up doing it - http://support.apple.com/kb/TA47831

ITunes has stopped automatically syncing new books placed in Library with open file. I have to drag the file to the device to get iTunes to sync the book. Why

iTunes has stopped automatically syncing new books placed in Library with open file. I have to drag the file to the device to get iTunes to sync the book. Why?
Ever since version. 7 iTunes has stopped syncing checked books without dragging them to my iPad. all settings are correct. I have set up 3 new devices and had to direct the new people to drag the books to their iPad. previous to ver. 7 this happened automaticlly just by syncling the device. This issue isn't just on my computer but at least three others. books purchased from apple sync just fine. If is drag the book from the library ad drop it on the device it syncs fine. What a pain if you have added several files now you either have to do the drag drop process for each one as you add it or try and remember which files you added the find them and do the process.
Thanks

Hello BBWEST11,
This may be due to iTunes 11 being set to manually manage content on devices by default.
By default, iTunes 11 and later is set to manually manage your content on your device. Manually managing your device allows you to choose the content you want to have with you.
Managing content manually on iPhone, iPad, and iPod
http://support.apple.com/kb/HT1535
Cheers,
Allen

How do I get custom book themes to appear in Aperture?

I want to create two custom book themes in Aperture - A4 Landscape and A4 Portrait - so that I can print them on A4 photo paper. However, after creating the custom themes, they do not appear in the custom theme list which is preventing me from creating an A4 sized book. I closed and restarted Aperture and I have also closed and restarted my MacBook.
My Aperture version is 3.5.1 and I am running Mac OS X 10.9.1.
Folders for the two custom themes I have created do appear in Users/MacPro/Library/Application Support/Aperture/Book Themes.
Regards
Schof

Folders for the two custom themes I have created do appear in Users/MacPro/Library/Application Support/Aperture/Book Themes.
Schof,
I will try your suggestion of creating a new Aperture library and let you know what happens.
If a new library does not fix it, there is probably a permissions problem with your user library, or a problem with the "Books Theme" folder.
I'd try to trash the "Books Theme" folder:
Quit Aperture.
Delete your "Users/MacPro/Library/Application Support/Aperture/Book Themes".
Log off and on again.
Create a new Custom Book.
Can you now see it in the "Themes" drop-down menu?
If that does not help, trash the preferences as well:
Users/MacPro/Library/Preferences/com.apple.Aperture.plist
and log off and on again, or restart the system.

After lots of tries, and going nowhere, I bit the bait and started a new library

Hi,
After going nowhere with my old B4.1 library, and spending too much time on it, I decided to start fresh, and just export the XMP files, as suggested by several people here.
After a failed attempt at exporting all of the 24,000 pictures XMPs (left the computer doing it at the night but when I came LR had crashed), I decided to export only the last year of photos (where adjustments were mostly made with LR). It took a while, failed to do that for 2 pictures (over 5,500 or so), but it finished.
So, yesterday I moved around the pictures in my HD (a reorder was needed anyway), and start the import... finished today, it gave some problems ("different files had different errors" but the errors were nowhere to be seen, I believe some of them are related to PSD without the compatibility flag, but without the exact error that LR is seeing, it's really hard to know, or worse, to fix it - another thing that IMHO needs to be solved) with some files, but almost all of the photos were in.
I had also been thinking about using DNG for a long while (I always use raw in my camera, a 20D and previously a Digital Rebel)... and this morning I decided to convert all of my library to DNG. It's been working for a big while (Activity Monitor displays 4 hours and a half of CPU time for LR), after a crash when doing the first 1,500 or so. Anyway, it has still maybe 65% of my library to go, so it's going to take easily all day. Fortunately this operation uses several threads/processors, not like the exporting of XMP, that seems to use only one, which is... well... 1/4 of the processing power of my mac :-) (hint hint Adobe!)
Anyway, let's hope tomorrow I can finally start working and seeing the new things that the release version of LR has. Have read some reviews and parts of the manual, and it really looks promising.
Thanks Sean and Geoff for the help with my corrupted library, I still haven't got answer from Adobe customer service (no surprise here, I'm still waiting for response or at least aknowledge from a case I opened almost 15 days ago...), but maybe it's better starting with a new library than reimporting an old one in who knows what conditions...
Regards,
Rodrigo

Well... too late :-)... as I said, it only crashed me once, and I really don't know why. I see that another thread is running, "Acumulating metadata" that I would like to stop, but it doesn't seem to stop. So far everything has been running smoothly, so I expect the 65% that still needs processing will end correctly.
If I get some problem I'll with smaller batches... but I sure hope this ends by itself. I still get the creeps of thinking of going picture by picture as I did some days ago trying to fix my library import issues...

Export custom book as new library

Similar Messages

Maybe you are looking for