HTPC Testbed Components

In choosing the Streacom FC10 and Nano150 as the chassis and PSU for our testbed, we were practically restricted to a mITX or uATX motherboard. There was a toss up between building a Trinity-based testbed and a Ivy Bridge-based testbed. In the end, the fact that Trinity emerged as being a capable madVR candidate (with software based decoding), and the fact that madVR recently introduced DXVA scaling (an upside for Intel since its offerings weren't fully madVR capable earlier, and something that we wanted to test out) persuaded us to go for an Intel-based testbed.

Processor:

Intel's best GPU offering to date is the HD 4000, and the cheapest Ivy Bridge with the HD 4000 GPU is the Core i3-3225. The Core i3-3225 is a 2C/4T processor with a 55W TDP. It has a 3 MB L3 cache, and can run at 3.3 GHz. The HD4000 runs at 650 MHz by default, but, can turbo up to 1050 MHz when necessary. Like all other Ivy Bridge processors, we have support for DDR3-1600 memory.

Motherboard & Chipset:

The Asus P8Z77-I Deluxe is a Z77-based mITX motherboard with integrated dual-band Wi-Fi / Bluetooth and plenty of HTPC oriented features with Wi-Fi GO!, including the ability to interact with the PC using a mobile device, making it act as a DLNA media hub and so on. This video from Asus captures the capabilities included in the Wi-Fi GO! feature. Ian will be presenting a detailed review of the P8Z77-I Deluxe. However, in the context of our HTPC testbed, the motherboard fulfills all our primary requirement that at least one free PCIe slot be available for installation of a discrete GPU at a later point in time.

Asus also has a Wi-Di enabled model with an Intel Wi-Fi adapter instead of the Broadcom-based one in the P8Z77-I Deluxe.

Memory:

We had used the G.Skill Ares kit in our Trinity HTPC testbed, and given the fact that it can run even at 2133 MHz, we decided to use the same model for this system build also. As a refresher, the DRAM runs with a 9-11-10-28 latency configuration. We also decided to use only one module to give the system 4 GB of DRAM. The reason to not go in for 8 GB will be made clear in the next section.

Primary & Optical Disk Drives:

We used one of the old SSDs lying around, the Corsair F120 120GB. Our intent was to use the SSD only for the OS and program files, and leave all the media on a NAS in another location. Installing a hard drive for increased capacity was ruled out because we wanted a silent HTPC.

One of the constraints posed by the FC10 chassis was the fact that we could only use a slot-loading optical drive. Despite the fact that we wanted a silent system, we did make one concession and decided to install a ODD in the system. Some of our ASRock HTPC samples are now being used as headless systems for network testing, and we decided to take out a Blu-ray drive (Philips Lite-On DL-4ETS) from one of those and use it in our HTPC testbed.

 

Passive Build Chassis & PSU Build Process
Comments Locked

63 Comments

View All Comments

  • colonelciller - Sunday, December 23, 2012 - link

    Does the i3-3225 support 23.976 playback?
  • Aikouka - Sunday, December 23, 2012 - link

    Last I recall, Intel's drivers do have a "24 FPS" setting, but it is not true 23.976. However, my information may be out of date!
  • casteve - Saturday, December 22, 2012 - link

    Thanks for the review, but what are the units of time in the graphs? seconds, minutes, mayan long count?
  • ganeshts - Saturday, December 22, 2012 - link

    Apologize for the oversight. The time unit is in (s). The first graph is not very clear (I had actually let our power logger script run for 100 minutes = 6000s). For the loading temperature graphs, I had indicated in the text that the burn-in testing was run for 12 hours (=43200s).
  • kyuu - Saturday, December 22, 2012 - link

    First paragraph on page 3:

    "There was a toss up between building a Trinity-based testbed and a Ivy Bridge-based testbed. In the end, the fact that Trinity emerged as being a capable madVR candidate (with software based decoding), and the fact that madVR recently introduced DXVA scaling (an upside for Intel since its offerings weren't fully madVR capable earlier, and something that we wanted to test out) persuaded us to go for an Intel-based testbed."

    Am I missing something or is this messed up? You describe (what I assume are) positive aspects of Trinity, then use that as the justification for using Ivy Bridge? Huh?
  • ElvenLemming - Saturday, December 22, 2012 - link

    The way I interpreted that was that because the madVR support is newer and less-tested for Intel, they decided to go with an Intel build here so they could use the same machine for future madVR testing.

    The paragraph wasn't worded very clearly, but that's what I got out of it.
  • ganeshts - Saturday, December 22, 2012 - link

    Yes, I could have conveyed that in a better manner, but ElvenLemming's interpretation is right. In our Trinity and Ivy Bridge reviews, we found that 720p60 H.264 streams gave trouble to HD 4000. Recently, madVR introducied DXVA scaling, and I have it from very reliable sources that Mathias (madVR developer) is working closely with Intel. So, we wanted to have the right platform to evaluate these developments.
  • kyuu - Sunday, December 23, 2012 - link

    Ah got it. Thanks for the clarification.
  • Schafdog - Saturday, December 22, 2012 - link

    What's the idle power of the system?
  • ganeshts - Saturday, December 22, 2012 - link

    That is coming in Part 2 of the review :) As a sneak peek, I can say it is around 28 W. Power measurement during Blu-ray playback and other workloads will be dealt with in detail in the next series installment.

Log in

Don't have an account? Sign up now