GPU acceleration Issues

[John Rofrano]

[David Norman] “Anyone else seeing this type of issue?”

Unfortunately yes. 🙁 Sometimes I have to disable GPU acceleration to get my projects to render correctly. It really defeats the whole purpose of having a GPU and I’ve got an $800 Quadro 4000 so when I have to turn it off, it really pisses me off. Luckily it only happens on certain projects and not all but it does mean that you have to sit and watch every frame of every render looking for problems which is a big waste of time! Vegas Pro was never like that before. This whole GPU thing is a mess.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Roger Bansemer]

I too purchased a new video card to take advantage of the GPU and I seldom have trouble rendering to an MXF format. Only once in a while does it hang up.
I think I may be one of the lucky ones.

Roger Bansemer – PaintingAndTravel.com

[David Norman]

yeah, I think when video editors and other professional software started supporting consumer GPUs from different brands it made it harder for them to get good results.

just too many drivers and hardware combinations.

I would bet if they went back to supporting the pro level cards only the same issues would not be happening….

but they are way expensive so then less people would have the chance to use them

Sony Vegas Movie Studio
Intel i7 3770, 32gb, 2xRAID0 Intel 240gb SSD, 2x2TB WD Green, 3×23″ Samsung LCDs
http://www.SelmaBearsSoccer.com

[Norman Black]

>>just too many drivers and hardware combinations.
>>
>>I would bet if they went back to supporting the pro level cards >>only the same issues would not be happening….

Vegas uses OpenCL for GPU support. Driver and hardware independent.
The AVC encoders use OpenCL or CUDA depending. Driver and hardware independent. CUDA being Nvidia specific but hardware independent.

Assuming Vegas code is bug free, a very big assumption, the independent API means Vegas has no issue and all driver/hardware combinations are the problems of the driver developers and there is nothing Vegas can do about it. In other words there is nothing for Vegas to “support”. The point being that the OpenCL/CUDA compilers, and driver developers need to get their act together.

Valid OpenCL code is valid regardless of driver or hardware. This is the whole reason for encapsulation layers so you do not have to worry about “supporting” hardware.

“pro level” cards have used the same actual GPU core chips as the consumer cards, and therefore the drivers are substantially the same and as far as Vegas is concerned they are identical. OpenCL is OpenCL no matter what is running underneath. You can even run OpenCL on the CPU but Vegas does not allow that. That could be a useful differential diagnosis tool for GPU drivers issues verses a possible Vegas code bug.

The video driver guys are always trying to make their drivers faster and they tend to break things that were once working. AMD for example recently broke something in OpenGL (different than OpenCL, not a typo). This affects the NewBlue Titler. 13.4 broke this. 13.1 and earlier is fine.