Totally Disgusted

FilmvsDigital wrote on 1/16/2017, 3:08 PM

I've been a defender of V14 for a while but as I continue to work with it on developing a project I have slowly, reluctantly, but surely decided this product is ready for prime time NOT. I'm undecided as to what to do at this point. Unfortunately, I have a number of functions and special effects that are V14 but what good is that when you can't even get a render when you add one of these? I will either return to V13 or move on to DaVinci. I love the Vegas approach and its association with other products such as Sound Forge, but, again, what good is all that when you can't get your project out the door? V14 can't make up its mind on how to do anything. Case in point: if I turn on GPU, I eliminate the scrubbing timeline aborts due to the endless Unmanaged Exception - C:\WINDOWS\SYSTEM32\nvoglv64.DLL by turning GPU on. Renders with GPU on are useless. Renders with GPU off add one more Unmanaged Exception - C:\WINDOWS\SYSTEM32\nvoglv64.DLL to the list. And yes, scrubbing aborts continue apace with dynamic ram preview = 0. And yes, I've got the latest video driver installed and no, I'm not going to play Russian roulette with back versions on the "hope" that "magic" will happen. A bitter pun to end: V14 Suite is not sweet at all.

Comments

astar wrote on 1/16/2017, 3:25 PM

Before you give up on Vegas, you should really uninstall the NVidia drivers from your machine, and get your GPU back to using the microsoft default driver. Then run CCleaner reg clean, apply all windows updates, and reboot. PIckup and install a AMD RX-480, R9-390x/290x, or FuryX GPU with the latest GPU drivers.

NVidia simply sucks with OpenCL support compared to AMD, and Vegas is OpenCL based. GPU based rendering of MP4 is so passe, so do not worry about it and use Sony AVC profiles or the Handbrake output.

Since you do not post system specs on your system, or your workflow, its hard to tell what GPU would be best for you are doing.

While you are replacing the card, it would be a good time to verify:

  • the new GPU is interfacing at 16X (GPU-z)
  • memory bandwidth is max for your motherboard (winsat mem),
  • a complete pass of Memtest86+
  • SFC /scannow completed with no errors
  • Windows is fully updated.

 

xberk wrote on 1/16/2017, 6:25 PM

>>if I turn on GPU, I eliminate the scrubbing timeline aborts

Are you saying that with GPU off, scrubbing the timeline causes Vegas to crash?

Paul B .. PCI Express Video Card: EVGA VCX 10G-P5-3885-KL GeForce RTX 3080 XC3 ULTRA ,,  Intel Core i9-11900K Desktop Processor ,,  MSI Z590-A PRO Desktop Motherboard LGA-1200 ,, 64GB (2X32GB) XPG GAMMIX D45 DDR4 3200MHz 288-Pin SDRAM PC4-25600 Memory .. Seasonic Power Supply SSR-1000FX Focus Plus 1000W ,, Arctic Liquid Freezer II – 360MM .. Fractal Design case ,, Samsung Solid State Drive MZ-V8P1T0B/AM 980 PRO 1TB PCI Express 4 NVMe M.2 ,, Wundiws 10 .. Vegas Pro 19 Edit

NormanPCN wrote on 1/16/2017, 8:16 PM

Before you give up on Vegas, you should really uninstall the NVidia drivers from your machine, and get your GPU back to using the microsoft default driver. Then run CCleaner reg clean, apply all windows updates, and reboot. PIckup and install a AMD RX-480, R9-390x/290x, or FuryX GPU with the latest GPU drivers.

NVidia simply sucks with OpenCL support compared to AMD, and Vegas is OpenCL based.

The Nvidia drivers should be fine. After all the drivers that are Windows "native" are written by Nvidia.

I think it is more accurate to say that Vegas sucks with Nvidia. Nvidia does just fine in OpenCL these days in an app like Luxrender (OpenCL).

 

astar wrote on 1/17/2017, 1:08 AM

I am not saying to use the default windows NV driver for his card, I am saying remove all traces of the NV card and try an AMD card as a comparison. The "Microsoft Basic display" driver was not written by NV. Seriously?

NV had its own game plan with regards to OpenCL, and was trying to keep things proprietary and in their fence line. Recent changes in their OpenCL performance likely comes from a loss of market share in a shrinking desktop market of discrete GPUs. When players like Apple and Dell stop soldering your cards onboard due to performance gaps, and Adobe changes software from CUDA to also support OpenCL, that will make your company switch to the other standard fast and focus on improvement improving benchmarks. haha. Think about it, Apples top pro product runs AMD, if you are Adobe, you are going to make sure you operate properly on AMD with the creative suite.

Also you are talking about only NVs latest products the 980/1080, previous generations are not magically upgraded. Most Vegas users are still struggling with older NV cards that just sucked in Vegas performance.

Do your own Comparison of OpenCL versions, GFLOP performance, and release dates. NV is playing catch up, and Vega is going to raise the bar yet again for them.

Both manufacturers seem to care more about low power/performance vs trying to beat the other with the most horsepower you can put under the hood. The numbers for scoring a new portable device release are much higher than desktop discrete GPUs.

The days of enthusiasts combining parts to build their own machines are numbered. We all being driven into a world of small integrated devices, where upgrading is done by purchasing the newest unit.

FilmvsDigital wrote on 1/17/2017, 3:02 AM

@xbrk - yup. @astar workflow is simple. Save video from whatever source, shot, purchased, etc. to raid then make a copy which is then taken into Vegas and have at it. Have core i5-3930k and 32k memory which Vegas can't seem to use 1 byte of. Nvidia is GTX670 which Vegas can't seem to handle. Creative Cow has a post about how to bring V14 projects into V13. Spent a chunk of time doing that only to add another Unmanaged Exception - :\WINDOWS\SYSTEM32\nvoglv64.DLL to the list so am now concluding it's Nvidia. If dumping the Nvidia card for AMD would clear this mess up, it might be worth it. As of now, I'm busy exporting from Vegas to DaVinci and see how that works. Of course, the project will have to be re-done given all the Ignite/NewBlue stuff but if it's solid, it's worth it.

NickHope wrote on 1/17/2017, 3:46 AM

...And yes, I've got the latest video driver installed and no, I'm not going to play Russian roulette with back versions on the "hope" that "magic" will happen...

I'm afraid, as it stands, you're probably going to have to do that if you want to fix it. I suggest a full uninstall of your driver using something like this, and then trying some older drivers. Read this comment from Magix staff about Nvidia driver versions.

FilmvsDigital wrote on 1/20/2017, 7:12 PM

I believe I have found the problem. The footage in question is anamorphic (1.33); I took the dimension changes this represents and entered them as a new video template of 2554x1080 (also tried 1920x812). Finally decided to take a look at PAR drop down and try leaving video template alone (1920x1080) and set pixel aspect ratio to 1.3333 (HDV 1080), it appears we are stable. Sorry for all the hulabaloo. I think we have here a classic case of user error. :( Please change title of post to Totally Stupid.)

NickHope wrote on 1/20/2017, 10:34 PM

I believe I have found the problem. The footage in question is anamorphic (1.33); I took the dimension changes this represents and entered them as a new video template of 2554x1080 (also tried 1920x812). Finally decided to take a look at PAR drop down and try leaving video template alone (1920x1080) and set pixel aspect ratio to 1.3333 (HDV 1080), it appears we are stable. Sorry for all the hulabaloo. I think we have here a classic case of user error. :( Please change title of post to Totally Stupid.)

Glad you got it working but entering any resolution and/or PAR that Vegas will accept should not cause an "Unmanaged Exception - C:\WINDOWS\SYSTEM32\nvoglv64.DLL" as you described.