[mythtv-users] Oddness in app and functionality

[brendan kearney]

After fighting for a while trying to figure out why mythbqckend can't talk
to 192.168.200.1-0.0 - 0.3, I set it to use RTP and finally have the
backend talking to the ceton card consistently.  Woohoo.  Go me.  Now I
have some other issues / concerns.

Schedules direct - some piece does not honor the proxy environment
variables and I had to punch a hole in my firewall for it.  I think its the
provider retrieval because I see the grabber using the proxies for the show
schedule data.

Mythbackend does honor the proxy env vars, but does not take the
no_proxy/NO_PROXY directives into account.  When set to use a proxy, and go
direct for the ceton IP via the no_proxy directive, mythbackend still
attempts to use the proxy for the cwton IP and communications fail.

Mythweather Perl scripts seem to have wrong permissions/ownership and
cannot be executed.  What owner/group should be set, and what permissions
should be set?

Mythweb seems to be stateless and uses the backend to manage/maintain the
session state via MySQL.  Is this correct?  I have two webservers load
balanced and I would like to have them run mythweb instead of the backend.
Can I load balance across two mythweb instances without breaking connection
states/statefulness?  How does the experimental flash player (or any other
functionality) figure into this?

When using the frontend to watch live tv, the video will tune, and the
audio will take a second to queue up.  Once locked, playback will work for
a few seconds and then the audio will cut out, go to full volume and blare
snow/static out the speakers.  This is maddening and a shocking jolt.  I
notice that pulse is reporting a buffer under flow.  Where do I begin
looking for a way to correct this?

Many thanks for mythtv and thanks in advance for any help here.

Brendan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20130215/195f6fa4/attachment.html>