[mythtv-users] Disabling the internal player

[Tom Dexter]

On Tue, Feb 23, 2010 at 9:07 PM, Raymond Wagner <raymond at wagnerrp.com> 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 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.

Removal of external player support still seems like a significant loss
of functionality to me.  I could see it if supporting it is a big
burden on development, but most all of what you mention are burdens on
the person who wants to _use_ the external players.  I could see
making people go a little out of their way to enable external players
and to use the internal player by default.

Would this change mean that everything would use storage groups and
need to be in the database?  I don't tend to leave many videos on my
backend permanently and tend to use file browse mode with an empty
videometadata table.

Tom