[Mark Barton]

I usually use the BETA drivers, because I think it is more that they are waiting for Microsoft to get the logo that they have been certified by them. It is my understanding that the company has to pay Microsoft for every time they rev the driver to get the certified logo. I really doubt that Microsoft does any real testing, so I trust the BETA version of the drivers as incremental fixes for the driver that got the logo. What brand NVidia card did you end up with? I have the EVGA version and they have a utility call EVGA Precision X that displays the GPU utilization. Usually Vegas never pushes mine past 25% utilization, but when I run Folding at Home (application that leverages the GPU to help researchers compute protein folding simulations) it pushes it to 99% utilization. Another thing to watch are the GDI objects being used by the Vegas120.exe process in Task Manager as shown below:

In Task Manager, you can add that column by choosing Select Columns from the View menu.

There is a limit on the number of GDI Objects and sometimes I have seen Vegas get into the thousands. Seems to be if I work with a lot of OFX dialogs. But I would not expect you to reach the limit within 10 minutes of work.

[Mark Barton]

I would try with the 310.54 drivers from Nov 12th 2012. I’m using these drivers with the GTX 570 card. I have both Vegas Pro 11 and 12, so it is not a generic problem with upgrading to 12.

[Mark Barton]

John,

That was exactly the type of comparison information I had been looking for on the website. Since there was no trial version and the video of the FASST App glosses over things very quickly, I was concerned I would be throwing away money if I already had Production Assistant 2. Could you comment if Production Assistant 2 will be replaced with a suite of FASST Apps in the future?

Thanks,

Mark

[Mark Barton]

I wonder if it was related to this change:

2.0 What’s New
Notable fixes/changes in version 12.0 (Build 394)
File IO

Fixed a crash importing variable frame rate H.264 MP4 clips from After Effects (CS6).

You should open a ticket to Sony.

[Mark Barton]

build 700 is the latest 32bit version of SVP 11 and build 701 is the latest 64bit version of SVP 11.

[Mark Barton]

[Mark Krueger] “In SVP12 I render out the video for bluray. In Architect I set it up to burn a BR. In Architect it renders it again, and I have my BR.”

I have noticed this too. Why does Architect need to render again if we choose a BR template in SVP12?

[Mark Barton]

In the View menu under extensions, do you see them there? On mine, I just had to select Production Assistant 2.0 from this menu to get it to display in my normal view again.

[Mark Barton]

I would suspect bad RAM if it was running fine before. First try re-seating the memory modules in the board again. You also may want to check the virtual memory settings to see if they were updated to match the additional memory you added. Usually that is based on the memory in the system when Windows is installed.

As you see mine is set to 12GB based on the total RAM I have. If that does not work, try running a memory test overnight to verify that the RAM is good.

[Mark Barton]

Was one of the things you tried a macro mode or adapter? I was curious if I could do something like this with the Panasonic TM900, so I tried and got the shallow depth of field if I set it to the macro mode. I’m going to give it a try this weekend.

[Mark Barton]

Just curious why you are not running build 701 (64bit version) since you mentioned you are running Windows 7 64bit. Are you using 32bit plugins and need build 700?