From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} Time for hardware upgrade(s)
Date: Wed, 06 Jul 2011 21:08:40 +0200 [thread overview]
Message-ID: <1551665.iJ0hyvx9t0@localhost> (raw)
In-Reply-To: <CAN0CFw29g0ggQ4Y+1jb4u2iHCa1vDR71Sz-VgiDwrQ7V0xZtfg@mail.gmail.com>
On Wednesday 06 July 2011 11:54:29 Grant wrote:
> >> Yes, since a htpc doesn't need a powerful cpu (or a powerful gpu)>
> > My learned-this-the-hard-way advice: while this is generally true, if> you
ever come across a 720 or 1080p video that doesn't use a> hardware-accelerated
codec, you would rather the HTPC not sound like> it's about to launch itself
into orbit doing software decoding.
> Completely true. I switched from nvidia-drivers to nouveau and now Irely on
ffmpeg threads to decode 1080p. It works great most of thetime. There are
some videos that won't decode via threads, theyreturn some sort of "cannot
parallelize" error.
> I went with this Phenom II X4 3.7Ghz hog:
> http://www.newegg.com/Product/Product.aspx?Item=N82E16819103934
> I wonder if I'll be able to decode 1080p in software on a single corenow
without losing A/V sync. I kinda doubt it. I've been on anAthlon X2 3.1Ghz.
> > And if you're going to keep it in a cabinet, you would probably also>
rather said cabinet not catch fire (I had to cut holes in the back and> mount
fans).
> I'm discovering that fans which are said to be very quiet actuallyare. I'm
going to increase my case fans from 0 to 2 along with thisaftermarket CPU
cooler:
> http://www.newegg.com/Product/Product.aspx?Item=N82E16835608016
> Thanks a lot for everyone's help.
> - Grant
oh.. a tower cooler.. and only 92mm... hm..
well with fans bigger = better. A 14cm monster can push the same amount of air
as a 12cm or 8cm fan with a lot less rpm. The less rpm the better.
I can't hear any of my 4 14cm fans ;)
--
#163933
next prev parent reply other threads:[~2011-07-06 19:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-02 15:41 [gentoo-user] {OT} Time for hardware upgrade(s) Grant
2011-07-02 18:06 ` [gentoo-user] " Grant
2011-07-02 19:36 ` Dale
2011-07-02 19:59 ` Grant
2011-07-03 0:26 ` Dale
2011-07-03 1:32 ` Grant
2011-07-03 2:50 ` Dale
2011-07-03 3:23 ` Grant
2011-07-03 1:34 ` meino.cramer
2011-07-03 2:36 ` Dale
2011-07-02 21:54 ` Peter Humphrey
2011-07-02 19:42 ` Nikos Chantziaras
2011-07-02 22:22 ` Grant
2011-07-03 1:26 ` meino.cramer
2011-07-03 1:47 ` JD
2011-07-03 4:06 ` meino.cramer
2011-07-03 6:17 ` [gentoo-user] " pk
2011-07-04 16:30 ` Grant
2011-07-04 17:01 ` Dale
2011-07-04 19:21 ` pk
2011-07-04 20:32 ` Grant
2011-07-05 4:39 ` pk
2011-07-05 13:57 ` Michael Orlitzky
2011-07-06 18:54 ` Grant
2011-07-06 19:08 ` Volker Armin Hemmann [this message]
2011-07-06 19:15 ` Grant
2011-07-07 11:13 ` Stroller
2011-07-09 23:10 ` Grant
2011-07-10 0:20 ` Dale
2011-07-10 21:15 ` Grant
2011-07-10 22:22 ` Peter Humphrey
2011-07-05 15:49 ` Bill Longman
2011-07-05 9:54 ` Peter Humphrey
2011-07-20 18:49 ` Joost Roeleveld
2011-07-20 21:43 ` Bill Longman
2011-07-04 22:56 ` [gentoo-user] " masterprometheus
-- strict thread matches above, loose matches on Subject: below --
2011-07-04 17:08 [gentoo-user] " Pandu Poluan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1551665.iJ0hyvx9t0@localhost \
--to=volkerarmin@googlemail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox