Migration from iphoto 5 to iphoto 9, many problems

Hello!
Sorry for my english!
I just buyed a new mac, the marvellous 13,3 pro.
I have many problems with the migration, between iphoto 9 and iphoto 5.
On the old PB there was a library created with iphoto 5 until june '09. Before these there was another one created whith iphoto 6. Cause an Hard disk crash i was using the original iphoto 5.
After the migration, iphoto 9 shows these strange problems:
- use the old library, (the one created with the 6)with photos and albums before the hd crash;
- shows only miniature (thumbs) of many photos, without showing the large file (but it's present in folder, in the library of the finder!)
- shows only the albums of the iphoto 6 library
I try to re-import the photos from the july 08, but the MB answers "They're already in the library!"
How can i see the photo from july 08 until now?
And how i can transfer last albums ( 2009) from the PB to the MB?
I try to create a DVD with the PB and i make a reimport from the DVD, but after the reimport i still can't see new photos and albums.
thanks to all.
miluleo

Welcome to the Apple Discussions.
How did you get the old Libraries to the new Machine? DId you import them to iPhoto or simply open them with iPhoto?
IF you *did not* import them:
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
Regards
TD
Message was edited by: Terence Devlin

Similar Messages

  • LabVIEW DSC: Migration from 6.1 to 8.6 problems

    Colleagues,
    I need help from someone who experienced with LabVIEW DSC. I would like to recompile pretty old application written in LabVIEW 6.1/DSC 6.1 to LabVIEW 8.6, and got lot of troubles with this.
    At the first I have tried to migrate my old scf file as described here: "Migrating from LabVIEW DSC 7.1 to 8.0".
    Well, it seems to be OK, and LabVIEW.lvlib library with variables was created, but when I tried to double click on the some items, then exception occurred in LabVIEW (see dsc_exception.png in attachment).
    Can you please open test project (attached to this post) and double-click on the Slave005_A0 Item? Is crash happened only by me or by someone else?
    The second problem with understanding.
    In LabVIEW DSC 6.1 I have used "Read Tag.vi" / "Write Tag.vi" vis for accessing the items. When my VI opened in LabVIEW/DSC 8.6, then these calls replaced with "legacy_Write_Tag_(analog)7x.vi" (see screenshot). I'm unable to found according VIs in DSC 8.6. How can I write/read my tags in the latest version? As far as I can understand, I can use Shared Variables directly. Is this correct? But then how can I read multiple tags? Through DataSocket VIs?
    The same with "legacy_Get_Tag_List7x.vi". How can I get items list in DSC 8.6 programmatically?
    Or should I leave all legacy* vis in my application?
    thanks in advance and best regards,
    Andrey.
    Attachments:
    dsc_exception.png ‏26 KB
    dsc_legacy_Write_Tag.png ‏3 KB
    TestProject.zip ‏4 KB

    Hi Andrey,
    Yes, my LabVIEW crashes as well. As you may have noticed, a lot has changed in LabVIEW 8.0 with regards to DSC, the most important being that tags are replaced with Shared Variables. I would recommend that you go through each variable and create them by yourself to ensure the most reliable performance. 
    If you are interested in reading 'tags', then you just need to drag the Shared Variable and place it on the block diagram (that's the direct way). If you are interested in doing this programatically, then have a look at the DSC Module -> Engine Control -> Variables & I/O Servers -> Get Shared Variable List palette on the block diagram. You can then use DataSocket to access the Shared Variables.
    Don't leave the legacy VIs on your block diagram. Upgrade your whole project; shared variables are here to stay. Have a look at the following article to get a thorough understanding of them:
    Using the LabVIEW Shared Variable
    Let us know if you have more questions.
    Adnan Zafar
    Certified LabVIEW Architect
    Coleman Technologies

  • Migration from WLI2.0 to WLI2.1 - problems and solutions

    We have experienced a number of issues when migrating from WLI2.0 (no service packs)
    to WLI2.1 - We are only using the WLPI (BPM) part of WLI. We decided to publish
    these issues in case they can be of help to others.
    Problems:
    1. The documentation (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#998197)
    says the migration process works from WLPI 1.2.1 and from WLI 2.0 (SP2, 3, 4).
    What about WLI2.0 with no service packs - I don't see why BEA should have left
    out migration from that platform. We decided to follow the process and see what
    happened.
    2. There is no indication in the documentation of how to run the GUI based migration
    tools on Unix, only for Windows so we had to follow the manual route.
    3. The Manual process refers (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#999969)
    to the DB variable setting scripts. It then says to run "migratedb.sh". None of
    these files have extensions ".sh" - the files that were installed have no extension.
    Obviously that did not stop us running them but the documentation needs correcting.
    4. The migratedb scripts calls "WLI_HOME/setenv.sh" - it is confusing that there
    is a second copy of this file in the bin folder called "setenv". Why are there
    2 copies. Also I note that the one in bin is executable and the other is not.
    All very confusing!!
    5. The migratedb script fails to run because we have not previously run setDomain.
    This is not documented.
    6. Running setDomain on a domain moved from a WLI2.0 installaion fails since it
    does not contain the expected folders. That basically means you cannot migrate
    such a domain. We carried on with the process using the bpmdomain so that we could
    at least migrate our database automatically.
    7. Having run setDomain, we tried migratedb again but it failed because we had
    not run switchdb. Again, this is not documented. We ran switchdb successfully.
    8. Now running migratedb creates a file called "migrate.sh". Unfortunately the
    script migratedb then attempts to run a file called "migrate". This is evidence
    that no-one has ever tested this script at BEA and we are very disconcerted by
    this fact!! We renamed the script and ran migratedb again - this time it ran the
    migrate script.
    9. This still fails with the following errors (when calling migrateCommonRep)
         -v (No such file or directory)
         null
         java.lang.NullPointerException
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:120)
         at com.bea.eci.migration.Migrate.getConnection(Migrate.java:207)
         at com.bea.eci.migration.Migrate.main(Migrate.java:73)
         java.lang.NullPointerException
         at com.bea.eci.migration.Migrate.main(Migrate.java:192)
    10. It also fails because it cannot find "sqlplus" - a fatal problem - we do not
    have sqlplus installed on the same machine as WLI and yet again this requirement
    is not documented. At this point we gave up trying to run the migrate script as
    there seemed to be no route forward.
    The process we took to move from WLI2.0 (WLPI only) was as follows:
    a. Since we had done no changes to filerealm.properties we simply copied the one
    fron bpmdomain into our own domain.
    b. We have been unable to run the step to migrate the common repository (see note
    9). If this is referring to the XML repository then that should not be a problem
    to us as we have not used it.
    c. We moved the "migrate/BPM_20SP3-21.sql" script to an NT machine and ran that
    script on our database. This seems to have successfully updated the database.
    Lastly, having completed the migration process we tried to run the server but
    it fails. This is because the startWeblogic script fails to call checkdomain properly.
    We modified the line to become:
         ". $WLI_HOME/bin/checkdomain"     # the '.' was missing
    Does anyone else have any experiences with this that would help us all?
    Pete

    Pete,
    Please post this to the weblogic.integration.interest and weblogic.integration.developer newsgroups?
    Pete Edwards wrote:
    We have experienced a number of issues when migrating from WLI2.0 (no service packs)
    to WLI2.1 - We are only using the WLPI (BPM) part of WLI. We decided to publish
    these issues in case they can be of help to others.
    Problems:
    1. The documentation (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#998197)
    says the migration process works from WLPI 1.2.1 and from WLI 2.0 (SP2, 3, 4).
    What about WLI2.0 with no service packs - I don't see why BEA should have left
    out migration from that platform. We decided to follow the process and see what
    happened.
    2. There is no indication in the documentation of how to run the GUI based migration
    tools on Unix, only for Windows so we had to follow the manual route.
    3. The Manual process refers (http://edocs.bea.com/wlintegration/v2_1/migrate/4zubemig.htm#999969)
    to the DB variable setting scripts. It then says to run "migratedb.sh". None of
    these files have extensions ".sh" - the files that were installed have no extension.
    Obviously that did not stop us running them but the documentation needs correcting.
    4. The migratedb scripts calls "WLI_HOME/setenv.sh" - it is confusing that there
    is a second copy of this file in the bin folder called "setenv". Why are there
    2 copies. Also I note that the one in bin is executable and the other is not.
    All very confusing!!
    5. The migratedb script fails to run because we have not previously run setDomain.
    This is not documented.
    6. Running setDomain on a domain moved from a WLI2.0 installaion fails since it
    does not contain the expected folders. That basically means you cannot migrate
    such a domain. We carried on with the process using the bpmdomain so that we could
    at least migrate our database automatically.
    7. Having run setDomain, we tried migratedb again but it failed because we had
    not run switchdb. Again, this is not documented. We ran switchdb successfully.
    8. Now running migratedb creates a file called "migrate.sh". Unfortunately the
    script migratedb then attempts to run a file called "migrate". This is evidence
    that no-one has ever tested this script at BEA and we are very disconcerted by
    this fact!! We renamed the script and ran migratedb again - this time it ran the
    migrate script.
    9. This still fails with the following errors (when calling migrateCommonRep)
    -v (No such file or directory)
    null
    java.lang.NullPointerException
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:120)
    at com.bea.eci.migration.Migrate.getConnection(Migrate.java:207)
    at com.bea.eci.migration.Migrate.main(Migrate.java:73)
    java.lang.NullPointerException
    at com.bea.eci.migration.Migrate.main(Migrate.java:192)
    10. It also fails because it cannot find "sqlplus" - a fatal problem - we do not
    have sqlplus installed on the same machine as WLI and yet again this requirement
    is not documented. At this point we gave up trying to run the migrate script as
    there seemed to be no route forward.
    The process we took to move from WLI2.0 (WLPI only) was as follows:
    a. Since we had done no changes to filerealm.properties we simply copied the one
    fron bpmdomain into our own domain.
    b. We have been unable to run the step to migrate the common repository (see note
    9). If this is referring to the XML repository then that should not be a problem
    to us as we have not used it.
    c. We moved the "migrate/BPM_20SP3-21.sql" script to an NT machine and ran that
    script on our database. This seems to have successfully updated the database.
    Lastly, having completed the migration process we tried to run the server but
    it fails. This is because the startWeblogic script fails to call checkdomain properly.
    We modified the line to become:
    ". $WLI_HOME/bin/checkdomain" # the '.' was missing
    Does anyone else have any experiences with this that would help us all?
    Pete--
    Developer Relations Engineer
    BEA Support

  • Migrate from Lightroom 3 to Aperture 3 - Problems with DNG

    Hello : )
    I will migrate from Lightroom 3 to Aperture 3. I've tested Aperture for a while and I like it, but I have one problem. If I import DNG files, I lost all the settings I've made in Lightroom, except Metadata. Is there any way to import DNG files and get all the settings? If not I think a migration to Aperture will not be possible to me, because I've over 50.000 DNG files and I don't want to convert them to tiff or other formats and lost all the benefits of the RAW files.
    Thanks
    derRabe

    Look at the video below- I think it will solve your problem.
    http://www.youtube.com/watch?v=7R4HgOZ3oBc

  • Migrating from Aperture to iPhoto

    I no longer wish to use Aperture because I much prefer the ease of functionality and simplicity of iPhoto.  How can I transfer my entire Aperture library to iPhoto?  Thereafter I will uninstall Aperture.
    Thank you
    Kate

    Which iPhoto version do you have? If your Aperture and iPhoto versions match, you can simply open your Aperture library in iPhoto. The library format is the same and no need to transfer anything.
    In iPhoto 9.6 you would simply launch iPhoto, use the "File" menu. File > Switch to Library, then select your Aperture library from the library chooser panel and you are done.
    See this support document:   Aperture 3.3: Using a unified photo library with iPhoto and Aperture
    There is no need to uninstall Aperture. It will not save much space, and even if you want to use iPhoto from now on, you can always open your iPhoto Library in Aperture, if you want to use an advanced editing option or need to repair links to missing original files or similar.

  • After migration from sccm 2007, there are many systems with no client installed

    Hi Everyone,
    We have migrated our environment from SCCM 2007 to SCCM 2012 , And Manual client push installation has been done by HeadQuarter SCCM admins on site code of our region.
    But as i see , in all systems collection based on OU, there are approx 50% systems with no client installed.
    There may be some stale systems in AD.
    Is there any way so that i can list out all Stale or old computers which are not in use anymore records of systems from Active directory and so that i move them to OU for which system discovery is not enabled.
    Also, it will very useful if i get more information on lastLogonTimeStamp and such more properties which specifies system as stale or OFF the network for some period..

    You could also remove the objects without a client and adjust the settings in the
    Options tab of the Active Directory System Discovery Properties. By tweaking those options you can make sure that you're not discovering those old objects in the first place.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Migrating from NIS to JDS 6.3 - problems with addNISObject

    I'm trying (again) to transfer our NIS maps to the LDAP server using the inityp2l command.
    This seems to work. It sets up the NISLDAPmapping and the /etc/default/ypserv files, but when I run ypserv -Ir, I get the following errors:
    Mar 30 15:45:14 sun34 ypserv[6260]: [ID 473756 user.error] addNISObject: ldapAdd error 32 (No such object) for (dn: dc=starfleet,dc=example,dc=com)
    Mar 30 15:45:15 sun34 ypserv[6260]: [ID 473756 user.error] addNISObject: ldapAdd error 32 (No such object) for (dn: dc=com)
    Mar 30 15:45:15 sun34 ypserv[6260]: [ID 556977 user.error] addParent: Unable to create parent (dn: dc=com) of (dn: dc=example,dc=com) in the DIT
    Mar 30 15:45:15 sun34 ypserv[6260]: [ID 556977 user.error] addParent: Unable to create parent (dn: dc=example,dc=com) of (dn: dc=starfleet,dc=example,dc=com) in the DIT
    Mar 30 15:45:15 sun34 ypserv[6260]: [ID 572537 user.error] Could not make nisDomain object for starfleet.example.com
    Now, I've looked for the nis attributes in the LDAP server, and I can't find any. Do I have to manually add all of the nisObject classes? I used the ldapsearch command giveni n the following site here.
    I still get nothing when I use the following command:
    ldapsearch -b cn=schema objectclass=* | grep nisDomainObject Anyway, it looks like the LDAP server instance in JDS 6.3 doesn't include any nis object classes at all. Following the instructions in the documentation results in the errors above.
    Interestingly, the errors log has the following entry (which leads me to assume that JDS 6.3 does not include nis object classes):
    [30/Mar/2009:13:28:49 +0100] - ERROR<5894> - Schema - conn=10 op=1 msgId=2 - User error: Entry "dc=example,dc=com" has unknown object class "nisDomainObject"
    Note that I had to add that objectclass myself.
    Any ideas?
    Thanks
    Edited by: cannonac on 30-Mar-2009 15:53

    You've done it again. I have to say, I'm new to this but I thought, and the documentation doesn't really give much of a clue, that idsconfig was meant fo iPlanet Directory Server 5.x, not JDS 6.x. That's why I hadn't done anything with it.
    Thank you for all the help you've given me with this install. I'd be bald with frustration now if it wasn't for your help.
    Andy

  • Migrating from Windows (Adobe PE + Bridge(?)) to Mac (iPhoto + Adobe PE)

    I have a family member who is thinking about switching from Windows to a Mac. She is currenlty using Adobe stuff on Windows (PE 4) where she edits and organizes her photo's.
    I've set her up for trial with one of my Macs with PE 4 installed. Now the question is, will she be using iPhoto or Adobe Bridge on the Mac and what is more important, how can she migrate in either situation?
    Personally, I think iPhoto/PE is the best solution, but how should she migrate her Windows photo database to het Mac and might migrating to Adobe bridge not be easier?

    Gerben:
    If Photo Bridge can write the metadata, primarily the keywords, to the files then importing the folders that the file are located in will create rolls in iPhoto with the same title as those folder. Also the keywords should be read by iPhoto and included in its database.
    As you know iPhoto is a image management application but one with the additional features of slideshows, books,etc. It can group photos by whatever criteria the user want. Bridge is primarily a browser type application.
    To migrate her Windows photos to iPhoto she should first copy the folders of image files to the Mac. Then download and run BatChmod on each folder with the settings shown here, putting your administartive name in the owner and group sections. You can either type in the path to the folder or just drag the folders into that field. This will assure that the permissions/ownership are properly set before importing into iPhoto.
    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.

  • Migrating from iPhoto 5 to iPhoto '11

    I have experienced many problems moving from an iMac G5 PowerPC to a new iMac Intel, particularly in relation to iPhoto where I was using iPhoto 5 (Vn 5.0.4) on my old machine and iPhoto 11 (Vn9.1.1) on the new.
    Having decided against using  Migration Assistant  I  tried several of the workarounds on various message boards. However whilst I was able to import my 26,000 images into my new Mac, all titling (i.e. names) on them disappeared in the transfer.
    I found a way around the problem. My suggestion is  to EXPORT  each of the album folders in turn from iPhoto 5 to an external hard drive (EHD) on which you have created a new folder with the same name as the album you are exporting. So if your iPhoto album is called "Greek Holiday" create a folder with that same name on your EHD.  Then in iPhoto 5 go to Share > Export Photos. In the window that comes up, keep Format as Original, check Full Size Images and  Use Title and also check Use Extension. (Ensure that every image has a title i.e. the 'name' section in info is not blank, before you start or this won't work!) Click Export and choose the newly created folder on the external hard drive.
    Once that is done, step two is to disconnect the external hard drive  from the old iMac and connect it to the new one. Open iPhoto in the new machine and go to File > Import To Library. Select the appropriate file on the external hard drive and iPhoto imports the images and, more importantly, their titles!
    It is a slow process and may take a few hours but far better than renaming 26,000 images! Note that  neither 'star rating' data nor original camera file name (e.g. image XXX) is transferred this way but everything else is including camera data.
    I also had problems moving my music from iTunes 7 to the newer iTunes 10. First time I moved all the relevant files from the old machine to the new one, I discovered that my album sleeve images didn't come with them. The simple answer to this is to open the old  iTunes and go to   > Advanced > Consolidate Library before transferring all the relevant files to the new machine, ideally via an external hard drive.
    Having been a Mac user for over twenty five years (though still not a 'Techie"!) I feel the the company has not managed the move from older Power PC machines to Intel machines as well as it might have done. Migration Assistant usually brings across lots of files which just won't work with the Intel processor and indeed which may even hinder its operation, as my wife discovered when I used it on hers. Far better to have a clean install!

    Thanks - time machine already up and running. I will also duplicate library and copy that to external drive.
    I tested the process of migration on my Macbook (where I have just a few test pictures - my main library is on my iMac). It all seemed to migrate fine. I then merged library with Aperture and everything seemed to transfer across - including Descriptions nicely migrating to Caption metadata. Quite impressed.
    I am able to switch between iPhoto and Aperture library with ease in both applications. Nice!
    Will try it for real later in the week and report back success or issues for the benefit of any other user who is contemplating the same thing.
    Cheers all,
    Simon.

  • Missing photos after migration from iPhoto to Photos

    Last week I upgraded my desktop MacPro from OS 10.9.latest to OS 10.10.3. When I first opened Photos, it did the migration from iPhotos without apparent problem. But I have noticed that many (hundreds at least) of the photos from my pre-migration iPhoto library are now not in Photos. I mounted my pre-upgrade backup drive on a laptop running OS 10.9.latest, and can find specific missing photos OK on the backup. But if I search the main drive on my desktop Mac, for example for "P1440608", I get no results. I have tried rebuilding the Photos library with no change - the missing photos are still missing.
    One option is to erase my MacPro main drive and restore from the backup drive to OS 10.9.latest. This should put me back to where I was. Is there a viable alternative? Please note that my iPhoto version was 8.1.2. It will not open in OS 10.10.3, and the App Store will not let me upgrade to the most recent version. I do have Time Machine plus external bootable (SuperDuper) backup of the desktop MacPro, plus that laptop running OS 10.9.latest as resources available.

    Apply the two fixes below in order as needed:
    Fix #1
    1 - launch iPhoto with the Command+Option keys held down and rebuild the library.
    2 - run Option #4 to rebuild the database.
    Fix #2
    Using iPhoto Library Manager  to Rebuild Your iPhoto Library
    1 - download iPhoto Library Manager and launch.
    2 - click on the Add Library button and select the library you want to add in the selection window..
    3 - Now that the library is listed in the left hand pane of iPLM, click on your library and go to the Library ➙ Rebuild Library menu option.
    4 - In the next  window name the new library and select the location you want it to be placed.
    5 - 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

  • How do I continue a migration from iPhoto to Photos that was interrupted part way through?

    I began a VERY large migration (40k+ photos) from iPhoto (v9.6.1) to Photos on an external hard drive.  I have a MacBook Pro with Yosemite 10.10.3 that is connected to a network that has a Synology network drive.  The iPhoto library is on that drive and I was wanting to create the Photos library also on the drive.
    The process was very slow and has taken days, but that is expected and it was definitely making progress (I could see the files being added over time). Unfortunately, the transfer was interrupted part way through (my kid closed my laptop, which disconnected it from the network). I tried to start it over with the partially created Photos library folder as the destination, hoping that it would pick up where it left off.  It worked until it reached the same files that were previously created. The migration stopped at that point, and the following error appeared: "Photos was unable to make a copy of your library before preparing it. There were file system or hardware issues…”  I assume the inability to overwrite previous files with the same names was the case of the "file system or hardware issues."
    Is there any way to either continue the migration from where I left off, or maybe even manually move the rest of the files over? Or do I have to wipe out the entire partially migrated Photos library and start over?

    You probably will have to start over
    And I suspect that you are incorrect - as far as I know NO NAS is formatted Mac OS extended - A NAS is basically a Linux computer with no display or keyboard that uses a Linux format drive - a headless computer
    Unless you have a directly connected drive correctly formatted you are cgoing to continue to have issues - your photos and your choice what risk you put them at but you are treading in very dangerous water with you set up - is it documented not to work and similar set ups have been reported here hundreds of times as causing major problems and losing lots of stuff
    LN

  • Migrating from Windows Photoshop Elements to iPhoto '08

    I recently got a Mac and I'm looking into migrating from Windows Photoshop Elements 6.0 to iPhoto 7 ('08).
    I've seached this forum, but I didn't find any detailed tips, tricks and recommendations on how to do the migration. I know about the PE (Photoshop Elements) command to write keyword information into the files (something like File->write tags to file). Someone (IIRC Barbara B.) also mentioned something about scripts to make the transition smoother, although I haven't seen any detailed information on what and where these scripts are. Basically, I'd like to hear from users who have migrated from Windows Photoshop Elements. I have thousands of pictures and prior planning can save me lots of time.
    Some questions:
    1. Photoshop Elements has a tagging feature, which is similar to iPhoto's keyword feature. Not sure how iPhoto will process the keywords. Do I just import the pictures into iPhoto and iPhoto will recognize the keywords? Should I create the keywords in iPhoto ahead of time prior to import (using names that exactly match Photoshop tag names) ?
    2. In PE, I've assigned captions to pictures. Can iPhoto read the captions and treat them as titles or descriptions?
    3. In PE, I've assigned ratings to pictures. Can iPhoto read them, or do I need to manually redo the ratings in iPhoto?
    4. One PE feature that I will really miss is hierarchical tags (e.g. Family->Kid's name). (Aside: everyone, please put in a request to Apple to support this feature!!) While I would prefer a native iPhoto feature to support hierarchical tags, I saw that there are 3rd party plugins available. What's the best one in terms of features and long term support/viability? Is it Keyword Manager?
    5. Any easy way to translate my PE Album definitions when migrating to iPhoto? I assume I would need to recreate them from scratch based on keywords and optionally ratings?
    6. I'm afraid to ask this next question (and I'm sure this is worthy of many separate threads). I'm still grappling with the concept of Events. In my mind, an event is something "monumental", and I've used Albums in PE for these "monumenal" events. A large percentage of my pictures don't really fit into a "monumental event" categary. Instead, they are pictures that were taken in a random/candid manner. Or, I might have pictures that are truly events, but maybe only 1 or 2 pictures would fit into an event. If I started using iPhoto from the very beginning, it may be easier to deal with the concept of events. However, I already have thousands of pictures. I'm wary of importing all my pictures in one shot (rather than on a per "event" basis), since it may result in hundreds of events, which, IMO, wouldn't provide much organizational value. Anyone have any tips/philosophical opinions on how to deal with events when thousands of pictures need to be imported? Someone (T.D.?) mentioned they organize by year for older pictures. Any suggestions?
    Thanks!

    randman
    Can't answer all your questions, but I'll have a go at a couple.
    1. Photoshop Elements has a tagging feature, which is similar to iPhoto's keyword feature. Not sure how iPhoto will process the keywords. Do I just import the pictures into iPhoto and iPhoto will recognize the keywords? Should I create the keywords in iPhoto ahead of time prior to import (using names that exactly match Photoshop tag names) ?
    If you write the tags to the file then iPhoto will recognise them as part of the IPTC data. There is no way to create tags in advance.
    2. In PE, I've assigned captions to pictures. Can iPhoto read the captions and treat them as titles or descriptions?
    Can Elements write these to the IPTC data? If so, iPhoto should read them. A little trial will confirm.
    3. In PE, I've assigned ratings to pictures. Can iPhoto read them, or do I need to manually redo the ratings in iPhoto?
    No, the IPTC data does not recognise ratings.
    4. One PE feature that I will really miss is hierarchical tags (e.g. Family->Kid's name). (Aside: everyone, please put in a request to Apple to support this feature!!) While I would prefer a native iPhoto feature to support hierarchical tags, I saw that there are 3rd party plugins available. What's the best one in terms of features and long term support/viability? Is it Keyword Manager?
    Keyword Manager is the way to do this.
    5. Any easy way to translate my PE Album definitions when migrating to iPhoto? I assume I would need to recreate them from scratch based on keywords and optionally ratings?
    What do you mean by "album definitions"?
    About Events:
    Don't get hung up on a word. They could have as easily called them 'trousers' and it would make almost as much sense
    An 'Event' is an import that is automatically divided into folders depending on the criteria you set in the iPhoto Preferences.
    Events in the iPhoto Window correspond exactly with the Folders in the Originals Folder in the iPhoto Library package file (Right click on it in the Pictures Folder -> Show Package Contents).
    You can move photos between Events, you can rename Events, edit them, create them, as long as you do it via the iPhoto Window. Check out the Info Pane (wee 'i', lower left) the name and date fields are editable. Edit a Event Name using the Info Pane, the Event Folder in iPhoto Library/Originals will also have the new name.
    So, really an Event is a Folder.
    For my money, Events are a very limited way of organising photos. They are strictly date and time based. As time goes by I consolidate them - Spring 06, Summer 07, America 08 (I do this as we have three cameras feeding the Library).
    I organise using Albums, Smart Albums and Keywords.
    Albums (Smart or otherwise) are virtual entities. Unlike Events, they reference files on the HD, so a pic can be in 1,10 or 100 Albums with no extra disk space used. (To have a pic in two events requires two copies of the files.) They are infinitely flexible and offer a much richer set of possibilities.
    How have you your photos organised currently? In folders? On what basis? If you can explain how that works we may be able to help you recreate this system in iPhoto.
    Regards
    TD

  • Migrating from iPhoto 08 (v7.1.5) to iPhoto 11 (v9.3)

    Greetings iPhoto gurus,
    I currently run iPhoto 08 (v7.1.5) and I have an extensive library of pictures, albums and slideshows. I'm considering upgrading to iPhoto 11, but will only do so if it will retain and migrate all my current stuff. In the process of upgrading, will the resulting iPhoto 11 library contain all the slideshows, albums and metadata (particularly the Description field which I have made extensive use of and do not fancy retyping for several hundred piccies) be migrated?
    I also have the latest version of Aperture (v3.3) which I have only just started to use. What prompted this query is that I now see that Aperture v3.3. and iPhoto 11 v9.3 can share the same libraries without exporting/importing, which is obviously appealling to me.
    My ultimate nirvana is being able to merge the migrated iPhoto 11 library with my current Aperture library so that I can have one database with all my legacy pictures, slideshows and metadata alongside the new stuff that I have been populating since procuring Aperture.
    Can anyone advise on:
    1) Will migrating from iPhoto 08 to iPhoto 11, as described above, work?
    2) Will I be able to merge the resulting iPhoto 11 library with the Aperture 3.3 library?
    Many thanks in anticipation.
    Simon.

    Thanks - time machine already up and running. I will also duplicate library and copy that to external drive.
    I tested the process of migration on my Macbook (where I have just a few test pictures - my main library is on my iMac). It all seemed to migrate fine. I then merged library with Aperture and everything seemed to transfer across - including Descriptions nicely migrating to Caption metadata. Quite impressed.
    I am able to switch between iPhoto and Aperture library with ease in both applications. Nice!
    Will try it for real later in the week and report back success or issues for the benefit of any other user who is contemplating the same thing.
    Cheers all,
    Simon.

  • I have copied Iphoto library from other MAC using the migration assistant, when starting Iphoto the rebuild however stops half way (no progress after 24 hours)

    Using the migration assistant I copied my users from an old MAC (2007) to a brand new on. After a few attempts and software updates this worked. For Itunes and mail for example all data was available. On starting my Iphoto however there was a problem. When starting there is the message that the library, to be able to work with the new Iphoto Version, needs to be updated. In the process of doing this the programm seems to get stuck after 40 % of progress and even after 24 hours does not continue. I have tried to use the I-Photo First aid, but before starting any of the steps it wants to re-allign the old library to the new Iphoto version ans subsequently get's stuck on the same spot again !! Is there any advice you could give ?
    Thanks,
    John 

    I have tha same problem.
    iPhoto asks for updating, then it shows a bar about the conversion in progress, then it shows that it is working on faces library and then the circle spot stop to turn on faces library and starts in the middles of iPhoto window.
    After three days nothing changed!
    Any help?

  • HT201386 migrating from IPhoto to Photos

    Since I accepted migrating from IPhoto to Photos, both applications gave up working and the quit as soon as I open them. Could you olease help me? Thank you!

    You were asked to sign a non-disclosure agreement when signing up for the beta program:
    CUSTOMER SEED AND CONFIDENTIALITY AGREEMENT
    OSX Beta Program FAQs>
    The NDA prohibits you from discussing software beta issues here or anywhere else. The two documents above describe how to submit problem reports  to Apple.

Maybe you are looking for