Slashdot Mirror
MythTV Compared with Windows Media Center
legoburner writes "Tom's Hardware has a nice comparison of MythTV and Windows Media Center Edition, and it seems that they preferred MythTV by quite a margin: 'Enter MythTV, a grand unification of personal digital video recording and home theatre technology, and a magnum opus of modular design, freedom of expression and personal entertainment.'"
Good news Tom's Hardware picks MythTV over Windows MCE (Media Center Edition), but maybe not so much a surprise. Tom's Hardware's preference isn't going to mean a lick to the general consumers. I can't tell my neighbors MythTV is bitchin' because they're not going to have a clue how do it themselves, and I'm running out of support hours and don't have time to set up everyone with MythTV, let alone support it afterwards.
What would be really cool is if some company pulled a Red Hat, or Suse, etc., with MythTV whereby they offer their "version" of a MythTV distribution bundled with hardware and all. With minor standardization, it's a product that could spark consumer interest. This would offer an alternative to the always present MS MCE, and an interesting competition (potentially) with TiVo.
1) Its an article about MythTV which doesn't even really mention MS Media Center except in one small table at the very end
2) The table mentioned above compares Myth against MCE 2004 not MCE 2005 which has been out forever, MCE 2005 R2 which has been out for some time, or Vista which is almost here.
"reality has a well-known liberal bias" - Steven Colbert
Features in MythTV that are not in Windows MCE 2004:
- Open Source; free to obtain, use, and modify
- Software and hardware decoding support
- Output to DivX and MPEG2
- Runs on Linux and MacOS, feeds to Windows (Windows MCE runs on -- guess what -- Windows only!)
- Ultra-low system requirements
- Support for companion and third-party plug-ins
- Scalable network architecture (master/slaves) (MCE has only basic TCP/IP support)
- Record once, transcode and play anywhere (in MCE you can only record and play using the same device)
Features in Windows MCE not in MythTV:
- Simple setup and configuration
Guess which one will have the biggest market share?
Let me speak on both sides. I have been running Linux since 1994, and am not a noob by any stretch of the imagination. I just built a mythtv box, and things are bother better and worse that you might expect. First I chose to buy a PVR-150 card, and to use ubuntu as a base. Both decisions made the process much easier than it would have been otherwise. Most of the set-up was just adding the correct repositories and typing apt-get install. EXCEPT for getting the ivtv drivers running. I have no idea why there is no pre-compiled driver for ivtv for ubuntu. The instructions on the howto pages are detailed about which version of the ivtv driver to use, and how to compile it, so why not just have it available as a pre-compiled module. (I know why don't I pre-compile them and make them available) If the compiled ivtv module was available it would have taken less than 30 minutes to have everything up and running.
Overall I think that the thing that will hold Linux back from becoming really widely deployed is the lack of automation for simple tasks. I wanted to burn a DVD from a show that I recorded in mythtv. I can find several good recipes, including in the mythtv documentation, about how to do it. If it is so easy to write a detailed list of how to do something, then why not automate it.
It enables me to make the ideal media setup, for me.
The potential for separation of backend and frontend allows me to have my loud, big, lots-o-storage system somewhere far away from my TV, and a quiet, yet affordable box with my TV.
My frontend is nothing but a micro ATX case with a motherboard (ASUS A8N-VM CSM), processor (Athlon XP64 3000), and 1 512M DIMM. No hard drive, no extra video card, booting diskless. Thanks to the linux base I'm able to PXE boot, and have a tmpfs root with about 40M of ram used, and nfs mount usr. Now I have a really slick frontend that I can sleep and resume, and it comes up in less time than my TV takes to turn on its lamp right back to whatever menu I left it at, but still have no hard disk whatsoever in it. It's very quiet, and passes the WAF test. The kind of power and flexibility I can get out of a mythtv on linux solution is far beyond anything that involves Windows (try having a fully persistant-storage free (including optical drives or usb storage) windows box that can run MCE and serve reliably as a frontend, persisting through all sorts of activity including sleep... My backend records OTA HD and uses a free service to get TV listings, no subscription, has everything stored on a software RAID5 with 4 250GB disks, and I can access it to make scheduling changes from anywhere via the web if someone say recommends a show while I'm at work. Can also download other media (i.e. fansubs), dump them in a particular directory tree, and the frontend can access it in an easy-to-use interface as well.
One thing I will say is that for more exotic configs, it naturally takes more work to set up than probably other things do, and in allowing the exotic configuration, a lot of confusing options end up facing the novice user (kinda like vi vs. notepad). Also, as it is only part of a full solution, it can't even simplify some config options because it quite frankly has no idea if the user will have a remote, if so what remote, if they will use a keyboard, maybe a joystick, if a joystick no idea on the keymapping... If it will be running backend and frontend type tasks on the same box, if separate the frontend may not know where the master backend is... It has various playback options that work better depending on your video card and such, and while they have a 'decent' default behavior, it doesn't de-interlace by default, doesn't enable any sort of sync to vblank by default, and doesn't enable XvMC by default, because it can't assume any of these are wanted or will perform right with the frontend's hardware. It could be assissted by a discovery architecture for the frontend (if localhost not responding, discover backends), and maybe a hardware/configuration database where it uses, say, lspci data and checks for XvMCConfig and other config files to have a better guess as to what the user can do, but it shouldn't sacrifice the power of it's configurability whatever may happen.
Once configured, it's slick and easy to use, no one has ever been confused by the interface that's used it at my house, I've never had to answer any questions pertaining to usage and once I got everything behaving correctly, I haven't had to touch configuration. Other people have scheduled recordings without being confused or anything, and that's about the hardest task left to do with the frontend. It could be leveraged as a part of a pre-configured solution where hardware and software config is already known (last I heard MCE had particular config requirements, so mythtv's ability to cope with a wider config probably contributes to this criticism).
XML is like violence. If it doesn't solve the problem, use more.
I have some experience with Linux ... I've played with Ubuntu, Red Hat, DreamLinux, and Freespire on my brother's PC, so I only ever get occassional exposure. I'm good with the OS X command line, but don't use it for day to day tasks usually. I'm familiar with apt-get and Synaptic and can usually work around dependency problems.
however, getting MythTV running on my brother's box proved to be really, REALLY difficult.
Enter KnoppMyth.
20 minute install and 10 minutes to configure. And it all just worked. I'm sold.
Plus, he can use his main machine, a Tiger-running Mac, as a front end as well. Its terriffic. Download it. NOW.