It definitely does not happen for me with only a single PNG on the timeline. It requires a sequence of PNG (or JPEG). I'm using the latest NVIDIA studio driver also, but on a 2022 XPS with Win 11.

The bleed effect is very pronounced (the two clips are superimposed/garbled over each other after the image sequence ends). In this case I can render out using the Main Concept HEVC engine, so it's not a deal breaker. If I can come up with any other ways to trigger it, I'll post back. Thanks for trying to duplicate it!

@RogerS It's a different variation of the broken full screen image problem I"ve shown in past. Vegas would have had this bug since VP15. There are likely many other variations.

Also I"m using AVC media, not HEVC

Voukoder shows correct operation. Magix encodes are broken, they do not show the 5 seconds of still image.

It definitely does not happen for me with only a single PNG on the timeline. It requires a sequence of PNG (or JPEG). I'm using the latest NVIDIA studio driver also, but on a 2022 XPS with Win 11.

The bleed effect is very pronounced (the two clips are superimposed/garbled over each other after the image sequence ends). In this case I can render out using the Main Concept HEVC engine, so it's not a deal breaker. If I can come up with any other ways to trigger it, I'll post back. Thanks for trying to duplicate it!

If you have other ideas (or a sample project) I'm willing to test again, especially as I use timelapses in my work. I believe it exists and replication should bring us closer to solving it.

@ALO I tried how (I think) you described, but do not see an encoding defect, the cat picture however causes the video to freeze but that problem is unrelated to HEVC video

Video being used is DJI HEVC 420 10BIT

@ALO In the past I learnt to use Mainconcept to render anything with png's (pics/text) because NVENC messes with the pictures. (Not always but it's not guaranteed NV won't mess it up so it's safer to not use that option)

This is a 5.3 GoPro, a text png sequence & a couple of png pics.

I've only done one test with two renders,

With Magix HEVC NV Encoder

With Magix HEVC Mainconcept

This is just one test but from past experience of trial n error with the settings I don't believe there's anything I can do to change this...

@Former user Tried twice with Magix NVENC HEVC, looked fine, tried once with Magix NVENC AVC, got the artifacting OP describes.

@Former user I normally use AVC & haven't recently (2023-24) made any videos so haven't had to deal with this.

The ones I did above are Magix HEVC but the project was/is still on the timeline so I tried it with Magix AVC NV Encoder,

Just one render gave the same glitch as my Magix HEVC NV Encoder which is similar to yours,

@Former user Tried twice with Magix NVENC HEVC, looked fine, tried once with Magix NVENC AVC, got the artifacting OP describes.

 

 

thank you everyone for the repo! Hope this gets fixed

This has been a fault since 2017,so it appears they have no plans to fix. As a coverup the meme of 'hardware encoding is low quality' was created in the Vegas forums. And everyone here parroted the same, even though the developers knew the hundreds of complaints were valid, and the artifacting was due to bugs.

VP17 is earliest Vegas I have it behaves the same,

The NVIDIA NVENC graphics glitch dates to VP15 I believe. That's when I first encountered it

That's not related to hardware renders are low quality, which I remember being more about earlier implementations of QSV.

@RogerS , @ALO said he see's the artifacting from his demonstration on QSV and NVENC, you don't feel that could contribute to glitching with QSV in general and could have similar problems?

But you do say you've noticed glitching with NVENC for a long time, and I'd guess by now you're experienced enough with QSV to say it doesn't happen or rare in comparision?

I saw glitching until VP19 connected with NVENC and dynamic ram preview. I don't really see it often anymore as the devs did listen and address it (I was one of the many reports of this problem).

These days I do draft renders with MagixAVC and NVENC and final through x264 and Voukoder (usually).

I haven't seen glitches with QSV encoding but also don't often use it so don't doubt others reports.

For render quality if matters for a GPU encode I give it more bitrate to work with. I see its tradeoff with datarate inefficiency as a different issue than artifacts.

@RogerS Try a test with this file https://www.dropbox.com/scl/fi/52jv1c76dop3dxn6jli8o/input-render-test.mp4?rlkey=wuh4oybmpvf2o9b0dup8wpdhy&dl=0

Use MAGIX AVC NVENC 2160P 59.94 render template, change the frame rate to match project 23.976. Do same with QSV.

If either of the encodes are different to the original describe.

I find here significant differences - between the QSV encoded footage and the original footage. The NENC footage seems to be quite similar to the original footage.

Original:

Intel QSV encoded footage:

Is that what you were looking for?

@Wolfgang S. it encodes like this for me (Nvenc)

I"m using the 2nd most recent Nvidia studio drivers. If nobody else shows the same I"ll reset Vegas

Hard to say what you should do. I can confirm only, that I do not see the colored artefacts in my nvenc supported AVC rendering - that your video shows in the beginning in the cat part of the video. I have found another issue with QSV encoding, and that is something that I have reported.

But you should be aware that I am using an old nvidia driver (522.30) for the simple reason, that this works for me. And there are for sure differences in the testing enviroment that I use here, too.

So it is hard to give you an advice how to proceed. Maybe it is worthwhile to reset Vegas, but then I would recommend to export the preferences before you do so (Options/Export preferences).

But frankly spoken, my expecation (and I may be wrong here) is, that it could be that a reset is not the solution. Maybe it is a driver issue, maybe it is a issue in the actual version of Vegas you use, maybe both of it. So you can only try, maybe reset Vegas, but also think about to deinstall the nvidia driver you use, and test an older one - and see if that shows positive results.

@Wolfgang S. Hi, from my experience this has been an issue with all versions of VP since my first VP18 & all drivers that have been released since,

Can be. Funny enough, that I do not see this issue in my test environement with the clip delivered by Todd. ;)

I appreciate a good test!

I see a ton of render artifacts in the NVENC render:

Completely unusable.

The QSV render looked similar to the source though there are the usual compression issues (mild blocking)..

I'm seeing the same with the NVENC render, also with the older driver 522.30

No problem with QSV or Mainconcept rendering

Have repeated the test twice. Now I see artefacts also in the NVENC samples - but there is still nothing in the first render test. Funny.

This is a comparison of 2 MAGIX NVENC encodes, and a slightly different test, The top encode at the lower bitrate is successful it shows the cat, the bottom encode does not show a cat, although it should. The problem looks to be related to the much lower bitrate P frame at position 102, which will forbid the cat from appearing, probably for as long as the cat is shown. I've tested a maximum of 10 seconds of cat, but no cat is encoded.

frame 102 is where the jpg first appears on timeline