One of the new function of build 543 - Project archiving  - 

That feature is and has been in Vegas 13. It was one of the new featgures in V13. I've never cared to use it.

read somewhere it's just rebranding release?

From MAGIX_Eric_D further up in this thread:

"This is correct.  As we are still making Vegas Pro 13 available, that program version was rebranded.  The new features are on the way, in the September release of Vegas Pro 14."

Could someone who is running the new MAGIX Vegas Pro 13.0 (version 543 or later) please post a screen grab of the "Plug-in Chooser - Video Event FX" window with all FX displayed? I would like to compare with Sony Vegas Pro 13.0 (build 453), in particular the FX name changes from "Sony Whatever". Plugin authors should find this useful. To clarify what I mean, my window in build 453 is shown below (obviously I have a lot of 3rd party FX on display here besides the bundled ones).

Yes, export to Vegas project archive is broken in build 543.

Marco

This attitude is a little worrying

VisionColor LUT plugin for SV not working in this relese! 

Nick - all those "Sonyxxx" plugins are now called VEGASxxx...

Piotr

Could someone who is running the new MAGIX Vegas Pro 13.0 (version 543 or later) please post a screen grab of the "Plug-in Chooser - Video Event FX" window with all FX displayed? I would like to compare with Sony Vegas Pro 13.0 (build 453), in particular the FX name changes from "Sony Whatever". Plugin authors should find this useful. To clarify what I mean, my window in build 453 is shown below (obviously I have a lot of 3rd party FX on display here besides the bundled ones).

 

This attitude is a little worrying

VisionColor LUT plugin for SV not working in this relese! 

 

 

Nick Hope, here's my Plug-in chooser... as Piotr said, all the Sony*** named files are now simply named VEGAS***, there don't appear to be any additions or subtractions.

grovercluver -- I don't have the VisionColor LUT plug-in but my HitFilm LUT plug-in issues the error "Invalid file format"... I don't know if there is a connection... but maybe the developers can do something with this info.

Nick Hope, here's my Plug-in chooser... as Piotr said, all the Sony*** named files are now simply named VEGAS***, there don't appear to be any additions or subtractions.

This changing of plug-in names has broken most of our VASST tools that deal with FX. We ship a lot of presets and load FX by name in our scripting tools and all of those names have now changed as a result.

VASST customers are advised to stay on the Sony version of Vegas Pro 13. We do not support the MAGIX Vegas Pro 13 version with renamed plug-in names.

So one answer to the question:

Q. Whats new in Magix Vegas Pro 13.0 Build 543 ?

A. It doesn't support VASST command extensions or script plug-ins anymore. 😞

We are working on supporting MAGIX Vegas Pro 14 as an upgrade.

~jr

John Rofrano
VASST Support

Thank you Piotr & BradfordWest.

Let's hope MAGIX or someone finds a way to do some internal remapping when plugins and projects are read.

With the New Blue TitlerPro 1 the program VPro 13 build 543 crashes immediately by clicking on that titler in Media Generator

TitlerPro 4 crashes for me too. Sent an error report.

I downloaded DaVinci Resolve yesterday to see what it offers and discovered that it appears to be simpatico with the GTX970/CUDA and renders about 3.5 faster than VEGAS13 for my typical purpose which is to downscale GoPro 4 Black footage to YouTube/Vimeo format. It also appears to render to 4K in near real time.

For Vegasaur users: In version 2.7 added support for MAGIX build 543

So fast altarvic. Thanks a lot!

I'm curious, are all the 6 Sony render codecs still branded "Sony"?

Great!

As far as I know, Excalibur should continue to work fine in the newest build.

MAGIX has been working with VASST on the plug-in problems and has notified me that a new build 545 of Vegas Pro 13 is available for download which fixes all of the missing Command Extensions and Video FX naming problems. 

All of the VASST plug-ins seem to be working now and I’m happy to announce that we fully support MAGIX Vegas Pro 13 Build 545 or greater.

~jr

Great! OT maybe, but what's the situation with MAGIX MS Platinum 13?

I also noted that the new build still does NOT fix the ability to enable GPU Acceleration under Tools/Preferences/Video even though I have a nVidia GTX 970 card. The "GPU acceleration of video processing" box only offers the "OFF" option which I find perplexing since it worked under Windows 10 Pro when I first installed it about a year ago, but then at some point it simply stopped working—which seems to be a sore topic with many Vegas 13 users.

I hope you will fix/patch GPU acceleration in version 13 since it was originally advertised as feature which once worked and was a deciding feature for making the expensive upgrade from basic Vegas 11. The mysterious disappearance of acceleration greatly degrades the quality of previews and severely drops render speeds. Adobe Premiere blazes over Vegas on previews and renders with the GTX 970 and has me thinking about dropping Vegas altogether and fully switching to Premiere though I never liked the interface as much.

For what it's worth, my GTS450 does appear in the list for acceleration in "Options, Preference, Video" and I can and do select it for GPU acceleration. Maybe try winding back your NVIDIA driver?

MAGIX has been working with VASST on the plug-in problems and has notified me that a new build 545 of Vegas Pro 13 is available for download which fixes all of the missing Command Extensions and Video FX naming problems. 

All of the VASST plug-ins seem to be working now and I’m happy to announce that we fully support MAGIX Vegas Pro 13 Build 545 or greater.

~jr

Thanks for the confirmation John. So I guess my Ultimate S Pro 4.1 should work without any much issue?

This should conform the compatibility for the next Vegas Pro 14.

So I guess my Ultimate S Pro 4.1 should work without any much issue?

Yes, I tested Ultimate S Pro 4.1 and it appear to be working correctly with MAGIX Vegas Pro 13.0.

This should conform the compatibility for the next Vegas Pro 14.

No. MAGIX has already stated that they will be changing the Script API namespace and ALL SCRIPTS will be incompatable with MAGIX Vegas Pro 14. We (VASST) will need to make programming changes in order to get things working again. I don't have an estimate yet of how long that will take but things will definitely not just keep working.

~jr

Any update on the availability of Ultimate S Pro 4.1 for Vegas 14?

Any update on the availability of Ultimate S Pro 4.1 for Vegas 14?

We have been working on it. Unfortunately this move by MAGIX has forced us to upgrade the tools in our development environment and some of our old tools did not work with the new ones so it has been a huge (and frustrating) time waster trying to figure out the right combination to make everything work. I think we have this all sorted out now so we can start planning to roll out the updates. 

We hope to have all of the updates completed by the new year. Hopefully many can be completed before Christmas. We do plan to roll out the updates as they are ready. Ultimate S Pro is next on the list so it should be the first one to be released in the coming weeks. ;-)

~jr