How To

Firmware update available for WD TV

There’s a firmware update available for the WD TV. It’s version 1.01, and you can download it and install it right now from the WD website. A lot of issues were resolved. The complete list is available in the release notes.

Here’s a summary of the salient points:

  • Now you can update the firmware when using a drive larger than 500GB. You may think this is an unlikely scenario until you try to use a large storage device like the Drobo with the WD TV.
  • Better subtitle support (SMI, SUB, ASS, SSA, MKV) with user-selectable font size for subtitles
  • Disk volume name display in folder navigation; this was an annoying bug, as you couldn’t tell which drive you were browsing if you had two of them connected to the WD TV
  • Jump feature: while fast forwarding or rewinding, if next of previous buttons are pressed, the WD TV will jump 10 minutes forward or backward
  • EXIF orientation flag functionality for auto picture rotate. Thank goodness! It was really annoying to have to turn my head sideways or bother with the rotate feature every time a photo taken in portrait mode was displayed.
  • Display sizing menu for photo playback: fit to screen, full screen, keep as original
  • Resolved issue where WD TV would not turn back on with remote after extended period of inactivity; previously WD TV had to be unplugged and was unrecoverable with the remote
  • Added 1080p 24hz support
  • Resolved info bar display issues in PAL (European display standard) mode

It’s important to note that there’s still a known and unresolved issue, namely this: if the user unsafely removes an HFS+ formatted drive from the media player without using the Eject button, the drive will become read only media. I’m not sure when this will be resolved.

The installation instructions for the firmware are what one would expect them to be and fairly simple to follow. I’ll reproduce them for you here from the WD release notes for firmware version 1.01:

  1. Go to and download the latest firmware update compressed file for your Media Player. (Here’s the direct download link for version 1.01.)
  2. Click “Downloads” then the product name (or photo).
  3. Extract the two files (.BIN and .VER files) to the root folder of a portable USB drive.
  4. Connect the USB drive to the HD media player’s USB port.
  5. Press HOME, and then select the Settings bar.
  6. Select the firmware upgrade icon, and then press ENTER.
  7. You are prompted to perform the firmware upgrade.
  8. Select OK on the firmware update prompt, and then press ENTER.  This will restart the system.
  9. After restarting, the system automatically enters firmware upgrade mode.
  10. Once the update process is completed, the HD media player will restart again.
  11. Once the HD media player restarts, the new firmware is automatically loaded.

Is it easier to design for the enterprise or for the consumer?

I was thinking about the difference between hardware and software products designed for the consumer and those designed for the enterprise. In particular, I thought about how vocal consumers can be nowadays vs. companies, and how that affects the process of making and selling products to them vs. the business market. I think it makes it more difficult.

You’d have to be braver, as a company, to put your product out there for the consumers in this day and age when anyone can chime in and voice their opinion on the Internet — even when they’re not well-informed, or worse, they intend to do harm to your brand, for whatever reason. Whatever the pitfalls of this brave new age of feedback, it is a good thing, as you’ll see by the end of this article.

On top of that, consumer needs are a lot more varied than business needs. It’s notoriously hard to figure out what people want. Let me ask you something: when was the last time you spent your own time filling out an online survey? If you’re like me, that’d be years ago. How about filling out a survey at work, on the company’s time, because you got an invitation from one of the vendors? I bet that happens quite often. So you see, businesses making stuff for the enterprise have a much easier time figuring out what customers want, while those making stuff for the consumers are stuck paying people to take surveys and doing focus groups and who knows what else in order to get an idea of what they want.

Individual taste is also something that enters into the equation. Individuals will have different tastes, and while your product may appeal to someone, it might appear downright ugly to the next person. Generally speaking, taste and design have little do with enterprise products, which are utilitarian and function-oriented. They are meant to perform certain duties, and as such, not much thought is given to how they look.

How about the difference in ease of use between enterprise products and consumer products? I don’t think I can think of a single instance when an enterprise product was easier to use than a consumer product. Not one. Sure, they perform more complicated tasks, but still, little thought (if at all) is given to making the user interface easier or more intuitive. Mostly, enterprise products are difficult to use, difficult to navigate (if they’re software), difficult to learn, and overall, frustrating. You simply can’t get away with that when you make stuff for consumers, because no one will buy your products. They’ll laugh you right out of the marketplace.

Finally, how about price? Isn’t it true that enterprise products are insanely expensive when compared to consumer products? And yet, the rationale for that huge price difference is always hard for me to find. Every time I ask why they’re more expensive, the answer I get is because they’re enterprise products. That’s never been a good enough explanation for me. Sure, the market for enterprise products is smaller, and you have to price them higher in order to sustain your business — the economy of scale just isn’t there to make up for a lower price. Plus, the stuff you make for the enterprise has to perform more complicated tasks and be more reliable under heavy levels of use. But I’ve always believed that enterprise products were overpriced simply because they’re marketed for the enterprise and for little else — and I haven’t yet been offered any conclusive proof to the contrary.

A few examples came to my mind as I thought about all this. Let’s call them mini case studies. I want to look at each one in particular. First, we have two consumer products, the Drobo and the WD My Book Pro Edition II:


The folks at Data Robotics had a tall order on their hands. They wanted to come up with a consumer-oriented product that would give people the benefits of RAID, the ability to increase storage space on the fly, the flexibility of using drives of any size, and a dead-simple way to replace hard drives. Did they succeed? Yes, I think so. On top of delivering on all of those functional criteria, they managed to design a beautiful enclosure, too.

Were the odds stacked against them? I think they were, and while people are enthralled with the product once they begin to use it, there are a lot of questions they need to answer for themselves before and after the purchase. One of them is the file system, called BeyondRAID. Is it compatible with other file systems? Can you get the data off the drives without a Drobo? Another issue is the price. People find the entry price expensive, and they’re quite vocal about that, wherever you look. (For a representative sample of what people think, just look at the comments section of my Drobo review — the 110 comments posted there should give you a pretty good idea.)

Besides all of this, the Drobo is a new product, literally. There is nothing quite like it on the market. Sure, it works in comparable ways to other external storage products out there, but still, the inner workings are new, and the way in which data is stored is new. That means resistance, automatically. When you go against the grain, you get friction. It’s the way things work. So that’s why I say creating the Drobo, marketing it, and actually selling it and getting people to use it properly was a tall order.

Data Robotics had to work extra hard at this. And it was crucial that they provide good product support, or they would have failed. When I say they provide good support, I mean it. You might say I’ve been a frequent user of their support plan — and the Drobo folks might say they could have done with a little less complaining from me.

If you should read through my Drobo review, you will see what problems I had. My situation was a bit different than most. I have three Drobos, two with me in the DC area, and one with my parents in FL. I got a chance to see how the Drobo would work through the changing seasons of a temperate climate in the DC area, on a PC and on a Mac, and also how it would work in a pure Mac environment, in the sub-tropical climate of South Florida.

Now my primary Drobo is a new, second generation, Firewire unit, which I’ve been using happily for the past couple of months. But over the past year since I bought the Drobos, I had noise issues and various other bugs that surfaced through my intense use of the other units, and I went through a few unit exchanges and many email conversations with the folks at Data Robotics. I can say, without a doubt, that they’ve been responsive, courteous, helpful, and even went out of their way to help me sort through the issues and replace units that I didn’t think functioned correctly.

What was their motivation? Perhaps they’re just good people. That’s quite possible. But that’s not what this article is about, is it? It’s about the difference between making consumer and enterprise products. So I think in the end it boils down to needing to work extra hard as a company, because they’re not only making a product for the consumer, but they’re making a new product and they need to carve out a slice of the storage market. Sure, they’ve got good name recognition now, but they’ve had to work extra hard at it, and I think that played greatly into the level of customer support they provided. For me, it’ll be interesting to see how their customer support evolves over time, as they become a more established company.

Western Digital My Book Pro Edition II

This external storage device was an example of how not to design for the consumer market. The drive was meant for the Mac user, although it could be used just fine on PCs. It was a triple interface (USB2.0, FW400 and FW800) device, but it only worked on USB or FW400, depending on who you talked to. It also overheated frequently, and it sometimes crashed the computers to which it was tethered. As if that stuff wasn’t bad enough, some people experienced data loss, or the inability to get at their data because the drive would either crash their systems or it wouldn’t stay on long enough for people to copy their data off it. For a good summary, see the Wikipedia entry for the WD My Book drives, or have a look at my two articles about the drive, one of them the original review, and the other detailing the problems I’d had with it. (I’m one of the cited references on Wikipedia.)

WD Support were responsive, but, at the first lines of phone support, also clueless. The were willing to help, but all they could was to keep sending me refurbished replacement units, each one in worse cosmetic shape than the other, and all exhibiting the same issues. The problems unfortunately ran deeper than a replacement with this line of drives, and WD never really came clean and confessed, which would have helped their image quite a bit. Instead, they were content to sweep the complaints under the proverbial rug and hope they would somehow go away. That didn’t happen. People were getting even more vocal, and there was quite a bit of talk about a class action lawsuit at one time.

I think the problems with the My Book Pro line were hardware-deep. I know WD tried to fix them via firmware upgrades, but they were only partially successful. While the enclosure design was nice, it didn’t lead to easy cooling of the drives, and they overheated. The circuit board was also not successful, and the USB and FW connections tended not to work properly. The on-board thermometer likely didn’t measure temperature correctly, and shut off the units prematurely because it thought they were overheating. It also caused the fan to run into overdrive, which made an awful racket.

Thankfully, a few people among the WDC executives saw the greater picture and stepped in to help in individual cases. I was one of those lucky cases. I got another replacement unit, this time a My Book Studio Edition II drive, which has worked wonderfully for me since day one. Stepping back from my case, I believe that if Western Digital hadn’t mended its image with the My Book Studio Edition, things could have gone badly for them. Just look at the comments left on my two articles (23 on the review and 104 on the one detailing the problems), and you’ll see that people were getting progressively angrier with the company.

I think the problem with the My Book Pro line of drives is that it was put out by a large company. WD just doesn’t look at the market the same way as Data Robotics does. First, they’re one of the big players in the storage market. They not only make enclosures, but they make the hard drives that go in them as well. That’s actually the biggest chunk of their business. When they launched the Pro line, it was just another model line in their large product lineup. Did they do proper product testing and QA? The tally of the real-world results comes in at a resounding no. Did they listen to the customers as the first problem reports came in? No. Did they address customer issues appropriately? No. I bet there still are plenty of My Book Pro users out there who can’t use their drives properly, if at all. I think things went differently in my case because I was vocal about it. My article gained traction and as it started to come up on the first page of Google search results (it was up among the first results for a while), and it posed a real threat to the company’s public image, which they needed to address.

As a side note, I’m glad they chose to address my case correctly. They were polite and helpful in their interactions with me, and while I had to wait a long time to get the final replacement, I didn’t get bullied in the meantime. That was nice.

To get back to the root of the problem, WD just didn’t look at things properly. They put out a faulty product because they thought they could afford to do so (they probably didn’t think that as they were making it, but when a product is one of many, that’s the unspoken thought). They had a dismissive attitude toward the consumers because they were big and thought they could ignore them, and in the end, it cost them.

Now let’s have a look at two enterprise-level products and see how the rules change in this market. I’ll be talking about a DNF SAN and VMware. First though, I want to look at customer feedback in the enterprise arena.

How feedback works (or doesn’t) in the enterprise market

What you’ll find here is the customers (the companies, rather) will tend to be much quieter than consumers when things don’t work as expected. This happens for multiple reasons.

For one thing, companies as a whole don’t have an outlet where they can complain about things like this. The larger the company, the tighter the rein on public relations, as they call it. You won’t find employees going on the company blog and writing about their bad experience with a product. It just won’t happen, because at traditional companies, every post tends to get vetted by multiple pairs of eyes, each concerned with legal and marketing and general image issues.

If the employees won’t do it, the company executives won’t do it, unless it’s off the record, among themselves, at certain gatherings. It won’t be in the public arena, unless a particular products stinks very badly and the company needs to blame it in order to account for poor results during a quarter or year, etc.

You also have resistance from within to let others know that a product is a real stinker. After all, when you’ve just spent a few tens of thousands or more on some fancy piece of hardware that’s supposed to solve your problems, and you find out it stinks, you can’t very well go to the executives and tell them you need to spend another five or six figures on another piece of hardware, because they’ll think you’re incompetent and you didn’t do your homework before recommending the purchase.

Another reason is that you don’t want to spoil a partnership. If your biz dev guys have just worked for months to get a partnership started and the company has put out marketing materials advertising said partnership, and there is promise of work in the future involving said partnership, you can bet your bottom dollar your company’s not going to go public with allegations that a certain product made by their gold/platinum/diamond partner stinks. And if you raise too much of a stink, internally, about said product, you’ll be told you’re not a team player, and you can’t be trusted to work with the valued company partners. What’s more, if the tone of your emails toward said partner gets angry, you may even be counseled.

There’s another ingredient to throw in this mess: the fact that most (if not all) support forums for enterprise products are behind login screens. Even if you should log on as an enterprise customer and voice your complaints on the company forums, those complaints will not show up on search engines, and other potential customers won’t be able to see that you’re having problems with the product until they, too, spend ridiculous amounts of money for the right to use said product and log onto the product forums, after which they find out they should have stayed away from it.

What you’ve essentially got is a muzzle on the customers in the enterprise market, for the reasons stated above. Is it any wonder then, that the companies making such products have very little incentive to be responsible, and to make good products? They can afford to charge ridiculous amounts of money for buggysoftware, ugly hardware, and despicable user interfaces, because the enterprise customers will pay for them and like it, or else.

Now, I’m not saying this is what happens most of the time, but let’s face it, when you’ve got a muzzle on your customers’ real-world experiences with your products, there’s little to keep you from going in the wrong direction and staying that way.

DNF Storage SAN

At one of the companies where I worked, we used to call it the “Does Not Function” SAN, which was a (sadly) true play on the acronym for its maker (Dynamic Network Factory). This SAN was purchased for the sole purpose of working with a VMware server cluster to act as storage for the company’s virtual servers. It never worked correctly. It was supposed to connect through iSCSI to the servers that controlled the cluster, and the iSCSI kept failing, time after time after time. Sometimes the RAID would fail, too. Throughput could never be maintained, the virtual machines sometimes didn’t want to boot up or took forever to do so, writing to the disks and reading from them was horribly slow, etc.

When the company called DNF, they got some support, but mostly, they were told the issue was with VMware. When they called VMware, they were told the the DNF SAN was no longer approved to use with VMware’s enterprise solutions, although it had been on the list to begin with, and that’s why it had been purchased.

Bottom line is the company got stuck with this thing which didn’t do its job and cost a pretty penny to boot. The staff bandaged it together and kept it going somehow, with frequent outages, until money could be gotten together so they could buy some SAN devices from EMC (VMware’s parent company). Those were on the aproved list of SANs to use with VMWare — funny how that works, isn’t it?

But wait, the fun doesn’t end here. Once the virtual servers were transitioned over to the new EMC SANs, the company wanted to repurpose the DNF SAN and use it as storage for various backups from their other servers — basically, use it as a network hard drive. It failed miserably at that task as well. First, one or more of the hard drives went, corrupting the RAID array. That meant starting from scratch. Once the setup was completed and another server stood up, people started copying data to it, and it got corrupted again. This time, it went down and stayed down for good.

At that point, after 2 years of struggling with this thing, and the support contract expired (not that the support was worth much anyway), the company was stuck with an expensive piece of hardware that took up space in the server racks and served no purpose whatsoever.


I’ve been working with VMware technology, daily, for the past two years and a half. I worked at a company which I think was at the forefront of using virtualization technology. We had production virtual servers when most companies were still only testing the waters. That was cool. Getting support from VMware with various issues that came up as we transitioned our physical servers to virtual ones and started to use them heavily, was not so cool.

While I wasn’t the main point of contact between our company and VMware, I had to take charge in a couple of situations when the POC was out. I remember quite well this one occasion when one of my production servers went down while live, and I couldn’t get it back up. It simply refused to boot at first, and when it did boot up, the networking went out. I called VMware and filed a support request. I asked them to mark it as urgent. I was promised while on the phone that someone would get back to me within 2 hours. No one did. I called again and was assured someone was researching the issue. I waited several hours. No one got back to me. I then called again, but couldn’t reach anyone. It was already the weekend. I kept monitoring my email account on Saturday and Sunday to see if anyone would get back to me, and no one did. On Monday, the main VMware person at our company was in, and he was able to get the server going again. On Tuesday, a VMware rep finally got back to me and, as if nothing happened, asked how the server was doing. I recounted the story, told him a 5-day delay in his response is not adequate for an issue marked as urgent, and expected an apology. I never got one, nor did I hear from him again. So I had a production server that was basically out of commission for a whole weekend, and VMware didn’t give a damn.

That’s not all. You remember from the DNF SAN story above that VMware kept blaming them for the iSCSI bandwidth/throughput issues. For about a year and half, we had to put up with slower than normal servers that could take as much as a half hour to boot up, not to mention that they’d often lose their networking connection on reboots, causing us to toggle between the internal and external virtual network cards multiple times in order to get it going again. When they did boot up, they just weren’t as fast as they should be. VMware and DNF SAN kept passing the buck on these issues.

When the company finally purchased EMC SANs, the problems didn’t go away, but at least VMware couldn’t play the blame game any more, since it was now their own hardware and software. Even then, it took countless hours on the phone with the VMware and EMC reps to get the issues resolved. After that, it could safely be said that the servers were adequately fast, and they booted up without issues, but bandwidth was still a major issue. Even though the company had a Gigabit network, writing data to and copying data from the virtual servers was still not at Gigabit levels (not by far), and I think that’s an issue with the iSCSI connections between the SAN and the VMware production cluster. This is why I said at the beginning of this diatribe of mine that iSCSI connections are problematic.

Another gripe of mine with enterprise software is that it’s needlessly complicated and badly designed. Sure, their virtual infrastructure client is pretty good, but we tested a piece of EMC (VMware’s parent company) software designed to keep virtual servers in sync (I forget its name), and boy, did it stink… First, it was hard to figure out what do do with it and how to do it. Second, the GUI looked as if it’d been designed in the early 90s by some dude with no taste whatsoever. Third, it cost plenty, too. The company ended up not using it.


If you’ve read this far, I’d love to hear what you think, although I’ll understand if corporate folks reading this would rather not say anything.

I’d also like to make it clear that I’m not singling out the companies and products I’ve named above because I have something against them. I don’t. I do have something against badly designed and overpriced products, no matter who makes them. I think as Western Digital proved, a company can turn things around if they want to, and in that case, I’d be glad to praise the things they’re doing right (see the WD My Book Studio review).

I hope I’ve made it clear that customer feedback is important. It’s very important as a matter of fact. Furthermore, I believe that public customer feedback, as in the case of people voicing their concerns on the Internet about a certain product, makes a company more responsible and more responsive to the needs of the marketplace. It also makes it harder for a company to create products for consumers, because the pressure to deliver a success is greater. But that’s a good thing, because if you’ve got a hit, word quickly gets out and the potential for profit is greater. That should make the bean counters and the execs happy.

When you muzzle your customers though, as is currently the case in the enterprise market, there is real potential for abuse. Companies have little incentive to price products correctly and to address issues that come up once those products get used. There is also no real incentive to design things well, so they look good and are easy to use, and I’m talking about both software and hardware here.

I think that we need to have a more transparent customer-vendor feedback loop in the enterprise markets. I think business customers ought to feel it’s their right as consumers to voice concerns about vendor products publicly if the vendor fails to address them privately. After all, when you’re paying five and six figures (or even more) for enterprise-level solutions, then you ought to get your money’s worth in every sense of the word.


Hardware review: WD My Book Studio Edition II

WD MyBook Studio Edition II - 02

I have been working daily with a WD My Book Studio Edition II drive for the past eight months (since April ’08). I mentioned it back in July in my popular “What’s on my desk” post. It is a quad interface (USB 2.0, FW400, FW800, eSATA) 2TB drive that can run in RAID 0 (2TB total space) or RAID 1 (1TB total space). My review can be summed up in these three words: it works great.

I should say here, just as I said in my other two reviews of the My Book Pro Edition drive (see paragraph below for links), that this drive was given to me by WDC as a replacement for my faulty My Book Pro drive. I didn’t purchase it, but at the same time, I am under no obligation to anyone to praise it needlessly. I do so because it has really worked for me.

After all these months of heavy use, I have nothing bad to say about this drive. I have put it through its paces, transferring terabytes of data back and forth from it to my laptop and to my other drives, I have used it daily, I have put it through sustained data writes of several hundred gigabytes at a time, and it has not failed me yet. In stark contrast to my experience with the WD My Book Pro Edition II drive, this drive has outshined all of my other external storage devices, including my Drobo.

True, while nothing beats the Drobo when it comes to sheer storage space and flexibility in terms of its building blocks (the drives themselves), the My Book Studio Edition II drive has been faster than the Drobo when it came to working with my photos in Lightroom, in both RAID 0 and RAID 1 modes, and it has also been faster when it comes to data transfers (writing to the drive itself).

WD MyBook Studio Edition II - 07

I did not have a chance to use the drive through the eSATA interface. I used it mostly through the FW800 interface, and, briefly, through the FW400 and USB interfaces. Given that it can transfer data at up to 3GB/s through eSATA, I might just buy an adaptor for my MacBook Pro in the future. I was pretty happy with the FW800 speeds though (up to 800 Mb/s).

My feelings about this drive are somewhat harder to understand for those of you that have not had to deal with a My Book Pro Edition drive. If you did not have to put up with constant overheating, data loss, fan noises, disconnects and computer resets while using that drive, then you can’t possibly appreciate how WDC managed to get things so right with the My Book Studio Edition drive.

Somehow, they have, and for me, it’s a pleasure to use this drive. It suffers from none of the problems of its predecessor. It works reliably, each and every time. It’s fast. It’s quiet. It doesn’t overheat. It doesn’t cause my computer to crash. It doesn’t lose any of my data. The enclosure looks even better. The white LED on its front is much less annoying than the blue LED on the My Book Pro. It has greater capacity. It has more interfaces. It has a 5-year warranty, which amazes me when I consider that most tech products have a 3-year projected lifespan. The list goes on and on, and I have only good things to say about it.

The drive uses the new GreenPower drives from WD, which use 30% less energy and do not get as hot as older hard drives. This means the new enclosure doesn’t need a fan. Another cool thing is that it’s much easier to replace the hard drives, since you won’t need a screwdriver. The enclosure opens easily, and the hard drives pull out with the aid of tabs. Having needed to open the enclosure for the My Book Pro Edition drive, I can tell you it was a lot more convoluted than this.

WD MyBook Studio Edition II - 08

The wonderful thing about this drive is that it’s such a great deal right now. As I pointed out in a previous how to article entitled “A look at hard drives: finding the best deals“, it’s always a good idea to compare the price of the hard drives themselves to the price of the enclosure plus the hard drives, to see how much you’re paying for the packaged, branded product, and whether it’s worth it. Well, 1TB hard drives are anywhere from $100-140 at the moment (there are two of them in the My Book Studio Edition II), and the product itself costs about $280-290 right now. That means, if you factor in the best price scenario for the hard drives, that you’re getting a quad-interface enclosure which is quiet and it actually works on most computers (which isn’t something I can say about other off-the-shelf DIY enclosures) for about $80-90. That’s a great deal in my book.

Detailed specs for the My Book Studio Edition II drive are available from the WDC website. You can buy it from Amazon or from B&H Photo.

Photos used courtesy of Western Digital Corporation.


Hardware review: WD My Passport Studio

While the WD My Passport line of portable drives is a couple of years old, their My Passport Studio models are new, and their specs and capacities were greatly improved recently. The My Passport Studio line is meant for Mac users and comes formatted in HFS+, although the drives can be used just as well with Windows machines if they are reformatted to NTFS or FAT32.

On 10/30/08, WD introduced Firewire 800 connections and new capacities (400GB and 500GB) for these wonderful little drives. The base capacity was upgraded to 320GB, and the 250GB size was phased out. These latest drives feature triple interfaces (USB 2.0/Firewire 400/Firewire 800), which is something one normally sees only on external desktop hard drives (the 3.5″ size).

Technology moves fast, doesn’t it? Just a few months ago, the My Passport Studio models featured USB 2.0 and Firewire 400 connections. The top capacity was 320GB. I myself have a 1st generation My Passport drive, a 160GB model with a USB 2.0 connection. I bought it in February of 2007, and it’s worked great ever since.

The more recent models from the My Passport line have something that my 1st gen My Passport drive doesn’t have: an external capacity gauge. I think it’s neat to see how much space is used up on the drive at a glance. These latest drives also have something I haven’t seen before: turbo drivers for faster data transfers. The drivers are available for Mac computers only. I haven’t used the drive yet, but when I get it, I’ll be sure to test out data transfers with and without the drivers, to see if there’s an improvement between the two modes. I hope the drivers are well-developed and won’t introduce any sort of OS stability issues. I’ll also test data transfers between USB, FW400 and FW800.

I’m really looking forward to getting a 500GB Studio drive, because of its unbelievable capacity. It is double the size of my MBP’s hard drive, which is 250GB. I’m going to be able to store lots of photos and videos on it when I’m traveling, and use it to back up important files from my MBP and my iMac. I also think the My Passport line of drives are some of the best-designed portable hard drives on the market.

I can’t find the 500GB model in any online stores yet. Newegg still lists the Firewire 400 models, albeit at reduced prices, and Amazon only has the 400GB model. B&H Photo also only lists sizes up to the 400GB model. I don’t think I need to worry, since it’s very likely that by the end of November or sooner, the 500GB model will be available in most stores.

Photos used courtesy of Western Digital Corporation.


WD TV is better than Apple TV

WD has put a new device on the market, and it’s called the WD TV HD Media Player. It’s a small box that can connect to a TV via HDMI or Composite output cables, and can take most USB external hard drives as input (it should even read USB flash drives as long as they’re formatted in FAT32). Once a device is connected, the WD TV will read the media from that drive (movies, photos, music) and let you browse through them and play them on your TV. What sets this device apart for me is that it has gone beyond other similar devices like the LaCinema Premier, or Apple TV. I’ll explain below.

The LaCie product, for example, doesn’t play as many formats as WD TV, and can only support NTFS and FAT32 file systems.

You’re limited in the amount of content you can play with LaCinema Premier, since the drive is integrated within the device itself, and because not as many video formats are supported (see the specs on the LaCie website). That means you have to lug the whole thing from your home office to your living room, re-connect it at each place, and copy files onto it when you want to refresh its inventory. The remote also leaves something to be desired (too many buttons).

I know and like Apple TV myself, having bought one and configured it for my parents, but frankly, I find it overpriced and under-featured. The more you use Apple TV, the more limitations you find:

  • It has an internal hard drive that syncs with content over a wireless network, which means you have to wait forever to get a movie onto it. The drive can also fill up quickly, depending on which size you pick. (Yes, you can also connect it via a Gigabit network, if you’ve pre-wired your living room and home office with Gigabit wires already — but most people have not.)
  • You can stream to it, but then you always have to keep iTunes open, and it’s a hassle to remember that, especially when you’ve just sat down on the living room couch and turned on the TV.
  • You also need to be able to troubleshoot WiFi issues in case you’re not getting enough bandwidth and Apple TV playback stutters.
  • You have to add every single video clip you want to play on Apple TV to the iTunes library, and I don’t care for that sort of thing. I just want to store my stuff in folders and browse it from a device (like WD TV).
  • Apple TV has a USB port on the back, but you can’t use it for anything but “diagnostics” unless you hack the device. This is stupid. I can’t use the port to connect Apple TV to my computer and copy content onto it, I can’t use it to connect an external hard drive to it and have it read the content from it (like WD TV), and it just sits there, unused, unless I pay for a hacking device like aTV Flash.
  • It overheats like crazy. It can burn your fingers if you’re not careful.

I love the design of Apple TV and its diminutive remote. I love the fact that I can swap remotes between it and my laptop if I want to. I think the on-screen menus are well done. I also like the fact that it can stream Flickr photos and YouTube videos, but these extra functions are just that: extra-neous. It simply cannot do its basic job well, and that is to play my media conveniently.

I’m not alone in being frustrated with it. Thomas Hawk has written repeatedly against Apple TV, and for the very same reasons I describe in this post. Steve Jobs recently said he’s not sure what to do with Apple TV. He’s treating it like an unwanted step child. It’s not listed in the Mac product lineup on Apple’s website. It sits off to the side in a section of its own, and you have to do a search for “Apple TV” in order to find it. Corrected 11/11/08: It’s listed in the iTunes and More line-up along with the iPods.

For one thing, Mr. Jobs, you can stop being so greedy in your approach to the device and let people use the USB port on the back. Or how about letting people stream Netflix videos with it, so they don’t have to buy a separate device? I’m a Mac user and have a Netflix account. Until Netflix release Roku and opened up its streaming program to Mac users, I was in the dark. You probably don’t want to do these things because it’ll cut into your video rentals and purchases, and you like that extra revenue stream, but the fact remains that sales of the device will always remain low if you insist on hamstringing it.

The WD TV Player, on the other hand, is made to suit most people. It has a USB port where you can connect most external hard drives. It will read NTFS, FAT32, and HFS file systems too. (I found that out from WD Support, because the info isn’t listed among the specs. They pointed me to KB article #2726.) There seems to be an issue with HFS+ file systems, but they’ll still work, only differently. I’ll have to look into that later.

Also not listed among the specs is an Optical Audio port, but when I look at the back of the device, it seems to me I can see one there.

To me, WD TV is the long-awaited answer to my media player needs. At around $99 (street price), this is one device that will make its way to my Christmas stocking pretty soon, because I’ve got a Drobo full of content I’d like to play my way, not to mention that I also have two WD Passport drives.

I may even get one for my parents, to replace their Apple TV. They’ve had to keep their Drobo connected to their iMac in the home office, with iTunes open, all this time, just so they could watch a movie or two from the Drobo. That’s not right. Once I get the WD TV, I can take their Drobo, put it in the living room, and hook it up right there, without worrying about WiFi, streaming, iTunes, and a whole bunch of nonsense. Apple dropped the ball with Apple TV, and WD picked it up and started running with it.

The WD TV supports the following file formats:

  • Music: MP3, WMA, OGG, WAV/PCM/LPCM, AAC, FLAC, Dolby Digital, AIF/AIFF, MKA
  • Video: MPEG1/2/4, WMV9, AVI (MPEG4, Xvid, AVC), H.264, MKV, MOV (MPEG4, H.264). It will play MPEG2/4, H.264, and WMV9 videos up to 1920x1080p 24fps, 1920x1080i 30fps, 1280x720p 60fps resolution. That’s awesome.
  • Playlist: PLS, M3U, WPL
  • Subtitle: SRT (UTF-8)

I plan to get one soon, and I’ll let you know in this post if it lives up to its specs and my expectations. If you’d like to get one too, Amazon lists them. See below.

You can buy the WD TV Player from: