Posts Tagged ‘MythTV’

Some CableCard Content Will Be Available to Linux

Monday, August 16th, 2010

CableLabs, the independent consortium of cable operators which creates specifications for cable television compatible products has approved two measures that will permit Home Theater PCs running Linux to take advantage of some U.S. cable television content.

Cable providers can set copy control information for their content to specify how the content can be duplicated, setting it to Copy Once, Copy Never, or Copy Freely. In the United States, the Federal Communications Commission, or FCC, specified that all broadcast television channels must be set as Copy Freely. Non-premium subscription programming has to be set to at least Copy Once, but of course can be set to Copy Freely. This is where cable providers vary, as some tend to set all programs as Copy Once and others tend to set all programs as Copy Freely.

CableLabs has approved the passing of content coded as Copy Free without Digital Rights Management, or DRM. DRM allows a content provider to restrict what you can do with content once downloaded or recorded. No current Linux based software has licensed or been approved to carry content with DRM, and the decision by CableLabs means that users of MythTV, will be able to decrypt and record some content. CableLabs is charged with approving all CableCard compatible devices.

A CableCard is a PCMCIA card which a carrier is legally obligated to offer on request, which can be added to a tuner to decrypt content. However, until recently, PC CableCard peripherals were extremely limited. Two manufacturers have worked hard to open up the PC market to this hardware and have advocated for Linux support. Ceton, just recently launched its InfiniTV4 PCI-Express card, and Silicondust, creators of the popular and Linux compatible HDHomerun networked digital tuner are set to release a cablecard enabled version later this year.  Jeremy Hammer, VP of Systems integration for Ceton, and a Fedora user, advised that the Ceton product will fully support Linux and to the extent they are able.

Unfortunately for us, our service provider, Time Warner Cable, sets nearly everything to Copy Once, this rendering the device pretty much useless unless they change their ways. Comcast, however, apparently is much more open(surprising, isn’t it?), setting most of its non-premium content to Copy Freely. Being as you need to rent the cable card from the cable company anyway, we do not see the point of restricted content they know you’ve paid for.

However, we’ve never quite gotten the point of DRM in general. It more often restricts legitimate usage over actually stopping piracy. And as we’ve been reminded recently, fair use for recorded content is not to keep it on your hard drive forever. If you really like something enough to keep, you probably should buy it. You’ll get a better quality version…and if you’re lucky…extras.

  • Share/Bookmark

The Other MythTV Rig

Friday, April 9th, 2010

We recently did a review of our setup. But, we omitted the Other rig, where old parts come to their final resting place. Most of the parts here were once part of the primary rig, and have moved to this secondary location.

The rig in question, codenamed Glendale, is an AMD X2 BE-2400 low wattage processor, the same we use for one of the frontends in the main setup. But this one pulls double duty as both a frontend and a backend.

Inside are two old PVR-150s, as this location still has analog cable service, which has been eliminated at the primary location. There is also a Silicondust HDHomeRun, gotten inexpensively during a Black Friday sellout. The location has absolutely no broadcast reception. We figured, if the recorder ever goes out, any old system can stream from the Homerun, including a netbook.


The system has an old refurbished 250MB hard drive, which had failed in the primary backend and been replaced by the manufacturer. A recent addition is that of two E-Sata ports. Since this is a less frequently used location, we bring up video material to enjoy over recording it on location. E-Sata even would allow us to make the entire media drive for this system external with no loss of speed.

The stand is an audio stand we found one day on clearance at Staples, marked down to $10. On top of the Antec MicroATX cube is an old Radio Shack amplifier, hooked into some old speakers that used to be part of a Cambridge Soundworks speaker set. Next to it is a refurbished digital photo frame, and below it is a mini-keyboard and mouse.

The whole assembly is hooked into an APC power strip with a master control outlet, so when the computer shuts down, all the peripherals, including the monitor, shut down. This is useful, since this system takes advantage of a feature we don’t use at the primary site, ACPI wakeup. When there are no recordings, the system can be shut down and programmed to wake up in time for the next recording.

During the trip when these pictures were taken, we added VDPAU acceleration, so the system can encode the files recorded off the HD-PVR at our primary location.

As mentioned previously, we have hopes of upgrading our primary monitor to one that is HDMI capable, at which point we’ll net a widescreen monitor for this location to replace the current 19″.

The system runs Fedora, as is our custom. We have thought, as this is isolated from the rest of the systems, of switching to a distribution such as LinHES, MythDora, or MythBuntu. More on this if it happens.

  • Share/Bookmark

MythTV 0.23 Release Candidate 1 Released

Wednesday, March 24th, 2010

Watch Recordings Menu under Graphite theme

Today, the MythTV Development team released the first release candidate for version 0.23. Highlights include:

  • Beta of MythNetVision, which we previously reported on. MythNetVision is a an official Internet video plugin being developed for . It uses user contributed scripts scripts to parse information so that it can be extended to additional sites as time goes by. When possible, it will download the video to the drive. Otherwise it will launch a browser(MythBrowser or otherwise) to view it.
  • Rewritten Audio System
  • A New Event System to trigger user specified actions when certain events occur in .

Looks good so far. We’ve been waiting for MythNetVision, and a lot of the fixes set to come with future versions. The best news is the more rapid release cycle. The gap between 0.21 and 0.22 was much longer than anyone preferred. Hoping to see more.

  • Share/Bookmark

MythTV Rig: Part 3 – The Home Theater Frontend

Sunday, February 21st, 2010

As the third part, and for now, the final part, of our multipart series, Better Know a MythTV configuration, we profile the second of our frontends. This frontend is the older of the two, and is hooked into some home theater equipment for a more immersive experience.

Now, with all of these systems, bear in mind they’ve been designed, redesigned, expanded, etc. But we are, by no means wealthy over here. Some concessions have been made, and parts upgraded and replaced as financial and practical considerations demand it.

The current system was built when HDMI was still at the upper end of hobbyist grade. Now, many computer monitors and amplifiers include HDMI switching. This system was designed originally with component video in mind, at the cusp of our upgrade to HD programming. It is set up for expansion, and likely will be, piece by piece in the future.

As you can see, we’ve continued our modular Ikea furniture theme from the other setup. Originally we did have a more conventional audio rack here, but switched to these two separate pieces. The router, the Silicondust HDHomerun, and the modem are actually stored in the bottom of one of those cabinets, and the glass door hides a tape deck and could hide additional equipment. An IR remote control would actually work through that glass.

Both rooms where you see the frontend setup were designed as possible backend locations. The whole goal of a redesign we implemented over the last two years was to allow us to rearrange the equipment in a variety of ways depending on changing need. For example, we moved a file cart to the right of the setup to show the wire hookups for relocating the backend if needed.

The receiver is located on the right, and is an inexpensive Yamaha that incorporated all the features we wanted at the time. On top of the frontend you can see what looks like an old style radio. It is that and a record player. It adds to the character of the room, in our opinion.

Then we finally get to the frontend itself. The case seen is long since discontinued. The closest current model is the Antec Fusion NSK2480, which is a newer version of what we actually have. Like all of the others, this system also has an Asus motherboard.  There is another CrystalFontz 635 LCD panel in this system, this one in Green. We prefer the blue, which is why we got it for the second panel.

The processor is an AMD Athlon(tm) 64 X2 Dual Core Processor 4200+, which was retired from the backend during a previous upgrade.  Both frontends have 2GB of RAM. RAM is fairly cheap nowadays anyway. The remote is an RF Snapstream Firefly.

The screen here is a 23″ Westinghouse LCD with DVI and Component inputs and a maximum resolution of 1600×1200, mounted on a swing arm. This is one of the pieces we are hoping to expand soon into a larger, higher resolution with HDMI inputs, which will certainly, if nothing else, allow a thinner cable down to the computer.

You can see under the monitor the Left, Right, and Center channel speakers, the right speaker nestled in between Tux the Linux Mascot and the Time Machine, which we recently bought on a whim. The configuration of the room, a long rectangle, is not 100% conducive to a home theater design. To the left of the image is a window, and thus the positioning of the monitor and speakers is the only way to make sure viewing isn’t on top of the monitor, and that optimal viewing and sound is accomplished from either the couch, placed on a long wall, or a chair placed in the center of the speakers.

The rear speakers are not pictured, but are placed in the traditional isosceles trapezoid configuration, oriented according to the limitations of the space, again planned to surround primarily a person seated in a chair in the middle of the room. Under the shelf that holds all the speakers pictured is a through-the-wall air conditioner, which is why the units that hold the equipment are not placed against it. As mentioned, some of the decisions were made due to the configuration of the room. If anyone thinks they might have a better idea, please suggest it, as we’ve yet to figure out a superior layout.

So, that is it for now. We certainly have expansion hopes for the future, including to migrate to a monitor with an HDMI input, and possibly the receiver as well. Someday we’d like to try an Atom-based frontend, for the size of it.

Hopefully, you’ve gotten some ideas for systems of your own. What we’ve learned over the years is to build simply, but build room for expansion and redundancy. Any questions?

  • Share/Bookmark

MythTV Rig: Part 2 – A Frontend

Sunday, February 21st, 2010

As the second part of our multipart series, Better Know a MythTV configuration, we profile one of our frontends.

This is the newer of the two frontends we currently have in use. The case is a Silverstone Sugo SG-02, which looks rather nice in black. Inside, you can see a generic DVD drive and a CrystalFontz 20×4 LCD display that hooks into the internal USB headers on the Asus mainboard.

The processor is an Athlon X2 Dual Core BE-2400, the lowest power dual core available at the time of purchase, and rather inexpensive even then. The newest component is a NVidia GeForce 8400 series graphics card, which replaced an older video card. The card supports overloading of video decoding/playback under Linux, allowing a computer with little processing power to playback high definition video.

The hard drive is only used for the operating system, and happens to be one of the retired drives from the file server. A USB drive would work just as well, but would slow boot time. We could also have tried booting and loading data off of the network, but using an old drive to store the OS seemed simplest.

The monitor is an Acer 22″ computer, not television monitor, with a maximum resolution of 1600×1200.

One of the features that is unique to this frontend is the addition of the pullout X-Arcade Solo Controller, which slides in below the monitor when not in use. This system can also double as an arcade emulator, for the playing of classic arcade games. The monitor is even set to rotate to accommodate the portrait style screen of such a system, however when we put the system into its current cabinet, we didn’t account for the fact the monitor does not currently have enough clearance to rotate without being removed, a problem we have not bothered yet to solve.

We’re not big gamers, but we enjoy the nostalgia of playing the ones we played when we were young. includes a plugin/launcher for this.

The speakers are Creative Gigaworks T20 speakers, and do not offer a subwoofer. Our other system has full surround audio, but this one was designed to be much quieter, so we opted for a simpler speaker setup.

Finally, the remote is a simple Windows MCE infrared remote(not pictured). The system, when not in use, is turned off. It is plugged into a power strip(not pictured) with a master outlet, which shuts the power to the speakers and monitor when the computer turns off.

There have been other features/tweaks we have contemplated. for one, triggering the start of the computer with the remote, which we’ve run of but have been unable to get working. Like anything else, systems continue to improve.

The last major addition added Hulu Desktop for Linux into the Frontend, so it can be launched, control handed over to Hulu, then back to .

Next time, Part 3, the final backend.

  • Share/Bookmark

MythTV Rig: Part 1 – The Backend

Tuesday, February 16th, 2010

As part of the first of our multipart series, Better Know a MythTV configuration, we profile our Backend.

Our backend has gone through a lot of changes over the years. The first iteration was in a yellow server case on wheels. We went through a period of overbuilding, and the yellow version of the case was $17, the other colors were all closer to $100. We probably have a picture of that iteration somewhere, and will post it if it is ever found.

The current iteration, pictured left, is an Antec Three Hundred Mid Tower Case. This model is rather unique in that the power supply is at the bottom of the case, as opposed to the top. It was the first tower we ever had with that configuration. As you can see in the picture, there is space for 2 120mm fans in the front, right in front of the hard drive bays, and there is a washable filter in front of them. The top has a 140mm fan. and the back another 120mm fan. We used the quietest fans we could, but it can be heard as a low hum in the room. There is room for a side exhaust fan, which was have not installed.

There have been several generations of interior boards since the beginning. The current is an Asus board. The thing runs 24 hours a day, so we opted for one which, according to reviews, had high quality capacitors and good build quality. The computer runs headless, so we opted for a board with an onboard graphics card. There was no need for a discrete one when it was never used.

The processor is an AMD Athlon 64 X2 5600+. At the time of purchase, it was the highest speed AMD processor we could get that used 65W of power. Everything else used 95W or above. For our next generation, we are considering going to a higher speed, but low power Intel processor, but we’ll see where the market is when we decide for replacement.

A powerful processor is not inherently necessary for a backend. If you have a video encoding device that does its own encoding with significant use of the CPU, you could run the thing off of a low-power processor. But if you want to transcode some of your files into a smaller format for long-term storage, it helps to have something that can handle the extra load.

The system has 8GB of RAM, which is overkill, but the RAM was relatively cheap, and easier to install than the processor. Then we get to the hard drives. There are two 500GB drives in a mirroring RAID. So, in the event of failure, the system can go on. Only a small amount of the space is needed for the operating system and the database. The rest stores important data, our music collection, and any long-term video files.

To store active uncompressed recordings, we are currently taking advantage of ’s storage group function. It distributes the recordings between two Green drives. These drives spin at 5400RPM and are supposed to be more power efficient. One is a WD 1TB and the other a Samsung 1.5TB. Because of the design of ’s storage groups, files can be moved between any of the directories named in the storage group without pausing the server.

This means if one of the drives shows pre-failure, which we recently had, we can move the files to the other drive and take one of them out of commission. We also ensured that the system has an ESATA connector, which would allow us to plug in an external drive and add it to the storage group to keep the system running if we need the extra space.

The computer has two optical drives, and this was originally planned to allow for having one drive used to burn a rewriteable DVD on a time schedule, which would be rotated manually out of the system and placed in backup. That never happened, and at some point in the future, one of them will be replaced by a blu-ray burner, to allow for larger optical backups.

Support for firewire channel changing is what convinced us to dive in fully into . Originally, the output of the cable box fed into a PVR-150 capture card. Then, firewire recording became more reliable, so the PVR-150 was mostly retired. Finally, when the cable company changed its software and both capture and channel changing became unreliable, we switched to the tried and true infrared channel changing and high-definition capture using the Hauppauge HD-PVR box.

As having only one cable box and HD-PVR would mean we couldn’t resolve any conflicts, we have a Silicondust HDHomerun hooked directly into the cable lines, tuning any unencrypted channels, which are mostly local and public access stations. And, in the event cable goes down entirely, we hooked a line to the old roof antenna, disused for over a decade, and hooked it into an inexpensive card that could tune Over-the-Air digital. Digital Broadcast is often higher quality than the same channel over the cable lines, due to compression, so if you are an HD purest, you probably want to try to supplement your cable with digital broadcast.

The backend, as referenced before, also downloads video programming via MiroBridge and integrates it into the recording menus. This may change as time passes. Speaking of software, our system runs a non-graphical installation of the latest edition of Fedora, currently 12. We periodically update the system after a new release of Fedora has been released long enough for us to feel comfortable upgrading.

We upgrade by making a backup, then moving all the data from the RAID to the recording drives, wiping the RAID drives, installing the new OS, and moving the data back. The whole process takes a few hours, and most of it is waiting for the installation or copy to complete. Most configuration is already setup and just needs to be restored.

Here’s a wider shot of the system. Last year, we redecorated the room in early Ikea. The backend, codenamed Freshpond, sits on a rolling file cabinet called a Mikael. There is a sound baffling like material under it to prevent scratching, which is a cut piece of Ikea drawer liner. One of these days we may switch to a desk blotter or such for aesthetic reasons. There are both pros and cons to having the system off the ground. Next to it, you can see a printer and one of the two frontends currently operating. Behind that glass door is the HD-PVR and the cable box.

More on the first frontend, seen in the picture, in Part 2.

Like many, we constantly think about refinements to the system to improve it. Sometimes this is new hardware, sometimes consolidating redundant systems, and sometimes software improvements. For example, in addition to the once hourly check for new internet video from the RSS feeds we monitor to import, a separate job also searches for audio podcasts we have told it to monitor and downloads them.

Ultimately, like any hobby, maintaining the system takes on a passion. But for those of you looking to build a system, it really doesn’t take that much day to day effort and the basic setup is simple. More advance concepts…well, you can always ask someone who has done it. Like us, for example. Comments welcome.

  • Share/Bookmark

MythTV Rigs

Wednesday, January 27th, 2010

Recently, Geektonic featured a showcase of a setup. It has inspired us to break out the camera and take some pictures of our own equipment. You’ve already seen some screenshots from our setup, but coming soon, we’ll be offering some shots and specs on our current equipment setup, as soon as we clean it up.

In the meantime, check out Rothgar’s MythTV setup, courtesy of Geektonic.

  • Share/Bookmark

Internet Video May Be Coming to MythTV

Wednesday, December 16th, 2009

Earlier today, on the MythTV Users list, contributor Robert McNamara announced that he and Doug Vaughan(who wrote JAMU and the TVDB grabber) are working on a new plugin for MythT called MythNetVision.

has had Internet video plugins before. MythStream was one of the earliest. We never could quite get it to work consistently, and it hasn’t been rewritten for MythUI, and those won’t work under 0.22. None of these have ever been included as part of the official package, which this has the potential to be.

From their description, it would have the following features:

  • Easy to Extend with Scripts so New Sites can be added. Adding a site would be as simple as parsing an API or site and formatting each item as an RSS article in the output of the script. Parsing happens in the background as long as the frontend is open to keep information current.
  • Support both media which is web-only (by spawning a browser directly to the playback link) and downloadable (by threading off a download and playing in the internal player as soon as enough data is buffered). Also supports external players.
  • Like other plugins, completely themeable.
  • Compliant with the Terms of Service of the websites it uses and shipped with a number of popular sites already supported. Scripts would only be distributed that were totally compliant, but other scripts could be added separately, outside of the distribution.
  • Two parts: An internet video search and an internet video browser.  Plans to include a “tree view” for a site by dumping the video
    RSS feeds for the site into a grabber config file (adding Revision3 as a fully browseable site would be as simple as dropping the RSS feeds
    in the grabber config).
  • All existing grabbers return full screen, autoplay results when they are available and the API allows. When not possible, the best possible result is played.
  • Downloadable media will be integrated into recordings.
Watch Recordings Menu under Graphite theme

Watch Recordings Menu under Graphite theme

There is a screencast video that can be viewed here. They hope to release by 0.23, but possibly sooner.

McNamara used the following sites as Examples of sites that should be very easily (and legally) implemented: Comedy Central, The Escapist Magazine, Revision3, Recent Apple Movie Trailers, BBC iPlayer. They’ve already included Youtube, Vimeo, Blip.tv, MTV Video, and TMDB Trailers.

All of them are very interesting. The Escapist just recently unveiled its app in Boxee at the Boxee Beta unveil, for example.

Speaking of Boxee…it has shifted its focus from media stored on a local drive to online content. has to do the same. It is a DVR software, and should remain so. But with more and more online content becoming available, it needs to address it, and offer ways for that content to become a part of the interface.

MythNetVideo’s design seems to accommodate for that. It launches external programs, or imports video, whichever it can. doens’t need to be all-encompassing, it can hand off control to other programs. But having that option allows it to be easily extensible, and that is what it needs.

  • Share/Bookmark

So You’re Thinking of Trying MythTV

Monday, November 9th, 2009
inside my new ubuntu linux PC
Image by spadger via Flickr

We’ve been writing a lot about the new features of the latest release of MythTV, which has now been fully released. Assuming we, or the myriad of other enthusiasts have convinced you to try as the core of your HTPC(Home Theater PC) system, what should you think about?

Go HD – Don’t Even Bother with SD

In this modern world, even though SD is cheaper, why limit yourself? High Definition TV is the wave of the future, so you should plan for it, even if you aren’t yet ready for it.

You don’t even need a powerful computer anymore to do playback. Just a good graphics card. Under Linux, the best supported cards are the Nvidia line of graphics cards. The 8000 and 9000 series support VDPAU, the latest in offloading video playback from the CPU to the GPU. With one of these graphics processors, you can even use an inexpensive low-power processor like the Atom(common in Netbooks) to run your system.

Now, that is playback. As for recordings, hard drives are fairly straightforward. Get enough space. GBs are cheap now. Beyond that, you need a recording device.

Even with Over-The-Air broadcasts, you can get HD programming using a tuner card. After that, if you have cable or satellite, you can get some channels unencrypted on the cable line, usually local stations as well. Beyond that, you can take the output from the cable or satelite box and pipe it into computer for recording. If you are lucky, you can get channels over a firewire cable from the box(cable only), if not, you can use the HD-PVR 1212 to capture from the analog outputs.

After that, all you need is a remote to control it, and a TV or computer monitor to output it to, and you have the basics of a setup. Easy, huh?

More to come…

  • Share/Bookmark

MiroBridge – A Link Between Miro and MythTV

Friday, November 6th, 2009
Image representing Miro as depicted in CrunchBase
Image via CrunchBase

The MythTV wiki defines MiroBridge as a script which “enables Miro to emulate a recording device.” However, we feel this is rather inaccurate.

MiroBridge doesn’t appear as a recording device. It does create a channel, defaultly assigned to 999, to assign the Miro recordings to, but it is more an importer of Miro downloaded programs. You configure Miro with your desired online programs, and then set up a cron job to have MiroBridge run.

Miro is an Internet television application that downloads videos from RSS-based channels, manages them, and plays them. It does incorporate a Bittorrent client, but torrent features are disabled in MiroBridge for legal reasons.

MiroBridge in Action

MiroBridge in Action

MiroBridge will let Miro download new episodes, then it will symlink the downloaded episodes into the recordings directory and import the details of the program as a Recording. It can also move the episodes to MythVideo.

This is an amazing addition to . Scripts to do this have existed before. We used MythNetTV, which takes RSS feeds for Podcasts and imports them into . It has never been an official part of though. MiroBridge is now becoming official, and relies on Miro, which is a popular piece of software in its own right, and well maintained.

If you think about it, with cable becoming more expensive, a box with a broadcast based system, adding in internet produced programming. If you don’t have cable, at the very least, in the news department, the websites of various cable networks offer limited versions of their programming as RSS feeds you can incorporate in.

Youtube can be distributed as an MP4-based RSS feed as well, using some secondary sites, and thus incorporated in as well. Essentially, there is nothing you can’t do if you can find RSS-distributed video.

  • Share/Bookmark