Desktop Pictures: the quality source

Sometimes Google can be dim. Search on "desktop pictures" and you get a lot of sites that, at least to me, aren't very useful.

On the other hand, the old "About this Particular Macintosh" site maintains a Desktop Picture archive that's free and excellent. A bit of a hidden gem I guess.

Personally I prefer gray scale images because color images make it hard to find my desktop icons, but I'll try switching some of these to gray scale. The one exception is that in XP at work I use Microsoft's desktop manager, and in that setting I reserve one environment for desktop operations. The other two can have full color backgrounds, and I rely on the backgrounds to tell me what environment I'm in. I'll be using these ...

Apple's iClip 1.0 (iMovie '08) shaft: what they should have done

iClip 1.0 (aka Movie '08) is a nasty trick. It has real promise and some real innovations; with another year of development it could be a great application. It needs a real media management solution, probably extending some of the approaches Aperture takes to managing a media library. iPhoto doesn't cut it as a media management solution. It also needs some of the core functionality that once belonged to iMovie HD. Most of all, it needs another year of work.

In fairness to Apple engineers, maybe it originally relied on functionality that was part of 10.5, and what we see now is a hack designed to work on 10.4. Or maybe it was supposed to be much more than it is, and as schedules slipped Apple threw it out the door in desperation.

Alas, it may well be a great commercial success. That happens. It doesn't change the shafted feeling iMovie HD users are going to experience.

The honorable thing for Apple to have done would have been to provide iMovie HD users with an upgrade path to Final Cut Express (which might also require some updates to FCE, I'm not sure how serious Apple is about that product). In a bit more detail, this is what they could have done:

1. Announce iClip (iVid?): a promising solution for rapidly sharing clips stored in iPhoto.
2. Announce that iMovie was, regrettably, being discontinued.
3. Let iLife '07 users have the option of a $75 transition to Final Cut Express. Some would choose to spend their money on FCE instead of iLife '08, others might choose both.
   

If Apple had taken that route I'm sure some users would still grumble, but they'd be spared the nasty reviews. There's still time for them to reconsider.

Sad Apple moments: Apple abandons file reference indirection

I think the single greatest innovation of the original MacClassic OS was the implementation of unique file identifiers.

Instead of hard coded paths and file names, files were identified by permanent unique identifiers. Applications called the Toolbox to get the current path as needed. Files could be "moved" (renamed, relationship to folders changed, etc), but references didn't break. Everything just worked (as long as the files stayed on the same physical drive).

Since Apple migrated to OS X they've been moving away from this. I looked a few months back and could find almost no documentation of indirection at the file system level in OS X HFS+. Increasingly Apple's applications seem to require fixed paths.

Apple's warped iClip (called iMovie '08 by Apple) is another nail in the coffin for indirection:

Gordon's Tech: iMovie '08: How the heck is it supposed to work?

As an experiment I relocated the iPhoto Library that iClip (iMovie '08) was referencing. I found, again, confirmation that Apple has abandoned file redirection in favor of hard coded paths.

Somewhere an group of former Apple engineers are mourning a great contribution that has been pointlessly abandoned. Whoever you are, wherever you are, thanks team. I appreciate what you did.

Update 2/26/09: A Stack over flow question pointed to the an Apple tech doc on The "/.vol" directory and "volfs" that demonstrates how badly this key innovation was hurt in the switch to OS X:

... This directory is used as the mount point for the "volfs" file system. The "volfs" file system is a key component for supporting the Carbon File Manager APIs on top of the BSD file system. Historically, BSD systems only allow you to access a file or directory by its POSIX path. However, the Carbon File Manager API also allows you to access an item by its catalogue node ID (CNID, a file ID reference or a directory ID). "volfs" provides a bridge between these two models, allowing the Carbon File Manager APIs to work on top of the BSD file system.

So Apple hacked BSD to enable file IDs with OS X, but Carbon is their deprecated API and file IDs are tied to HFS, a decrepit file system. I wasn't able to find mention of a Cocoa API for accessing CNIDs...

iMovie '08: How the heck is it supposed to work?

So how is that never should have been released "iClip" (so-called iMovie '08) supposed to work?

This is my best guess, after making a movie from some digital camera AVI files:

1. The clips are stored in iPhoto. (Despite my previous comments that Apple appeared to be abandoning iPhoto as a mixed media store.) This is pretty odd since iPhoto almost ignores AVI files, can't export them, can't share them, etc. Nonetheless, this is how iMovie/iClip expects to work. It has NO facilities itself for managing an clip store, it only manages references to clips. Now do keywords between iPhoto and iClip? I'd be amazed if they did.
   
2. The outputs from iMovie (.mp4, forget those other formats) are to be stored and managed in iTunes. Not in iPhoto.

Now if you think about this a while, your first question will be ... how the heck do I move an iClip project, or a set of clips, from one machine to another?

Very good question.

My guess is, you can't. Ever. Move. Anything. Otherwise, all the projects will break.

Is it easier to use with clips than iMovie '07? Minimally, maybe. Once you learn the weird UI and application model you can throw something together very fast. You can also draw from a large number of clips for a series of different outputs. On the other hand, iMovie was far more powerful than iClip, and you could actually backup, restore and move your projects between machines.

iMovie isn't as big a fiasco as, say, Vista, but I'd line up to throw a (harmless) pie at a cartoon of the iLife product manager ...

PS. It's not been much remarked, but this is the first Apple software that has Intel only features. The newest digital video compression formats are supported only on Intel.

Update 9/2/07: As an experiment I relocated the iPhoto Library that iClip (iMovie '08) was referencing. I found, again, confirmation that Apple has abandoned file redirection in favor of hard coded paths. The video files were still on the local drive, but iClip could no longer find them.

The following Event used in this project is not currently available:
iPhoto Videos - MN State Fair Sept 1, 2007
The portions of the project which reference this Event will show black frames.

Update 3/25/2008: A Flip Video experiment exposed what a lousy product iMovie '08 is. Any longtime Mac users would expect that iMovie '08 would be able to import any video source that QuickTime can recognize.

Wrong.

iMovie '08 imports DV, .mov (quicktime) and MPEG4. It doesn't leverage QuickTime's infrastructure.

This is a truly miserable product.

iMovie '08: It's so unfinished that ...

iLife 2008 iMovie is so unfinished that there's no help entry for "join clip". "Join Clip" is the name of an item on the Edit menu.

iMovie 2008 would have been ready around October. Yech.

OS X 10.5, btw, won't be ready until April 2008. My prediction.

Update: The string "join clip" doesn't appear in the PDF tutorial either. It's as though the feature wasn't implemented, but Apple forgot to remove it from the menus. I'm starting to feel like the Emperor has no clothes and I'm the only one who's saying anything ...

Update: I figured out by experimentation what split clip does. If you move a clip to a project, then click and drag to select a portion of the clip, you can then split that portion out. If I could ever figure out how to select more than one clip at a time I could probably join them, but again the help file is useless.

How to uninstall an iPhoto plug-in

I had no idea there was an official uninstall, I'd previouslly opened the package and deleted inside the plug-in folder:

Picasa Web : Frequently Asked Questions

We hope you love Picasa Web Albums Exporter for iPhoto, but we won't be mad if you want to uninstall it. Here's how:

* Quit iPhoto if it's open.
* In the Finder, open the Applications folder.
* Click iPhoto once to select it.
* Choose File > Get Info to open an Info window.
* Find the section of the Info window labeled Plug-ins. If necessary, click the little triangle for Plug-ins to see the list of items in that section.
* Scroll through the list until you find PicasaWebAlbums.iPhotoExporter. Click that entry to select it.
* Click Remove.
* In the scary alert box that appears, click Continue.

Apple needs more QA testers: Version XIXXIII

Apple doesn't have enough QA people. Maybe Apple's culture disdains the entire idea of QA testing. Grumph!

Latest episode. The Child account on our machines has a locked Dock. When I installed iPhoto 2008 Apple's own installer stuck an iMovie icon on the locked Dock. I can't remove it unless I escalate the Child account privileges, remove it, then restore them. A real nuisance.

Apple needs a knock on the head about QA.