I have recently upgraded from Sony Vegas Pro13 to Pro 14.
I use VASST StillMotion (v1) often and do not want to uninstall Vegas Pro 13 before I am certain StillMotion will work in Pro14? How do I get StillMotion to work with Pro 14? (is there an update?)
Both S V 13 & 14 are installed in on my computer. Thank you. Nico
[Nico van Rensburg]"I use VASST StillMotion (v1) often and do not want to uninstall Vegas Pro 13 before I am certain StillMotion will work in Pro14? How do I get StillMotion to work with Pro 14? (is there an update?)"
Do not uninstall Vegas Pro 13 because StillMotion will NOT work in Vegas Pro 14. Due to changes that MAGIX has made to the Script API, none of the current VASST plug-ins work with MAGIX Vegas Pro 14.0.
We are working on making the necessary changes to make our plug-ins compatible but we do not have a date for the completion of that work yet. It is not as simple as MAGIX claims. We recommend that you use Vegas Pro 13.0 if you need to use our plug-ins until they can be updated.
Unfortunately, there is no workaround. MAGIX chose to make Vegas Pro 14 incompatible. Now we are faced with the mess of fixing it. ? All I can advise you at this time is to stay with Vegas Pro 13 for now.
[Steve Rhoden]"John, MAGIX chose to make Vegas Pro 14 incompatible or was it unavoidable due to legal reasons of the change of ownership where the namesake "Sony" had to be stripped from everything entirely?"
Rebranding something is one thing. Breaking backward compatibility of an API that no one will see except developers is, IMHO, going too far. Now everyones favorite plug-ins stopped working because of it and developers must bear the burden of fixing it. It was a bad idea regardless of who's idea it was.
[Steve Rhoden]"I know you have a lot of work ahead of you to update all those tools for Vegas 14 compatibility, but hope its accomplished soon for the many users of this new Vegas Pro...."
I'll be honest with you, I still don't have a way forward. This change broke all of my development tools because it required upgrades to .net 4.0 that some of my tools are not compatible with. So I'm not sure how I'm going to solve this dilemma.
Oh my goodness!
Breaking the backward compatibility of Vegas API is a big unnecessary NO NO on the part of Magix.
That is a very stupid thing to do while rebranding Vegas, especially given the delicacy of it at this transitional stage.
Well... in fairness to MAGIX, if I was a Windows developer and kept my tools updated each year by investing in new ones, everything would have been compatible. I don't even own a Windows computer anymore (I'm on the Mac now). My Windows development tools are from 2008 but they still worked with Vegas Pro 13. It is Vegas Pro 14's use of .Net 4.0 that broke the tooling. My tools only support up to .Net 3.0. ? So it wasn't anything MAGIX did that is causing my problem. It is more of a Microsoft tooling issue with .Net Framework.