This page is up-to-date as of MythTV version 0.27, the current release is 0.27.5
This is meant to be a simplified overview of the various pieces that together compose MythTV. It is hoped that after studying this, users new to MythTV will better understand how it works and be able to make more intelligent planning decisions about their own installations. It would actually be a good idea to read this document carefully, and then read the installation documentation in it's entirety before you actually begin any work at all.
MythTV is basically a big multimedia jukebox primarily meant to record television programming to be watched later ("time-shifted") when it's more convenient to the viewer. The base system also plays video files that have been manually added to the system. There is a plugin to play music that has been manually added to the system (MythMusic). Conceptually there are three parts of the system that perform different functions, and which talk to each other at various points, as illustrated by the diagram appearing on the right.
...also known as "the free parts".
There are three main pieces to the software end of MythTV, but only two of them are actually the MythTV distribution. These can all run on a single machine (provided you have the 1.2Ghz or so of CPU power) or on separate machines, depending on what you'd like to do and just how robust you'd like your home theater media system to be. It's important to understand what role each of these pieces plays in order to be able to make correct decisions about which pieces to run on what hardware, and what hardware you might need to purchase.
MythTV keeps track of programming schedules, configuration information, upcoming recording events (i.e., what you wanted it to record) and the inventory of (both recorded and imported) media MythTV has in a relational database. The database is probably the most important component of MythTV because without it absolutely none of MythTV can function.
MySQL is the only supported relational database that works with MythTV. Use the latest or a recent stable version. MythTV requires version 5.0.15 or higher. Don't get crazy and try using beta or development versions of MySQL unless you're a very experienced programmer and fully intend to take on debugging and patching things to work without any outside help.
The database server is going to need a meager amount of disk space to store the actual database information about what has been recorded and when. The amount of disk space it needs varies depending on a number of factors (whether or not you have a massive music collection, or whether you only have four or five broadcast channels to worry about) but ranges between 256Mb of disk space (comfortable minimum) and 1-2Gb of disk space (not many people will ever have a database larger than this). Also, if there's any part of your setup that you'll want to arrange regular backups for, it's the database files. Without them, MythTV will no longer have any idea of what things it has recorded, and there's no easy way to put things back into the database once those records have been lost.
Unlike the other components of MythTV, there must be only one database server involved. If you want to (for whatever reason, probably masochism) spread the database out to multiple machines using some kind of clustering or replication scheme, go right ahead, it's your equipment--just understand that MythTV only needs one database server and doesn't really have a use for any others.
The backend server is the drab little workhorse part of MythTV that takes care of managing tuner cards, recording actual programs, deleting expired programs, and downloading updated TV schedules. When using hardware encoders and digital tuners, none of these tasks require significant CPU power, and the backend only needs enough throughput to send content to the frontends. The backend also runs one Jobqueue (see below), so it may still be advantageous to have a powerful system to perform whatever batch tasks you may have.
The backend needs to be able to communicate with the database to find out when it's supposed to record programming, as well as keeping track of what's already been recorded so that it won't record the same thing twice (unless you wanted it to do that).
If you use a television service that requires an infrared remote control to change channels (such as Comcast Digital Cable in the U.S.), your back end will need to have an IR Blaster which points at the cable box's receiver. You will need to set up the LIRC software (which also supports remote controls for use with the front-end system) to control the IR blaster.
The backend is typically where you're going to want to have the bulk of your fixed disk storage. The amount of required disk space will vary with user preference and content, but with new drives readily available for under $0.033/GB the purchase of new and very large disks should not pose a problem. Although an external dedicated fileserver isn't out of the question, the backend process is where most of the tons of realtime video data will be coming from so it makes sense to keep the backend process and the bulk of your disks as close together as possible.
You may set up multiple backend machines with multiple tuners in each and MythTV will handle distributing recording among them just fine. You may however only have one master backend that tells the others what to do.
The frontend client is basically the graphical interface that shows you the menus and displays the videos on your screen, so obviously it needs X to be on the same machine. Since it is the interface, this is also likely the best place to install any IR receivers or transceivers you have so that you can use a remote control with MythTV. Because of the way the plugins work, it's also probably the logical place to install an optical drive if you intend to watch DVDs or VCDs with MythTV. What it doesn't need is any particularly large amount of storage space since it doesn't really write much except the cached theme files.
Mythfrontend gets it's configuration information (including where the backends are) from the database so it must be able to talk to the database. It gets information about which tuners are available and almost all video data from the backend server, so it needs to be able to talk backends as well.
You may have as many frontends as you wish, but understand that the number of them that you can watch different live television programs with will be limited to the number of active tuners you have. If you want to have a frontend in your study, and another frontend in your living room, and you intend to watch a different live program on each, your backend(s) will need at least two tuners installed.
...also known as "where has all my money gone?"
CPUs and RAM
CPU power is very essential for a number of the tasks MythTV performs. While the frontend doesn't really use much more power than is necessary to play a video in full-screen mode and the database really doesn't work all that hard at all, the backend can use literally as much power as you can possibly throw at it if you plan to do transcoding or commercial flagging. If you plan on doing framegrabbing (this is only applicable to analog tuners without hardware encoders, which are not likely in any modern system) you're going to need lots of CPU power, preferably about 1.2Ghz per tuner. Commercial flagging is fairly CPU-intensive, but transcoding really takes the cake since technically it's doing as much work as playing a video plus the work it takes to compress that video all over again.
The frontend and database server don't particularly benefit from a dual-core or multiprocessor system, but the backend can potentially be running many tasks at the same time, and dual-core setups can be very useful for this. What you can't do is split one job between multiple backend machines, but aside from that, more CPU == good, with the absolute lowest acceptable minimum being about 600Mhz for machines with only one (non-framegrabbing) tuner and a frontend playing back standard-definition (a.k.a SD or "normal" TV) content only (high-definition content would be a recipe for failure) and job prioritizing very carefully arranged. Unless you're a Linux guru, stick with the former 1.2Ghz per tuner specification.
MythTV by itself doesn't need a huge amount of RAM, although there are some factors to keep in mind. Most people's setups with everything running on one machine and a single tuner card should be able to get by with a mere 256Mb of RAM. Definitely allocate about 256Mb of RAM per framegrabbing task if you intend to do framegrabbing, although again, a hardware-accelerated tuner card makes the effort required to record quite minimal. Most people will probably find 512Mb of RAM a very comfortable amount of memory for the machine.
Disk storage is going to be the system's life blood. You will be amazed at how quickly your new MythTV box can just gobble up disk space. Standard definition recordings will typically use 1-3GB per hour, and high definition recordings will use between 4-8GB per hour. Depending on how you recorded the video, you may be able to transcode to a higher efficiency format. Transcoding can save considerable space, depending on the amount of compression already in use. Transcoded to x264 HD video uses 1-3GB per hour with no noticeable quality loss when you use appropriate settings. Video requires a lot of throughput compared to other tasks, but it's nowhere near the levels of throughput even older IDE disks can supply, so you needn't worry about needing a RAID striping solution. What you will want is simply lots and lots of disk space for the backend.
The only other serious thing to keep in mind about disk space is what will be used by the database. The amount of space the database is going to need will vary between 128Mb at a bare minimum (someone using no plugins who only has four or five broadcast channels) all the way up to possibly as much as 1Gb of disk space (people with satellite TV, a giant collection of mp3s using MythMusic, and archiving some things into MythVideo). Most people should consider 256Mb~512Mb of space for their database, and it's probably a good idea to make this space into it's own partition to ensure that nothing else (or you) can accidentally fill up the available disk and cause the database to crash and become corrupted beyond repair. Once the database is destroyed, there is no easy way to get the information about what you had recorded back into it without simply restoring a copy of it from a backup you probably didn't make. This is why a weekly backup of the database is an essential component of the system.
MythTV does not rely heavily on the network for anything much except pulling down the program guide information, so if all you have is a on-demand dialup gateway at home, you should be fine. If you go for an advanced configuration with separate frontends and backends, although streaming video across a home network can use a bit of traffic, a plain wired fast ethernet network (i.e., 100base-T cabling, 100Mbit) should work for several frontends with standard or high definition content. If you plan on using multiple backends or copying these resulting massive files around your network from one machine to the other, you're probably going to be much happier with Gigabit ethernet (i.e., Cat5E or Cat6 cabling, 1000Mbit) and a switch. There are also tuners that are network attached and if you are using one of these then Gigabit ethernet is the way to go. If you are setting up a new network, definitely you should got with Gigabit throughout, since the cost is not much more than 100Mbit.
Wireless throughput, on the other hand, tends to fluctuate more than most people realize due to all the various and sundry things that can interfere with it, so don't expect 11Mbps 802.11b to handle it without the occasional hiccup. 802.11g or 802.11a (if you can afford it) is somewhat recommended, and should offer enough bandwidth for a single HD stream, but the real problem is consistency of throughput, which radio devices tend to lack. Users are reporting good experience with 802.11n equipment, which promises to be more robust against interference, however you still share a limited amount of throughput with all connected machines. Do not expect to get the advertized speeds with wireless and do not expect to run a remote frontend with HD on a wireless network.
A better option than wireless is powerline network adapters. Like wireless you do not get the advertised speed, but an adapter that advertises 500Mbit speeds can deliver 50Mbit speeds and successfully work with HD.
Some of the other pieces you might need would be an optical drive, and of course the ever-present infra-red remote control required for high "spousal acceptance factor".
A DVD burner (even a dual-layer model) installed to the frontend can be used by a plugin called MythArchive to burn backups of videos you've recorded to DVD in a format that consumer DVD players can play back, and thankfully they're pretty cheap. A DVD player application is built in, and it can make use of a DVD drive as well.
A good remote control is probably what most people would consider to be an absolutely essential piece to add to the frontend. Some tuner cards come with an infra-red receiver element and remote control, but even if yours doesn't you should be able to get a nice generic remote control at department stores, and there are a few places mentioned on the wiki that can sell you a pre-built receiver or transceiver on the cheap. Those of you who are planning on trying to record premium content (i.e., content that is normally scrambled but gets descrambled for you by the cable box you get for being such a well-paying subscriber) will probably need to consider also purchasing an infra-red transmitter or transceiver (one that both sends and receives IR signals) so that the MythTV box can emit the IR signals necessary to tell the cable box to change channels.