![]() QuickSync appears to stress the GPU more, possibly because of the copy-back step for the decoded frames. The utilization numbers provide proof of the same. EVR is very lean on the GPU, as discussed earlier. The GPU utilization numbers follow a similar track to the power consumption numbers. On the other hand, the QuickSync decoder is able to handle it with the VC-1 bitstream decoder in the GPU. This is because there is currently no support in the open source native DXVA2 decoders for interlaced VC-1 on Intel GPUs, and hence, it is done in software. The odd-man out in the power numbers is the interlaced VC-1 clip, where QuickSync decoding is more efficient compared to 'native DXVA2'. Using native DXVA decoding, the frames are directly passed to the renderer without the copy-back step. In general, using the QuickSync decoder results in a higher power consumption because the decoded frames are copied back to the DRAM before being sent to the renderer. Admittedly, the passive Ivy Bridge HTPC uses a 55W TDP Core i3-3225, but, as we will see later, the power consumption at full load for the Haswell build is very close to that of the Core i3-3225 build despite the lower TDP of the Core i7-4765T. ![]() Power consumption shows a tremendous decrease across all streams. It makes use of the specialized decoder blocks available as part of the QuickSync engine in the GPU. In addition to DXVA2 Native, we also used the QuickSync decoder developed by Eric Gur (an Intel applications engineer) and made available to the open source community. However, for our tests, we used the DXVA2 mode provided by the LAV Video Decoder. It is usually used in conjunction with MPC-HC's video decoders, some of which are DXVA-enabled. EVR-CP is the default renderer used by MPC-HC. Deinterlacing and other post processing aspects were left at the default settings in the Intel HD Graphics Control Panel (and these are applicable when EVR is chosen as the renderer). The GPU is not taxed much by the EVR despite hardware decoding also taking place. EVR is mostly used in conjunction with native DXVA2 decoding. It is a lean renderer in terms of usage of system resources since most of the aspects are offloaded to the GPU drivers directly. The Enhanced Video Renderer is the default renderer made available by Windows 8. The former provides hints on whether frame drops could occur, while the latter is an indicator of the efficiency of the platform for the most common HTPC task - video playback.Įnhanced Video Renderer (EVR) / Enhanced Video Renderer - Custom Presenter (EVR-CP) GPU usage is tracked through GPU-Z logs and power consumption at the wall is also reported. Our decoding and rendering benchmarks consists of standardized test clips (varying codecs, resolutions and frame rates) being played back through MPC-HC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |