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

  • ganeshts - Monday, March 2, 2020 - link

    Has been discussed ad-nauseam.

    If you don't like Bapco's SYSmark, feel free to skip the section.

    We believe it presents credible comparison points because it uses *publicly available builds of commercially used software*. The same Adobe applications and MS Office applications are going to be used by consumers whether they have an Intel-based machine or an AMD-based machine.

    FWIW, the Frost Canyon numbers in SYSmark actually show that there is no major gains in the benchmark to be had with the addition of the two cores compared to Bean Canyon. Whether people like it or not, most real-world applications fall back on single-threaded performance - Here, Bean Canyon and Frost Canyon are essentially neck-to-neck.
  • Irata - Tuesday, March 3, 2020 - link

    I know this has been discussed a lot, but isn‘t the consensus that it cannot be used as it‘s essentially an Intel sponsored benchmark. I mean nVidia, AMD and Via pulled out for a reason.

    Also, they have a history of skewing results by stressing certain tasks that feature specific CPU architectures over others going back to the P4 days. Why should this be different now?
  • James5mith - Monday, March 2, 2020 - link

    I have 64GB of RAM in my Bean Canyon NUC running VM's right now. How is this the first one to support it?
  • ganeshts - Monday, March 2, 2020 - link

    The keyword is 'officially supported'

    Max Memory Size is 32GB on this page: https://ark.intel.com/content/www/us/en/ark/produc...
  • MDD1963 - Monday, March 2, 2020 - link

    Pg 1 "... is stil a bit of an unsteady eara" Eara? :)
  • Zok - Tuesday, March 3, 2020 - link

    Ugh. Come on! Give me a NUC with 2+ NICs.
  • snowsurferDS - Tuesday, March 3, 2020 - link

    The AsRock mini 300 should be tested with a 3400G not a 2400G, at least.
  • dontlistentome - Tuesday, March 3, 2020 - link

    Prices keep on going up for no reason (seriously, why should this be so much more epensive than the i7s of a few years ago?).
    And that power consumption? 64W peak.
    next gen the power brick will be bigger than the NUC box.
  • alpha754293 - Tuesday, March 3, 2020 - link

    It's too bad that the thermal management design on these systems are so bad that under heavy CPU and/or CPU+GPU load, it's runs very quickly against the thermal limit, and therefore; has to start throttling itself due to the thermals.

    If the system had a better thermal management solution and was ACTUALLY able to run at full load for extended period of time, in this form factor, then it would be worth it, else, having a 6-core processor in there is so pointless since you can't even make full use of the previous 4-core CPU in the NUC8.

    This is my biggest complaint about my two NUC8s that I have. If it had better thermal management so it wouldn't throttle itself due to thermals, it would present a compelling argument against, for example, the Mac Mini.
  • ROD.LEE - Tuesday, March 3, 2020 - link

    was thinking of upgrading from my NUC8I7BEK, after your review, umm no.

Log in

Don't have an account? Sign up now