Wednesday, September 30, 2009

An iTunes 9 annoyance

With the latest version of Apple's erstwhile music playing app--now the 800 MB do-it-all gorilla known as iTunes 9--came a total revamp of the iTunes store. And while there's no denying it's prettier, it has also introduced an annoyance that I can no longer overlook.

Take a look at this screenshot (click to enlarge):


Notice anything odd? Yep. All the album names are truncated. I know that there's an album with some Rachmaninoff and that it's probably related to the piano rather than the greek letter pi, but I have no other immediate visual information about the album. Hovering my mouse over the album does nothing. Clicking the "i" information button brings up a pop-up that tells me this album is entitled "Rachmaninoff plays Ra..."


Excuse me, but WTF? I had no idea that the Egyptian sun god wrote piano music. OK, my incredulity is forced. You get my point. But at least the track names are all there, you say. And yes, it's true. In this preview window, the track names are all present and accounted for in full. So why then, if I click the "Album Page" link to see the recording's dedicated page, am I presented with this:

While I finally get to see what the full album title is, now all the track titles are truncated. I have to hover the pointer over the track name to see it in full. It's as if iTunes is some sort of control freak who doesn't want you to know too much lest it feel it's loosing control of the situation.

The worst thing is, there's no way to expand the track name (or any other) field, so in this case, I can't find out the full artist name (Zenph Studios and Serg...) unless I preview the track and look in the iTunes display window (Zenph Studios and Sergei Rachmaninoff). Sure seems like a lot of work to find information that's on the cover of any CD. (Incidentally, don't you think it's noble of Sergei to let the studio take first billing; I guess it's easy to be magnanimous when you're dead.)

So yeah, the new iTunes store is pretty, but at least the old one had some substance. I logged a feedback note with Apple about this issue, but I must say crappy UI design is pretty rare in an Apple product. All the more reason why when something like this does get into a release, its so startling.

Wednesday, September 23, 2009

Two weeks with Google Quick Search Box

Quicksilver, I'm sorry, but barring a miracle, you're dead to me. After installing Snow Leopard a few weeks back, I upgraded to QS B56a7. The good news: it works; the bad news: it hogs 100 percent of my MacBook Pro's CPU. So, er, no.

Hence, it's back to Google Quick Search Box. And to be honest, I'm pretty happy with it. It works well, and after setting it up to use the same launch key combo that I used for QS, I hardly notice the difference. It lets me mount and eject disk images with a few keystrokes, just like QS.  I've even managed to assign the same Command-esc shortcut to send a file (not a folder though) to QSB. Unfortunately, once there, QSB can't do anything useful with it yet. QS would let you email it or move it or make an alias of it somewhere. These are functions I would really like to see in QSB soon.

In the meantime, I'm trying to figure out how to use Automator and Snow Leopard's revamped Services menu to bridge the functionality gap between the two apps. But I'm an Automator novice and it's slow going. One thing is sure: QSB is winning over my heart.

Saturday, September 12, 2009

Is this the end for Quicksilver?

I've been a Quicksilver user for many years. In many ways, it is integral to my experience as a Mac user. It's the kind of program that becomes part of how you use your machine, so much so that when I come to another computer that is not equipped with QS, I often find myself at a loss, grumbling about how inefficient it is to use a mouse for everything.

Quicksilver worked really well through OS X.4 (Tiger), so when reports of bugs in the program began to appear after Apple released Leopard, I was very, very worried. But my fears were mostly unfounded. Though it was definitely buggier, Quicksilver still worked reasonably well on Leopard. It's a true testament to Quicksilver that so many users were willing to put up with more than a few bugs. That's how amazing Quicksilver was.

But the other day, after installing the most recent QS build--even before upgrading to Snow Leopard--the app went from finicky to downright ornery (to paraphrase a tweet by Merlin Mann). I could no longer use the "Create alias in..." command with the "Current selection" proxy action. And something about the new build would periodically prevent me from moving folders in the Finder until I had logged out and back in again. Not to mention even more crashes than usual and an apparent desire to use the computer's fans to get airborne on occasion. I have since downgraded to the previous version, but that old fear of what will happen after I upgrade to Snow Leopard is back.

So I've been giving Google's Quick Search Box a try. And though I sorely miss a few hot-key triggers, QSB does almost everything I want it to, works similarly enough to QS that the transition is fairly painless, and has the advantage of being actively developed by the same dude who developed QS. No one who has used any of Quicksilver's advanced features would call QSB anything but a pale imitation at this point, but it definitely has potential.

As much as it pains me to say it, I think it may soon be time to put poor old Quicksilver out to pasture. Don't worry, I'll come and visit as often as I can, my pockets filled with apples and sugar lumps. You've been a faithful steed, but this cowboy needs to move on.

Wednesday, August 08, 2007

More on .Mac price discrepancies

In the last day or so, I've been doing some more thinking about this issue (rather than getting some real work done). In fact, I went so far as to make a spreadsheet (using the 30-day trial version of Numbers, thanks very much) of the various prices Apple charges for .Mac around the world. I listed the actual price in the local currency, then the equivalent of 99.95 USD in the local currency, and then the difference between those two prices, converted to USD.



As you can hopefully see from the chart above (click on it to view a larger size), .Mac subscribers in almost every country pay more than people in the the US do--sometimes significantly more. The only exception is the Japanese, who get a break to the tune of over US$18. The rest pay a premium ranging from less than $1 for those living in Hong Kong to over $40 for you poor suckers in Great Britain. The rest of us fall somewhere in between, with the average discrepancy sitting at just under $18.

What this means is that for every .Mac subscriber Apple has outside the US, the company is taking in about $18 more than it does for its US customers.

So I guess this isn't just about the exchange rates between two countries. This appears to be systematic for the .Mac service. Perhaps it's even Apple policy; maybe they don't want to "confuse" consumers by adjusting the price of .Mac. But it seems to me that by not periodcially adjusting their prices, Apple is hindering the adoption of what is at last shaping up to be a pretty nice service.

As a footnote to this post, just for fun I checked out the prices for the new low-end iMacs at a couple of the international Apple stores. I must say that we Canadians have it pretty good by comparison. For example, the Australians pay the equivalent of US$265 more for their machine than those in the US. The Brits have it even worse: the price of 799GBP works out to be amost US$430 more than the US price--That's almost 40 percent more. Ouch!

When will the Canadian price for dotMac reflect the exchange rate?

Among all the announcements Steve Jobs made on August 7, the improvements to dotMac were, to my mind, perhaps the most exciting and most overdue. The new web gallery feature and 10GB of on-line storage are significant improvements to the service that make its price tag a little easier to swallow.

However, for Canadian dotMac subscribers, one thing that has rankled for the last few years--and continues to rankle--has been dotMac's price. At $139, it is significantly more expensive than the $99 US subscribers pay. Now it was one thing to have a higher price when the Canadian dollar was valued at 65 or 70 cents US, but it is quite another thing to retain that price when the Canadian dollar has risen significantly in value against the US dollar over the last year or two. And this, for a service that is widely hailed even in the US as being highly over-priced.

As the US dollar has fallen over the last little while, many other currencies have gained value against it, and many goods imported from the US have fallen in price (though many consumers groups say this isn't happening fast enough). To whit, many of Apple Canada's products have come significantly down in price over the last 18 months, to the point where some are now being sold at par with US prices. This is true of the new iWork 08 and iLife 08 suites, along with the new keyboards and the Mighty Mouse.

I don't expect Apple to change its prices every two weeks to reflect the exchange rates, and I fully accept that a certain amount of rounding will occur. Indeed, I think for the most part, Apple has done a pretty excellent job of reflecting the currency exchange rate between Canada and the US in its prices. Which is why I just don't understand why Canadians still have to pay 40-percent premium on dotMac. As it stands, I refuse to pay $139; I have always managed to get it on sale, either at the Apple.com one-day sale in November or from a brick-and-mortar retailer such as Future Shop. But I'd be happy to pay the full price if that price reflected the exchange rate a little more closely. Say $109.

So I'm challenging the Canadian dotMac-using blogosphere. Write a post about this issue, get people talking about it. Let Apple know you're upset about it. Maybe, just maybe, if we make enough noise about it, we can convince Apple to reconsider it's policy.

OK, so I'm living in a fantasy world, but at the very least, it's good to vent.

Tuesday, July 17, 2007

MacBook Pro one week in

I've had my MacBook Pro for about a week now, so I figure it's time to take stock of my impressions. First, two complaints, then a boatload of complements.

I find the wireless networking to be fairly buggy (lots of reports in the Apple support forums on this... hopefully a software update will fix it). The Airport range is pretty poor. I'm sitting maybe 40 feet away from my router and not getting full bars. I know the PB/MBP line doesn't get as good reception as the iBook/MB line, but 40 feet is well within the range where I should be getting full bars. I've tried sitting only a few feet away and I still don't always get full bars. I also find the connection somewhat flakey, often dropping out for a few seconds then resuming. So far no kernel panics or anything like that, so I guess I should count my blessings, but I'm gathering evidence for a call to Apple Care about this.

The only other issue is that I was experiencing a slight delay in the trackpad sensitivity. Sometimes I would have to move my thumb around on it for a second or two before the cursor would move. Other times, it was instantaneous. This also seems to be a known issue, one that is apparently resolved by unchecking the the "Ignore accidental trackpad input" box under the Trackpad preferencess. So far it seems to have fixed the problem, though I haven't decided which is worse, the delay or the "accidental trackpad input."

Other than these two bugs, I really love the machine. There are so many little things I appreciate about it. For instance, I never thought the MagSafe connector was such a big deal, but after experiencing it first hand, I'm blown away. My brother-in-law, a longtime PC user, was also really impressed by it. This is the sort of thing that makes Macs stand out--the kind of design detail that Apple is known for.

Battery life is about what I expected, maybe a little better: about 4.5 hours on a full charge if the screen is turned way down and with Bluetooth turned off, and not doing anything that requires the GPU to work hard. I figure I could maybe get 5 hours if I turned off the AirPort too. But if you start watching video or video conferencing, the battery run time drops like a rock.

I'm pleasantly surprised by the machine's quietness (virtually silent most of the time). Laptops are of course much quieter than desktop machines by nature, but the MBP is even quieter than my old iBook. I can't hear the hard drive spin or click at all, and unless the fans are working hard (as in watching video), I can't hear them either.

I also love the screen; it's so bright that I rarely have it turned up all the way. And the backlit keyboard is another feature I was blah about before experiencing it firsthand.

The keyboard itself is wonderful. I like laptop keyboards in general, but this one feels better than most. Just the right stiffness under the keys, and a very satisfying click. I feel like I'm typing much faster than I could on my old iBook. And two fingered scrolling on the trackpad... what a revalation!

That's my roundup of pros and cons so far. No real regrets to this point, though I have yet to take it on the road, where the poor wireless reception may be a real hindrance. I just hope Apple fixes the wireless bugs soon.

Wednesday, June 27, 2007

Finally moving to Intel

I thought I'd be able to hold out a little longer, but after a crazy week of rehearsals where it seemed everyone was toting a new MacBook, and after waiting for what seemed like hours (minutes in reality) to open a fairly large Excel file, my patience finally ran out.

A few hours ago, I clicked "Make purchase" on a low-end MacBook Pro. I've been drooling over the updated MBPs ever since they were recently updated. With 2 GB of RAM and an LED backlit screen, it's a pretty sweet machine as is. I considered the mid-range MacBook, but once the RAM is bumped up to 2 GB, the difference in price to move up to a pro machine didn't seem like such a leap.

My only real qualms are a) that I like the smaller form factor of the MacBook, and b) it is my understanding that, like the old iBooks, they get better wifi reception than the MacBook Pros. However, the MPBs are also apparently better than the old PowerBooks in that regard, so we will see. I almost went back and changed my order, but I think the pro machine will serve me better in the long run.

Now I have to wait till it gets here.

Wednesday, May 16, 2007

Nike+iPod + podcast hack

For my birthday a few months back, my wife kindly bought me a Nike+iPod unit to go along with my new red iPod nano. I must say, I'm seriously impressed with it. It worked flawlessly out of the box, and even before I calibrated the sensor, it was calculating my distance to within 10 percent. Now that it's calibrated, its accuracy is within 2 percent.

Previously, I was never one to listen to music while working out; I preferred the zen state your mind enters during a good run. But there are advantages to running to music, not the least of which is trying to keep up with a song whose tempo is just slightly faster than your normal pace--a great way to improve your speed.

But as any serious runner will tell you, it's also important to work on endurance by slowing down going for distance rather than speed. These are the times when running to music can push you faster than you want to go. In such cases, you could simply unplug your headphones and run without the music (the unit still works sans headphones), but to my mind, a good hour-long podcast (say, MacBreak Weekly... oh wait, that usually runs way overtime...) is the perfect accompaniment to a long, slow run.

Problem is, podcasts are for some reason not available in the Nike+iPod menu (I guess Apple never figured anyone would be crazy enough to listen to a podcast while running). This is where iTunes' smart playlist feature comes in handy once again (see my previous entry about rolling your own autofill feature for iPod nanos using smart playlists).

There are two solutions available, depending on how choosy you are about what you want to listen to. The first is to simply create a smart playlist that has all your most recent podcasts in it. This way, when you select the playlist from the Nike+ menu, you'll get the first podcast in the list.

In iTunes, select "New Smart Playlist..." from the File menu. Then choose Genre from the lefthand dropdown menu, "is" from the next one over and then type "Podcast" in the field at the right. Then click the "+" button to get another rule and select Date Added from the lefthand menu, "is in the last" from the middle menu and "1 weeks" in the righthand field (see screenshot).


If you want to exclude any podcasts from this list, simply add another rule that states "Name... is not... [name of excluded podcast]".


A second option is to create separate smart playlists for every podcast you'll want to run to. It's a little more time consuming, but it gives you more flexibility. In this case, select a new smart playlist, create a rule that states "Name... contains... [podcast name]", then add a rule to exclude all but the most recent episode: "Date Added... is in the last... 1 weeks".


Repeat for all your favourite podcasts. Then connect your nano and under the "Music" tab of your iPod (not Podcasts), make sure to check the new smart playlists you have just created and click "Apply" at the bottom right of the iTunes window.

Assuming you already have these podcasts on your iPod, the new playlists won't even take up any more precious space on your iPod since they are just a different way of addressing the audio file, one that the Nike+ menu can see.

Now, get out there and go on a nice long, relaxing jog!