[mythtv-users] Updated MythTV RPMs

[Paul Jara]

I dunno.. It seems like network transfer of data is adding another level
of complexity that could be avoided, but if sound dampening is
necessary, then it's a necessary evil :).

My understanding was that an uncompressed mpeg2 stream ran at
18mbits/sec, which translates to:

send->18mbit
recv<-18mbit
buffer->18mbit (for delayed playback)

Means that you're using about half of a 100baseTX connection (depends on
the card.. duplex notwithstanding).

I might be making all this up.. It's rather late at night..

Let me know how everything works out :)

Cheers,
Aaron 

On Wed, 2003-02-12 at 23:21, Henk Poley wrote:
> > Van: Aaron Stewart <acs at hourglassone.com>
> > 
> > Seems like a bad idea from a purely bandwidth standpoint.. 100mbits/sec
> > only stretches so far :).. you'll be hammering your switch pretty hard,
> > and congesting your network if any other machines on it use your storage
> > box .
> 
> Huh?
> 
> Even WiFi @ 5.5mbit/s nominal can [..barely..] handle the DivX stream that
> MythTV is generating. Booting the OS form network shouldn't be a big
> problem, IF you have a small distro. AFAIK, there are dozens of companies
> that use thin clients (again) nowadays.
> 
> Or at least kernel + X + WM + Myth* + QT(?) frontend, should run natively
> on your frontend machine, I guess. People are already running MythTV 0.7
> (before the split) on machines with 128MB, those machines have diskcaches
> too. I don't think you'll run into (low) memory problems. But as always,
> the proof of the pudding is in the eating.
> 
> 	Henk Poley <><
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at snowman.net
> http://www.snowman.net/mailman/listinfo/mythtv-users