<div class="gmail_quote">On Thu, Aug 5, 2010 at 2:41 PM, Tyler T <span dir="ltr"><<a href="mailto:tylernt@gmail.com">tylernt@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im">> So basically, I would install, say my local TV/Cable tuner card as just one back end.<br>> I would do the same thing with say my DVB-S2 card and now would have two backends.<br><br></div>Probably more appropriate to put the two tuners in one backend. Or 5<br>
tuners in one backend.<br>
<div class="im"><br>> As I have not played with mythtv yet, I am getting the sense that the reason<br>> why my post is unclear is that when one builds a separate front and back<br>> end, the two need to talk together and A/V needs to stream between them.<br>
<br></div>Try not to think in terms of A/V. I would consider this more of a data<br>transfer; request and fulfillment.<br>
<div class="im"><br>> If this is right, then it means that mythtv already encodes to something which a UPnP device could pick up over the LAN.<br><br></div>When the UPnP device requests it, yes, Myth will send data to it. The<br>
UPnP is not picking anything up; it's receiving the data that it<br>requested -- data that is sent directly to it, and nowhere else. If<br>you have a second UPnP device request the same channel, a second<br>stream will be sent to the second device (creating twice the LAN<br>
traffic).<br>
<div>
<div></div></div></blockquote>
<div> </div></div>
<div class="gmail_quote">The best analogy I can think of for what myth is would be a news aggregator like google news.</div>
<div class="gmail_quote"> </div>
<div class="gmail_quote">If you ran your own news aggregation, you would have a server that collects content from multiple sources processes it into a common format and stores it locally. You might need multiple news aggregation servers to scour all the sources you want to include. Then you need a database server to index all of the items collected. Next you would set up a web server to host the news items you collect so that that any machine with a web browser can view it. You might want other servers too so that users can read your news items in other ways. Finally, your users would use their web browsers to read the news your aggregating.</div>
<div class="gmail_quote"> </div>
<div class="gmail_quote">Mythtv works the same way. You have servers that collect content from multiple sources and store that data locally called backends. You have a database server that indexes everything (among many other things) called the master backend. You have various methods by which you might obtain the content from the backends (the myth:// protocol, mythweb, upnp). And finally you have your playback device, typically a PC running mythfrontend or another application that speaks the myth:// protocol (such as XBMC)... but could be any UPNP capable player, or even just a web browser in the case of mythweb.</div>
<div class="gmail_quote"> </div>
<div class="gmail_quote">Either way, there is no "broadcast" onto you lan. All playback involves and individual request and dedicated stream. Just like opening an article at google news.</div>