iView MediaPro 2.6 - converts iPhoto libraries?

iView MediaPro Weblog » New Release: iView MediaPro 2.6 (Windows, Mac)

New 'Getting Started' dialog includes option to convert iPhoto libraries as well as links to online learning resources.

---

Here's what the manual says:

Mac: In the Getting Started dialog, check Import iPhoto Library. MediaPro will automatically find the iPhoto library for the active operating system user, launch iPhoto in the background and import all original photos into a new catalog. This feature only works with versions 2 and 4 of iPhoto.

The new catalog contains references to your photo files that are still inside the iPhoto library folders. If you wish to move these files out of the iPhoto library, you can select all the images in the catalog and select Transfer to Folder in the Action menu. Choose Move files, reset paths, delete orginals. This will move your original images to a folder of your choice, sets the paths to the new location and delete the images from your iPhoto library.

To free up additional hard drive space, you could delete all the proxy images (thumbnails) created by iPhoto. To do this, simply trash the iPhoto Library folder from the Pictures folder. Or you could leave them where they are and have media in both iPhoto and iView MediaPro.

The new MediaPro catalog will also containsyour iPhoto albums as MediaPro Catalog Sets (in the Organize Panel). Your catalog also contains any metadata (such as EXIF digital camera data, comments or keywords) that were assigned to your images in iPhoto. The chart above details how iPhoto annotations map to iView MediaPro annotation fields.

---

Sounds very interesting. It leaves iPhoto pictures in place to start with, so it's easy to experiment with. This is a big deal, until now iPhoto has been a one way street. Since iView MediaPro runs on Windows too, it's potentially a way to move iPhoto content to Windows.

Update: I imported a 900 image iPhoto Library. It took an hour or so, but it did a nice job. I think one loses image sequence from albums. Also many images which I'd rotated now were malrotated. I think this may be related to a bug with Image Capture -- it duplicates the EXIF orientation tag and creates conflicting values there.

This is indeed very interesting. I may allow me to have a single view into ALL of my iPhoto Libraries for example.

OS X 10.1 and Firewire Drive Mount/Sleep Issues? Results with my VST and Oxford 911 Drives:

OS X 10.1 and Firewire Drive Mount/Sleep Issues? Results with my VST and Oxford 911 Drives:

I have seen zero problems mounting my portable VST 12GB drive (firmware v56) and my AC powered Oxford911 bridge based case kit drive with onboard IDE formatted IBM 75GXP 60GB drive (the one used in my review and build guide posted here on the Firewire articles page.) used with my G4/500 DP system running 10.1. No problems with them after waking from sleep either. (I repeated these tests over half a dozen times.) The drives were still mounted and usable.

---

So 3 years ago on a very early version of OS X firewire worked better?

Cooking For Engineers

Cooking For Engineers

Recipes for geeks.

SPOD/beachball shutdowns on OS X

macosxhints - How to cleanly shut down when things go wrong

1. reboot
2. Kill coredservicesd
3. shutdown then reboot

Canon releases iP6000D and iP8500 PIXMA printers in the US

Canon USA Consumer Products - Printers

Figures. I gave up 2 days ago and ordered the IP4000. Now the iP6000D, iP5000, iP4000R and iP8500 are out. The iP6000D replaces the i960. It's a "six" (five really) color system. The ip8500 it's an "eight" (seven really) color system.

The product naming and sequencing is very confusing.

I think the iP6000D may be a "pure" photo printer, whereas the iP4000, iP4000R and iP5000 clearly print both photos and documents. The iP4000R has integrated 802.11G support, the iP5000 is faster than the rest. The best photos in this $140-$200 group come from the iP6000D. For our family purposes the iP4000 may suffice.

The iP8500 is in a different category. It exceeds the photo printing of the iP6000D while still doing document printing; and it's faster than the iP5000 for similar resolutions. It's also almost twice as much.

Maybe I won't return the iP4000 after all. It may be about right -- I can replace it with next October's models ...

Gmail runs on Apple xServe boxes?

PBS | I, Cringely . Archived Column

Gmail, itself, runs on Apple xServe 1u boxes.

---

Cute of Cringely to just toss that one out. Apple hasn't said anything about this. I think most folks assumed GMail ran on Intel/Linux boxes.

The beauty of Symlink and SymbolicLinker - OS X

SymbolicLinker

Now that I had my big external drive, the next step was to download and install the OS X development tools. Tons of utilities, documentation, AppleScript studio -- you name it.

So I try the install -- and discover it wants to install on my boot disk! Sigh. The original Mac didn't have these problems -- but OS X is more like Windows. Paths matter. Not all progress is linear. Losing the innate indirection design of Mac Classic is quite sad.

But the documentation mentioned "symlinks". This is a Unix thing, too "advanced" even for my O'Reilly OS X Unix book!

Symlinks come in two forms. One is like a Microsoft Windows shortcut/alias. That's a "soft link". Main limitation is it holds a hard coded path. Move the destination and it breaks. Just like Windows.

Other form is a "hard link". BAD. DANGEROUS. Stay away. Ask no more.

There is risk even to a softlink. Some non-Apple deletion tools get confused by a soft symlink and delete the originals. The trashcan knows better.

Symlinks are created via the terminal. It's probably not too hard, but SymbolicLinker 1.1 is freeware and is very safe and convenient. I downloaded and installed it. Lovely, thank you Nick.

So I moved the "Developer" folder I'd started with to my new external drive, and used SymbolicLikner to create a symlink. It created an item with the name "Developer symlink". I can't change the name. I moved it to my boot disk. Then I continued the install. Worked perfectly.

These look like handy ways to get around a number of odd things that require installation on the boot disk. Symlinks exist at the BSD level, so they're transparent to most Cocoa applications.