Greg Reinacker’s Weblog

Never one to let new toys sit on store shelves too long, I picked up a Magic Mouse as soon as they were available in the local Apple stores. I was one of those rare folks who actually liked the mouse-formerly-known-as Mighty Mouse, so thought I’d write about it from that perspective.

First, I love the scrolling action when you slide your finger on the mouse. _Love_ it. I also find that I really like the momentum scrolling option, which, like the iPhone, dampens the scrolling effect when you lift your finger rather than stopping abruptly. I thought I’d hate the momentum (makes sense on the iPhone, but on a computer?!?), but it didn’t take long to get used to it, and then like it, and then actually be bummed when it didn’t work well in an app. The only app I’ve found so far that it doesn’t seem to work well in is Tweetie; I think it is actually working, but it’s so highly damped that you can’t really tell. [I saw a tweet from Loren saying he's waiting for his mouse to come in so he can work on it.]

If you want to stop the scrolling abruptly, like other mice, just don’t pick up your finger when you’re done scrolling…and it will stop in its tracks. Perfect.

The only scroll-related gotcha I’ve found is when you’re in an app where you can scroll down one line at a time (the example for me is the ThinkOrSwim trading app, looking at level 2 quotes, trying to scroll down one line at a time)…with the mighty mouse, it was easier to scroll down just one line, or three lines, or whatever you wanted. With the magic mouse, it’s still possible, but takes some finesse, which I haven’t mastered yet.

The other thing I really like is the fact that you can use the whole surface of the mouse for scrolling. Sometimes I’ll be reading a long web page, and take my hand off the mouse. Now when I want to scroll down a bit, I don’t have to position my finger right on the scroll ball, but in fact can just stick a finger anywhere on the mouse and scroll around.

Right-clicking on the magic mouse works exactly like it did on the mighty mouse, which works well for me. The two-finger swipes to go back and forward in a browser do work…but I haven’t trained myself to do it yet. It’s a touch awkward now, IMHO, but who knows, maybe I’ll grow to like it.

I do miss the extra buttons on the mighty mouse, which I had assigned to dashboard and expose. My hope is that Apple maybe adds some options in the mouse preferences to re-map the two-finger swipe to other functions, so we can customize the behavior to our liking. Or perhaps there are other gestures the mouse can recognize that just aren’t implemented in the driver yet. I’m not holding my breath, though. :-)

All in all, I like it a lot. I’ll probably end up buying another one for my other computer now. And, in case you want one, here are make-me-rich Amazon links for the Magic Mouse and the wired mouse!

Back in February, I wrote about the performance I was seeing with my Mac Pro, and compared it to several other machines. My intent was to compare performance between various different machines and configurations…but it had the unexpected side effect of giving me a baseline with which to measure new versions of Adobe Photoshop Lightroom.

This data proved to be quite useful when Lightroom 2.0 was released, and I could test the 32-bit build against the 64-bit build. What I found was surprising.

Just like last time, the basic test was generating 1:1 previews for 211 raw images (compressed NEF format from a Nikon D200), about 1.75GB of files.

First, Lightroom 2.0 32-bit:

Mac Pro, 2 x 2.8 GHz Xeon, 8 cores, 12GB RAM, OS X 10.5.5
CPU utilization between 350-500% throughout
Total time 4:57, average 1.41 sec/image

And Lightroom 2.0 64-bit:

Mac Pro, 2 x 2.8 GHz Xeon, 8 cores, 12GB RAM, OS X 10.5.5
CPU utilization between 500-550% throughout
Total time 7:06, average 2.02 sec/image

So the 32-bit version on OS X 10.5.5 was actually a bit faster than my previous tests of Lightroom 1.3.1 on 10.5.2, which could be due to either the Lightroom 2.0 upgrade, or 10.5.5 changes.

But the 64-bit version of Lightroom 2.0 totally blew chunks, as you can see. Pretty disappointing, and totally reproducible for me, so I opened a ticket with Adobe. They got back to me saying they could reproduce the problem, and also had a bunch of mumbo-jumbo about how there is more overhead in accessing memory in 64-bit mode (which I’m not sure I believe, but I’m not up to speed enough on the Leopard 64-bit implementation to know for sure).

Well, Lightroom 2.1 was recently released, and here is the data:

Lightroom 2.1 32-bit:

Mac Pro, 2 x 2.8 GHz Xeon, 8 cores, 12GB RAM, OS X 10.5.5
CPU utilization between 350-500% throughout
Total time 4:55, average 1.40 sec/image

Lightroom 2.1 64-bit:

Mac Pro, 2 x 2.8 GHz Xeon, 8 cores, 12GB RAM, OS X 10.5.5
CPU utilization about 400% throughout
Total time 4:05, average 1.16 sec/image

Wow – obviously a big change; the 64-bit version now totally rocks. There was something in the 2.1 release notes about enabling SSE extensions in 64-bit mode – sounds like that might have been the bug!

I didn’t record the memory usage numbers, unfortunately…but I remember watching during the runs, and the 64-bit version seemed to be using about twice the memory that the 32-bit version did.

By now we all know about the couple of days it took for the .Mac to MobileMe transition to happen. I didn’t really complain about it – during the whole time, email was working fine (from a mail client), and sync was working most of the time. It was just the new web apps that took a while to come up.

More recently, on Friday, there was a complete mail outage for 1% of MobileMe users, and said outage has still not been fixed (as of Wednesday mid-morning). I’m in that 1%.

I’m not really too upset for myself; I’m watching this more from an academic perspective. I use the MobileMe sync a lot between two Macs and an iPhone, and I do use the email, but not often. The fact that mail is down doesn’t dramatically affect my life at the moment. And in general, I’ll be the first to say I really like MobileMe and what they’re doing with it.

But after the email being down for 5 days so far, the techie in me can’t help but wonder what is wrong. Apple put up a KB article about it, saying:

On Friday, July 18, 2008 (2008-07-18) we experienced a serious issue with one of our MobileMe mail servers. This issue is currently affecting approximately 1% of MobileMe members. Affected members are unable to send or receive email at www.me.com or access email using any email client software such as Mail on a Mac or Microsoft Outlook on a PC.

Let’s look at what could perhaps cause something like this:

1. Complete server failure. Well, in 5 days, you could for sure have another server in there. Actually in more like a couple of hours, assuming their service contract with Sun (they appear to be using Sun’s mail servers) is up to date.

2. Disk failure. Perhaps the entire disk array that this 1% of mailboxes is stored on melted down. Even if this was true, you could almost certainly restore from backups in hours, or worst case days.

3. Centralized disk failure. If they’re using large storage arrays, it’s possible there was a systemic failure and they can’t get it back online. However, they’d probably have a much bigger problem than a 1% outage if this was the case.

4. Multiple storage failures. If multiple drives all failed at one time, causing an array to come down, and there was no usable backup, then they might send the failed drives out for data recovery – eek. But still – I would think this could be completed in a day. I’ve never done it, though, so perhaps this takes a while.

5. Data corruption. If something went terribly wrong, and the server was writing corrupted data, it could conceivably destroy a lot of data before your monitoring knew something was wrong. Hmm. Restoring from backup is the obvious thing to do, although you might have incremental data loss from the window since the last backup (assuming transaction logs corrupt also).

Like I said, I like MobileMe, although it’s certainly taking a PR beating right now. But I’m definitely curious what’s going on, and what could possibly take 5+ days to recover from. Any ideas?

It seems lot of folks are having problems getting Exchange push email working reliably with the new iPhone 2.0 software. For me, it worked flawlessly when I was outside of the office, but when I was in the office and connected to our corporate LAN via wi-fi, it was unreliable at best. If I instead connected to another wi-fi network (like the guest network from the folks two floors below us), everything worked fine.

There is an Apple KB article talking about this:

When roaming between home and office networks with Wi-Fi enabled, “push” may stop working if your company’s Exchange ActiveSync server has a different IP address for intranet and Internet clients. Make sure the DNS for your network returns a single, externally-routable address to the Exchange ActiveSync server for both intranet and Internet clients. This is required so the device can use the same IP address for communicating with the server when both types of connections are active. A workaround to avoid this issue is to disable Wi-Fi on the iPhone.

Yep, that sounded like the problem. Our internal and external DNS for our corporate mail server is different, just as the article surmised. But it turns out in our case, it was non-trivial to change them to be the same thing.

But it turns out there is a workaround that works for me. If you go into Settings / Wi-Fi, find your wi-fi network, and click the blue button next to it, you’ll see something like the following:

And here’s the tricky part. Tap on the “DNS” setting, and edit it. In my case, rather than using the internal DHCP-assigned DNS servers, I typed in two external DNS servers. These new servers will override whatever is returned from DHCP, and when asked for the IP of our mail server, they will return the externally-facing IP, since that’s all they know about.

And that was it! The push email is now working 100% reliably. A little too reliably, actually. :-)

Note – I obviously no longer have internal DNS resolution within my corporate LAN, but that’s not a problem for me. Your mileage may vary.

Note 2 – this also assumes your external mail server IP is accessible from your LAN. This may or may not be the case, depending on how your firewalls and the rest of your network are configured.

It’s been about 8 months since I started using an iPhone. Oddly, I wasn’t even interested at the time; I got the phone as a freebie for going to the Office 2.0 conference in 2007, and it sat on my desk for a week before I even activated it. Color me unexcited.

But then, things changed. Turned out I did like it, a lot. It was “fun”. I’m a sucker for fun gadgets. I switched my regular phone number over about a week later, and I’ve been using it ever since.

So the other day, I was out to lunch with someone, and he asked how I liked it. And while I was answering, I had two interesting realizations:

1. It’s still fun. I mean, all the little animations and eye candy. The little things. Could I live without them? Sure. But having them there somehow makes the whole experience continue to work.

2. It’s the first “smart” phone I’ve ever had that didn’t annoy me. I mean, really. Smartphones I’ve had in the past (from Audiovox, Motorola, Palm, and others) all eventually sucked at the little things. You know, like making phone calls. Sometimes I’d find that the phones were too busy doing something (gosh knows what exactly) to even let me make a call. Or too busy to ring when a call was coming in. Sometimes they’d lock up. Sometimes they’d get into a weird mode where anything I did would take 10+ seconds. Sometimes they’d make me want to throw them against a wall.

But oddly, the iPhone has done none of these things. It’s not perfect by any means – it’s got a few little bugs…but at risk of sounding like a fanboy, I have to say it works better as a phone than any phone I’ve had in the last 3 years.

And that is something I never thought I’d say.

This last week, I was working on getting Back to My Mac working on my computers. This requires everything in your router (specifically UPnP or NAT-PMP) to be working just so…and it wasn’t. :-) I had a Linksys BEFSR41, which is on Apple’s supported list, but no love. UPnP was enabled, but nothing.

So then I get the crazy idea to just unplug the router’s power, and then plug it back in. I mean, if all else fails, power cycle, right? Well lo and behold, it started working…who would have thunk? So then I’m playing with Back to my Mac, and it’s all looking good. For a while.

Then my router started getting flaky. Like, every few minutes it would stop responding in the admin interface, and connections to the internet would be stopped. The only way to fix it was to either wait a few minutes for it to come back, or power cycle it. Clearly this was not going to be ok.

So I went down to the Apple store (about 5 minutes away), and bought the last 500GB Time Capsule they had in stock. I was thinking about doing this anyway, since I wanted 802.11n in the house, but a dead router was a great excuse to do it sooner rather than later. Got the Time Capsule home, plugged it in, everything worked as expected. Actually, not everything worked right away – I had to power cycle my cable modem to get things talking to each other – but after that everything was great. And Back to My Mac is working fine.

On the storage side of things, I switched my Time Machine backups to use the drive in the Time Capsule; again, everything worked as expected. I’m seeing about 10MB/sec doing backups over a gigabit ethernet network – not stellar, but it’s fast enough for what I’m using it for. And it’s working about 5x faster than Glenn Fleishman is seeing in his Macworld first look, for some reason. I won’t complain about mine. :-)

I’ve been torturing myself with the idea of buying a Mac Pro for a while…I mean, come on – 8 cores, for $2799? So last week, I finally broke down and pulled the trigger. But of course it didn’t stop there – I added another 10GB for a total of 12GB of RAM, and added a couple of disk drives as well.

It certainly “feels” fast – but I wanted to actually make some measurements, to see if it was just my imagination. I could run benchmarks, but that didn’t sound like much fun. So instead, I ran a process in Adobe Lightroom 1.3.1 to create 1:1 previews for 211 raw images (compressed NEF format from a Nikon D200), which is roughly 1.75 GB of files.

Here’s what I did. And yes, I’m apparently geeky enough that this sounded like fun. :-)

On the Mac Pro and the Macbook Pro, I generated these 1:1 previews in an existing Lightroom catalog with about 12,000 images in it. On all other systems, I generated the previews in a brand new catalog with nothing in it other than these 211 photos.

All of the virtual machines mentioned below are using VMWare Fusion, running on the Mac Pro.

Here are the configurations I ran, and the results:

Mac Pro, 2 x 2.8 GHz Xeon, 8 cores, 12GB RAM, OS X 10.5.2
CPU utilization between 350-400% throughout
Total time 5:36, average 1.59 sec/image

Macbook Pro, 2.2 GHz Core 2 Duo, 2 cores, 4GB RAM, OS X 10.5.2
CPU utilization between 150-200%
Total time 13:35, average 3.86 sec/image

Dell XPS 420, 2.8 GHz Pentium D, 2 cores*, 3GB RAM, Windows XP SP2
CPU utilization about 50%
Total time 27:00, average 7.68 sec/image

Virtual machine, 2 processors, 3GB RAM, Windows XP SP2
CPU utilization between 150-200%
Total time 8:58, average 2.55 sec/image

Virtual machine, 1 processor, 3GB RAM, Windows XP SP2
CPU utilization about 100%
Total time 15:12, average 4.32 sec/image

Virtual machine, 2 processors, 3GB RAM, Windows Vista
CPU utilization between 150-200%
Total time 8:29, average 2.41 sec/image

* – not sure why this process on the Pentium D only seemed to be using a single processing core, that’s what happened when it ran.

Clearly the Mac Pro is pretty darn fast, and Lightroom interestingly appears to use up to 4 processing cores. The VM data was interesting to see, as well; I can run Windows XP in a VM dramatically faster than running it on my (admittedly old) Dell XPS 400. I wish I had a Core 2 Duo windows machine handy that I could try this on – would be interesting to compare that data with the virtualized Xeon processors on the Mac Pro.

UPDATE 10/30/2008: Additional data from Lightroom 2.0 and 2.1, on OS X 10.5.5, comparing 32-bit and 64-bit performance.

As I mentioned in my post last week about switching to a Mac, I’ve had a number of posts in the back of my mind, many of them observations that I’ve made since taking the plunge.

Today’s is about how the Mac seems to sell itself. And all of us Mac users tend to help. :-)

I’ve got two examples from my own recent experience (I’ve actually got more, but I’ll keep it down to two here).

I was over at my sister’s house for Thanksgiving, and her and her husband had a couple of friends over to join us. One of them brought along his Macbook Pro. My brother-in-law mentioned that he had just installed a new printer, and it was on his wireless LAN, but some configuration thing must have been messed up because none of his (windows) computers could see it.

His friend, just for grins, opened his Mac and went to the printer setup area, and within seconds it discovered the printer on the network, and installed it. He printed a web page…and while my brother-in-law was in the next room picking up the print, his friend called over to him “it looks like your cyan ink cartridge is low!”

Pretty funny…but the important point here is it just worked, without any CDs or complicate configuration. You know what he asked for for Christmas? Gift cards for the Apple store, so he can buy a new Mac.

The second example is a coworker, who has a nice video camera, and has played with some movie editing, but has not been able to successfully burn a video DVD from Windows (it always ends up with problems on his DVD player). He’s going home tonight with a DVD created with iDVD – and he said if it actually works, there’s a pretty good chance he’ll get a Mac for himself.

I think Apple is in the middle of a bit of a perfect storm at the moment. People I’ve talked to, while not necessarily disillusioned, are not generally impressed with (or excited about) Vista. It seems there is no “wow” factor making the average Joe want to take that step, unless he’s buying a new machine where it comes already installed. And even then, I’ve got some friends (Tom is one of them) who have new laptops with Vista, and are trying to figure out how to switch back to Windows XP. So while usage remains obviously strong, I think loyalty to Windows is waning.

At the same time, it seems that – especially at home – the Mac has plenty of software available for it. Mention just about any common task that we all do with our computers, and while there might not be as many Mac apps as Windows apps, there are typically enough to choose from. And I think this may be the case even in the office, but that will be the subject of another post.

And finally, the Mac has the reputation of being easy to use and trouble-free.

I think all of these things have come together to form quite a force. When I mention to people that perhaps they should consider a Mac, and they hear that even I use one :-), probably 80% of them at least consider it. And that, I believe, is a pretty big shift from where things were say 5 years ago.

As some have noticed, and others have gloated about :-), I’ve been using a Mac (specifically a Macbook Pro) as my primary machine for about a month now. I’ve been a died-in-the-wool Windows guy every since Windows 3.0, and scoffed at all of the people playing with their silly Macs. Well, I guess they showed me, because now I’m using one. I’m even writing this post in MarsEdit.

Don’t get me wrong – I still like my friends in Redmond…but this experience has opened my eyes to some extent to how the “other half” lives.

I thought as a Windows user for so long, I might have a different perspective on the Mac…so I’m going to write a few posts (well, at least one – lol) talking about the whys and hows of my experience. So let’s get to it…and this post will be about “why oh why did I switch to the Mac?”

It all started with Windows Vista, actually. As a Windows guy, I was all excited when it was released, and installed it on my work laptop as soon as I could. Hmm…didn’t seem to get much faster, and I didn’t have a cool enough video card to run Aero, but hey, it was shiny and new. And the power management worked way better than XP ever did.

But then I got home, shrink-wrapped copies of Vista Ultimate in hand, and contemplated upgrading my home machine (which was running XP). This machine was the one I use for my photography, and it’s running Lightroom, Photoshop, and some other apps. Vista wasn’t such an obvious choice here, specifically for three reasons:

1. There were no Vista drivers yet for my Epson R2400, which I use for proofing and some print jobs. Eh? When is the last time a currently-available Epson printer didn’t have drivers for the latest version of Windows? Hmm.

2. The Spyder color calibration device I was using didn’t have Vista drivers either, and the manufacturer wasn’t planning to support it. I was less upset about this, because I was thinking about replacing this device anyway.

3. Color management on Vista – and this is the biggie – is apparently totally broken. From an article on Digital Outback Photo:

As you use Vista, you are occasionally interrupted by the OS as it confirms you have the admin-level privileges required or confirms certain actions. As a user-interface effect, Vista dims the screen slightly while offering the user a password dialog. Unfortunately, this dimming of the display clobbers the calibration curves in the graphics card and they are not replaced.

Are you kidding me? This is a total show-stopper. Combine this with the fact that it’s never 100% clear in Windows if your display profiles have been loaded (since only color-aware apps use them), and it seems it’s a total crapshoot.

Hmm. My photographer friends with Macs never seem to complain about their color management. Something about “I don’t know, I calibrate it and it just works.”

So I filed that away, and decided I’d just live with XP for a while.

But then I found myself with a shiny new iPhone, which I got for free at the Office 2.0 conference (and subsequently fell in love with, much to my surprise). Suddenly I started seeing Macs everywhere – conferences, coffee shops, you name it. I’d ask people about them – and every person I can remember said they loved it. I’d turn on my Vaio, and wait a couple of minutes for Vista to boot, and all the while admire their fancy Macbook Pro awaking nearly instantly from sleep (because I’ve rarely seen anyone actually turn off their Mac).

Then I stumbled across the page on the Apple web site where they have all of the Mac vs. PC ads, and (I can’t believe I actually did this) I watched the whole series of them. And you know what? They were fun. And Mac is clearly much cooler than PC.

So I thought, what the heck, and pulled the trigger. I knew lots of people who could help me if need be, and I figured worst case, we’ll use the machine for testing and such at NewsGator. So the evening Leopard was released, I cruised over to my local Apple store, and went home with a shiny new Macbook Pro, and a Leopard t-shirt.

And the moment I was sure I made the right decision? Right after I calibrated my monitor, created a profile, and selected it in OS X – and the whole screen updated immediately to reflect the new profile. Ahh…confidence.

Since then, I’ve observed a great many things…and I’ve got a few blog posts in the back of my mind about these:

• Macs sell themselves, and Mac users sell even more
• It’s totally possible (even advantageous) to use a Mac at work
• Mac apps are different
• Apple stores are different

I’m writing this in MarsEdit. I’ll preview it on the web in Safari. I’ll then get back to my email in Apple Mail. And you know what? I don’t miss Windows. At least not yet.

Everyone knows by now that the most visible feature of the iPhone’s recent software update is the iTunes wi-fi music store. When I first saw that, my thought was “ho hum”…I mean, I’m excited that Apple is changing the mobile game and updating devices with new features, but I had very little interest in buying songs from my phone.

Ha. Apple clearly knew better than me.

They completely nailed the interface. It works, it’s fast, and it’s fun. I was sitting around over the weekend, just browsing through the store. Tapping the “preview” buttons, tapping the “buy” buttons…it’s all so easy. And being one tap away from new music, on your device, is something that’s very cool – and cool enough it’s a little hard to explain exactly why. And knowing it will sync back to your PC, and there’s no downside to buying on your phone vs. buying from your desktop, really takes the last bit of worry away.

So nice work, Apple. You gave me a feature I didn’t want, made it easy for me to play with it even though I wasn’t interested, and you convinced me.