MacInTouch: timely news and tips about the Apple Macintosh
Problem: Spotlight fails to find filename strings that are right under its nose. It's cuckoo: type a string into a folder's Find box while you're looking at the matching file and watch it vanish with "0 Items" displayed...
Solution: Go to Network Preferences and turn off all networking for Firewire ports.
Wednesday, December 07, 2005
Tuesday, December 06, 2005
StickyBrain: An alternative to the MarkSoft Memo app
I use MarkSoft's Missing Sync to sync my wife's CLIE with iCal et al. The only weak link (other than some MS and OS X bugs) is the Memo.app -- it doesn't give me the support I want for moving items around.
MarkSoft suggested I try Sticky Brain instead. Not cheap at $40 but I'll take a look at it!
MarkSoft suggested I try Sticky Brain instead. Not cheap at $40 but I'll take a look at it!
Monday, December 05, 2005
Apple's Aperture bites - the Ars Technica review
The thorough Ars review is out, confirming everyone's emerging suspicions:
BTW, why is Aperture's metadata updating so slow? It's not fully clear, but it may be that Aperture actually lacks a relational (or object-relational) database engine. It appears to store metadata in a vast number of XML files. Apple appears to be fond of this approach; I personally despise it. It transforms a dual G5 machine into the equivalent of a Mac SE.
Aperture 1.0: the Ars review : Page 9Adobe must be grinning today. If Apple were an honorable company they'd refund liberally, slink off the stage, and release a half-fixed version for a lower price point and a free upgrade. IF!
Maybe by 2.0 Apple will have the foundation sorted out. At this stage Aperture is a big, expensive misfire and considering the hefty price tag, I can't think of a reason to recommend it. Reading this review, you may think I sound jaded, but I am genuinely angry for those who shelled out US$500 for a program that promised professional results and failed to deliver. Thanks for coming out Aperture, now get off the stage.
BTW, why is Aperture's metadata updating so slow? It's not fully clear, but it may be that Aperture actually lacks a relational (or object-relational) database engine. It appears to store metadata in a vast number of XML files. Apple appears to be fond of this approach; I personally despise it. It transforms a dual G5 machine into the equivalent of a Mac SE.
An astoundingly clear description of color gamuts and best practices for OS X
I've spent a small amount of time in the morass of color management over the past few years. Just enough to spot something very interesting in this occult domain.
This Aperture article is one of the best simple descriptions I've ever seen: Aperture: Color and gamma settings for print and web.
It does hint at some bugs in Aperture and OS X. For example, I think the recommendation to 'set gamma to 2.2 and white point D65 and never change it' is related to a bug in color profiles and fast user switching -- if not other color profile bugs. (A gamma of 2.2, by the way, will make the entire OS X interface look a bit odd. A seperate kb article mentions how the intersection of color profiles and external editors can crash Aperture ...)
I set my camera to sRGB, my screen to sRGB with Gamma 2.0 and white point D60, and cross my fingers and pray. For JPEG, with its inherently crummy color tables, this is probably good enough. It's a compromise between the Windows and Mac worlds. Pictures will look a bit dark on Windows and will print a bit dark from most print services.
I suspect that when OSX for Intel comes out, Apple will quietly change the hardware and OS to the Windows Gamma. It's about time ...
Update 12/20: Alas, introduce Photoshop and the view is murky again ...
This Aperture article is one of the best simple descriptions I've ever seen: Aperture: Color and gamma settings for print and web.
It does hint at some bugs in Aperture and OS X. For example, I think the recommendation to 'set gamma to 2.2 and white point D65 and never change it' is related to a bug in color profiles and fast user switching -- if not other color profile bugs. (A gamma of 2.2, by the way, will make the entire OS X interface look a bit odd. A seperate kb article mentions how the intersection of color profiles and external editors can crash Aperture ...)
I set my camera to sRGB, my screen to sRGB with Gamma 2.0 and white point D60, and cross my fingers and pray. For JPEG, with its inherently crummy color tables, this is probably good enough. It's a compromise between the Windows and Mac worlds. Pictures will look a bit dark on Windows and will print a bit dark from most print services.
I suspect that when OSX for Intel comes out, Apple will quietly change the hardware and OS to the Windows Gamma. It's about time ...
Update 12/20: Alas, introduce Photoshop and the view is murky again ...
Sunday, December 04, 2005
MacDevCenter.com: Five Fun Ways to Play with Audio Hijack Pro
I had a frustrating experience with AH Pro, but I now own it. This list of ideas suggests I might get some mileage from it someday: MacDevCenter.com: Five Fun Ways to Play with Audio Hijack Pro
Subscribe to:
Posts (Atom)