Linked

I don't monitor my traffic, but I don't think I have a really heavy readership. Every now and then I have a minor hit, but for the most part we're pretty hardcore systems administration around here. It takes a very special kind of geek to follow exploits such as Tiger Lab Migration, Three Platforms, One Server or External Network Unification.

Truly special.

But all of a sudden I started getting comments on an old article from just over a year ago. Seems the Mac OS X 10.5.2 update causes a similar problem to one in the 10.4.9 update — network slowdowns due to bad delayed ack values, or some such — and MacFixit has linked to the old post. Neato! I feel popular!

Anyway... Hi, MacFixit folks!

Opacity: Another Crash-Happy 1.0 App

It's 1.0 release week, here at TASB, apparently. It also appears to be crash week.

Another useful-looking app has caught my attention: Opacity. It's a graphics editor designed especially for doing one of my favorite things: icon creation.

Opacity, like ScreenFlow, looks like a really nice application built for doing one specific thing. Which makes it really good at doing that specific thing. And Opacity appears as though it will, someday, be quite good at icon creation. In fact, it looks to be the best icon-specific graphics editor I've seen thus far. But — and this seems to be a theme here lately — it crashes constantly.


Opacity: Crash-Happy
(click image for larger view)

I mean, like, unusably. Like during the tutorial. Not good. The saving grace here is that it at least autosaves a copy of your document. But when an icon editor, working on a single-layer, 512x512 pixel vector image, tells you it's out of memory (I have 5 GBs of RAM for crap's sake) when you're trying to save your file, you know there are some serious problems with the app. Am I right people? Seriously, who's with me here?


Opacity: Out of Memory? Already?
(click image for larger view)

'Nuff said, I think.

Opacity looks like it might be a really good application for icon creation — maybe the way to go. It's got some great tools for preview and output, and the price is right — it's about ten bucks more than Icon Builder, but is completely self-contained and doesn't require Photoshop. But it's far too unreliable for serious use at this point.

It's too bad that developers are releasing such buggy stuff. It leaves a really bad first impression, and makes me not want to rush out and purchase the product, no matter how hot it might look. I hope I get over that first impression before something else better comes along, or simply steals my attention.

In the meantime, as with ScreenFlow, I'll try to remember to check back for Opacity's 1.0.1 release.

ScreenFlow

Holy poo! ScreenFlow is one of the nicest, most polished, yet useful applications I've seen a really long time.

On the surface, Vara Software's ScreenFlow appears to be just another in a series of applications designed to capture your computer screen to a Quicktime movie as you work. Typically such captures are then used for demonstration purposes for new products, or workflows, or videocasts, or what-have-you. But ScreenFlow is much more than just another screen capturing app. ScreenFlow is really an entire environment for creating and finishing computer demonstration videos.

And it's gorgeous!

The most obvious thing that sets ScreenFlow apart from its competitors is the fact that, along with the computer screen, it can capture iSight (or DV camera) video and audio at the same time. By default it sticks this video in a reduced-size window in the lower right hand corner, though, as you'll discover, this can easily be changed. That's because ScreenFlow, in addition to being a screen capturing application is also a presentation editor.


ScreenFlow: Capture Screen and Camera
(click image for larger view)

Once you've captured your computer screen actions and your iSight video, ScreenFlow presents you with an editing interface. Here you can perform all sorts of actions, including zooms, pans and something called "Callout Actions," which allow you to highlight specific windows as well as the mouse cursor. Vara has a nice demo of this feature (in a video, of course, which by the way, is where I pulled these screen shots from) on their site. But the application is so smart and well thought out, that if you've ever used a screencast app, you'll find the learning curve incredibly gentle.


ScreenFlow: Edit Your Presentation
(click image for larger view)

I do want to point out that this is a 1.0 release, and I have experienced numerous bugs. On my work computer (a Quad Intel box with copious amounts of RAM), the application completely crashes my machine. Force quit will not rectify the crash; a hard reboot is required. On my home system (an 8-core Intel with 2 GBs of RAM) ScreenFlow functions well enough, but there are still problems. The iSight registers video and audio in the setup screen, but no audio gets captured for some reason. Also, when exporting my final product to DV-NTSC, I was presented with a set of options, one of which was "Letterbox Content." Though I checked it, ScreenFlow did not honor the "Letterbox Content" option, and my movie came out squished. In fact, I exported the same movie without the box checked and there was no difference between the two movies. Clearly this function is broken. Clearly, ScreenFlow has some kinks to work out.

Still, once the problems are solved — and I sincerely hope that happens soon — ScreenFlow is poised to be the application of choice for regular producers of screen-based videos. And beyond. I admit, I don't do a lot of screen-based capturing, but I'm starting to wonder if the reason is because there haven't been any great apps out there for doing it. ScreenFlow is one of those apps that gives you ideas. It instantly makes you want to use it and then you start thinking of ways to do so. Being in education, this has been pretty easy for me to do. Something tells me I'll be buying and using ScreenFlow in the very near future.

UPDATE:
Version 1.0.1 has just been released, and it seems to fix at least some of the problems mentioned above, in particular the iSight audio problem. Expect a re-review sometime in the near future.

Leopard Installer Certificates

If you've been using Software Update (like I have, up 'til the other day), you've probably missed one of the new features of Leopard: Installer Certificates. Major updates from Apple now come with certificates of authenticity.

So, for instance, download the standalone Mac OS X 10.5.2 installer and launch the package in the Installer application, and you'll notice a small, new certificate badge in the upper right hand corner of the installer window.


Apple Installer: Certificate Badge
(click image for larger view)

Click the badge and you can take a look at the certificate that's attached to the installer, replete with details about said certificate under the "Details" disclosure triangle.


Apple Installer: Certificate Details
(click image for larger view)

It's another preemptive step in the right direction, security-wise. Always nice to see.

iPhone Browser Cache

I love my iPhone. It is increasingly important to me for getting things done. I use it for everything: appointments, reminders, fact-checking, contacts, text, entertainment and, of course, as a telephone. It's boosted my productivity immensely, yet made my life easier and better in so many ways. I'm not sure how many products I can say that about.

Nevertheless, I have one persistent gripe when it comes to the iPhone, one thing that just pisses me off and confounds me every time I encounter it: Mobile Safari's cache is simply too small, to the point where it almost seems pointless to have cache at all. Case in point: I open a web page. It gets cached. I open a new window, and a new page in that new window. It too gets cached. Unfortunately, this new cache invariably wipes out the previously cached page, so that when I navigate back to the other window, the first page has to reload. And, just for the record, these are mostly text-based blogs, sometimes with a picture or two. It doesn't always go down this way, but more often than not it does. This defeats the usefulness of both cache and the multi-page interface available in the browser. I'm not sure what the point is.

I'm sure the browser cache equation rides a fine line between usefulness and unnecessary disc overuse. But for anyone who uses the Edge network on any kind of regular basis, I think they've got that balance wrong. And I can't help wondering why they don't give us a setting — just like in any other desktop browser — for cache size, within a sensible range, of course. Or, if not that, simply make the default a bit larger. The current one is pointlessly small.

UPDATE:
Fixed!