iPhoto 5 has become my achilles heel on OS X. It first started having semi-random beachballs soon after importing photos from my wife's Canon SD200, originally on my iMac then later on her eMac. I can consistently recreate it by launching iPhoto then immediately duplicating an image; the next action causes a beachball. I've done almost everything I can think of to permanently repair it (beyond what anyone's suggested when I've asked for help) and have even had temporary success. But the *@#$! problem eventually (and mysteriously) reappears, sometimes without having imported any new photos. There are a few more things left to try but since they're the most time-consuming I'm still procrastinating. My hunch is something in the image files from the SD200 corrupts the library, beyond what a rebuild is capable of fixing.
I don't know if it's a problem with the Canon but some cameras have about 30K of metadata per image which iPhoto then puts into it's library. A few thousand images later it bloats out to a few hundred megabyte. There's much debate on the Apple discussion forums about it.
If you keep thumbnails very small, you also get less problems.
My problem is that it all works fine for me and my Olympus camera but I can switch from iPhoto to another app and then when I go back it beachballs indefinitely. It's just useless. iPhoto 4 was better at everything except for supporting hierarchical folders. That's all I wanted added to iPhoto4, instead they gave us iPhoto5 and it's bizarre interface, slow performance and bugs.
Well, which does "Exclusive Widgets for .Mac members coming soon!" posted on the .Mac page fall under?
That's right.
I think so many widgets came out so fast and caught Apple a little off guard. Hopefully they will think of something else cool to give us. Backup (which I don't need cuz SuperDuper is awesome) and more iDisk space (which is nice) just isn't enough. New widgets or something cool. Come on Apple. You promised.
Oh, and based on this logic, MS has absolutely no blame for any and all security holes in their software. If there's a problem, you should've known better then to use the software. Thus MS isn't the problem, its the billions of windows users.
How you twist my words. Anywhere in my post did I excuse Apple for releasing Tiger with bugs? No, I didn't. Because Apple releases an operating system you can not assume that there are no possible concerns you should consider before upgrading your computer. An intelligent individual does not make ignorant decisions. Inform yourself next time.
I don't know if it's a problem with the Canon but some cameras have about 30K of metadata per image which iPhoto then puts into it's library. A few thousand images later it bloats out to a few hundred megabyte. There's much debate on the Apple discussion forums about it.
Yep, I'm aware of that problem and fortunately I don't have that one.
I've only got ~2100 images in my iPhoto library and my wife's is much smaller, yet we both have the same beachball symptom. That we've both imported SD200 images is the only common denominator I've come up with. And I had no trouble with iPhoto 5 until after I started imported those images. At first I suspected it might be related to video files I'd imported but my wife's never imported any into her iPhoto library.
Quote:
If you keep thumbnails very small, you also get less problems.
Thanks for the tip, I hadn't heard that. I'll try adjusting thumbnails later and see if by some odd chance that makes any difference.
Quote:
My problem is that it all works fine for me and my Olympus camera but I can switch from iPhoto to another app and then when I go back it beachballs indefinitely.
I've had that happen, too. In fact, that's when my last temporarily fixed library started generally misbehaving again (not right after an import) and I haven't attempted fixing it since.
The mystery continues.
Quote:
iPhoto 4 was better at everything except for supporting hierarchical folders. That's all I wanted added to iPhoto4, instead they gave us iPhoto5 and it's bizarre interface, slow performance and bugs.
Yeah, except for nested albums iPhoto 5 has definitely been a downgrade for me. It would be okay for my wife if not for the beachballing.
Thanks for the feedback and good luck with your iPhoto "adventure".
Comments
Originally posted by sjk
iPhoto 5 has become my achilles heel on OS X. It first started having semi-random beachballs soon after importing photos from my wife's Canon SD200, originally on my iMac then later on her eMac. I can consistently recreate it by launching iPhoto then immediately duplicating an image; the next action causes a beachball. I've done almost everything I can think of to permanently repair it (beyond what anyone's suggested when I've asked for help) and have even had temporary success. But the *@#$! problem eventually (and mysteriously) reappears, sometimes without having imported any new photos. There are a few more things left to try but since they're the most time-consuming I'm still procrastinating. My hunch is something in the image files from the SD200 corrupts the library, beyond what a rebuild is capable of fixing.
I don't know if it's a problem with the Canon but some cameras have about 30K of metadata per image which iPhoto then puts into it's library. A few thousand images later it bloats out to a few hundred megabyte. There's much debate on the Apple discussion forums about it.
If you keep thumbnails very small, you also get less problems.
My problem is that it all works fine for me and my Olympus camera but I can switch from iPhoto to another app and then when I go back it beachballs indefinitely. It's just useless. iPhoto 4 was better at everything except for supporting hierarchical folders. That's all I wanted added to iPhoto4, instead they gave us iPhoto5 and it's bizarre interface, slow performance and bugs.
Originally posted by the cool gut
Well, which does "Exclusive Widgets for .Mac members coming soon!" posted on the .Mac page fall under?
That's right.
I think so many widgets came out so fast and caught Apple a little off guard. Hopefully they will think of something else cool to give us. Backup (which I don't need cuz SuperDuper is awesome) and more iDisk space (which is nice) just isn't enough. New widgets or something cool. Come on Apple. You promised.
Originally posted by Louzer
Oh, and based on this logic, MS has absolutely no blame for any and all security holes in their software. If there's a problem, you should've known better then to use the software. Thus MS isn't the problem, its the billions of windows users.
How you twist my words. Anywhere in my post did I excuse Apple for releasing Tiger with bugs? No, I didn't. Because Apple releases an operating system you can not assume that there are no possible concerns you should consider before upgrading your computer. An intelligent individual does not make ignorant decisions. Inform yourself next time.
Originally posted by aegisdesign
I don't know if it's a problem with the Canon but some cameras have about 30K of metadata per image which iPhoto then puts into it's library. A few thousand images later it bloats out to a few hundred megabyte. There's much debate on the Apple discussion forums about it.
Yep, I'm aware of that problem and fortunately I don't have that one.
I've only got ~2100 images in my iPhoto library and my wife's is much smaller, yet we both have the same beachball symptom. That we've both imported SD200 images is the only common denominator I've come up with. And I had no trouble with iPhoto 5 until after I started imported those images. At first I suspected it might be related to video files I'd imported but my wife's never imported any into her iPhoto library.
If you keep thumbnails very small, you also get less problems.
Thanks for the tip, I hadn't heard that. I'll try adjusting thumbnails later and see if by some odd chance that makes any difference.
My problem is that it all works fine for me and my Olympus camera but I can switch from iPhoto to another app and then when I go back it beachballs indefinitely.
I've had that happen, too. In fact, that's when my last temporarily fixed library started generally misbehaving again (not right after an import) and I haven't attempted fixing it since.
The mystery continues.
iPhoto 4 was better at everything except for supporting hierarchical folders. That's all I wanted added to iPhoto4, instead they gave us iPhoto5 and it's bizarre interface, slow performance and bugs.
Yeah, except for nested albums iPhoto 5 has definitely been a downgrade for me. It would be okay for my wife if not for the beachballing.
Thanks for the feedback and good luck with your iPhoto "adventure".