[mythtv-users] Disabling the internal player

[jedi]

On Tue, Feb 23, 2010 at 09:07:52PM -0500, Raymond Wagner wrote:
> On 2/23/2010 20:36, Tom Dexter wrote:
> >On Tue, Feb 23, 2010 at 4:42 PM, Nick Rout<nick.rout at gmail.com>  wrote:
> >>On Wed, Feb 24, 2010 at 10:41 AM, Raymond Wagner<raymond at wagnerrp.com>  wrote:
> >>>Just a heads up, the shift in MythVideo to using storage groups and allowing
> >>>remote access rather than relying on NFS, will likely result in the removal
> >>>of external player support.
> >>That would be a shame, but that's another thread.
> >I agree 100%...that would be an absolutely awful change in my opinion.
> 
> It's all based around a push to simplify MythTV and reduce the
> opportunity for things to break.  With the internal player and
> storage groups, mythbackend manages all access to content to any
> frontends that want it, and any bugs that arise will be internal
> problems that can be diagnosed and dealt with.  With external

    The external player setup seems to be the single most robust part of
mythtv at this point. You can easily sidestep a lot of bugs and problems
and it's a very straightforward sort of workaround.

> players, you have to set up the external player, you have to set up
> NFS on all machines, you have to figure out whether issues are in
> mythtv or some other 3rd party software, and you may have to explain
> to frustrated users they need to seek help elsewhere.  Everything
> just becomes considerably easier to maintain as external
> dependencies are reduced.

    That's silly. MythTV still has frontend clients connecting directly
to the database and dragging in all of the associated issues dealing with
mysql. If you want to get rid of gnarly external dependencies, start with
that. Also have frontends inherit settings from other frontends rather than
needing to be tweaked from scratch.

[deletia]