EnDisEffects - free script

FocusOnVegas wrote on 10/28/2016, 9:31 AM

Update 04-11-2016 : major update of EnDisEffects to version 2.

Changes from version 1.0:

Possibility to define a preset when you add an effect.
New action “Change Preset”.
New switchable option to preserve “locked events” from changes by the script.
New (automatic) switchable option to filter the available effects in the effects list for the selected events.
Smart interactive user interface; automatic adaptation of the available choices when you change a setting in the user interface.
Some (minor) bug fixes.

*******************************************************************************************************
EnDisEffects is a compiled script with user interface to enable, disable, add or remove a selected filter or to change the effect preset for the selected events.

For Sony Vegas Pro 12, Sony Vegas Pro 13 and Magix Vegas Pro 14.
Free to use for personal or commercial Vegas Pro projects (but don’t sell my script).

Examples of possible operations for the selected events and the selected effect:
• Enable (all instances) of the effect.
• Disable (all instances) of the effect.
• Add 1 instance of the selected effect to the selected events with the selected effect preset.
• Remove all instances of the selected effect for the selected events.
• Change the preset of all instances of the selected effect for the selected events.

Windows 10 users: see the readme file to avoid problems; Windows 10 / Vegas Pro 14 blocks standard dll files that are made with another computer.

More info and download on my website (focusonvegas.com): EnDisEffects

Comments

Quitter wrote on 10/29/2016, 5:26 AM

works fine in VP13
doesn't work in VP 14

Quitter wrote on 10/29/2016, 6:35 AM

the NET Framework deactivating does not working for me (win 10 home, laptop)

FocusOnVegas wrote on 10/29/2016, 7:38 AM

The problem with Windows 10, EnDisEffects and Magix Vegas Pro 14 seems to be related to the .NET version.
I compiled the script for Vegas Pro 14 against .NET version 4.
According to this : https://msdn.microsoft.com/en-us/library/bb822049(v=vs.110).aspx
at least .NET version 4.6 should be installed with windows 10. I expect 4.6 to be 100 % downwards compatible with version 4, but maybe.....

What .NET versions are installed on your Windows 10 system with problems?
Let me guess : 3.5 for Vegas Pro 13 and 4.6.2?

To test I 'll compile EnDisEffects for Pro 14 with different .NET net versions and 'll ask you to test it (I don't have a PC with Windows 10).

Quitter wrote on 10/29/2016, 7:56 AM

Yes, as i wrote you per Mail
3.5 and 4.6 Advanced Services are installed (v4.0.30319)

FocusOnVegas wrote on 10/29/2016, 9:04 AM

Another possibility, maybe this is the same problem (and solution):

http://www.html5gamedevs.com/topic/24277-fix-3ds-max-dll-assemblies-not-loading-bug-in-windows-10/

The solution as described in the link is to unblock the dll file that comes from another computer. Windows 10 seems to be more strict with that. Right click the dll, choose "security" and "unblock" under the "General" tab. Seems to make sense.

Can somebody with problems with Windows 10 and the script try this?

FocusOnVegas wrote on 10/29/2016, 11:28 AM

Thanks Cornico for the confirmation.

I 'll update the readme for EnDisEffects for other users with Windows 10.

Quitter wrote on 10/29/2016, 3:12 PM

Affirm and thanks.
It works🙂

German dll:

Btw.: for your documantation, the folders are
C:\Program Files\Sony\Vegas Pro 13.0\Script Menu
C:\Program Files\VEGAS\VEGAS Pro 14.0\Script Menu

FocusOnVegas wrote on 11/4/2016, 9:09 AM

I updated EnDisEffects to version 2.
It is a major update with a lot of new features.

See first post for more info and the download link.

Quitter wrote on 11/4/2016, 10:45 AM

You got mail 😏

FocusOnVegas wrote on 11/5/2016, 8:26 AM

I got reports from people that EnDisEffects v2 works without problems, even with Windows 10.

I have 1 report (of Quitter) that EnDisEffects doesn't work at all and stops immediately with an error (index of 0).
He uses Windows 10 (German) and Vegas Pro (German). He "unblocked" (freischalten) the dll files of the script. He has no problems with version 1 of EnDisEffects (after unblocking).

I can not reproduce this behavior and it seems to be a mystery.

Are there more people with Windows 10 that can not start the script in Vegas Pro 12, 13 ("EnDisEffects V12V13 (v2).dll") or Vegas Pro 14 "EnDisEffects V14 (v2)"? Of course after you "unblocked" the dll script files, see the readme in the download.

If the answer is "yes", can you give detailed info (like Windows version, Vegas Pro international or localised version, error report)?

Quitter wrote on 11/5/2016, 11:04 AM

Here is what happens (It makes no difference whether events are selected or not)

Same behavior at VP14

Adi-W wrote on 11/5/2016, 1:31 PM

Here, Windows-7 64bit with .NET 4.6.2 and it does not work in vegas14 (but work in Vegas13). It give me the following error message :

System.IO.FileLoadException: Impossible de charger le fichier ou l'assembly 'file:///C:\Program Files\VEGAS\VEGAS Pro 14.0\Script Menu\EnDisEffects V14 (v2).dll' ou une de ses dépendances. L'opération n'est pas prise en charge. (Exception de HRESULT : 0x80131515)
Nom de fichier : 'file:///C:\Program Files\VEGAS\VEGAS Pro 14.0\Script Menu\EnDisEffects V14 (v2).dll' ---> System.NotSupportedException: Tentative de chargement d'un assembly à partir d'un emplacement réseau qui aurait entraîné l'utilisation de l'assembly en mode Bac à sable (sandbox) dans les versions antérieures du .NET Framework. Cette version du .NET Framework n'activant pas la stratégie CAS par défaut, ce chargement peut être dangereux. Si ce chargement n'est pas destiné à utiliser l'assembly en mode Bac à sable (sandbox), activez le commutateur loadFromRemoteSources. Pour plus d'informations, consultez http://go.microsoft.com/fwlink/?LinkId=155569.

Following this link, here are the explanation :

In the .NET Framework version 3.5 and earlier versions, if you loaded an assembly from a remote location, the assembly would run partially trusted with a grant set that depended on the zone in which it was loaded. For example, if you loaded an assembly from a website, it was loaded into the Internet zone and granted the Internet permission set. In other words, it executed in an Internet sandbox. If you try to run that assembly in the .NET Framework version 4 and later versions, an exception is thrown; you must either explicitly create a sandbox for the assembly (see How to: Run Partially Trusted Code in a Sandbox), or run it in full trust.

The <loadFromRemoteSources> element lets you specify that the assemblies that would have run partially trusted in earlier versions of the .NET Framework are to be run fully trusted in the .NET Framework 4 and later versions. By default, remote assemblies do not run in the .NET Framework 4 and later. To run a remote assembly, you must either run it as fully trusted or create a sandboxed AppDomain in which to run it.

Is it a modification that has to be done in the EndisEffects dll itself ?

FocusOnVegas wrote on 11/5/2016, 3:03 PM

@jwe
I have seen reports of that type of error (with Windows 10 and Magix Vegas Pro 14) before with EnDisEffects 1.0, see post above. Because the dll is made with another computer (my computer) and you downloaded it, the dll script files are not automatically "trusted".

Close Vegas Pro and try to unlock / unblock the "EnDisEffects V14 (v2).dll"'. Right click the dll, choose "security" and "unblock" under the "General" or "Security" tab. The procedure might be a little bit different for Windows 7. See post above.

The problem that Quitter has is different and even with Vegas Pro 13.