Namespace change coming for VEGAS Pro 14

GaryRebholz wrote on 7/19/2016, 2:28 PM
Hi everyone,

Prompted by a discussion on the Vegas Pro-Video forum, I wanted to give you all a little heads-up warning about a change for scripting in the upcoming VEGAS Pro 14.

Unfortunately, legal considerations will force us to change the scripting namespace and thus all existing scripts will need to be modified in order to work inside VEGAS Pro 14. It will be a minor, but critical change. We're still working out the details, but once we have them, we will tell you exactly what you'll need to change in your scripts.


Gary James wrote on 7/20/2016, 8:23 AM
This may let the corporate attorneys sleep better at night, but it will be a disaster for Vegas Pro users. Vegas scripting has been around for more than a decade. Vegas Extension Add-in's have been around since version 8.0. There are probably thousands of compiled script DLL's that will become obsolete the instant that VP 14 is released; many that were produced by people or companies that are no longer involved maintaining obsolete code.

I strongly suggest that someone sit down with the lawyers that dreamed up this hair brained scenario, and let them know just how bad an idea this really is. There's nothing quite like a company having to explain to all the long time users of their new software product acquisition, how they screwed up all their customers favorite scripts and Extensions when they took ownership of the product, so they could satisfy some legal technicalities. Yeah, that will go over really big.
Grazie wrote on 7/20/2016, 12:18 PM
Lawyers? I'd suggest it's far too late for that.

videoITguy wrote on 7/20/2016, 1:17 PM
Gary's comment is right on.

Essentially the real value of VegasPro as a software progression schema has a very high value in the scripting language that was adopted. The same could be said for DVDArchitectPro - but that particular software suffered greatly because there was very little deployment of the workings.

So back to square one, we are essentially looking at VegasPro being gutted by Magix acquisition and henceforth probably not be a player.

I don't understand how the people who are supposed to be looking at these matters, just seem to overlook the issues. Pure absolutely pure.. incompetence!
SFX Group wrote on 7/20/2016, 11:57 PM
This whole buying doesnt sit well with me at all, what with all the "pay for v13 to get v14 free" sounds alot like "get Windows 10 free [however all your printers and cameras wont work with it, BUT IT WAS FREE]".

I still have a box v13 thats never been installed (waiting on deploying the new server / PC), and i dont like there new "upgrade" thing, works for a year, if you need to re-install you need to pay AGAIN.

I am sure with this scripting issue alot will be looking at new software, unless things like scripting is resolved.

I use Vegas as just a video editing and production, i dont use scripting (that i know of, unless some plugins use it)....

Seb M wrote on 7/23/2016, 6:18 AM
Poor form - just get permission from whoever is needed to continue to use the same namespace. There are hundreds of scripts out there. In one fell swoop you'll lose a chunk of the key customer's reason for loyalty. Vegas is three years behind the competition.
GaryRebholz wrote on 7/28/2016, 4:21 PM
Obviously, this has significant impact which is why I've brought it up early. I have not lightly made the decision to proceed in this manner. The naming changes are not optional. Addressing them with a change to VEGAS Pro code comes with risk, not the least of which is that it would take developers off of working on desperately needed stability and performance issues that affect all users.

I will follow up soon with more details about exactly what will be happening so that you can formulate your solution plans. You who use simple one-off scripts will be pleased to find out just how easily you can fix this. As has been correctly pointed out in this thread (or the one in the main VEGAS Video forum), those of you who use compiled extensions have a more difficult problem to solve. I believe this community will pull together to help one another solve it.
Gary James wrote on 7/28/2016, 5:54 PM
I've already seen many people (among the very small number who are aware of this disastrous engineering decision) who have said this absolutely kills any chance of them upgrading to Vegas 14 and beyond from earlier versions. Many people simply can not use a Version of Vegas that abandons and tells them it's up to them to solve the cataclysmic impact and potential financial burden that immediate obsolescence of their most powerful 3rd party Scripts and Extensions will bring.

If you look back at the roll out of Vegas v13, you should remember the stink that was caused when v13 did not run all legacy scripts and extensions in its first few releases. What you're talking about is v14 NEVER running any of these.
videoITguy wrote on 7/29/2016, 10:06 AM
for GaryRebholz : when you say the "naming space is not going to be an optional consideration" - I think what you meant to say was that "the change was not affordable by Magix and further that those legal rights that remain held are with the intent to kill further exploration of the VegasPro line as a progressive software build. This would appear that whoever held the cards knew exactly what they wanted and Magix acquisition team had no idea. Very poor negotiation form!

Just again to reflect - for the salad days of DVD Architect Pro in its prime - the inclusion of scripting options was a huge bonus that without support by SCS -just fell on its face. Now even though the product is worthwhile and would be worth more if the internal scripting were further enhanced and supported - there is no marketplace left. Such issues can be considered timely - the Magix acquisition team is missing the boat entirely.
set wrote on 8/5/2016, 3:55 AM
As a user, looking forward for more detailed information regarding to script change requirements so we can ensure our owned-scripts can still run.

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city


System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB


System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD


* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

GaryRebholz wrote on 8/5/2016, 11:52 AM
Here's more information on what will happen:

The scripting namespace for VEGAS Pro 14 changes from “Sony” to “ScriptPortal”. In your scripts, any occurrence of items like “Sony.Vegas” or “Sony.MediaSoftware” must be changed to “ScriptPortal.Vegas” and “ScriptPortal.MediaSoftware”. We chose this namespace (“ScriptPortal”) in order to remove any company branding and thus avoid this problem in the future.

For stand-alone scripts (not a compiled extension), you can easily make this change yourself even without any programming knowledge. Open the script with Notepad (always work on a copy of the script in case you make a mistake) and replace “Sony” with “ScriptPortal”. Save the script with a new filename so that you still have a copy that works in pre-14 versions of VEGAS Pro.

As has been pointed out, if you use extensions (like JohnnyRoy's VASST tools or jetdv's Excalibur and Montage Magic) instead of simple scripts, you are dependent upon the script developer to make these changes and recompile the extension.

Next, any scripts that use Sony branded plugins will also need to change the name from Sony to VEGAS. For example, if a script currently uses "Sony Sharpen", you need to change that script to "VEGAS Sharpen". Again, you can easily do this yourself in Notepad (always work on a copy of the script in case you make a mistake) unless it is a compiled extension in which case the original developer must make the change and recompile.
couryhouse wrote on 8/6/2016, 3:34 PM
just knew there would be weirdness with the takeover.
new owner needs to cater to the user.

If you going to come up with some retched change
release a script or program that will automatically convert
all the old scripts to the new namespace.
paul_w wrote on 8/24/2016, 12:04 PM

Dont see a real issue here. Vendors, just recompile your extensions and alter your scripts. Then make them available to clients as v14 versions. Did i miss something? Also, we should be happy to see the back of Sony branding in Vegas after the bad service we got from them. Good riddance i say. Onward and upward!

NickHope wrote on 8/24/2016, 12:39 PM

paul_w, many authors of compiled extensions have "left the building". While some such as Vegasaur will surely update their plugins, others will not want the hassle (especially the authors of free plugins). Others will be difficult to trace.

paul_w wrote on 8/24/2016, 1:02 PM

I agree Nick. Older extensions with lost owners may now become obsolete due to this change. But its not the first time a tool became obsolete due to change. Like Mac Motorola code when they went Intel?. Or 32 bit CPUs when 64 bit only apps like Vegas came out... Maybe its just time to change. Just my opinion of course.. I do understand some would be upset. But i actually see this as progress. hopfully with new extensions, new plugins to replace the old. 10p's worth..

Grazie wrote on 8/24/2016, 1:46 PM

Fred Baumann?

Gary James wrote on 8/24/2016, 2:03 PM

paul_w, so how much money are you willing to spend to pay for each update from each vendor of your favorite Vegas add-ins who now has to create an entirely new version of their program for Vegas v14, and maintain two distinctly different versions of their Vegas extensions and compiled scripts?   After all, there are many thousands of copies of pre Vegas 14 out there with customers who expect to be updated when bug releases or new versions of their favorite extensions and compiled scripts come out. 

paul_w wrote on 8/24/2016, 2:19 PM

It really depends on the level at which you operate. If i were a professional editor and using these add-ins daily, then yes i would invest in the best tools available. If i were just a hobbyist then probably not but then again would it really matter?

Its not an 'entirely different version', no, its a simple edit in source replacing a namespace and re-compile, then package into an installer if needed. I guess an average time for that would be around 10 minutes tops if the toolchain is setup and ready to go. I dont really see much expense in doing this although i do see an opportunity for some companies to abuse it.  Hopefully not.

jetdv wrote on 8/24/2016, 2:33 PM

Gary, I know for Excalibur and Montage Magic, I will release a free Vegas Pro 14 update with no new features. There may, at some point, also be a paid update in the future but it will have more features. And it is likely that future updates will only be 14+. The Excalibur for VP13 I just posted will not work in older versions either because it uses a feature not fount in 12 and older.

jetdv wrote on 8/24/2016, 2:49 PM

Paul, there is more to it than just changing the namespace. How much more will depend on the script. 

paul_w wrote on 8/24/2016, 2:58 PM

Its pretty much 'find and replace' as detailed by GaryRebholz's post above. However, i can't see your source and scripts so you know best. I can only speak from my own experience and this would normally be a trivial task, even for a non experienced programmer. Kudos for the free v14 update though. Hope others follow that.

Chienworks wrote on 8/24/2016, 9:27 PM

Paul_w mentions an automated tool to do the conversion. This is very practical, even for already compiled scripts. Someone who intimately knows the structure of the scripting engines could knock this out in an afternoon. This would take care of the extensions for which the original authors are unwilling or unavailable to make the changes.

It should also be pretty easy to write a script that runs unmodified scripts and does the namespace change on the fly, allowing Vegas 14 to run old scripts as-is without modification. This is pretty straight forward stuff for anyone who has written language interpreters and virtual machines. Another bonus of this approach is that it could be taught to run even the old Sonic Foundry scripts, something the Sony versions couldn't do.

Not the end of the world at all, but it may take some time for these tools to become available.

wwaag wrote on 8/24/2016, 10:18 PM

This is very practical, even for already compiled scripts.

I'm no expert but AFAIK you cannot extract the source code from a compiled script ( *.dll).  Once it's been compiled as a script extension, you can not go back to the original source.  If I'm wrong, please someone correct me, and tell me how this can be done. 



Last changed by wwaag on 8/24/2016, 10:19 PM, changed a total of 1 times.

AKA the HappyOtter at System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Chienworks wrote on 8/24/2016, 10:34 PM

Don't really need to update the code, just the name space table which will be a small section of data within the .DLL file. Inside the code itself will merely be index numbers into the name table which won't need changing. Yes, this sort of programming is old hat now.

jetdv wrote on 8/24/2016, 11:13 PM

Just changing the namespace won't help if scripts add effects by name, as an example. Suppose a script adds the "Sony Border" effect. It won't be found. While the conversion can be done, you certainly need to check multiple things.