The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Straw Poll - MythTV machine spec.



I'm running a combined frontend/backend in a box, it's an Athlon XP 2.4G=20
with 512MB RAM and a 200GB hard drive.
It uses 2 x Avermedia 771 DVB-T cards for Freeview reception, with a MS=20
MCE remote...

The performance is fine as the DVB cards dump the MPEG2 (ish)  stream=20
straight onto the hard drive, the processor is barely doing anything...
The test box that I played with for a few months (before decided to=20
build the full version) was an Athlon XP 1800 with 256MB RAM, but only=20
one DVB card as it was a mini Shuttle XPC box with only one PCI slot, it=20
too was fine, no pauses etc. I'm seriously considering swapping the=20
processor in the Myth box with the one in the Shuttle box as it'll run=20
cooler and the 2.4 just seems like overkill...

The only performance eyesore is changing channels while watching live TV=20
(old style channel surfing) which takes 4-5secs on either box, though=20
from reading the forums, it seems this is normal - partly the digital=20
channel changing and then the buffering. That said the Tivo isn't far=20
behind this in terms of slow channel changing. In reality though I=20
rarely  watch live TV and even then don't surf like that, normally just=20
pulling up the EPG and then picking a channel...

Must also add that the KnoppMyth distro from mysettopbox.tv is fantastic=20
and does 99% of the setup for you...


> Just a quick thread to gather what spec PC's people are using with
> MythTV & what you perceive the performance to be ...
>
> --=20
> -S
> http://www.makepovertyhistory.org/
>







UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.