iPhoto 7 (iLife 2008): again, no Library merges

[Update: the link won't work because Apple deleted my post within 2 hours of my posting it. I'm not surprised. Maybe their vigilant reaction is a sign they're feeling some heat about this issue. There are very active complaint threads this morning about library merging.]

From my post on Apple's Discussion group (corrected because iLife 2008 is iPhoto 7, not iPhoto 8)

Apple - Support - Discussions - Feature request for iPhoto 8: Import ...:

You're traveling with your MacBook. Organizing photos, adding metadata, creating albums, slideshows, etc. You get home. You want to import your travel library to the main library, preserving ALL the versions and metadata.

You have just married the Mac Geek of your dreams. You need to merge Libraries into the shared folder (which can't be shared over a network, but let's just ignore that). How do you do that?

You created and used separate Libraries back with iPhoto bogged down at 2000 images. Now you want to combine them, preserving version relationships, album relationships, descriptions, titles, keywords, roll information, photo books, slideshows, etc, etc.

Yes, I know about iPhoto Library Manager. I license and use it. It does miracles with Apple's limited merge support, but some metadata is lost. I also had so many issues with earlier version merges that, even though I use it all the time, I'm gun-shy. Sorry, merging Libraries is very complex. It's hard to believe that anyone but Apple can do it safely.

iLife 2008 (iPhoto 7) is the fourth release in a row to disappoint those of us asking for Library management.

Choices? Aperture, which Apple clearly intends us to buy instead, doesn't allow one to edit dates on images (good-bye scans!), is dog slow (appallingly slow - still) by design, and can't handle video. Others? They don't import iPhoto Libraries. I ain't redoing metadata on 14,000 images.

Anyone interested in putting together an online petition to ask Apple to add Libary merge/import/management to iPhoto 2009? Picket Cupertino maybe?

I ordered it, of course. What choice do I have?

VueScan vs. Nikon Scan on OS X

I've published a few posts about VueScan; it's a well regarded cross-platform scan control software package that appears to be a one person show. The author's personal focus and prolonged dedication has produced an idiosyncratic product that, with a few quirks (auto-crop isn't what it could be) performs admirably well. I bought a "pro" license, so I get my updates as long as Hanrick toils away.

I've mostly used VueScan to do print and a few negative scans, but recently I worked on a set of my mother's slides. These range from about 40 to 50 years old, in various states of repair. I used Nikon CoolScan V I bought about 3-4 years ago, it's oddly still about state of the art for slide scanning (though slow now). I started out using Nikon Scan 4.02, downloading the latest OS X version from Nikon's support site (yechy non-Apple installer btw. I installed as admin, but the app works for a non-admin user). It's a quirky mix of various semi-integrated packages that Nikon resells, but it mostly worked. It was slow however, and I wasn't impressed with the results various image adjustment options. I got the best results turning everything off, working with the clumsy levels tool, and using Digital ICE for damaged slides. Performance on a G5 iMac was dog slow and, really, it was clumsy.

I then tried the same images on the G5 using the latest version of VueScan. It worked beautifully. Results were better than what I got with Nikon Scan. I didn't fuss too much with white balance or levels, I went with the very good initial results then dropped the 24bit TIFF into Aperture for finishing. From Aperture I exported high res JPEGs to store in iPhoto (note Aperture doesn't allow date editing, an incomprehensible defect). The processing was a bit slow, but the workflow was great.

Next I tried VueScan, which has full Intel support, on my dual core MacBook. Processing was 2-3x as fast.

If you're using a Nikon Cool Scan (CoolScan) with OS X, don't bother installing the ugly Nikon software. Buy VueScan (cheap at the price) and finish your TIFFs in a secondary image processing package (like iPhoto, Aperture, etc).

iLife '08

So true.

iLife '08 guided tour - The Unofficial Apple Weblog (TUAW)... The 20 minute video gives you the highlights of the iLife suite and tries to convince you it is worth $80, but you're reading TUAW so I am guessing that you already bought it.

It was an easy buy since Aperture still doesn't support #$#!$!@$ date editing. Of course Apple didn't add the one iPhoto feature I wanted -- Library merge/import. I bought it anyway for the new photo editing tools and iMovie. It will be interesting to see if iWeb allows one to update a theme -- the last version had the fatal flaw that one's initial theme selections were the eternal theme selections.

I'll have my comments in a week or two -- I don't have time to mess with it for a week or so so I ordered it online.

8/20/07: Well, I shouldn't have bought it for iMove, but iPhoto 08 has some good features. Here's the link to download the last good copy of iMovie.

Freecycle: Given away free stuff

I've had a hard time giving away good stuff in the past. Next time I'll try this:

TidBITS: Freecycle: Disposing of Good Old Stuff

...I had heard about the Freecycle Network, an Internet service that connects people with stuff to give away with people who want free stuff, but until this point I had never tried it. It turned out to be extremely simple. I went to the Freecycle Groups page to find the Ithaca group, followed the link to its Yahoo Groups mailing list, subscribed, and read the ground rules (this is important, since some things - like the required Subject tags - are not inherently obvious to a newcomer), and then sent a pair of email messages to the list, describing the LaserWriter and photocopier.

FlickrDown: make Flickr tolerable

Flickr allows users to download full res images, but it's a tedious multi-click process. It's pretty clear from reading the help forums that Flickr/Yahoo discourages distribution of full res images using Flickr, so they make the process as painful as possible.

GMAN: FlickrDown to the rescue. This open source free app is downloading my SIL's (sister-in-law) photoset as I type, I'll dump them in iPhoto later today. There's a similar open source app for OS X apparently, but my son is occupying the iMac at the moment. This one seems quite fine.

Google maps still route via 35W

I'm tracking how long it will take Google to correct route information between my office and Minneapolis. As of 8/3 they still route across our fallen I-35W bridge.

More interesting will be to see if Google will start including bridge quality and design metrics in their routes. Wouldn't you like to have a "avoid risky infrastructure" checkbox option? How about crossbones on I-35W type bridges with ratings of "deficient".

Google may be able to encourage some state governments to move investments forward ...

Rescuing data from 1993: archival surprise and a FullWrite Professional shocker

[8/3/07: Corrected notes on the import/export translators]

I was tossing out old files, when I came across printed versions of some reviews I wrote in the early 90s for MD Computing, the Journal of Family Practice (when it was an academic journal), and a few other geeky doctor journals. I decided to see if I could actually get at the data.

The file formats weren't the big problem (ok, with one exception and a big surprise - below). The big problem was the archival format. When I wrote these articles in 1992 to 1993, (yes, 15 years ago!) I routinely zipped a folder of .... 124 kb.

The 15 yo archived files didn't travel well. Apple's built-in unzip simply reported and error and halted. Stuffit Expander gave me an immortal SPOD that sucked cycles and forced a power cycle restart. "The Unarchiver" complained about a file defect, but it did extract the files.

WinZip on XP did better, albeit with a security warning and there was some problem with unzipping to a directory. I was able to drag and drop the ingredients however.

I had a tougher go with mysterious blank icon 36 KB extension-free document that nothing could open. Text Wranger showed a mess of non-ascii charcters and the string "FWRTFWRT" in the header. I guessed it was some ancient StuffIt archive and dropped it on StuffIt Expander -- this time it did expand.

The files turned out to be some GrandView outlines (I didn't bother with those), some MORE 3.1 files, MacWrite II, WordPerfect 5.0, and .... an Ashton-Tate FullWrite Professional document. Oddly enough, my G5 iMac has copies of MacWrite II, MORE 3.1 and FullWrite buried away. Only FullWrite wouldn't run; it sent my CPU to 100% but wouldn't start.

A Wikipedia article, however, pointed to a freeware version of FullWrite Professional. I installed the once monstrous application that crushed my Mac SE years ago -- it took up 2.8 MB. Yes, that's an "M". Less room than a single JPG.

2.8MB.

It launched perfectly under classic running in OS X 10.4.10 on my G5. No error messages, nothing, just opened the file with an outliner beyond anything currently available on any Word Processor in 2007. Yes, Word 2007 (ummm, maybe 2GB to install?) has nothing like the old FW outliner.

My next surprise was the import/export list of an immense number of file formats. It took me a while to remember that MacOS Classic included an OS facility for file translation available to every application. The lists was further extended if one licensed MacLink Plus. It's a very impressive list, though the quality of the translation isn't great:

(click to see full sized image)

The list of supported export formats includes: Acta, AmiPro, AppleWorks, Claris Works, FrameMaker (yes), HTML+, InfoDepot, MacWrite 5, II, Pro, Word, MS Works, MultiMate (remember?), Nisus, OfficeWriter (remember?), Professional Write, RTF, SDM Writer (what the heck?), SunWrite, MORE 3.1 (!), TeachText, Text, WorkPerfect, WordStar (omigod), WriteNow, XYWrite ... and one or two more. Plus a few variations of each. It's the same list for file open as well. Plain text, which probably came from FWP rather than from the common translator tools, did the best job of preserving the outlines look and feel.

I opened up a MacWrite document and saw my old email address again: 4867991@mcimail.com.

Between my old apps, the free version of FullWrite and some fiddling with archivers it looks like I can rescue most of the old documents. Of course classic is mostly forgotten (does 10.5 allow Classic even on PPC machines?), so there's not much time for this. A few more years and I'd have given up on the FW files.

BTW, Word 2003 did a fine job opening the old WordPerfect docs and saving them as RTF.

Did I mention the install is 2.8MB? The core application is 768KB.

768KB. Once, giants walked the earth.

Update 11/6/10: I received an email from Roy Leban, who was a lead engineer on the original FullWrite project. He has several blogs, but they're updated infrequently.