No subject


Mon Oct 30 22:48:16 UTC 2006


A high-def channel will typically be around 16Mbps.

HDHR->PC = 16Mbps.
PC -> NAS = 16Mbps.

Therefore:
HDHR = 16Mbps.
PC = 32Mbps.
NAS = 16Mbps.

If recording from two tuners then double all the numbers.

64Mbps will be no problem for a 100baseTX network.

Nick

PS - If you are still concerned, you can add a second nic card for small $$
and keep the HDHomeRun traffic on a separated.

> If you have another TV in your home, you may want to use the Shuttle box
> as
> > a second frontend.
>
> Dang.  THAT is a good point.  We moved the displaced TV back to the
> sewing/craft/guest room.  Might be nice to have a mythbox there.
>
> > Or, you may want to move your mythconverg database to
> > this box.
>
> Does it make more sense to separate the db to its own box?  If so why?
> Would it make accomodating multiple backends easier?


I've been wrestling with this question.  I think that I am going to do this.

There are times when I bring up the recordings screen and it takes a long
time to fill the list.  Same for many of the screen with a lot of data.
Keeping the db optimized helps a lot.  But when the master backend is busy
recording and streaming to other front ends, then db access seems to
suffer.

The downside I see, it that it introduces another point of possible failure.
Right now, if the master backend dies or develops a network problem, then
the whole system is unusable.  Moving the DB to another box means that if
either has a problem, then the whole system is unusable...

> In any event, more boxes means more options - never a bad thing.

>
> True, up to a point.  However, one eventually does run into issues like
> the electric meter whirling like a dervish (keeping all those machines
> spooled up costs real money these days, plus a lot of heat getting
> thrown into the immediate environment - welcome in the winter but
> UNwelcome in the summer), and the daily reboot-and-journal-recovery for
> a half dozen boxes when (not if, this is north central Florida we're
> talking about!) the thunderstorms take out the power.
>
> Hmmm... I hadn't really considered the power consumption issue until
> just now, and it's a biggie - our electric bill's out of hand as it is.
> That would tend to mitigate in favor of a combined frontend/backend
> everything box in the stereo cabinet, moving the current frontend back
> to the sewing/guest room TV, and decommissioning that big loud hungry
> dual PIII machine.


All valid points.  I'd like to explore the possibility of putting my systems
to sleep when idle, but it seems that this is still a black art, - and while
the challenge intrigues me, I don't have the time.

Also, the system is finally mostly stable, and my wife is starting to get
comfortable with it, so I don't need to introduce anything that has the
potential of undermining her confidence.  For now, that is worth a few $$$
to me.

Jury's still out on the PCHDTV 5500 vs the HDHomeRun; I'd appreciate
> hearing more from folks using either of those two options.  I'm really
> leaning more toward the PCHDTV card at present; they were early and
> enthusiastic linux advocates, and I like to support companies that take
> the pro-open-source stance.


The thing I like best about the HDHomeRun is that it draws no resources on
my backend.  It justs sits by itself and does what it is told.

Setup is a breeze.  Just plug it in to the network.  Tell mythtv-setup that
you want to add two HDHomeRun tuners.  Myth auto-detects the HDHomeRun
tuners.  That's it!

I've never setup an PCHDTV 5500, but I believe it's a tad more complicated
than that.

Tom

------=_Part_16920_20229780.1184254277091
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 7/12/07, <b class="gmail_sendername">Bruce H McIntosh</b> &lt;<a href="mailto:scotsman at afn.org">scotsman at afn.org</a>&gt; wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Several people have suggested this gizmo to me.&nbsp;&nbsp;What sort of bandwidth<br>requirement emerges from the notion of streaming two hidef vid streams<br>at the same time?&nbsp;&nbsp;Would I be looking at needing to throw money at a<br>
GigE switch?&nbsp;&nbsp;Hmmm... that actually begs the question of recording two<br>HD streams in the same backend box - will I swamp the PCI bus or the<br>SATA controller?</blockquote><div><br>From Silicon Dust&#39;s tech support forum:
<br><br><span class="postbody">
A high-def channel will typically be around 16Mbps.
<br>

<br>
HDHR-&gt;PC = 16Mbps.
<br>
PC -&gt; NAS = 16Mbps.
<br>

<br>
Therefore:
<br>
HDHR = 16Mbps.
<br>
PC = 32Mbps.
<br>
NAS = 16Mbps.
<br>

<br>
If recording from two tuners then double all the numbers.
<br>

<br>
64Mbps will be no problem for a 100baseTX network.
<br>

<br>
Nick</span><br>&nbsp;</div>PS - If you are still concerned, you can add a second nic card for small $$ and keep the HDHomeRun traffic on a separated.<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
&gt; If you have another TV in your home, you may want to use the Shuttle box as<br>&gt; a second frontend.<br><br>Dang.&nbsp;&nbsp;THAT is a good point.&nbsp;&nbsp;We moved the displaced TV back to the<br>sewing/craft/guest room.&nbsp;&nbsp;Might be nice to have a mythbox there.
<br><br>&gt; Or, you may want to move your mythconverg database to<br>&gt; this box.<br><br>Does it make more sense to separate the db to its own box?&nbsp;&nbsp;If so why?<br>Would it make accomodating multiple backends easier?</blockquote>
<div><br>I&#39;ve been wrestling with this question.&nbsp; I think that I am going to do this.<br><br>There are times when I bring up the recordings screen and it takes a long time to fill the list.&nbsp; Same for many of the screen with a lot of data.&nbsp; Keeping the db optimized helps a lot.&nbsp; But when the master backend is busy recording and streaming to other front ends, then db access seems to suffer.&nbsp;&nbsp; 
<br><br>The downside I see, it that it introduces another point of possible failure. Right now, if the master backend dies or develops a network problem, then the whole system is unusable.&nbsp; Moving the DB to another box means that if either has a problem, then the whole system is unusable...
<br>&nbsp;</div>&gt; In any event, more boxes means more options - never a bad thing.<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>True, up to a point.&nbsp;&nbsp;However, one eventually does run into issues like
<br>the electric meter whirling like a dervish (keeping all those machines<br>spooled up costs real money these days, plus a lot of heat getting<br>thrown into the immediate environment - welcome in the winter but<br>UNwelcome in the summer), and the daily reboot-and-journal-recovery for
<br>a half dozen boxes when (not if, this is north central Florida we&#39;re<br>talking about!) the thunderstorms take out the power.<br><br>Hmmm... I hadn&#39;t really considered the power consumption issue until<br>just now, and it&#39;s a biggie - our electric bill&#39;s out of hand as it is.
<br>That would tend to mitigate in favor of a combined frontend/backend<br>everything box in the stereo cabinet, moving the current frontend back<br>to the sewing/guest room TV, and decommissioning that big loud hungry<br>
dual PIII machine.</blockquote><div><br>All valid points.&nbsp; I&#39;d like to explore the possibility of putting my systems to sleep when idle, but it seems that this is still a black art, - and while the challenge intrigues me, I don&#39;t have the time.&nbsp; 
<br><br>Also, the system is finally mostly stable, and my wife is starting to get comfortable with it, so I don&#39;t need to introduce anything that has the potential of undermining her confidence.&nbsp; For now, that is worth a few $$$ to me.
<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Jury&#39;s still out on the PCHDTV 5500 vs the HDHomeRun; I&#39;d appreciate<br>
hearing more from folks using either of those two options.&nbsp;&nbsp;I&#39;m really<br>leaning more toward the PCHDTV card at present; they were early and<br>enthusiastic linux advocates, and I like to support companies that take<br>
the pro-open-source stance.</blockquote><div><br>The thing I like best about the HDHomeRun is that it draws no resources on my backend.&nbsp; It justs sits by itself and does what it is told. <br><br>Setup is a breeze.&nbsp; Just plug it in to the network.&nbsp; Tell mythtv-setup that you want to add two HDHomeRun tuners.&nbsp; Myth auto-detects the HDHomeRun tuners.&nbsp; That&#39;s it!&nbsp; 
<br><br>I&#39;ve never setup an PCHDTV 5500, but I believe it&#39;s a tad more complicated than that.<br> </div><br>Tom</div>

------=_Part_16920_20229780.1184254277091--


More information about the mythtv-users mailing list