Vp15 B311 Intel HEVC rendering (QSV) on i7-8700k

Peter_P wrote on 2/22/2018, 2:49 AM

Hello together,

when rendering XAVC-S UHD(p30) footage to UHD(p30) using the Intel HEVC encoder should not be done with an existing, older render template. This may crash the system.

Please make a slight change. For example use the 30-40Mbps template, set the upper limit to 42Mbps and save this to one with a new name. Thereby the template is newly written by Vp15 B311 and rendering with this template should not cause any problem.

I think this problem is not really related to the footage. But this is, what I tested.

Rendering to Intel HEVC 10bit still does not work on i7-8700k.


john_dennis wrote on 2/22/2018, 10:22 AM

Are you proposing that version dependencies exist for “custom” render templates from previous Vegas Pro versions, or standard render templates included with previous Vegas Pro versions?

My main system:
Motherboard: ASUS ProArt Z790-CREATOR WIFI
CPU: Intel Core i9-13900K - Core i9 13th Gen Raptor Lake 24-Core (8P+16E) P-core Base Frequency: 3.0 GHz E-core Base Frequency: 2.2 GHz LGA 1700 125W Intel UHD Graphics 770 Desktop Processor - BX8071513900K
GPU: Currently intel on-die video adapter
RAM: CORSAIR Vengeance 64GB (2 x 32GB) 288-Pin PC RAM DDR5 5600 (PC5 44800) Desktop Memory Model CMK64GX5M2B5600C40
Disk O/S & Programs: WD Black SN850 NVMe SSD WDS100T1X0E - SSD - 1 TB - PCIe 4.0 x4 (NVMe)
Disk Active Projects: 1TB & 2TB WD BLACK SN750 NVMe Internal PCI Express 3.0 x4 Solid State Drives
Disk Other: WD Ultrastar/Hitachi Hard Drives: WDBBUR0080BNC-WRSN, HGST HUH728080ALE600, 724040ALE640, HDS3020BLA642
Case: LIAN LI PC-90 Black Aluminum ATX Full Tower Case
CPU cooling: CORSAIR - iCUE H115i RGB PRO XT 280mm Radiator CPU Liquid Cooling System
Power supply: SeaSonic SS-750KM3 750W 80 PLUS GOLD Certified Full Modular Active PFC Power Supply
Drive Bay: Kingwin KF-256-BK 2.5" and 3.5" Trayless Hot Swap Rack with USB 3
Sound card: Realtek S1220A on motherboard. Recording done on another system.
Primary Monitor: ASUS ProArt 31.5" 1440p HDR10 Monitor PA328QV
O/S: Windows 10 Pro 10.0.19045 Build 19045
Camera: Sony RX10 Model IV


Peter_P wrote on 2/22/2018, 10:47 AM

No, just use an Intel HEVC template, that is shown when you start 'render as ...' and alter for example the upper bitrate and save this new template. This ensures that the template is written by the actual Vegas pro version and that's important.

However,  I just had a hard crash with system reboot while rendering an existing UHDp30 project to Intel HEVC with an altered template. So this may not always help on i7-8700k systems. 


Peter_P wrote on 2/24/2018, 11:22 AM

However,  I just had a hard crash with system reboot while rendering an existing UHDp30 project to Intel HEVC with an altered template. So this may not always help on i7-8700k systems.

A couple of further tests with many hard crashes leads me to the assumption, that these crashes are caused by the restriction to “1” render thread to avoid Mercalli glitches.

Today I rendered a short 08:23 UHDp30 XAVC-S project to Intel HEVC UHDp30 first with the max. render threads set to “1” and the system crashed to a reboot at TL ~ 05:21. Then I rendered the same project twice successfully with max. render threads set to “16”, but I got Mercalli glitches.

The crashes do not occur when I render to UHDp30 MAGIX AVC/AAC QSV  nor to FHDp30 with Sony AVC with max. set to “1”.

I did not have these crashes  with max. render threads set to “1” on my (old) i7-6700k with previous Vegas versions.

Is there any hint how to avoid the Mercalli glitches and crashes rendering to Intel HEVC on an i7-8700k?

Peter_P wrote on 2/25/2018, 11:03 AM

I could now find a solution to render with Intel HEVC to UHDp30 without crash and no Mercalli glitches. The current  mxhevcplug folder was replaced with the related content from B216 and the max. render threads can be set to “1”, without causing the system to crash. Using this approach requires to rewrite the Intel HEVC render template with a slight change. If not, I get again the color artifacts.