Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'fix iphoto and avoid Nikon? I think not...' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
fix iphoto and avoid Nikon? I think not...
Authored by: dmayer on Aug 23, '05 02:02:14AM

I agree that stripping the exif data isn't necessarily a good idea, although most iPhoto users likely won't miss most of this info. If I'm not mistaken JPEGs have a header with this info anyway (for use by the software).

But as for "avoid[ing] these types of cameras...Nikon in particular", I think you are WAY off the mark. Disclosure: Yes, I use two digital Nikons (with different RAW formats!), and yes I use iPhoto (but not as my main cataloguing program). I also use Nikon's software Capture in addition to Photoshop CS2, and all this is running fine on my mac, thankyou. I have no problems with the loading of iPhoto5 with thousands of photos (all Nikon, some NEF/Raw), although I almost abandoned iPhoto in previous versions because of how bogged down things got with large libraries. The new version has so far fixed this for me.

So, which software of Nikon's doesn't run on the Mac?

As for Nikon "threatening to use the DCMA", can you post a link where Nikon actually says this? Adobe has an issue with the D2x encryption, and that issue is basically a legal liability issue courtesy of DCMA, but that doesn't mean Nikon is the one trying to throw their weight around. And Nikon is not the only company to encrypt their RAW data. See www.openRAW.org for a thorough discussion of this issue. To put it another way, RAW data from any camera manufacturer is not open source but proprietary. If you choose to avoid a company for not using open source only, you wouldn't be using a Mac for one thing.

If you have thousands of photos, you might consider using another program for cataloging. The way iPhoto stores edited versions and originals tends to add up to a lot of disk space very quickly. And iPhoto (previous versions at least) stripped a lot of exif data anyway, meaning if you wanted to preserve this data you needed to import your photos another way for backups, which meant even more disk space. I personally use PhotoMechanic (not perfect, and very pricey), and reserve iPhoto for updating my .mac web pages and making photobooks.

If iPhoto is running slow, consider another workaround, that is to use multiple libraries and an app like iPhotoLibraryManager. I have used this since previous versions of iPhoto, but it still works with iPhoto5 under OS 10.2.4.
Hopefully, Apple will fix this problem soon. (Although I'd rather they put all their resources into fixing the latest security update fiasco).



[ Reply to This | # ]