File Sizes Surge with Merger of Aperture an iPhoto Libraries

I merged an Aperture library and an iPhoto library. All went well. However, the resulting file sizes on BOTH new libraries have increased significantly. The iPhoto file size went from ~ 50 gigs to ~144 gigs and the Aperture library went from ~90 gigs to ~ 102 gigs.
I thought I would be able to delete one of the libraries (iPhoto) after the merger, but now that it is so big...I;m not sure what to do.
I can understand the post merger Aperture library getting larger, but why the iPhoto library?
Also, I read that the iPhoto library may contain "originals" and that only versions merged over into the new Aperture (post merger) library. Is that true? If so, what can be done to move over the originals to whicheveer library survives?
Thanks!

How exactly did you merge? And what are your Aperture and iPhoto versions?
Why are there two new libraries after merging an Aperture library and an iPhoto library? Merging two libraries should create one merged library, or am I missing something?
WIth Aperture 3.3 or later and iPhoto 9.3 or later:  If you want to merge an iPhoto library into an Aperture library, you would open the Aperture library and then use "File > Import > Library" and select the iPhoto Library to merge the iPhoto Library into your Aperture library.
The Aperture library should increase in size to accomodate your iPhoto images, but the size of the imported iPhoto library should stay the same.
Also, I read that the iPhoto library may contain "originals" and that only versions merged over into the new Aperture (post merger) library. Is that true? If so, what can be done to move over the originals to whicheveer library survives?
That will depend on the iPhoto and Aperture versions you are using. With any Aperture version later than Aperture 3.3. both the originals and edited versions will be imported into Aperture, when you import an iPhoto library as library to merge it into the Aperture library. Only if your iPhoto library is referenced (the original image files not included in the iPhoto library), then Aperture will also reference these original files and not import them into the Aperture library.  YOu can consolidate the originals later in aperture.
But we need to know, how exactly you merged your libraries to be able to understand, how both libraries increased in size.  Did you not use "File > Import > Library"?
-- Léonie

Similar Messages

  • Merge multiple Aperture and iPhoto libraries into Photos?

    I have around 80GB of material in multiple Aperture libraries, and around 12GB of old material in iPhoto. Is it even sensible to think about holding all this data in Photos, and if so, how is it possible to import multiple libraries? The option to convert an existing library only seems available at first start-up, and is then limited to only one library.

    Yes it is practical - but you have to merge the libraries before converting libraries to Photos - Aperture can do that
    LN

  • HT201340 moving aperture and iphoto libraries

    My aperture and iphoto libraries have consumed my little MacBook. What is the best method for moving all libraries to a different harddrive?

    Make sure the drive is formatted Mac OS Extended (Journaled)
    1. Quit iPhoto and/or Aperture
    2. Copy the iPhoto Library / Aperture Library from your Pictures Folder to the External Disk.
    3. Hold down the option (or alt) key while launching iPhoto. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library. Repeat form Aperture.
    4. Test the libraries and when you're sure all is well, trash the ones on your internal HD to free up space.
    Regards
    TD

  • File size problems with a banner

    I'm working on a banner in Illustrator CS3. It is 2m x .88m (roughly 33.5inches by 79inches) at 300dpi.
    The banner is not complete and I can't save it as a pdf anymore for customer preview- it's too big. It also often reverts to overview and won't redisplay in preview.
    The file has a full size background based on a photographic collage made in photoshop. This was flattened and saved as a pdf to come into Illustrator. There are other photographic objects that have been cut out in photoshop and saved on a transparent background to be placed in Illustrator. All these files are linked not embedded. Some of these have a drop shadow effect. The AI is over 440meg!!
    I'll admit to being inexperienced with developing banners and posters this large. I'm sure I must be handling it all wrong. I know I can merge some layers but I'll lose my ability to move things around. I still need to add some photos over the top.
    I'd really appreciate some advice on handling a project this large. I'm sure it is possible, lots of people are having pop banners this size printed with photgraphic images.
    I'm working on 3.4gig pentium dual processor, 3gig RAM, running Windows XP pro.

    > He says it's probably better to build the whole thing in PS at around 150dpi
    Leonie,
    For future reference, it's a matter of common sense. Generally speaking, the larger the final output format, the lower the raster resolution. Think about it this way:
    Why are things printed big?
    Because they are viewed from a distance.
    Why is 150-300ppi the conventional-wisdom rule-of-thumb?
    Because 150 lpi halftone ruling is a very common halftone screen for process printing viewed at (at most) arm's length. 150ppi means that the square raster pixels are at least as small as the halftone dots, so their square shape won't be evident (in other words, you won't see "the jaggies.")
    Would a 150 lpi halftone screen be sufficient if the page was meant to be read by an ant? No. The ant is much closer. The ant would see a bunch of meaningless large circles. A much higher halftone ruling and therefore a much higher raster ppi would be required--but the page would be much smaller, too.
    So forget this nonsense about 300 ppi raster resolution being needed for everything in print. Consider the optical scaling factor of displays meant to be viewed from a distance. No one makes billboards using 300 ppi raster images printed at 150 lpi halftone rulings.
    JET

  • PDF file size grows with each save if .access property set on a field

    We are seeing an odd form behavior and have isolated the apparent trigger to something we are doing in the form script.  I'm hoping someone can confirm they see the same problem, details follow:
    We have a form generated in LiveCycle.  It contains a text field.  In the docReady event for that field we have javascript which sets the field to be readOnly (TextField1.access = "readOnly").  We reader extend the form so we can save it from reader and/or the plug-in/control which is used by a browser when reading PDFs.
    With that simple form, open the form via the browser (we've tested with both IE and Chrome) and without doing anything else, just save the form (with a new name).  When we do that, the saved copy of the form is significantly bigger than the copy we started with.  If we then repeat the process using the newly saved file, the third copy is bigger than the second.
    This file growth does not happen if you open the file in Adobe Reader (instead of in the browser).
    When we look at the file contents via a text editor, what we have found is that each save via the browser is tacking on a chunk of data to the end of the file AFTER the %%EOF mark.  This new section appears to be one or more object definitions and ends with another %%EOF.  The first portion of the file (prior to the first %%EOF) is identical in all versions of the file.
    If you take a copy of the file that has these extra section added, then open and save it in Adobe Reader, it eliminates those extra sections and you get a 'clean', small version of the file again.  So those extra sections are clearly erroneous and unnecessary.
    Another thing worth noting, we took the script for setting the field access property out of the docReady event and put it as the click event on a button added to the form.  If you then open the form, press the button and save it you see the file growth (but not if you don't press the button.)  So it doesn't appear related to the docReady event, or timing of when we set the access property of the field.
    On the small test form described above the growth of the file is around 13KBytes.  But in testing with our real forms we've found that the amount  of growth seems to be tied to the size/complexity of the form and the form data.  In our most complex form with multiple pages with hundreds of fields and a large amount of XML data (form size is 2+MB), we are getting a file size increase of 700KBytes on each save.  This is a therefore, a significant issue for us, particularly since the process in which the form is used requires the users to save it a couple of times a day over the period of a month or more.

    I would start by exporting the XML data from the form before and after it grows to see if it is the underlying data that is growing and where. Did you define a schema and bind your form fields to a data connection created from the schema? That is always my first step when creating a form. It makes for a smaller saved file not including multiple levels of sub forms in the data structure.

  • File Size - Photoshop With LR or Bridge

    When I open files from LR (Ctrl-E) in Photoshop, LR immediately creates a .tiff file approximately 5 times the size of the original DNG. Then it quadruples in size again when it is converted into a Smart Object.
    Here is what I did:
    From LR Ctrl-E (ProPhoto,.tiff,16-bit). In PS Convert to Smart Object. Save File and the size went from 9.73mb to 175.6mb.
    From Bridge, double click on the same photo. In ACR choose Open Object. In PS Convert to Smart Object. Save File and the size went from 9.73mb to 95.1mb.
    What is going on here? Is there some benefit to having files twice as big for what appears to be the same result in the image?

    I checked, both are 16-bit.
    It appears that an unflattened image processed from LR is much larger than when the same image is processed through Bridge. For example, a 9.5mb DNG becomes a 216.5mb image after Curves, Levels, and Unsharp Mask when processed as a Smart Object in PS. The same file processed with the same adjustments through Bridge is 139.4mb.
    Once the image is flattened, there is little difference in file size whether processed in LR or PS.
    For my work flow, it seems appropriate to commit to the adjustments, flatten, reduce the image size, and convert to 8-bit. The 216.5mb file then becomes a 5mb file. For the rare occasion that I want to reprocess a file, I just have to do it all over again starting from the DNG. This defeats the main benefit of being able to tweak the adjustments using Smart Objects, but my storage demands are greatly reduced.
    For those really rare times when I have a large investment of time adjusting an image, it makes sense to process is through Bridge and save the large file. However, I can see no benefit to opening such an image from LR and ending up with a file twice the size.

  • File size issue with exporting PDF

    We write a newsletter for our daughter's gym and are trying to export a Pages '08 document into a PDF small enough for e-mail. When we export with Best settings the file size is 3.2MB, with Better the file is 4.1MB and with Good the file size is 3.8MB. Why would the lowest quality setting (Good) result in a larger file size than Best?

    Welcome to Apple Discussions
    That does seem odd the "good" export would be bigger. One thing that causes Pages documents to be so big is the graphics. If you pre-process the images to close to the actual size you'll use it will reduce the size of your Pages document. I prefer using GraphicConverter but you could use any image editor such as Photoshop Elements.
    Also, if you do any image manipulation in Pages, it will greatly increase the file size because Pages keeps all of the images in the document package.
    You can also try the "Reduce File Size" filter in ColorSync in the Print dialog. Click "Copies & Pages" > ColorSync & then Reduce File Size under Filters, Then click the PDF button in the lower left of the Print dialog. I don't find that the Compress PDF choice in the PDF menu saves much, if any.

  • Saved file size decreases with time

    Hi all, 
    I am using Data acquisition system with  rate 10000 and 1000 sample per channel (exist 4 channels) to acquire analog voltage signals to measure the amplitude in each channel.
    Moreover the raw signals are saved as TDM file of 1 minute. The system is running continuously for one week. I noticed that after 3 hours the saved file size is decreased as a function of time.
    The size starts with 50 MB/min and after 3hours it became 42MB/min, after 1 day became 11MB/min. That indicated the data was lost , please, what is my programing mistake.
    Thanks
    Solved!
    Go to Solution.
    Attachments:
    Acquisition system.png ‏177 KB

    From the State Zero code, there are several things that could be improved here.
    1. You only need to create the task once before your main loop.
    2. You probably do not even need the outter loop if you use the DAQmx Configure Logging like I have already stated.  And you can use properties to say how many samples to go into a file before moving on, so that part of your code is eliminated.
    3. The display can just be a simple chart (it looks like you are probably already using a chart).
    What is your chart history set for?  That could be causing your slowdown if there are too many data points.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • File Size Reduction With AA 3.0

    Greetings,
    I have an audio file, the quality of which needs to stay intact, that needs to be reduced so I can put it on a WordPress website.(Much like one does to send a picture over email)
    Is this possible with AA 3.0, if yes how do I do it and if no do you have any suggestions?
    Thanks,
    Mona

    To go on a bit from what Ryclark said:
    In fact, there ARE some "lossless" compression algorithms (such as FLAC) the will make your file smaller without compromising quality.  The trouble is, they don't make your files all that much smaller--and the codecs for people accessing your Wordpress blog are far from universal.  If you need a format that everyone can open without messing around, you're pretty much stuck with MP3 as a compromise. 
    If you only need a few people to listen to your file in optimum quality--and if they are willing to download necessary codecs--you can get the software you need from http://www.vuplayer.com/audition.php .  There are other FLAC codecs available for simple playback if you don't need it to plug into Audition.
    However, for universal playback, you're likely stuck with MP3 (which IS a lossy compression system).  You'll have to experiment and use your ears to determine the best compromise between file size and quality.
    Bob

  • File size issues with remote workflow

    Hi everyone
    I am currently reviewing InCopy as a tool for our two 24 page full colour quarterly publications and the problem I am currently facing is the design team are claiming the file sizes would be a problem for us to use the remote workflow - how do you guys manage large files over email? Any tips or advise?
    Also, regarding the layout workflow, does it require a large effort from the design team to divide into individual spreads? As this is another issue.
    We currently have a cumbersum process and would like to resolve asap.
    Would greatly appreciate any advise you may be able to offer
    Thanks in advance

    If you are using a remote workflow ... designers are sending off-site editors InCopy Assignment packages (ICAPs) .... then they need to create assignments in order to package them for the remote InCopy user. So there's no need to split up a layout into smaller files or anything.  An assignment is a subset of the INDD file; multiple assignments -- each encompassing different pages or sections -- are created from the same INDD file.
    When the designer creates the assignment, have them turn off "Include original images in packages"; that should keep the file size down.
    Or -- like Bob said -- you can avoid the whole remote workflow/assignment package rigamarole all together by just keeping the file in a project folder in the Dropbox folder on teh designer's local hard drive, and have them share the project folder with the editors. In that workflow, editors open the INDD file on their local computer and check out stories, just as though they were opening them from a networked file server.
    I cover how the InCopy Dropbox workflow works in a tutorial video (within the Remote Workflows chapter) on Lynda.com here:
    http://www.lynda.com/tutorial/62220
    AM

  • FILE SIZE LIMIT WITH UTL_FILE?

    Hello all,
    is there any file size limit using utl_file on SUSE LINUX 5.3
    (RDBMS 8.0.5)?
    We have created a file with UTL_FILE.FOPEN, put some line into it
    (UTL_FILE.PUT_LINE), and close the file (UTL_FILE.FCLOSE).
    The file size is never greater than 32 kB.
    On 7.3.4 the same procedure works fine with files larger than 1
    MB.
    Thx
    R. Petuker
    null

    Robert Petuker (guest) wrote:
    : Hello all,
    : is there any file size limit using utl_file on SUSE LINUX 5.3
    : (RDBMS 8.0.5)?
    : We have created a file with UTL_FILE.FOPEN, put some line into
    it
    : (UTL_FILE.PUT_LINE), and close the file (UTL_FILE.FCLOSE).
    : The file size is never greater than 32 kB.
    : On 7.3.4 the same procedure works fine with files larger than 1
    : MB.
    : Thx
    : R. Petuker
    Robert,
    There is no limit on the size of the file created using the
    utl_file package. It could be the limitation of the shell
    above which you are working on. You may verify the filesize
    limit of the shell and try it again.
    Maturi
    null

  • File size increase with Camera Raw

    I have a bunch of scanned .tif files. If I open them in Photoshop (cs5) then resave them the file size stays the same. If I open them in Camera Raw then "Open Image" to enter Photoshop, the file size doubles (both the size reported by Photoshop and the  file size if I "save as").
    Any idea why this happens?
    The .tif files are not compressed. The same thing happens if I go through Lightroom.
    Thanks
    Diane

    It's likely you have ACR/LR set to open images as 16 bit rather than 8 bit...

  • Merging pictures from several iphoto libraries in aperture

    I have 5 separate iPhoto libraries becaue of the large amount of picture. Now I want to consolidate all 5 star ***** rated pictures of all 5 iPhoto libraries into one "Aperture Project".
    When I switch Libraries in Aperture I can's see the Library anymore where I want to consolidate some of the photos.
    There should be a way that I can drag pictures for one iPhoto Library to a Project folder in Aperture, switch to a differen iPhoto Library, drag more photos to the Project folder in Aperture, switch to a third iPhoto Library, drag more photos ......   etc.
    Is this possible in Aperture?
    Thanks for any suggestions.

    There should be a way that I can drag pictures for one iPhoto Library to a Project folder in Aperture, switch to a differen iPhoto Library, drag more photos to the Project folder in Aperture, switch to a third iPhoto Library, drag more photos
    You open one library in iPhoto and one library in Aperture, and even drag  images from iPhoto to Aperture, but unfortunately this way you can only drag the previews of the edited versions to Aperture, so you would lose image quality.
    Why not open each iPhoto Library in turn in Aperture, export  your five***** rated images a a new Aperture Library, and then merge this new library into your main Aperture library by importing it? This way you will import the original master image files as well as the adjustments and ratings and don't lose any image quality in the transit.
    Regards
    Léonie

  • Choosing an optimal size ( file size, MB's,tiff or jpg) for iphoto

    I apologize to Old toad and others who have responded. OT seems to be the only one who answers so much. He deserves a standing ovation which i am giving him now.
    But:
    Lets start at the beginning. I am a semi-pro (i do not make my living on my photography) who never used Iphoto but must now because i wish to create a 100 page book.
    I have files mostly tiffs that range from 17.2 to 60 MBs in size ( 3008-5000 /2000-3000 dpi ). I see that Iphoto ad nauseum creates a thumbnail, and a copy of the original photo for each photo. This is not HD friendly.
    How big in pixel size/file size in MB's should the files be so that i do not use so much HD space? Should i just go ahead and drag the files that i have and allow for 5-10 GB of photos to accumulate on my HD? I realize i do not need
    my files so big and that is why i ask here in the forums.
    I realize most of my files are non compressed tiffs,i.e. big in file size.
    What say you? Please be specific. Mention a specific file
    size in MB's please
    thanks

    Glen:
    I've created several books. They were with cameras that produced 1600 x 1200 pixel image files which will give a maximum 300 dpi size of 5.3 x 4 inches. All of my books have been the Storybook theme so the one photo per page is not a full page and I've never run into the warning for low resolution. Possiblly a full 8.5 x 11 photo page would have given me a warning. For the intended use of the books I found them to be very good. My Canon camera's color profile is very close to the Apple recommended sRGB so I've calibrated my monitor with the sRGB profile. Any edits I do with Photoshop CS3 embed the sRGB profile in the resulting file.
    My current camera gives me 2272 x 2704 images. Haven't ordered a book since I've started using it but am in the process of creating one right now.
    It's not the MB size of the file that's important but the number of pixels in the image. For a full page photos, an image size of 3300 x 2250 would meet the optimal 300 dpi of the printing by Apple's suppliers. However, I have no doubt that my current camera's files would produce a good print at that size. That is if I got a good sharp image to start with.
    So a 3300 x 2250 pixel jpg would provide just as good a print as the same sized tiff. Just keep as many pixels in the image as you can. For those good photographers that can do their cropping when they take the image that will maximize the files pixels for printing. I don't have the eye for that. But then my photos are of rapidly changing family situations and I don't have time top compose the picture.
    I asked Apple about the printing and quality of materials used in the books and here's their replay:
    I contacted Apple and asked for information that I could pass on. Here's the reply I received from Apple:
    "Thank you for contacting the Apple Print Products Customer Service.
    I understand that you would like to know the printing process that is used and the color mode the files should be in, so you can better advise users in the iPhoto forum.
    iPhoto version 4 or later, allows you to import and print files through the Apple Print Product service as RGB, grayscale, or CMYK color space. JPEG files with RGB color space are recommended for best results.
    While iPhoto 2 can import files of various formats, including RGB color, grayscale, and CMYK, this version requires JPEG files with RGB color space when printing photos and books.
    For more information regarding iPhoto 2, please visit the following article:
    iPhoto: Color, Black and White Prints Appear Garbled or Distorted
    For more information regarding iPhoto 5, please visit the following article:
    http://docs.info.apple.com/article.html?artnum=165501
    Here are some of the technical specifications for the books, cards, and calendars. I hope this gives you an idea about their quality and form.
    BOOKS
    All iPhoto books are printed using acid-free paper for long-lasting image quality. The photos are printed at a high resolution (300DPI if you use iPhoto 6). There is no external modification--such as sharpening or contrast adjustment--of the photos; what you see in the application is what is printed in the book.
    Hardcovers Books
    The cover is hard-bound and covered in linen. You select the linen color during the book-ordering process. The hardcover books have a solid, stiff binding that is glued and crimped. The internal pages, measuring 8.5 x 11 inches, are printed on McCoy 100# Text Gloss paper stock.
    Softcover Books
    The softcover books come in three sizes:
    - Large 8.5 x 11 inches
    - Medium 6 x 8 inches
    - Small 2.6 x 3.5 inches
    All of the softcover books have internal pages that are printed on McCoy 100# Text Gloss paper stock. The large softcover book has a white cover (Kromekoteplus Folding Cover, 16 point) with a cutout on the front that reveals the cover-page photo in the book. The covers for the medium and small softcover books have the cover image and title printed directly on the cover. All of the softcover books have a glued binding and feature a thick cover of McCoy 100# Cover Gloss paper stock.
    CARDS
    All cards are printed on McCoy 120# Silk Cover paper stock. The postcards measure 4 x 6 inches, and the greeting cards measure 5 x 7inches.
    CALENDARS
    All calendars measure 8 x 10 inches and are printed on McCoy 100# Silk Cover paper stock.
    To ensure the best print quality, we have chosen to use Kodak NexPress technology. The press uses a dry toner, which is fused to the surface of the paper. Please see NexPress' site for more information:
    KODAK NEXPRESS 2500 Digital Production Color Press
    I hope you find this information helpful in answering questions on the iPhoto forum."
    As Apple stated, I hope this information is helpful.
    Do you Twango?
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
    MBP 2.16Ghz; G5 Dual Core 2GHz, 2G RAM ea, 250G HD; G4 Dual 1Ghz, 1.5G RAM;   Mac OS X (10.4.10)   22" LCD, 710G FW HDs, Canon: SD700IS/i850/LIDE 50, Epson R200, 30G iPod, 2G Nano

  • Unify aperture and iphoto libraries: the book (tricky) issue

    I had been in the process of migrating from iPhoto to Aperture for a while now.
    I imported iPhoto library in Aperture few monthes ago and am now using only Aperture.
    Everything is fine for two things:
    - I could not import the books (format is not compatible), so i had to keep the iPhoto library
    - I didn't want to duplicate the orignals , so they are still in iPhoto library
    With Aperture 3.3, the library could be unified with iPhoto
    I would like to move all originals to Aperture library and still be able to open from iPhoto (so far, easy) but also keep the iPhoto books (which as far as i know are still incompatible with aperture books formats)
    In other words, i want one aperture library, including masters, and I want to be able to open it from iPhoto, and still keep the old books (that were built from the initial iPhoto library) in iPhoto
    Any clue ?

    Hi Leonie,
    You're really full of resources (not sure if this french expression translates well in english, but you get the idea) !
    I finally found a way, not the most elegant one, but it's working:
    0. Open each book in iPhoto. Delete in the book non-used photos of the book (in project list, choose book, then choose photos in the toolbar in the bottom, display non placed photos, delete). Now books projects only contain photos actually used in the book. (this step may not be necessary, but it speeds the process)     
    0. bis: Backup your Aperture library. don't forget to stop also any automatic backup process (like time machine)
    1. Open the iPhoto library with Aperture (remember i had already migrated to Aperture 3,3 & iPhoto 9, which makes the libraries compatibles)
    2. Export each of your books as a phototheque (right click on the book in the inspector navigator/ choose export impression project as a phototheque). Give specific name, for example "project x"
    3. Open first created book phototheque in aperture
    4. Tag photos of the phototheque with a specific keyword, for example "book x"
    5. Close phototheque for "book x" and resume on step 3 for other phototheques
    6. Open default aperture Library
    7. Import first phototheque, merge with Aperture Library
    8. Normally you get duplicates, especially if you have added metadata or edited the photos in aperture since you created the books in iPhoto. At least that's what happened to me
    9. You can now grab the recent metadata on the one that was already in Aperture and apply it to the imported one. To do that, create a smart album with the keyword "project x"; then move all new imported events from iPhoto to the event where they belong in aperture. Then in the smart album, for a specific picture when you choose "display in the project" (i have defined a shortcut) you are in the event where the duplicate photo also sits. Choose cmd shift C on the photo with metadata, cmd shift V on the photo with the tag  "project x" to transfer the metadata. You can delete the first one, except if you had edited the original differently in the book and in aperture and want to keep both. You still have to re-enter the faces on the imported one
    10. You can erase the tag "project x"
    11. Go back to step 7 for other books
    12. Check you can see your books in iphoto when opening aperture library with iphoto. You can now consolidate the aperture library and migrate all referenced iPhoto pics inside the aperture library
    13. you can erase iPhoto Library and other books phototheques created in step 2
    You now have one unified library, that you can use in aperture and iPhoto, with your old iPhoto books in it.
    (you also have lost a few hours...)

Maybe you are looking for