Steve Rhoden and John Rofrano: Scripts in Vegas Pro 14

[John Rofrano]

[Richard Jones] “I wonder if either of you can comment please.”

Gary Rebholz of MAGIX has “officially” stated that scripts WILL need to be MODIFIED to work with Vegas Pro 14.0.

Just to be very clear: Existing scripts WILL NOT continue to work!

We don’t know if the extent of the change is simply a namespace change from Sony.Vegas to something else, or if it goes deeper into removing com.sonycreativesoftware from all of the OFX plug-in presets or the word “Sony” from all of the FX names (e.g., “Sony Chroma Key, Sony Levels”, etc.) but changes will need to be made to scripts and command extensions by their authors and if the authors have abandoned the script then it may never work with Vegas Pro 14.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[Graham Bernard]

And just to be VERY CLEAR too, this needs support from MAGIX, and when I say support, I mean $upport for their Scripting Partners. I think that’s fair?

Rubs both ways.

* Grazie

Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge

[Richard Jones]

Thank you John — and I’ve just had a chance to catch up with your post on the Vegas Pro forum in the thread I referred to above.

Your argument about covering the costs to continue your business on a sensible footing is well taken although questions of customer service will obviously have to be taken into account and this in its turn might depend on the amount of work involved. I fully understand and appreciate this but the need to upgrade scripts, especially the problems this will cause consumers for those no longer being supported, might, just might, be an upgrade killer:)

Richard

[Jeff Lee]

Seems to me the reasonable solution is for Sony to license the paths for scripts to MAGIX. What a crappy thing for Sony not to due. But Sony has proven that they don’t care about the end users. Seems to me that MAGIX is trying hard to make this deal work. If I were the commercial script producers I would want to produce an “upgrade” for a small fee. The free ones, well if one is very popular I would think the commercial guys might want to fill the market void.

[Edward Troxel]

Subject: RE: Namespace change coming for VEGAS Pro 14
Reply by: GaryRebholz Sony Certified Vegas Trainer
Date: 8/5/2016 10:52: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.

Edward Troxel

[Edward Troxel]

I do plan to recompile a Vegas Pro 14 version as soon as it is possible to do so. This would be a free update with no new features.

Edward Troxel