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

Similar Messages

  • 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

  • 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

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

  • 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 import folders from one library to another? My original library has become to large and I want to split it. There is not enough memory to select all the folders I want to move to create a new library.

    I also created a new library and tried file-import but cannot see / access any files in the original aperture library with that command.

    If you use the Command to Export Project as New Library, then such a Library can be imported into another Library with the command to  Import Library/Project.  The first such export as New Library can be the"seed' Library for starting the process.
    But the most important point is there is no performance gain from small Libraries where you think one has become too large, if the new Library is to be on the same disk drive as the original.  My primary library is 1 TB in size, and works as well as tiny test libraries.
    Ernie

  • Exporting Multiple Images from Library - Resized CP4 to CP5 Project

    I am getting corrupt files when attempting to export multiple images at once:
    OS: Occurs on both Win 7 and XP
    Source: CP4 project imported to CP5. Original CP4 project was captured at 1024x768 and later resized to 1024x738.
    1. Open Library Backgrounds folder.
    2. Select more than one background image
    3. Right-click over selected objects
    4. Click Export from the context menu
    'Browse for folder' dialog appears.
    5. Select a folder
    6. Click OK
    Files are created in folder, but are corrupt. When exporting the same images individually, they come out fine. Individual image export file size ends up ~ 2MB each. Multiple image export file sizes end up ~60kb. All are exported as .bmp (not given a choice when exporting multi-select).
    Multiple file export works fine in a new CP5-native project.
    I've reported it as a bug.

    What version of Aperture do you have? This is simple with AP3. Fle -> Export -> Project as New Library. At the far end, Import Library....
    Regards
    TD

  • Export parts of my library (referenced) to be used on other Mac w/ Aperture

    I need to export parts of my library (all items are referenced, none internal) to be used on other Mac with Aperture. So my images, projects and albums shall end up on the other Mac in Aperture. A simple proejct export doe snot do the job as the path to the referenced images are not available on the other Mac. Thus, I need to hand them over within the project, or how?
    How can my workflow look like to be able to do this export?

    Have you tried exporting the items as a new library?
    1) In Aperture 3 select the projects you want to export (you can command-click to select non-contiguously)
    2) Go to File>Export>Items as New Library…
    3) In the following dialog you'll have the choice of consolidating the files in the new library package: do that.
    Once this is done you should have an independent library containing all the needed files. When you've copied this new library to the other computer, you can keep the files managed or simply use Relocate Masters to put them on another referenced drive. It should work.
    Jade

  • Have tried to copy ratings over to a new computer using the export playlist function and this fails... can anyone suggest why?

    have tried to copy ratings over to a new computer using the export playlist function and this fails... can anyone suggest why?

    Because ratings don't travel with the files or the playlist.
    These are two possible approaches that will normally work to move an existing library to a new computer.
    Method 1
    Backup the library with this User Tip.
    Deauthorize the old computer if you no longer want to access protected content on it.
    Restore the backup to your new computer using the same tool used to back it up.
    Keep your backup up-to-date in future.
    Method 2
    Connect the two computers to the same network. Share your <User's Music> folder from the old computer and copy the entire iTunes library folder into the <User's Music> folder on the new one. Again, deauthorize the old computer if no longer required.
    Both methods should give the new computer a working clone of the library that was on the old one. As far as iTunes is concerned this is still the "home" library for your devices so you shouldn't have any issues with iTunes wanting to erase and reload.
    I'd recommend method 1 since it establishes an ongoing backup for your library.
    If you have an iOS device that syncs with contact & calendar data on your computer you should migrate this information too. If that isn't possible create a dummy entry of each type in your new profile and iTunes should offer to merge the existing data from the device into the computer, otherwise the danger is that it will wipe the information from the device.
    If your media folder has been split out from the main iTunes folder you may need to do some preparatory work to make it easier to move. See make a split library portable.
    Should you be in the unfortunate position where you are no longer able to access your original library, or a backup of it, then see Recover your iTunes library from your iPod or iOS device for advice on how to set up your devices with a new library with the maximum preservation of data. If you don't have any Apple devices then see HT2519 - Downloading past purchases from the App Store, iBookstore, and iTunes Store.
    tt2

  • BUG: Library- Export Playlist FAILS to export playlist containing Playlist

    iTunes 8.0.2 now allows “Playlist Folders” to contain other “Playlists” and be included in a “Playlist”.
    To create an env't to demonstrate the BUG create a new playlist called playlistFldrA by selecting File->New Playlist Folder. Move into playlistFldrA and create another File->New Playlist Folder and label it level1. Also create File->New Playlist and label it musicSet1, populate musicSet1 with some songs. Move into level1 and create another File->New Playlist Folder and label it level2. Create File->New Playlist and all it musicSet2, populate musicSet2 with some more songs.
    To replicate the BUG select playlistFldrA and use Library->Export Playlist to export the Playlist called playlistFldrA. Being a legitimate playlist created by iTunes, within iTunes, the export Playlist shouldn't be grayed out. The BUG causes the Export Playlist option to be inaccessible. Playlists: musicSet1 within playlistFldrA and musicSet2 within level1 can be exported, but the BUG prevents playlists: playlistFldrA, level1, level2 and the playlists they contain from being exported by the Library->Export Playlist function.
    When will this BUG be corrected?
    Thanks,
    Peter

    Katrina,
    Thank you for providing the link to the feedback page. Before posting this BUG report I searched apple.com for current instructions on how and where to do so. The feedback page seemed to me to just be just a place to add a feature request to products wish list instead of a place to report a BUG. But I also entered the same BUG description on to that form. Have to wait and see which BUG report apple support acts upon first.
    Thanks again,
    Peter

  • Moved Library & Need To Synch Playlists to New Location

    I relocated my library to a new drive and imported my playlist but the playlist shows the old drive location. For example, my library was on my F:/ drive, now it is on my C:/ drive. When I imported the playlist the locations for the files are still showing F:/
    How can I synch my playlist to the new location?

    Do you have a backup version of the library file that you deleted? If you're not bothered about Date Added and have all the content that you want then I guess it doesn't matter too much but it might be best to start from where you were, rather than where you are now.
    When you export playlists from iTunes it records the absolute paths to each file, so changing the folder you import the playlist from doesn't work. Setting a new media folder path in iTunes and then consolidating to it would have worked. See make a split library portable for the approach I would have taken at the outset.
    If you rename the folder on F: breaking the links from the library you may be able to get iTunes to reconnect to the copies in the media folder on C: otherwise I have a repair tool for broken links.
    tt2

  • 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

  • I lost my old ipod and got a new one, the new one wont receive my playlists from my library. what am i doing wrong?

    new one wont receive my playlists from my library. what am i doing wrong? It looks like they are synched and i have the latest version of itunes on both but the only way to access my music is through the store

    See:
    Syncing to a "New" Computer or replacing a "crashed" Hard Drive: Apple Support Communities
    If all your synced media like apps and music is in your iTunes library then simply:
    - Backup to iTunes.
    - Restore the iPod from that backup.
    For how to do both see:
    iOS: How to back up

  • 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).

Maybe you are looking for