HTPC Credentials - Local Media Playback and Video Processing

Evaluation of local media playback and video processing is done by playing back files encompassing a range of relevant codecs, containers, resolutions, and frame rates. A note of the efficiency is also made by tracking GPU usage and power consumption of the system at the wall. Users have their own preference for the playback software / decoder / renderer, and our aim is to have numbers representative of commonly encountered scenarios. Towards this, we played back the test streams using the following combinations:

  • MPC-HC x64 1.8.5 + LAV Video Decoder (DXVA2 Native) + Enhanced Video Renderer - Custom Presenter (EVR-CP)
  • MPC-HC x64 1.8.5 + LAV Video Decoder (D3D11) + madVR 0.92.17 (DXVA-Focused)
  • MPC-HC x64 1.8.5 + LAV Video Decoder (D3D11) + madVR 0.92.17 (Lanczos-Focused)
  • VLC 3.0.8
  • Kodi 18.5

The thirteen test streams (each of 90s duration) were played back from the local disk with an interval of 30 seconds in-between. Various metrics including GPU power consumption and at-wall power consumption were recorded during the course of this playback. Prior to looking at the metrics, a quick summary of the decoding capabilities of the Intel UHD Graphics is useful to have for context.

The Intel UHD Graphics GPU is no different from the GPUs in the Bean Canyon and Baby Canyon NUCs as far as video decoding capabilities are concerned. We have hardware acceleration for all common codecs including VP9 Profile 2.

All our playback tests were done with the desktop HDR setting turned on. It is possible for certain system configurations to have madVR automatically turn on/off the HDR capabilities prior to the playback of a HDR video, but, we didn't take advantage of that in our testing.

VLC and Kodi

VLC is the playback software of choice for the average PC user who doesn't need a ten-foot UI. Its install-and-play simplicity has made it extremely popular. Over the years, the software has gained the ability to take advantage of various hardware acceleration options. Kodi, on the other hand, has a ten-foot UI making it the perfect open-source software for dedicated HTPCs. Support for add-ons make it very extensible and capable of customization. We played back our test files using the default VLC and Kodi configurations, and recorded the following metrics.

Video Playback Efficiency - VLC and Kodi

VLC doesn't seem to take advantage of VP9 Profile 2 hardware acceleration, while Kodi is able to play back all streams without any hiccups.

MPC-HC

MPC-HC offers an easy way to test out different combinations of decoders and renderers. The first configuration we evaluated is the default post-install scenario, with only the in-built LAV Video Decoder forced to DXVA2 Native mode. Two additional passes were done with different madVR configurations. In the first one (DXVA-focused), we configured madVR to make use of the DXVA-accelerated video processing capabilities as much as possible. In the second (Lanczos-focused), the image scaling algorithms were set to 'Lanczos 3-tap, with anti-ringing checked'. Chroma upscaling was configured to be 'BiCubic 75 with anti-ringing checked' in both cases. The metrics collected during the playback of the test files using the above three configurations are presented below.

Video Playback Efficiency - MPC-HC with EVR-CP and madVR

LAV Filters with EVR-CP is able to play back all streams without dropped frames, but madVR is a different story. Almost all streams 1080p and higher see varying levels of significant spikes in power consumption pointing to the decode and display chain struggling to keep up with the required presentation frame rate. Given that the GPU is weaker than the one in Bean Canyon, this is not a surprise. Overall, the Frost Canyon NUC is acceptable for a vanilla decode and playback device without extensive video post-processing.

HTPC Credentials - YouTube and Netflix Streaming Power Consumption and Thermal Performance
Comments Locked

85 Comments

View All Comments

  • PeachNCream - Monday, March 2, 2020 - link

    Ganesh explained why the NUC was opened up in the article. Besides that, NUC systems are built to be user-accessible and are pretty simple to pull apart. It's like 4 screws to get the case open and pulling one ribbon cable off the motherboard to disconnect the mechanical drive. The barebones models are the same hardware and you have to crack the case to add storage or RAM or you do not have a complete computer.
  • nico_mach - Tuesday, March 3, 2020 - link

    I don't actually disagree with his reasoning, but I definitely have mixed feelings as a review.

    I forgot about the Atom NUCs completely. There's a name I haven't heard in a long time.
  • watzupken - Monday, March 2, 2020 - link

    With the new AMD APU arriving this year, I wonder if this is dead in the water considering the higher cost of the NUC. 14nm+++ is not going to save Intel when facing off 7nm from AMD as shown in the current processor stack from both teams.
  • timecop1818 - Monday, March 2, 2020 - link

    "7nm".

    Intel's "14nm+++++" (keep adding pluses, retards) is closer to 10nm than AMD's crap.
  • Fulljack - Monday, March 2, 2020 - link

    while fabrication nomenclature are now nowhere near it's actual marketed size, Intel's 14nm are still nowhere close with their own 10nm, and couldn't compete with TSMC's 7nm
  • Qasar - Monday, March 2, 2020 - link

    keep posting useless, anti amd, crap. keep showing the rest of us, and demonstrate to the world that you are a nitwit, then we will let you hang yourself, king oft trolls
  • Lord of the Bored - Thursday, March 5, 2020 - link

    Isn't this copy/paste'd from one of your other shill threads? Come on, man. Intel isn't paying you to repost the same old bullshit, your fans demand new content!
  • Korguz - Thursday, March 5, 2020 - link

    timecop1818 cant post new content, cause it doesnt have any.
  • xenol - Monday, March 2, 2020 - link

    The NUC product line is sort of dead in the water any way, I'd argue.
  • YB1064 - Monday, March 2, 2020 - link

    It would be helpful to include a small table that of benchmarks vs CPU performance scaling. Perhaps this is hard to do, but as a naive simple example:
    Benchmark#1 - scales with threads/cores
    Benchmark#2 - scales with clocks/IPC

    This is most likely highly complicated, but if anybody can do it, it is you guys. Ian, care to take a stab?

Log in

Don't have an account? Sign up now