(2012-11-08, 16:52)NewJerseyNinja Wrote: Would mythtv play nice with TVheadend on the same machine?
I'd like to test both before abandoning Mythtv.
I find its pretty easy to go back and forth between the two. MythTV confines all of its settings to its own user, as does Tvheadend (hts). You really just need to remove whichever daemon you are not using from init.d/upstart when you switch. I can't provide detailed instructions but your distribution's documentation should be enlightening.
Having used both, here are my anecdotal observations. I'm using ATSC OTA in the United States, with a somewhat flakey signal for some stations.
Tvheadend
PROS
- lightweight, easy to set-up, easy to use
- instantaneous channel switching
- developers are inclusive and quick to respond to feedback, especially Adam
- all development is focused on XBMC clients
- headless set-up. installation can be done via ssh shell, further configuration is via a lightweight web server
- normally keeps better pace with XBMC development. opdenkamp supports and uses tvheadend and is peripheral to XBMC team. Adam Sutton has been very active in last six months.
CONS
- git head for both backend and add-on are not super stable
- problem solving is arduous, as issues could be in XBMC code, add-on code, or backend. none of which are stable
- latest stable release is ancient and missing key features
- no timeshifting in git head, haven't tried branch
- for me, tv stream would lock up when signal strength was low and this has not been addressed. this doesn't seem to affect non-OTA users.
Myth
PROS
- guide/epg support, especially for tv series is much better, and duplicate detection works. recorded programs are handled better (sorted by series/date)
- 0.25+ back-end is rock solid. rarely a suspect when things go awry
- timeshifting supported using git head. only pause/start, but is big feature for live events
- currently "just works" for me, where tvheadend doesn't. This is more of a personal anecdote and may be because myth is far more tolerant of intermittent signals
CONS
- frontend not always stable. right now I have to restart PVR services every few days.
- myth and its many services tend to be a resource hog, as does mysql.
processes are among among biggest drains on a NAS cpu
requires installation of many dependencies
- configuration of Myth requires X forwarding via SSH or plugging in a monitor.
- existing Myth install base is focused on mythfrontend. xbmc users seem to be lower priority
- can lag behind XBMC features. developers are not part of core XBMC team. This is less true now, as there are two active developers (janbar and fetzerch), but before that happened, cmyth add-on was very out-of-date.
When/if Adam gets tvheadend up to speed, it is definitely the path forward. Day-to-day, I tend to use Myth, as it is less likely to drive my wife crazy or cause me to miss football. I prefer tvheadend when it works.