[mythtv] [mythtv-commits] Ticket #2708: patch: Allow remote FE/BE to prefer to use the myth protocol
Mark Buechler
mark.buechler at gmail.com
Tue Nov 21 15:34:19 UTC 2006
Um, wouldn't blanking the db setting "RecordFilePrefix" for the frontends
you want to use the myth protocol for work just as well?
I am very interested in the myth:// protocol, however, I find it a bit
unstable wrt changing channels. It's a huge help, though, with HDTV
playback.
- Mark.
On 11/21/06, Chris Pinkham <cpinkham at bc2va.org> wrote:
>
> * On Tue Nov 21, 2006 at 01:11:17PM -0000, MythTV wrote:
> > #2708: patch: Allow remote FE/BE to prefer to use the myth protocol
>
> > Comment (by danielk):
> >
> > Chris, if you apply this please don't make it default to being enabled.
> >
> > Streaming is much slower for most people and we'll get more 'channel
> > changing is too slow' complaints, and 'browsing the recorded list is
> too
> > slow' complaints, if myth streaming is the default.
>
> You don't have to worry about that. I think I was the one who committed
> the original code to allow remote frontends to read via nfs rather than
> streaming, because from day 1 of using Myth (back in the 0.7 days), I have
> used a separate NFS server for my main backend storage. Later I added the
> GetPlaybackURL() method to standardize how "players" determined how to
> access the file.
>
> I'm not sure what parts of this patch I'll use or even be able to use, but
> I wanted to snag the ticket since some of it is irrelevant with the
> current
> Storage Groups code I'm testing on my production systems right now.
>
> --
> Chris
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-dev/attachments/20061121/531932b3/attachment.htm
More information about the mythtv-dev
mailing list