Getting started w/ MythTV

[Thomas Charron]

http://wiki.cs.uiuc.edu/cs427/MythTV+Architecture+Overview which is part of
a larger document at http://wiki.cs.uiuc.edu/cs427/MythTV+Architecture

Some applications will go directly to the MySQL database running on the
master backend, but mostly, communications takes place via a TCP socket.

  Thomas

On 11/9/06, Paul Lussier <p.lussier at comcast.net> wrote:
>
> "Ben Scott" <dragonhawk at gmail.com> writes:
>
> > On 11/8/06, Thomas Charron <twaffle at gmail.com> wrote:
> >> The cost diference between, say,
> >> the PVR-150, 250, 300, 500, etc, is the inclusion of hardware based
> >> encoders.
> >
> >   That's what I expected, but it's confusing as hell.  Their marketing
> > department needs to work on product differentiation on their website.
> > I finally found this:
> >
> > http://www.hauppauge.com/pages/compare/compare_pvr.html
> >
> > which explains some things.  The PVR-150 is the same functionality as
> > the -250, just with new and cheaper parts.  The -350 adds a
> > decoder/TV-out.  The -500 adds a second tuner/encoder (but no
> > decoder).
>
> Read the MythTV docs.  It spells out these things pretty clearly.
>
> The one thing I didn't find in there that I would really have liked to
> was an architecture diagram displaying the relationships between
> Master/Slave backends and front ends with an explanation as to which
> tuners get used in which priority, where the database runs, and who
> accesses it when/why.
>
> This type of thing may be up on the MythTV site somewhere, I just
> haven't found it yet.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/mailman/private/gnhlug-discuss/attachments/20061109/74b38bf7/attachment.html