Did your old eyes miss 29 frames of this detritus in the AMD VCE rendered output in the first video? The problem happens from 00:00:04.00 to 00:00:04.28.

It likely will not fail for CPU Only, NVENC or any codec other than AMD VCE.

@john_dennis I see the problem in the samples you provided. Downloaded your test projects and had good intentions of providing feedback, but I just found out my AMD R9 390 will not render UHD!!! I have no idea why. It does 1080 fine, so I'm of no help.

Indeed, I'm and stay a happy user with only Intel and Nvidia GPU's. 😁

Full HD doesn't fail with my RX480. I once had an Nvidia brand preference and I have an Intel adapter, but I'm really a hardware whore. 

Yess, and I think there's something terribly wrong with your brand, but if it gives you joy stay with it.😉

My weary eyes were still able to notice the artifacts around 4 secs. The renders (Intel 630/QSV and Nvidia 1050/NVENC, Magix AVC/AAC Internet 4K 29.97 were OK as j_d suspected. No AMD to test)

After pecking around the R9 390 is VCE 2.0 and requires 4.0 for 4K. I was able to up it a little bit to 1440p, and the render did not fail and no problem with the outcome, which really doesn't help you compare the problem with your UHD.

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. 

Confirmed the same artifact results using Vegas 15, but with an R9 NANO. Magix AVC/AAC CPU 4K UHD rendered it w/o artifacts.

Thank you. Did the project "Test 15 VCE - One Frame Crossfade.veg" run successfully?

Got the same issue with your project without crossfade on my RX470. No issue in the project with crossfade.

However, I've found something strange in your project (see picture). When I fixed this, it was rendered without issue.

The notch appears to be the ProType Titler indication of four seconds, the length of the title, but it's not on a frame boundary.

How did you fix it? 

This issue surfaced within a project where I reused assets, but Vegas Pro 15-416 fails from a new project where the user does absolutely nothing to the generated media or source media.

I'm still looking for confirmation that it doesn't happen in Vegas Pro 16.

P.S. No notches were created or harmed in the making of this video.

> The notch appears to be the ProType Titler indication of four seconds, the length of the title, but it's not on a frame boundary.

Sure. But I do not know how it happened because the length of the media generated title specified as 4 seconds and the position where it is ended is also 4 seconds. It should not be there (I never saw anything like this before, but I never worked with 29.970 footage as well, my footage 59.940 or 50p)

> 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.

Altered project (in case you'd like investigate)

P.S. I'm not trying to say that there is no bug. I just provided some additional details that may or may not be useful during further investigation.

@john_dennis

I have run both projects in both V15 and V16 without issue. I used both the Magix implementation of VCE as well as HOS. They all encoded perfectly. I even chose the Intel GPU for FX processing and rendered using VCE and there was no problem--only slower. I am using a 5 series card--the 550 which may account for the difference since I believe you are using a 4 series card. I also rendered with Nvenc on another system and there were no issues.

Thanks fifonik. The altered project ran on my machine also.

Thanks Wayne for the response on Vegas Pro 16 and the 550 card.

john_dennis.

I just ran your sample project on AMD VCE rendering on VP 15,16 I don't see any artifacts. This test done on AMD Vega 10 Frontier Edition Card.

Good. It's good to know that later versions of hardware and software are not affected by this phenomenon. I'll investigate locally with drivers, settings and such.  

I'm "Unauthorized   You are unauthorized for this action." for the Vimeo link.

Good. It's good to know that later versions of hardware and software are not affected by this phenomenon. I'll investigate locally with drivers, settings and such.  

I'm "Unauthorized   You are unauthorized for this action." for the Vimeo link.

Sorry Dennis. Removed done.

Good. It's good to know that later versions of hardware and software are not affected by this phenomenon. I'll investigate locally with drivers, settings and such.  

I'm "Unauthorized   You are unauthorized for this action." for the Vimeo link.

Sorry, I know am late to this thread. I tested the projects with my Fury X and VP15&VP16. I get the same artifacts as @john_dennis. However, if I set the project to 32bit video levels only it all goes away.

Thank you, Old Smoke. You're not too late. I think I'd be more likely to drag the black generated media one frame over the video than change the Pixel Format of the project. It didn't work for me, though.

HO shows the tail time in gold. The event is executed in a loop. Maybe this short section confuses Vegas.

It is always a good idea to match the length of the generated media to the event length. The short piece is only a fraction of a frame and should not be a problem. But, it's worth a try. Unfortunately I can not try it with my R9 380.

I tried Match Event Length on the ProType Titler event and the Generated Black, but the artifacts remain in the rendered output.

if I set the project to 32bit video levels only it all goes away.

I tried change pixel format ro 32-bits video levels and still got the issue.