PLEASE FIX GPU ACCELERATION FOR GTX 970 CARDS ON WIN 10 x64!

BradfordWest wrote on 8/25/2016, 2:11 AM

To keep my future business I would like to see MAGIX fix problems with GPU acceleration in Vegas Pro 13 before mucking about with Vegas 14 since it was a feature that once worked great but then broke for some reason and Sony never fixed it—probably because they knew that one day it wouldn't be their problem anymore. Hello MAGIX!?

Back when Vegas 13 was originally released, I ran the trial version and GPU Acceleration worked great, previews ran beautifuully in  Best (Full) mode and renders @ 1080 x 1920 would render faster than real time. So I shelled out for the expensive upgrade from basic Vegas 11 Pro to Vegas Pro 13 Suite. But after a few new version builds and many Win10 upgrades, and now the aquisition of Vegas by MAGIX, the ability to turn on GPU acceleration simply absent. The only selection available now is "OFF".

This is hugely disappointing because now I have to put up with much poorer previews, and renders take 3X+ longer because Sony would not fix the problem. To put it simply, I did not get what I paid for and it's been enough of a handicap that I'm forcing myself to learn to use Adobe Premiere because previews are much better and renders are accelerated as they should be.

Will MAGIX work hard keep it's long time users happy? Many of us are understandably worried.

Comments

Former user wrote on 8/25/2016, 8:22 AM

Did you try reinstalling the Nvidia software? After I updated one computer to the latest Windows 10 and update a Win 7 to Win 10, I had to reinstall the drivers to get Vegas to see the GPU

BradfordWest wrote on 8/25/2016, 12:34 PM

Did you try reinstalling the Nvidia software? After I updated one computer to the latest Windows 10 and update a Win 7 to Win 10, I had to reinstall the drivers to get Vegas to see the GPU

I've tried so many things to troubleshoot this problem including resetting my systems completely, which I do once every 6 or so months anyway, and reinstalling Win10 from a known stable build, then immediatelty installing the latest Nvidia drivers (currently v 372.54) then a fresh install of VP13Suite/U before anything else and still get the same problem. The option to set GPU acceleration is not available, the only option is "Off."

I've seen this problem discussed on many forums across the internet and it seems to affect users with a GTX 5x, 6x, 7x or 9x cards the most. My card is the GTX 970 and I have yet a post anywhere where someone says that specific card is working as expected with VP13. 

I'd love to hear from anyone with a VP13 and a GTX970 installed where acceleration is working as expected for them. It's fiarly rare when I cannot troubleshoot a resolvable problem.

Former user wrote on 8/25/2016, 12:40 PM

Sorry you are having troubles, but you mentioned something different than I suggested. I would try installing the drivers (or reinstalling) AFTER you have installed Vegas, if you haven't already. I am not using that video card though, so I can't help anymore.

OldSmoke wrote on 8/25/2016, 12:47 PM

To keep my future business I would like to see MAGIX fix problems with GPU acceleration in Vegas Pro 13 before mucking about with Vegas 14 since it was a feature that once worked great but then broke for some reason and Sony never fixed it—probably because they knew that one day it wouldn't be their problem anymore. Hello MAGIX!?

Back when Vegas 13 was originally released, I ran the trial version and GPU Acceleration worked great, previews ran beautifuully in  Best (Full) mode and renders @ 1080 x 1920 would render faster than real time. So I shelled out for the expensive upgrade from basic Vegas 11 Pro to Vegas Pro 13 Suite. But after a few new version builds and many Win10 upgrades, and now the aquisition of Vegas by MAGIX, the ability to turn on GPU acceleration simply absent. The only selection available now is "OFF".

This is hugely disappointing because now I have to put up with much poorer previews, and renders take 3X+ longer because Sony would not fix the problem. To put it simply, I did not get what I paid for and it's been enough of a handicap that I'm forcing myself to learn to use Adobe Premiere because previews are much better and renders are accelerated as they should be.

Will MAGIX work hard keep it's long time users happy? Many of us are understandably worried.

Do you have an oboard GPU too? I am not sure of your full system spec. If so, try to set the discrete gard as your primary.

While the GTX970 should work to a certain extend, it was in my opinion the wrong card to start with. Nvidia has neglected OpenCL in favor of their propritary CUDA. Vegas, in particular preview with FX processing, is OpenCL oriented for which AMD cards are better suited. We dont know if Magix will change that, hopefully Semptember will tell.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

BradfordWest wrote on 8/25/2016, 1:02 PM

Tried that too Donald... as well as rolling back the driver to several out of date versions. Updating to the latest driver at one time seemed to be a universal fix, but in this case every driver release in the past year hasn't touched the problem and one version of the driver that did work as of late last year doesn't work now either. I also tried not installing the GeForce Experience software in case that was the culprit. Still no fix. I'd love to be able to afford to install a GTX 1080 since there have been several happy reports about it, but that'll have to wait. 

I'd be happy to Beta Test VP14 to help make sure this problem is eliminated in the future. There are so many GTX970 cards out there that GPU acceleration works fine with on other editing platforms, it'd be a pity if it's not eventually supported by VP.

BradfordWest wrote on 8/25/2016, 1:27 PM

Do you have an oboard GPU too? I am not sure of your full system spec. If so, try to set the discrete gard as your primary.

While the GTX970 should work to a certain extend, it was in my opinion the wrong card to start with. Nvidia has neglected OpenCL in favor of their propritary CUDA. Vegas, in particular preview with FX processing, is OpenCL oriented for which AMD cards are better suited. We dont know if Magix will change that, hopefully Semptember will tell.

I've tried with the onboard both enabled and disabled and the GTX is set as primary in the UEFI/BIOS. I've become aware that VP is friendlier with OpenCL and that's understandable, but with Nvidia moving foward with CUDA and Tesla development, avidly supporting that branch of cards (no pun intended), would seem to be a sensible priority. Sadly with so many options, it's hard to pinpoint where the fault lies... with Vegas? With Microsoft? With Nvidia? Even if CUDA is proprietary, Nvidia has developed such a huge user base that supporting it should be a given.

OldSmoke wrote on 8/25/2016, 1:51 PM

Nvidia has developed such a huge user base that supporting it should be a given.

I would think that Vegas wasnt profitable enough for Sony the invest and pay royalties to Nvidia; OpenCL is and will be free.

I am wondering if Vegas can see all the memory on your card and if not decides to ignore the card. There is a "OpenCL memory filter" setting in the Internal settings of Vegas. Press the SHIFT key while opening the "Preferences" menu, this will enable the "Internal" tab. At the bottom there is a field where you can key in "opencl memory" and it will show all entries related to it. The default value is 384 and I would try reducing it or even set to 0. What brand is your card?

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Stiven wrote on 8/25/2016, 3:21 PM

Most of the videos I render using Mainconcept codec, and what I notice, performance using CUDE / OpenCL / CPU is same on my system. This is on both my PC, All intel, one is on GTX780ti second is using 980ti Nvidia GPU. I really get fellling that Sony Vegas is not using GPU at all when I render my videos. I'm waiting to see my old Geforce GTX460 gpu back on the system, to check out is it true that Sony Vegas only works with NVidia >560 GPU's.

Kind a wish I can see better and improved GPU usage, since sony vegas does not use my GPU at all when i check HW monitor. but CPU is always 85+%

OldSmoke wrote on 8/25/2016, 3:31 PM

I did a video in 2013 when I still had my two GTX570 and VP12 installed. It clearly shows that Vegas uses even both GPUs and can render videos to MC AVC very fast.

Currently Vegas uses CUDA only for MC AVC rendering and only supports GPUs up to GTX580. This has been discussed to death in old forum, too bad the search fucntions isn't working yet.

 

Somehow the video doesnt play

Last changed by OldSmoke on 8/25/2016, 3:44 PM, changed a total of 7 times.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

vkmast wrote on 8/25/2016, 3:34 PM

You can search old forums here http://forum-archive.magix.info/search.asp

The link to archives is in News, Messages, Welcome... thread.

The text refers to only audio forums, but it seems they are all there.

Btw, the video plays now here.

Stiven wrote on 8/25/2016, 3:42 PM

Well now when we confirm this, I wish someone from Magix come here and say to us we will have / or not have latest Nvidia GPU supported. I would even pay 200$ for upgrade from 13 -> 14 with only that change and nothing else... Else I don't see the point of upgrade if HW acceleration isn't improved at all. Sony Vegas was selling lies with performance upgrades... Hope Magix won't follow that path and do something about it.

NormanPCN wrote on 8/25/2016, 3:58 PM

The other thing to remember about Vegas and GPU use is that there are two independent items. The Vegas video engine and "render as", file encoding.  The engine uses OpenCL and is always used. Playback and "render as". When you do a "render as" you are encoding a file. The video engine is used normally and then the frames are sent to the file encoder. Both the GPU uses have their own independent options to control ON/OFF.

I don't think Mainconcept will update the shader based GPU encoders as used in Vegas since it seems the market has moved to fully hardware fixed function AVC and HEVC encoders. Of these Vegas only supports Quicksync via Sony AVC.

GPU file encoding can be fast but the quality is not as good. At high bitrates you can't really see the diffs so it all depends on your needs.

NickHope wrote on 8/26/2016, 12:56 AM

Places to enable/disable GPU-acceleration in Vegas Pro 13:

1. Preferences > Video > GPU acceleration of video processing:

Having tried it with both AMD HD 6970 and Nvidia GTX-580, I now leave it off 😉

2. Preferences > Preview Device > Optimize GPU display performance:

This one is a bit mysterious to me, and I didn't find benefit from switching it on, so I leave it off.

3. Render As > Sony AVC/MVC > Customize Template > Encode mode:

Options include Intel Quick Sync. No CUDA.

4. Render As > Main concept AVC/AAC > Customize Template > Encode mode:

Options include OpenCL and CUDA.

I thought there were now some other GPU-accelerated Sony render formats but I can't find them. Did I imagine this?

NormanPCN wrote on 8/26/2016, 10:58 AM

AFAIK Only MC AVC and Sony AVC have file encoding ops on the GPU. It is the only two that Sony ever acknowledged used GPU for file encoding on web topics I have read.

When you select "use GPU if avaialble" on Sony AVC it uses OpenCL if you have an AMD GPU and CUDA on Nvidia. Nothing in the UI tells you this but when you did into the DLL's you can find this out. As previouslty stated, Sony AVC does not do much on the GPU. I think it only accelerates the motion estimation search on the GPU. The rest of the file encoding function being done on CPU.

File encoding is just not a good fit for GPU compute. By that I mean massively parallel compute. Video processing is an excellent fit to massively parallel compute. This being effects and compositing. This is what the Sony Red Car demo project was all about. Throwing effects and composting at you.

peterh337 wrote on 8/26/2016, 2:02 PM

I wish they fixed GPU acceleration at all. I have a GTX750 2GB Kalm (the fastest fanless video card) and while MSP11 and 12 (winXP-32 and win7-64 respectively work fine with default settings (use GPU if available) Pro 13 (win7-64) just crashes in various ways during render. The only way to use Pro 13 is to disable GPU in the main Preferences. The card supports CUDA but Pro 13 doesn't work with it. I am getting render speeds around 1/5 to 1/10 of real time. Main Concept AVC 1080P.

Wolfgang S. wrote on 8/26/2016, 3:49 PM

I agree with Nick - I never found the GPU support great for rendering. But my R9 390X supports effects in the timeline and the playback behaviour in a great way, and that is why I use it.

I have also a Quadro K4200 in my system, and with the latest driver it seems to work fine also for Win10. But I tend to use the R9 390X as standard. For Win10 my impression is that one may have to make sure that you have installed the latest driver for the nvidia cards.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

Wolfgang S. wrote on 8/26/2016, 3:49 PM

I agree with Nick - I never found the GPU support great for rendering. But my R9 390X supports effects in the timeline and the playback behaviour in a great way, and that is why I use it.

I have also a Quadro K4200 in my system, and with the latest driver it seems to work fine also for Win10. But I tend to use the R9 390X as standard. For Win10 my impression is that one may have to make sure that you have installed the latest driver for the nvidia cards.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

NigelO wrote on 8/26/2016, 11:30 PM

The OpenCL/CUDA implementation is Vegas is not good. It is recommended you get the fastest processor you can afford, typically an i7 or a Xeon CPU. I would avoid i5.

peterh337 wrote on 8/27/2016, 12:46 AM

I already have - i7-970 3GHz 24GB RAM.

megabit wrote on 8/27/2016, 1:22 AM

As I wrote in my own thread, and commnented in another one - my installation can make great use of my GTX 1080 CPU. especially for timeline accelration. As far as rendering - with Sony XAVC codec is simply blastingly fast as well (with othe codes yielding differing results, but always faster than renders with CPU-only settings). No reaon to complain wahtsoever!

Piotr

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)

peterh337 wrote on 8/27/2016, 2:14 AM

What sort of speedup do you get on rendering, using GPU over CPU?

paul_w wrote on 8/27/2016, 2:41 AM

What sort of speedup do you get on rendering, using GPU over CPU?


That really depends on the ratio of CPU to GPU power and will vary from system to system. But as an example my i7 and GTX570 gives a render speed gain around x5 times.

peterh337 wrote on 8/27/2016, 3:07 AM

A 5x gain is astonishing. I have heard of Final Cut Pro rendering in real time. I never got Vegas better than 1/3 even on the simplest jobs - 1080P 50FPS. I cannot understand why Sony didn't put more effort into this aspect because one is talking hours.

paul_w wrote on 8/27/2016, 3:16 AM

To clarify, thats a x5 gain comparing CPU render times to GPU render times. Not to be confused with real time playback or render times compared to real time.

For HD 1080, i see a 1:1 speed compared to realtime, in other words GPU renders roughly the same speed as it plays.. It varies, obviously the more FX you place on the timeline, the slower it gets.. For CPU renders, its something like 5 times slower on my machine. Hope that clearer.