Vegas 12 Pro and rendering NewBlue Effects

Merv Keys wrote on 11/22/2012, 2:13 PM
Before I start - AMD Quad Core 3.1Ghz running Windows 7 64 bit and AMD HD 6700.

I have been in contact with NewBlue in relation to a problem peculiar to Vegas 12 Pro. It does nort occur in Vegas 11 Pro.
The example of this is as follows:
On the timeline I have three events on three separate tracks. On track 1 is an AVCHD event with NewBlue Picture in Picture OFX applied. On track 2 and immediately below the event on track 1 is another event with the same NewBlue effect applied. Below that on track 3 is an MP4 event for the background for the PIPS above. It has no effect applied. I am able to preview the event without any problem.
However, when I try to render it as an Main Concept MPEG2 (DVDA Widescreen) file, the rendering will stop. Each time it will stop at somewhere different in the rendering i.e. 10%, 31%, 50% etc, etc.
If I replace the NewBlue OFX with a non OFX effect it will make no difference it will still stall when GPU acceleration is on. When I turn off GPU acceleration both NB effects will render without any problem.
I have tried other NB effects (Non OFXand OFX) and have similar problems.
However when I replicate the above circumstances in Vegas 11 Pro, whether GPU Acceleration is on our not, the events render without any problem. The events also render without any problem using Main Concept MP4 template in both Vegas 11 & 12.
NewBlue suggested reducing dynamic RAM preview - no change - it is already down to 200MB.
Also suggested reducing number of threads - no change - already down to 1.
They suggested updating AMD/ATI drivers - no change - updated to latest AMD Catalyst 12.10.
The last email I got from them suggested that OpenCL and OpenGL were conflicting - qoute -
"Vegas GPU Acceleration uses OpenCL. NewBlue GPU Acceleration uses OpenGL. So, if both are accelerated, you're using both at the same time. I'm not sure what GPU Acceleration rendering to MPEG2 uses."
If I apply Pan/Crop to make PIPS in the events and apply a Sony effect to mimic the type of effect I get from the NB effect, it will render in 12 no problem (GPU on or off).
Now I dont know where I stand and have had to abandon Vegas 12 Pro and revert back to Vegas 11. Much of my work( I edit on a daily basis mainly weddings) makes use of NewBlue effects. I reiterate, that these problems do not exist in 11, so Vegas 12 was purchased needlessly.
The other point to make is that in Vegas 12 Pro, large projects take an absolute age to load - a 1 hour project with a lot of transitions and colour correction can take about 3 minutes to load. In Vegas 11 Pro it only takes about 35 secs. Why is this?

Is anybody else experiencing these problems?

Thank you
Mervyn Keys

Comments

videoITguy wrote on 11/22/2012, 2:28 PM
Most people who experience problems that are unique to VPro11 vis-a-vis VPro12 with GPU switch on/off for a given videocard - Face the following choice:
1) If the problem is simply different for GPU switch on/off
A) You face the solution of likely having to use a different version driver for a given video card. One version driver for Vpro11 work and another version driver for Vpro12
2) If the problem is more about issues with OFX driver function than the GPU switch - then the choice of videocard drivers may not really help in the long run.
Merv Keys wrote on 11/22/2012, 3:03 PM
Thats all very well, but why should there be such a difference between versions of Vegas Pro?
If what NewBlue is saying is correct, that Vegas GPU Acceleration uses OpenCL. NewBlue GPU Acceleration uses OpenGL then who is at fault - NB or SV?
I dont want to have to turn off GPU acceleration every time I want to render in MPEG2. Thats not why I bought Vegas 12.
As regards the different version of graphic driver, it would then be a case of trial and error to see which one works with both?
videoITguy wrote on 11/22/2012, 8:26 PM
Merv - the answer to case of trial and ?error?

YES