[Resolved] Stuttering HEVC output from Vp14 Intel Encoder

Back to post

Comments

liork wrote on 4/3/2017, 3:51 AM

I am facing same problem with HEVC rendering.

wwaag wrote on 4/6/2017, 10:11 AM

Here is a link to a short demo that suggests the problem lies in how Vegas implements the Intel hevc encoder. The timecode FX was added to enable one to step through the resulting renders. The first clip was rendered using x265 inside of ffmpeg. The second clip was rendered directly from the Vegas timeline using the default template (20 Mbps vbr). The ffmpeg x265 render was also 20 Mbps. Since there seem to be problems with how Vegas also decodes hevc, I used TMPGEnc's Mastering Works 6 to step through the resulting renders frame by frame. Here are the results.

As you can see, the x265 direct render steps frame by frame without issue. However, the Vegas-rendered clip shows a definite pattern of duplicating and then skipping a frame, which I suspect accounts for the observed stuttering.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Peter_P wrote on 4/6/2017, 10:56 AM

Since there seem to be problems with how Vegas also decodes hevc, I used TMPGEnc's Mastering Works 6 to step through the resulting renders frame by frame.

Interesting observation, however when I step through the Vp14 Intel HEVC encoded file (see link in first post) with MPC-HC, I do not see any duplicate frames. The same when taking the file into Vp14 B244 timeline. Could you please check the file in your environment?

wwaag wrote on 4/6/2017, 11:56 AM

@Peter_P

I tried the same file with MPC-HC. These were the frame numbers displayed:

0,1,2,4,5,7,8,10,11,13,14,16,17,19,20,22

In TMPGEnc, the frame numbers were:

0,0,1,3,3,4,6,6,7,9,9,10,12,12,13,15

It would appear that MPC-HC is simply skipping duplicated frames and as such probably not a good tool for testing.

Regardless, the file from Vegas is clearly problematic.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Peter_P wrote on 4/6/2017, 12:06 PM
Regardless, the file from Vegas is clearly problematic.

Thanks, obviously we can not do any thing on that output but wait for a solution in Vp14.

In the meantime I'm using Handbrake from Vegas pro that also support the Intel HEVC Encoder with QSV.

Peter_P wrote on 6/27/2017, 8:20 AM

Even though this problem is not listed to be solved with the new build B270,  with two of my test-clips it now does no longer show up under Win10 1703.

Thanks very much to the Vegas pro team !!!!