SageTV

» see sagetv.com as it lived, on the wayback machine

~ the last words ~

in 2008 i was a computer-engineering student running a desktop tower with too many drives in it. sagetv was the kind of software i read about on the home-theater-pc threads at avsforum and never actually installed. anyway, the demo videos always showed a us cable tuner card pulling in espn and tnt, with the user flicking through a tv-guide grid that did not really map to anything you could buy in ankara. the product was paid, the price was around eighty dollars at the time. the people running it were the ones who built media-center boxes in shuttle xpc cases out of dedication.

this part most of us in turkey watched from outside. honestly, even if you had built the box and bought the license, the guide data was us-centric. anyway, the tuner-card market in turkey was thin, satellite was the dominant tv path, and digiturk was still in dvb-s receiver territory rather than pc-tuner territory. for whatever reason, the few people i knew running an htpc were doing it through windows media center on vista or through xbmc, which was already free and getting good fast (close enough).

i was not paying attention to the company itself, but anyway. jeffrey kardatzke had founded frey technologies in goleta california, and shipped the first sagetv release in 2002. the cadence was steady, a major version about every year or two, with the hd200 set-top extender appearing in 2008. by then, the hd300 followed in 2010, both of those were thin clients that pulled video off the home pc and decoded it locally so you could put the noisy box in a closet (or roughly).

on june 18 2011 kardatzke posted on the sagetv forum that the company had been acquired by google. for whatever reason, the next sentence in the post was that no more licenses would be sold and existing customers would keep what they had. the team moved over to the google fiber tv project in kansas city. the public product line was end-of-lifed the same day with no replacement.

~ the record ~

~ what it actually was ~

sagetv was a server plus client pair, for whatever reason. the server ran on your always-on pc and owned the tuner cards, the guide download, and the recording schedule. anyway, the client was a 10-foot interface meant for a couch, with a remote and a grid that walked through every channel you had subscribed to (close enough). the windows build was the most-used, the linux build had a small loyal base since you could run it headless on a low-power box and still get the extenders working.

the hd200 and hd300 were the part that made the product feel premium. those were small set-top boxes that booted into the sagetv client and pulled video off the server. for some reason, the local decode meant you could run an old amd celeron in the closet and still play 1080i mpeg2 to the living-room tv with no transcoding step (roughly).

for whatever reason, the plug-in api around sagetv was the reason it had a forum culture. people wrote tools to grab cover art, schedule recordings by show rather than time slot, and build custom skins that looked nothing like the stock one. anyway, the community kept the plug-ins flowing for years after the company stopped selling new licenses.

~ the google deal ~

this part you had to be following the home-theater press for, mostly. for some reason, the press read the deal as a google-tv play. google had launched google tv on logitech and sony hardware in late 2010 and the early reviews were rough. anyway, the assumption was that sagetv would give google a dvr backend it did not have to build from scratch.

in fairness, the team ended up on google fiber tv in kansas city instead. by then, the first google fiber tv box used sagetv v8 as the dvr software behind the scenes. for whatever reason, none of that reached the public sagetv brand. the fiber team eventually replaced the sagetv-derived stack with an in-house build, and sagetv as a product name never reappeared inside google.

~ the long tail ~

the source code drop in july 2015 was the kind of post-acquisition coda you sometimes get when the acquirer has no reason to hold the ip any longer (or so it seemed). anyway, kardatzke had announced it in march 2015 and the github repo went live a few months later under apache 2.0. for whatever reason, the community picked it up and shipped a v9 line that ran on docker and added newer-codec support through 2016 and later.

the sagetv community in 2026 is a small handful of forum threads keeping the codebase compiling on current java and pulling guide data from the schedules-direct subscription service that survived the rest of the htpc ecosystem. honestly, the original goleta product is dead, the dna of it lives on in those community builds. the cultural footprint of sagetv was always narrow, the people who used it loved it more than almost any other piece of software they ran.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »