HTPC Credentials

Given the ECS LIVA Core's fanless nature and the presence of Intel HD Graphics, we expect many purchasers to use it as a media playback machine / HTPC. It is obvious that we are not looking at a madVR capable machine, but one targeted at the entry-level / average HTPC user or someone looking for a HTPC to put in a second or third room (non-primary HTPC). There are two HTPC aspects that we will explore in this section, one related to network streaming (OTT services), and the other related to local file playback. Prior to that, we have a small sub-section dealing with refresh rate accuracy.

Refresh Rate Accurancy

Starting with Haswell, Intel, AMD and NVIDIA have been on par with respect to display refresh rate accuracy. The most important refresh rate for videophiles is obviously 23.976 Hz (the 23 Hz setting). As expected, the ECS LIVA Core has no trouble with refreshing the display appropriately in this setting.

The gallery below presents some of the other refresh rates that we tested out. The first statistic in madVR's OSD indicates the display refresh rate.

Network Streaming Efficiency

Evaluation of OTT playback efficiency was done by playing back our standard YouTube test stream and five minutes from our standard Netflix test title. Using HTML5, the YouTube stream now plays back a 1080p H.264 encoded stream. Since YouTube now defaults to HTML5 for video playback, we have stopped evaluating Adobe Flash acceleration. Note that only NVIDIA exposes GPU and VPU loads separately. Both Intel and AMD bundle the decoder load along with the GPU load. The following graph show the power consumption at the wall for playback of the HTML5 stream in Mozilla Firefox (v 41.0).

YouTube Streaming - HTML5: Power Consumption

GPU load was around 47.56% for the YouTube HTML5 stream and 6.67% for the steady state 6 Mbps Netflix streaming case.

Netflix streaming evaluation was done using the Windows 8.1 Netflix app. Manual stream selection is available (Ctrl-Alt-Shift-S) and debug information / statistics can also be viewed (Ctrl-Alt-Shift-D). Statistics collected for the YouTube streaming experiment were also collected here.

Netflix Streaming - Windows 8.1 Metro App: Power Consumption

Decoding and Rendering Benchmarks

In order to evaluate local file playback, we concentrate on EVR-CP and Kodi. We already know that EVR works quite well even with the Intel IGP for our test streams. EVR-CP was used in conjunction with the LAV Filters bundled with MPC-HC v1.7.9. Settings were left at default (except for 4K decoding to be hardware accelerated).

In our earlier reviews, we focused on presenting the GPU loading and power consumption at the wall in a table (with problematic streams in bold). Starting with the Broadwell NUC review, we decided to represent the GPU load and power consumption in a graph with dual Y-axes. Nine different test streams of 90 seconds each were played back with a gap of 30 seconds between each of them. The characteristics of each stream are annotated at the bottom of the graph. Note that the GPU usage is graphed in red and needs to be considered against the left axis, while the at-wall power consumption is graphed in green and needs to be considered against the right axis.

Frame drops are evident whenever the GPU load consistently stays above the 85 - 90% mark. All our test streams managed to play back without issues in the two configurations that were tested out.

Moving on to the codec support, the Intel HD Graphics 5300 is a known quantity with respect to the scope of supported hardware accelerated codecs. DXVA Checker serves as a confirmation.

The only unfortunate aspect here is the complete absence of any sort of hardware acceleration for HEVC. Even GPU-aided hybrid decode acceleration for HEVC Main profile (8b) is not available. Other codecs work flawlessly, as evident from our decoding and rendering benchmarks. On the audio side, we had no trouble getting HD audio bitstreaming to work.

Networking and Storage Performance Power Consumption and Thermal Performance
Comments Locked

35 Comments

View All Comments

  • solarrocker - Wednesday, October 7, 2015 - link

    Uhm, 4 x 8 Gb (4 GB)?

    Is my Dyslexia affecting my math now as well...
  • Tobol - Wednesday, October 7, 2015 - link

    8 Gb == 1 GB so I guess 4 x 1 GB = 4GB is correct
  • solarrocker - Wednesday, October 7, 2015 - link

    True, didn't notice the lowercase b.

    Why are they even writing it like that, haven't seen such a notation for RAM in, well, ever. Or is this common practice now?
  • Stuka87 - Wednesday, October 7, 2015 - link

    Memory is technically always measured in bits (and thereby noted megabit, gigabit, terabit, etc). Its just simplified for the masses into gigabytes.
  • LoganPowell - Friday, November 27, 2015 - link

    Not my first choice for a desktop. The ECS Liva core does not even made it to consumer based rankings (see http://www.consumerrunner.com/top-10-best-desktops... for example...)
  • mctylr - Wednesday, October 7, 2015 - link

    Individual RAM ICs are measured in bits, whereas RAM modules are measured in both bits or bytes, depending on the audience.
  • solarrocker - Wednesday, October 7, 2015 - link

    Thanks, guess I never really looked at it that way.
  • wffurr - Wednesday, October 7, 2015 - link

    8 Gigabits (Gb) is 1 Gigabyte (GB). So 4 X 8 Gb is indeed 4 GB.
  • harpocrates - Wednesday, October 7, 2015 - link

    32 Gigabits is equal to 4 gigabyte. So in this case the ram uses four 8 gigabit chips to get to 32 gigabits in total. The Gb vs GB nomenclature is not very clear is it?
  • Vepsa - Wednesday, October 7, 2015 - link

    I wouldn't say that it isn't clear, its just that most people don't know they are different which is sad IMHO.

Log in

Don't have an account? Sign up now