What Nvidia driver version was giving you the black preview with your GTX 980Ti cards?

Perhaps the actual problem was that he had two such cards in the system.

What Nvidia driver version was giving you the black preview with your GTX 980Ti cards?

Perhaps the actual problem was that he had two such cards in the system.

I doubt that is the problem. Search the forum and you will form the solution. I would rather prefer the OP either corrects his tutorial or takes it down. To say the OFF means that Vegas is using the onboard video card for preview is just simply wrong... it is completely wrong.

I am using the latest Nvidia drivers 378.66 and always keep them updated, and two cards (or more) of the same type showing in the drop down simply means the system is likely in either a SLI or Crossfire configuration, and Vegas is detecting multiple GPUs/graphics cards. Can you explain why my Off comment is wrong? I will gladly change it if you provide evidence, thanks!

OFF in Vegas means that it doesn't use OpenCL, something Nvidia cards are not so good at as AMD cards, instead Vegas will use your CPU to process all FX, transitions and compositing. It does NOT mean it will use your onboard graphic card. If you would have an actual in board graphic card that falls within the Vegas spec, it would be listed under GPU acceleration, so would be any that is on the processor. This has been discussed in this forum since VP11 came out, please change it.

Thanks for the information. I have edited the original video and removed my comments about the OFF setting, and I also updated my original post with the newer youtube link. Thanks for the help and hopefully my tutorial helped someone out there in the same boat as me!

This is what I had to do when MS pushed an Nvidia driver update on my system about a month ago when it forced the upgrade to Win10 Anniversary. I even tried updating to the latest driver (387.66) with no success. The MS upgrader had insisted that the older Nvidia driver was not compatible with the current build of Win10.

But, maybe you should call this a workaround not a fix? By, turning off the GPU you disable any acceleration benefits of the GPU during preview playback -- it doesn't really fix it...

Right - so it fixes the issue of the preview not functioning at all in certain situations, and instead uses your processor to render the preview. However, what it doesn't fix is how to both utilize the GPU acceleration AND see the preview too. Does anyone know how to truly fix this, because I would much rather make that video instead, but in the meantime this workaround does allow me to continue my work within my project?

Things to try:

Remove one of the video cards.

Install different video drivers.

Search this forum for more information about cards that work.

Buy an AMD RX480.

Do your video processing on a machine optimized for video editing rather than game play.

Don't promise your viewers that every video file you place on the timeline after this fix will work just fine. Sooner or later you (they) will add something that won't play for a different reason.

The only fix I know of is to go back to an older Nvidia driver. Search the forum for "NVidia" and limit the search to the last month and you'll see quite a few threads / comments. But, as it is, I do so little editing nowadays, I'm just sticking to disabling the GPU during preview and rendering.

Driver 376.33 "should" work fine even with both cards.

Good points. The interesting thing about Vegas in my scenario is the CUDA button successfully detects and uses my GPUs, which appears to be utilized during rendering. The preview within the project does not work unless set to OFF, so in terms of rendering the video, everything seems to be working great with CUDA, it is just the preview within the project that has issues (OpenCL?). I understand that CUDA != OpenCL, but this is something that I noticed and I'm not sure if this reveals any further clues as to the real issue:

I think you'll find that CUDA is not = to OpenCL. An example.

Do people typically not have this issue with AMD cards, or do some AMD users also experience the exact same issue? @OldSmoke

Driver 376.33 "should" work fine even with both cards.

This is also what I would try first. See this comment from someone with a theoretically similar card to yours. My comment here may help you with the rolling back process. Please let us know if it works. If 376.33 is no good, you could take a very recent comment from Magix staff seriously and go all the way back to 337.88.

Do people typically not have this issue with AMD cards, or do some AMD users also experience the exact same issue? @OldSmoke

This black preview issue has become common very recently with Nvidia drivers 378.66 and 378.49, especially on older cards based on Fermi architecture. Your case is the first I've heard of it on a Maxwell2-based card. In this comment from bitman, that driver is OK with a GTX Titan-x which is also Maxwell2. So it's pretty hard to predict. The issue does not affect AMD cards.

SUCCESS - Thanks for sharing those threads/links Nick Hope!

Rolling back to either Nvidia Driver Versions 372.90 or 376.33 truly fixed the issue, and now preview works with one of my two GPUs selected.

Nvidia Driver Version 378.66 - This is the driver that did NOT work on my 2x980ti SLI Win7 64-Bit system, which was automatically applied because of my GeForce Experience settings to download/install automatically (Now Disabled).

I will make a brand new video, showing both the fix AND the workaround, as it seems this behavior is difficult to predict depending upon the Nvidia GPU architecture, and as new Nvidia drivers are released, it's nice to know which stable drivers to use.

I understand that CUDA != OpenCL, but this is something that I noticed and I'm not sure if this reveals any further clues as to the real issue:

CUDA is proprietary API and only applies to Nvidia. OpenCL is an open API, free of any royalties. Yes, the Mainconcept AVC render template will show you that you have CUDA but it will NOT use it. The load you can observe on your Nvidia GPU is not because of CUDA encoding but because Vegas can make use of the limited OpenCL capabilities of your card. Nvidia did improve the OpenCL capabilities within the new drivers, but it's just not as good as AMD at the moment. The Mainconcept CUDA encoder was developed for VP11 by Mainconcept, not by Sony and has never been updated since, to work with later GPU architectures; Fermi is the last one supported. In all fairness, Nvidia also made hardware changes in the way the compute units actually work from Kepler onwards which broke the Mainconcept encoder. I assume Sony didn't want to invest again to keep the Mainconcept encoder up-to-date, which is probably very expensive.

All this information is actually available in this forum, spread over hundreds of threats.

Aside from this, installing the Nvidia CUDA toolkit along with the latest driver will also cure the preview window issue. That would suggest that Nvidia forgot to package a certain module with the latest drivers that is required to get the preview working and the installation of the CUDA kist rectifies it.

Aside from this, installing the Nvidia CUDA toolkit along with the latest driver will also cure the preview window issue. That would suggest that Nvidia forgot to package a certain module with the latest drivers that is required to get the preview working and the installation of the CUDA kist rectifies it.

OldSmoke, could you please confirm exactly which card, driver and version of CUDA toolkit combo works? Previous discussion here didn't really confirm anything specific on that subject.

I'm building a spreadsheet of Nvidia driver compatibility for Vegas and plan to share it on Google Drive.

Driver 376.33 "should" work fine even with both cards.

In my system it doesn't, unfortunately - but what's even more weird and different from most other users' experience that I do have preview in VP13, but still not in VP14 (as you can find in my signature, I too have 2 nVidia cards)...

Piotr

Driver 376.33 "should" work fine even with both cards.

In my system it doesn't, unfortunately - but what's even more weird and different from most other users' experience that I do have preview in VP13, but still not in VP14 (as you can find in my signature, I too have 2 nVidia cards)...

Piotr

What's your OS version? If it's Windows 7 then installing .NET Framework 4.6.2 might help. It seems that the installation of that should have been included in (or triggered by) the VP14 installer for Windows 7 users as it is required for display-related stuff. (sorry if I've suggested this before)

Have you tried later drivers than 376.33? 378.66 works OK for bitman and his GTX Titan-x which indicates that the 378.XX drivers might be OK with recent/powerful cards.

It's Windows 10 and with newer drivers, neither versions of Vegas Pro has preview working properly. So to sum it up:

- even when it worked, TL acceleration was only minimal and made editing/grading 4K a pita, so I started gradually switching to Resolve

- now it doesn't work at all (which isn't a disaster per se, as I work with Decklink full-screen preview, anyway - but showing how pathetic VP is now, it sealed my full migration to Resolve)...

Now I not only grade, but also edit in Resolve Studio - and visit old good Vegas for some audio finishing touches only.

Piotr

Aside from this, installing the Nvidia CUDA toolkit along with the latest driver will also cure the preview window issue. That would suggest that Nvidia forgot to package a certain module with the latest drivers that is required to get the preview working and the installation of the CUDA kist rectifies it.

OldSmoke, could you please confirm exactly which card, driver and version of CUDA toolkit combo works? Previous discussion here didn't really confirm anything specific on that subject.

I'm building a spreadsheet of Nvidia driver compatibility for Vegas and plan to share it on Google Drive.

Nick, this "may" be more related to older cards. I did test this with my GTX580 and driver 378.xx. The driver broke the preview but installing the CUDA toolkit "repaired" it. I still believe that should work for newer cards too, I just cant test it.