Tick said:
If you're at all technically-inclined, running XBMC on a Raspberry Pi is a pretty sweet option. It's not as easy to set up, but the interface and library management (can run off a MySQL database) is pretty slick. Cheap, too.
I have two OpenELEC HTPCs at home and one Raspberry Pi. All running XBMC and networked to the same home server and database. Can pause/resume among devices, track watched, use apps, etc. Pretty happy.
Still trying to find a good OTA antenna solution, though. About 20 miles from downtown Chicago, but plenty of walls/trees in the line-of-sight.
Can you link to a tutorial on setting this up?
The best setup will be dictated by your needs. Are you primarily watching Netflix or Amazon Prime? Stored content on your home network? Live TV?
Basically, the most robust and flexible setups have a home server networked to clients around the house. That home server can stream local content to the clients, and the clients can still pull content from the internet as well if they're configured for it. This is the setup I use.
Don't let "server" scare you. It can mean a Linux-based dedicated NAS with a RAID-5 array, but it can also simply mean a home PC with sufficient storage. In my case, it's the latter. I have a Win8 PC with five hard drives (one 512GB SSD, 1x4TB + 2x3TB + 1x2TB) that sits in my office and looks like anyone else's home PC. It just has lots of storage capacity and is always on.
The benefit of a home server is that not only does it stream my content locally, but I can also use Plex to stream when I'm on the road. My home server also acts as my personal cloud server. I can use
TeamViewer to remote into it and use it as though I were at my desk at home. My in-laws need their boarding passes printed before leaving for the airport and I'm not home to help? No problem. I need my passport number and I don't have it -- it's scanned on my home server and I can look it up. Want to show a friend a photo you took of a recent vacation but you don't have it with you? Pull it up on the home server. It's like a cloud service with storage limited only by what you install in it, no ongoing fees (other than internet), and under your full control. It is limited by the bandwidth of your home internet service though, so sometimes it's worth it to bump-up a tier if you find things are too slow.
Anyways, that's my pitch for why a home server is good.
As far as clients, you can choose many different options.
HTPC: The most flexible. The
Assassin HTPC blog has some fantastic guides for building these (lots of stuff on servers too). I'm running one Intel-based and one AMD-based. I originally fought for months and months to get them stable and wife-friendly (e.g. working without having to screw with settings every time you turned it on) using Windows 7/8 but finally gave up and installed
OpenELEC. What a dream. While this limits the functionality of the PCs to home-theatre duties (can't use them as regular Windows PCs), they're stable and my wife will finally use them. And not roll her eyes every time I fire them up.
Off-the-shelf clients: A wide variety here, but less flexible. The Roku is great for streaming media from the internet. Not so great at streaming local media (DLNA required, no ISO support, etc). The
Western Digital Live series of devices are great at both. There are many more that I won't go into detail about. Just as a note, my mom and my in-laws both have WD Live Hubs, and use them for their stored/streaming media needs.
Raspberry Pi: A bit of a hybrid of the first two.
Here's a guide about putting RaspBMC on one. I have one in a spare bedroom that works great. My TV is even CEC-compliant so it passes through the remote commands to the Pi and I don't need a custom remote or receiver (the Flirc he mentions). The
Flirc is a great device though and I have one on each of my other two HTPCs.
I have made a few posts in other threads about my setup but they're getting to be a bit stale. Check
this one out for the basics on my home network and how I have things set up. Many of the devices on the network have been retired but you'll get the idea.
If you're running multiple
XBMC clients and you want to share the same library (which then permits pause/resume across devices and shared watched/unwatched flags), then installing a mySQL database on your home server is in order.
Here's a guide regarding that.
This all seems pretty daunting at first, but think of it as modular. You only build the pieces you want and can start small. I started with a single box that acted as both a server and a client. Now I'm running three clients. I installed
Plex on the server so that I can stream to my devices on the road. This weekend I plan to put a
HDHomeRun on my network so that I can get live OTA TV in XBMC. I have also put IP cameras on my Network, devices that can stream my DirecTV over the web (
Belkin @TV), etc, etc.