Please Test the AMD VCE UHD Render in Vegas Pro 15 and 16

john_dennis wrote on 2/21/2019, 2:45 PM

Please download and test these Vegas 15-416 Projects.

I was rendering in Vegas Pro 15-416 to the default Magix AVC/AAC Internet UHD render template AMD VCE option when I got these artifacts:

Adding a one frame crossfade produced these results, ceteris paribus.

With successful peer review, I would submit a bug report and go through all the analysis of O/S and video driver versions.

Big Note: This is not a decode problem. I replaced the source media six ways to Sunday.

I'm particularly interested to learn if the issue still exists in Vegas Pro 16.

Edit: 2019-10-31 Updated the project to include multiple points of failure.

Back to post

Comments

john_dennis wrote on 2/23/2019, 5:12 PM

HO VCE balanced CRF 20 doesn't fail.

john_dennis wrote on 2/23/2019, 5:43 PM

At its lowest common denominator, the AMD VCE render will act up if the titles and generated black are removed and/or a new project is created with the video started later than the audio.

john_dennis wrote on 2/24/2019, 3:13 PM

But alas! I've found there is a denominator even lower than the previous one. I rendered the project to uncompressed AVI and had no artifacts in the rendered output. Putting the uncompressed file back on the Vegas timeline of a new project and rendering to Magix AMD VCE produced the same artifacts without the drama of generated media being present in the project.

In this vignette I show that the driver I used is the latest one without getting into experimental territory.

john_dennis wrote on 10/31/2019, 10:15 AM

As one might expect when using hardware encoders, I retested this morning with Radeon driver 19.9.2 and the issue still occurs.

john_dennis wrote on 10/31/2019, 1:41 PM

@fifonik

> How did you fix it?

I trimmed one frame on the right of the media generated contents (titler and solid colour), trimmed one frame on the left of audio and finally moved the combined video/audio one frame to the left.

Tried again and the title not needed at all for the bug. I deleted the track and the bug is still there. It fixed when I just moved everything one frame to the right. Do not know how it is related.

This issue appears to be caused by a radical scene change occurring on an I frame in the rendered file in AMD VCE UHD renders (not in FHD as far as I am able to reproduce). Moving the scene change one frame in either direction makes it go away. Unfortunately, the location of I frames in the rendered output is not to of mind for me when I edit. I can identify the type of frame in VideoReDo.

john_dennis wrote on 10/31/2019, 2:17 PM

I updated the project to show that I can reproduce the failure anywhere the scene change happens on an I frame. Since some players just hang and show black during the bad video I included a track with time code. In MPC-HC you can watch the time code fail to update update when the video would be bad if you could see it.

... and oh yes, I am talking to myself. I do it all the time. Sometimes I even turn the radio down so I can hear what I'm saying.

vkmast wrote on 10/31/2019, 2:29 PM

@john_dennis we're all ears 👂👂 🙂.