Comments

JohnnyRoy wrote on 4/20/2014, 7:07 AM
> "I've been told that starting with SVP-13, Vegas will no longer be able to run Vegas Extensions that were written using anything other than Microsoft .Net Framework v4.0."

Not true!

Most of my VASST Extensions are written for .Net 2.0 for maximum compatibility going back to Vegas Pro 8.0 and they run perfectly fine in Vegas Pro 13.0. I didn't have to change anything to make them work.

~jr

John Rofrano
Sundance Media Group / VASST
www.vasst.com
www.fasstapps.com
videoITguy wrote on 4/20/2014, 8:59 AM
Yes, established that Net 2.0 is the basis for many scripts out there. BUT is it a problem for VegasPro13 release locating scripts running in an unusual folder location with a permissions issue if running the PC in users accounts mode ?

OR installing VegasPro13 in Win 8.1 OS ?

OR some combination of the above?
JohnnyRoy wrote on 4/20/2014, 11:34 AM
> "BUT is it a problem for VegasPro13 release locating scripts running in an unusual folder location with a permissions issue if running the PC in users accounts mode ?"

I'm not sure what you mean by "unusual folder location". Vegas only looks in a few certain places and that's where you need to put them. Some people still place their scripts under the Program Files folder which they should have stopped doing with Windows Vista. That was a Windows XP thing that no one should be doing anymore.

> "OR installing VegasPro13 in Win 8.1 OS ?"

All of the VASST Extensions work fine in Windows 8.1 with Vegas Pro 13.0 and almost all of them are compiled for .Net 2.0 with no changes required to work under Vegas Pro 13.0.

~jr