Trial Vpro 13 on Magix

Cornico wrote on 8/26/2016, 6:21 PM

When I was trying this trial the problems with older VASST and SeMW extensions became clear to me.
Installing as a "new" version over the old 453 all my VASST and SeMW extensions were gone and didn't came back after reïnstalling them.

For me personal a reason to not upgrade to version 14 unless there will be a solution as free updates or something like that for those extensions I  use a lot.😟

Comments

vkmast wrote on 8/26/2016, 7:04 PM

Good to know, thanks.

JohnnyRoy wrote on 8/27/2016, 4:56 PM

MAGIX has been made aware of this and is looking into a fix. They promised nothing would change until Vegas Pro 14 and then they changed Vegas Pro 13! (ugh!)

I would suggest that you stay on the Sony versions of Vegas Pro 13 until all of this gets sorted out.

~jr

winrockpost wrote on 8/27/2016, 6:37 PM

+1 Johnny..why update 13 when there are no changes or bug fixes ,,,just  taking sony name out  and replacing with magix...not that simple a process but ya know what I mean.

JohnnyRoy wrote on 8/27/2016, 8:10 PM

+1 Johnny..why update 13 when there are no changes or bug fixes ,,,just  taking sony name out  and replacing with magix...not that simple a process but ya know what I mean.

Yea, they got a little too aggressive with renaming everything. What they did was also update where Vegas Pro 13 stores it's extensions becasue it had Sony in the path and by doing that, it no longer looks in the old location where all of the current command extensions exist. I believe they are going to change 13 to look in both locations as the fix. In the mean time, I recommend that everyone stay on the last Sony build that actually works.

~jr

Grazie wrote on 8/28/2016, 1:31 AM

I'm reading download, install and build number references that indicate issues during this transfer period. I am now not installing the VP13 543 (re-branding) Build. I have it downloaded, but will desist and suppress my natural urge to be attracted by the first thing.

SphinxRa40 wrote on 8/28/2016, 6:04 AM

Good to know...thanks for letting us know, downloaded 543 to but was already to scared it will screw up VASST extensions, now deleted 543, and hope when VP14 comes out it will be fix, if not..no VP14 for me to

VEGAS_EricD wrote on 8/29/2016, 10:09 AM

In previous updates the application extensions folder was located in:
C:\Users\**username**\AppData\Local\Sony\Vegas Pro\13.0
**username** is the name of your user profile on the system.

In the current update the application extensions folder is located in:
C:\Users\**username**\AppData\Local\Vegas\Vegas Pro\13.0
**username** is the name of your user profile on the system.

If you copy the contents of the application extensions folder in the former path to the latter path you should be able to use them in the current rebranded update.

An update will be released in the near future which looks into both paths for extensions

JohnnyRoy wrote on 8/29/2016, 11:46 AM

If you copy the contents of the application extensions folder in the former path to the latter path you should be able to use them in the current rebranded update.

Customers of VASST products are strongly advised NOT to follow this advice!!!

Copying folders will confuse our uninstaller and cause problems when applying future updates!

VASST customers should stay on the old version of Sony Vegas Pro 13 until a formal fix has been issued by MAGIX for this problem.

~jr

John Rofrano
VASST Support

Marco. wrote on 8/29/2016, 12:22 PM

Eric, are you sure the new path is

C:\Users\**username**\AppData\Local\Vegas\Vegas Pro\13.0

I copied the folder "Application Extensions" to

C:\Users\**username**\AppData\Local\Vegas Pro\13.0

because at C:\Users\**username**\AppData\Local\Vegas\ there is no folder "Vegas Pro" (nor subfolder "13.0"). This works.

Marco