Even when I drop the ProRes file (no artifacts/issues) or AVI file (again, no issues) on the timeline, I still get the artifacting around where the png files were even though they've been rendered/baked into the ProRes/Avi files. Vegas has no knowledge of the originals, just frames to render to HVEC or AVC. I still get issues. This leads me to believe it has to do with either: A. the latest build or B. a combination of the latest build and a driver/codec not playing nice with my files.

And do the same things happen when you render to AVC and HEVC software encoders (not AMD and not NVENC)? Do the same things happened with "GPU Acceleration of Video Processing" turned off in Options->Preferences->Video? Have you tried updating your AMD and Nvidia video drivers in Help-Driver Updates? This information will help narrow down your issue for possible inclusion in a trouble report.

And do the same things happen when you render to AVC and HEVC software encoders (not AMD and not NVENC)? Do the same things happened with "GPU Acceleration of Video Processing" turned off in Options->Preferences->Video? This information will help narrow down your issue for possible inclusion in a trouble report.

I'll test that now and report back here in a few.

What should I choose here? I turned off GPU acceleration in Preferences.

Choose Mainconcept, which is the software encoder.

I suggest turning one thing off at a time, rendering, writing down the result, and then changing that setting back to where it was before changing anything else.

It's Troubleshooting 101. Changing two things at once is meaningless, because if you trigger different results, no one will know which one caused the change, will you?

For the first test, I chose MainConcept from that dropdown. I thought it hung at 100%, but it eventually finished and the file had no artifacts.

For the second test, I chose IntelQSV from that dropdown. It rendered out without issue. For the record, I'm using the same test secton I linked to above.

Choose Mainconcept, which is the software encoder.

I suggest turning one thing off at a time, rendering, writing down the result, and then changing that setting back to where it was before changing anything else.

It's Troubleshooting 101. Changing two things at once is meaningless, because if you trigger different results, no one will know which one caused the change, will you?

I'm tracking with you regarding how to troubleshoot. I just wanted to make sure I was tracking regarding the template settings. I was pretty sure NV and AMD weren't options, I just wasn't sure about Intel (since I don't have an intel chipset/cpu).

I am curious though if you turn off gpu processing in preferences, does that trump all the items in the dropdown I screenshotted above? In other words, could I choose the amd option or the nv option and render out files ignoring the gpu's? Which setting overides the other is the real question I'm asking.

Thanks for the help @Musicvid

Were these two tests run with GPU Acceleration of Video Processing turned ON or OFF?

You need to be very specific here, because any developer reading your Support Request will probably ask the same thing.

Using your Prores sample file I"m not able to replicate your fault when rendering Nvenc via MagixHEVC. I also have 30 series GPU (3080). I am still hanging on with 643 but will most likely try 550 next (previously on 532). I see no advantage to 643, only negatives

GPU is off.

Additionally, (while GPU is off) I went ahead and rendered AMD as well as NV. NV rendered completely to 100% and everything looked good until I hovered over the file it rendered in the folder it was saved in. It was 0 bytes. It spent all that time rendering and processing each frame to complete successfully, but it didn't produce anything but a blank file.

I also rendered to AMD. AMD resulted in a partial success as it produced a file that played about halfway through the chosen timeline selection before it froze in Windows TV & Movies player and artifacted and went to gray in VLC.

Using your Prores sample file I"m not able to replicate your fault when rendering Nvenc via MagixHEVC. I also have 30 series GPU (3080). I am still hanging on with 643 but will most likely try 550 next (previously on 532). I see no advantage to 643, only negatives

Just to be clear @Former user, you are NOT using build 643 or you are using 643? I couldn't discern what build you are actually on. Can you clarify? Thanks for chiming in and letting me know that things worked as expected on your setup. There's hope!

I am still on 643

NVENC can't work with your GPU turned off, although NVENC is different silicon to your GPU processor, NVENC requires GPU processing for NVENC encoding to work.

I am curious though if you turn off gpu processing in preferences, does that trump all the items in the dropdown I screenshotted above? In other words, could I choose the amd option or the nv option and render out files ignoring the gpu's? Which setting overides the other is the real question I'm asking.

No need to speculate here, because neither setting necessarily "overrides" the other. They are separate but related functions of GPU in Vegas.

Try to stick to using If/And/Then, and avoiding Converse statements when at all possible. Sorry to sound elementary here, but that is where the process starts, at least in my field engineering experience. Here is a visual model to get you started; I'm sure it will all come back bc you had it in school.

I have VP19b643 with Intel QSV, but I am more interested in your report than I am in testing right now.

I am curious though if you turn off gpu processing in preferences, does that trump all the items in the dropdown I screenshotted above? In other words, could I choose the amd option or the nv option and render out files ignoring the gpu's? Which setting overides the other is the real question I'm asking.

No need to speculate here, because neither setting "overrides" the other. They are completely separate functions of GPU in Vegas.

Try to stick to deductive reasoning, using If/And/Then, and avoiding Converse statements when at all possible. Sorry to sound elementary here, but that is where the process starts.

That's confusing to me. In Preferences I turned off GPU Acceleration. Logically it would make sense to remove any gpu options from my rendering templates if they are linked. The fact they are still there leads me to conclude they are not. The fact that you tell me to stick to deductive reasoning tells me that they most likely are not linked. But given NV and AMD are in the dropdown makes me press hard against that conclusion.

What do you know that you are not telling me :)

I am still on 643

NVENC can't work with your GPU turned off, although NVENC is different silicon to your GPU processor, NVENC requires GPU processing for NVENC encoding to work.

Seems like Vegas wouldn't let you waste time rendering for a file that results in 0 bytes. The polite thing would be to give you a pop up telling you that you shouldn't waste your time as it will not give you what you want. The best thing would be to remove that from the rendering options if you have GPU acceleration turned off so that it's not even an option.

Thanks for the response @Former user

I am still on 643

NVENC can't work with your GPU turned off, although NVENC is different silicon to your GPU processor, NVENC requires GPU processing for NVENC encoding to work.

Ok disregard what I said about Nvenc not able to work. ACTUALLY it does when GPU is turned off in Vegas. It does this because although Vegas isn't using your GPU for processing, Nvenc is still able to. So that was interesting to discover. And because of that, You should not have ended up with a zero data file.

You could try the full driver reinstall using DDU, see if that fixes thing

@Former user Once troubleshooting is done, I may just uninstall completely and reinstall once I have everything wiped clean.

The GPU settings in Preferences vs templates is confusing to me. Hopefully it becomes more clear through these type of conversations (and hopefully helps others who are reading).

One thought on zero byte files is to make sure bitrates aren't over maximums for the encoders. I would keep the 2160p template entirely stock and only change the type of encoder for now (Mainconcept, NVENC or VCE). The other time I've seen zero byte files is when there was no audio included, but I thought that bug was fixed.

Preferences/video is timeline and effects GPU acceleration, file i/o is GPU decoding and render templates have GPU encoding options. All 3 are independently set (though it is possible an unwanted interaction between them is causing the problem you see here and that's what you're testing now).

One thought on zero byte files is to make sure bitrates aren't over maximums for the encoders. I would keep the 2160p template entirely stock and only change the type of encoder for now (Mainconcept, NVENC or VCE). The other time I've seen zero byte files is when there was no audio included, but I thought that bug was fixed.

Bitrate should be fine as it is whatever comes up when I select NV from the drop down. Having referenced no audio, that is indeed how I rendered (unchecking the box to include audio on the audio tab). Maybe that was the issue. I can test that, but it will be tomorrow as sleep calls.

Preferences/video is timeline and effects GPU acceleration, file i/o is GPU decoding and render templates have GPU encoding options. All 3 are independently set (though it is possible an unwanted interaction between them is causing the problem you see here and that's what you're testing now).

That's helpful. That's what I was looking for. Thanks Roger!