[mythtv] [mythtv-commits] Ticket #2708: patch: Allow remote FE/BE to prefer to use the myth protocol

[Chris Pinkham]

* On Tue Nov 21, 2006 at 10:34:19AM -0500, Mark Buechler wrote:
> Um, wouldn't blanking the db setting "RecordFilePrefix" for the frontends
> you want to use the myth protocol for work just as well?

No, ProgramInfo::GetPlaybackURL checks the RecordFilePrefix of the host that
actually recorded the file and looks to see if the file exists locally in
that directory.  If not, then it checks in the local host's RecordFilePrefix.

Also, the RecordFilePrefix setting is going to go away when I commit Storage
Groups to SVN, so that is not a valid long-term solution if it did work.

> 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.

I have seen the occasional time when unmounting the nfs directory and using
the myth:// protocol was smoother, but they were my fault, not NFS problems.
My experiences occurred when my HD slave backend was also serving up its
recording directory via NFS to the main frontend.  When 2 things were recording
on my P3-500 as well as me trying to watch a recording, i would get occasional
buffer underruns.  The CPU on the backend was pegged at that time although
I'm not sure why as the capture cards in it are a pair of air2pc cards which
should have been using very little cpu at the time.  I just updated my production
systems to SVN head with my Storage Groups patch applied and am keeping an eye on
things to see if the slave backend really is using that much CPU all the time.
It seems to have been a semi-recent occurrance, it never used to do that.

--
Chris