The first thing I wanted to accomplish on my endeavor to create the ideal solution for home entertainment and automation was, quite simply, the entertainment aspect. I had an AppleTV (first generation) that had served me well, but I was recognizing a number of things I wanted to do but could not due to limitations of the device itself (the first generation AppleTV was designed as a front-end for iTunes, and required syncing media to the device or streaming it from an iTunes library).
While researching various media center alternatives, I ran across two applications that I really thought showed promise (in other words, I really like the look of the application and the way in which it would integrate with my existing media library). The first of these was Boxee (link), and the second was Plex (link). In the end I chose to use Plex as my preferred interface, and began constructing a solution around what would or would not work with the application.
Section One, Building Around Plex
Plex was originally derived from XBMC (X-Box Media Center), which was a well-known media center front-end. I looked into XBMC, but at the time I just really disliked the interface (I was testing these on a MacBook Pro, so there is a chance that the bugginess I found and the issues I had were related to relatively new hardware and incomplete support. Regardless, I fell in love with the Plex interface and never second-guessed my decision).
(Screenshot From Plex Website)
(Screenshot From Plex Website)
There were two things I wanted to ensure I could do that I could not accomplish without building a solution around my app and platform of choice, however. The first of these was to decide how to accomplish using a remote control instead of a keyboard and mouse, or how to restart the system if the need arose. In addition, I wanted the system to be easy enough to use that friends and family could control the system without any real learning curve. To that end I found the following things would be necessary to make it a true home theater/entertainment experience devoid of frustration:
1) “Universal” Remote.
2) Intermediary of some sort that could activate system actions by using the remote.
3) How do I make it as user-friendly as possible without creating a bunch of scripts and labeling a keyboard as a remote?
4) Thinking even more about it, what is the best thing I can do for storage? The Mini certainly can’t handle a growing library, and provides no backup for drive failure.
Section Two, Answering the Questions
As it turned out, these questions were far easier to answer than I could have ever guessed. The answer lies in two very powerful, and yet very easy to use, pieces of software. The first is Remote Buddy (link), which is basically a piece of software that runs on the Mini and “intercepts” signals from a remote control. In turn, a menu will pop up on the display that provides access to any functions that you choose to configure (but don’t think you have to configure anything, I left everything with the default settings, and it works beautifully).

(Screenshot from CNet Website)

(Screenshot from CNet Website)

(Screenshot from CNet Website)
Not only does Remote Buddy provide the perfect answers for questions two and three, it also provided me with the ideal answer to question one: the tiny, unobtrusive, easy-to use remote Apple includes with the AppleTV (or that can be purchased with any computer, or separately). Even better, if I ever decided to use a true universal remote (such as those manufactured by Logitech), I could simply add controls for the remote in the Remote Buddy configuration.
The second piece of software came later, actually, with the release of the iPhone and the development of native applications. At that time I wanted to be able to use my iPhone as a remote in addition to the Apple Remote, that way I could always have a remote within easy reach. The answer to that question was also easy to find by way of an application (with a server component that runs on the Mini) called Rowmote (link). In essence, it turns the iPhone into a virtual Apple Remote, which means that it is just as easy to use as my original setup.
It should be noted here that, recently, the good people who develop Plex have also released an official application that serves as a front-end for controlling Plex in general, and also allows you to stream something you choose to watch over the air (3G or WiFi) to an iOS device. I’ll come back to this in a later section, but wanted to mention it here in case someone is looking to achieve the same results and wants to invest the least amount of money.
This left me with one question unanswered: storage. I have a rather large iTunes library as it is, and wanted that to be accessible to Plex in addition to any content I chose to add to Plex exclusively. Further, I needed a good solution to house all of these files that would not set me back months, or potentially more, if a hardware failure occurred. It was not until recently that I actually implemented a solution I truly like, which I’ll come to in a later segment as well, but I found that using four Western Digital MyBook drives was a good, inexpensive by comparison, beginning. I elected to use four so that I could house my data on two and use the other two to “mirror” the originals. This way I at least had some redundancy if a drive failed, though I knew it to be an inelegant solution.
Section Three, Wrapping It Up
This was how my Home Theater setup began. In the next post I’ll go over how these items changed to become what I use today, which isn’t really a large change from where it began honestly. I’ll include screenshots of my setup instead of the defaults, as well as explaining how some additional applications (like the new Plex Remote application for iOS devices) have made this a very robust, and very nice, full setup. In the section after that I’ll go into the home automation side, and why I chose to include it in my Home Theater setup instead of doing something else entirely.













Recent Comments