V14 support scripts?

Gary James wrote on 7/26/2016, 12:43 PM

Though I've never written one, I believe Vegas Plug-Ins are written using C++, not C#. Meaning they are not Namespace dependent.

wwaag wrote on 7/26/2016, 1:06 PM

The ideal solution would be for Magix to include the frameserver as an included rendering option in a future release, thus insuring it would be updated as Vegas evolves. Perhaps if enough of us make this suggestion, Magix will listen. They do seem more open to user input than Sony. Or perhaps the folks at Vegasaur might consider adding it to their list of capabilities. The bottom line seems that someone other than a "volunteer" is needed and money is always a good incentive. I'd be willing to pay as well. As others have stated, without this capability, I will probably continue with V13.

wwaag

Marco. wrote on 7/26/2016, 1:15 PM

I completely second this. Frameserving should be a build-in export option.

GaryRebholz wrote on 7/28/2016, 4:18 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, 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.

Frameserving is a completely different topic which I have logged into my user-request backlog and will strongly consider for future work.

Marco. wrote on 7/28/2016, 4:26 PM

Thanks for it, Gary.

wwaag wrote on 7/28/2016, 5:46 PM

Thanks so much for looking into the issue of frameserving which is so essential for many of us.

wwaag

jetdv wrote on 7/31/2016, 8:06 AM

My plans at this time:

Excalibur and Montage Magic will be updated to the new namespace, recompiled, and a "Vegas Pro 14" released as quickly as possible after the release of Vegas Pro 14 and will be available for free.

As my scripts have been compatible from Pro 8 to 13, several new scripting features found in newer versions of Vegas Pro could not be used so I consider this a chance for a "clean start" to be able to add in access to some of those new features which would, at that time, need an upgrade price.

Edward

videoITguy wrote on 7/31/2016, 8:26 AM

As a long time developer of the most useful of scripts, jetdv, ED, your position is well-taken. However, it appears, that what you choose to do is what the situation forces you to do. I think the position of the Magix acquisition team forces you to bear the risks and the costs.

1) Your scripts to be updated would be very worthwhile.
2) Your time and effort to do so may NOT be rewarded by the revenue offset hoped to be there.
3) It would seem that development efforts to update any much older scripts have to be focused on two different versions available to the consumer. A) A script for VegasPro13 as an update and B) A script of VegasPro14 update. I think you have to charge for each of these versions. What revenue THAT would be a just reward for doing this is going to be your call.

set wrote on 8/5/2016, 3:49 AM

I just noticed this post by now as pointed by other user in other forum (LinkedIn Sony Vegas user group)

@JohnnyRoy,

Hi John, I have been using Ultimate S Pro 4 and it's been my very-useful scripts.
Let us know for any updated news regarding to this powerful script after your internal considerations...

Set

JohnnyRoy wrote on 8/5/2016, 8:00 AM

> "Let us know for any updated news regarding to this powerful script after your internal considerations..."

@Set

Will do.

Right now I'm as much in the dark as everyone else. I have no idea what the changes are that will be needed or if I can make them in time for a September launch. There is no information flowing from MAGIX on this topic.

Like I said, if it's only a Namespace change that will be one set of work that is fairly easy to do although any change that requires a recompile requires extensive enough testing to prove that it didn't break anything.

If, however, plug-in names like "Sony Color Corrector" changes, or OFX names like "com.sonycreativesoftware_colorcorrector" changes, the impact will be MASSIVE! I don't know how long it will take to make those changes because I assume that we will need to recreate these presets with the new plug-ins and re-export the settings, and re-package them for installation with our scripts, and re-test that it still works as it did before and I have no idea how many hours this would take or when it can be completed.

We are all in the dark on this together.

~jr

John Rofrano
VASST Software
www.vasstsoftware.com

set wrote on 8/5/2016, 9:51 AM

Thanks for the insight information...

Ah, well, if there's any such kind of 'Bulk auto find-replace' toolkit, that gonna be helpful...
but anyway, looking by this scenario, it's possible I think we might going to keep Vegas Pro 13 running together with new VP14 for a while..

Let's just see it in September then...

Set

altarvic wrote on 8/5/2016, 11:15 AM

If MAGIX change internal plug-in names (eg. "com.sonycreativesoftware_colorcorrector" to "com.magix_colorcorrector"), this will break the compatibility of projects - we will not be able to open old projects with those effects...

But they can add support for old plug-in names in "read only" mode - we will be able to open old projects, but this won't help script developers...

GaryRebholz wrote on 8/5/2016, 11:51 AM

I don't mean to keep you guys in the dark, but I wanted to have as much information as possible before I write since I realize how significant this is. But here's what I know so far:

First, 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.

Aside from the noted scripting change, there will be no compatibility issues with your current OFX plug-ins, so you will be able to open your old projects in VEGAS Pro 14.