Comments

Dexcon wrote on 6/30/2020, 6:23 PM

Much more information is needed, particularly at Section B of:

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

I am not sure why you have not named what the plugin is - it is critical information relating to the problem, so please be kind enough to name the plugin.

 

 

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

ADinosaur wrote on 6/30/2020, 7:01 PM

Much more information is needed, particularly at Section B of:

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

I am not sure why you have not named what the plugin is - it is critical information relating to the problem, so please be kind enough to name the plugin.

 

 

That shouldn't matter.

The plug-in is an OFX plugin called Transition Master that doesn't work in Vegas and isn't designed to but works in other software that I need. So I need it installed on my machine in the common plugins folder. I do not need it to work in Vegas nor do I expect it. I expect Vegas to launch though even if it encounters an OFX plugin not designed for Vegas

The problem is that there needs to be a way to tell Vegas not to try to load this plugin.

My system is Windows 10.

I seem to remember being able to disable specific audio plugin VSTs within Vegas when Vegas wouldn't startup because it couldn't load them. What I'm looking for is that option for OFX plugins.

Further, Vegas should not crash because it can't load a 3rd party plugin. It should just skip over the plugin and not offer it as an option in the software. It's ridiculous that I can't even start Vegas.

 

Dexcon wrote on 6/30/2020, 10:35 PM

From Transition Master's webpage:

https://aescripts.com/transition-master-basic/

Compatibility:

After Effects2020, CC 2019, CC 2018, CC 2017, CC 2015.3, CC 2015, CC 2014, CC, CS6

Premiere2020, CC 2019, CC 2018, CC 2017

Nuke/NukeX11.0, 10.0, 9.0

Davinci Resolve16

If this is the product that you are referring to, it looks like the software company that produces this plugin has not made it available for use in Vegas Pro.

Unlike VST audio plugins in Vegas Pro, unfortunately there is no similar function for video plugins. It would be great if there were.

Agreed that Vegas Pro should skip a plugin on opening if it can't load it rather than crash. The same issue was raised recently in another post on the forum (with a different plugin though).

Someone else on the forum will hopefully suggest a workaround if there is one.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

Musicvid wrote on 6/30/2020, 11:56 PM

Is it in the same folder as your Vegas ofx plugins?

You can always just rename the extension until you need it.

I have Vegas Pro 14 and Resolve. No such issue here.

ADinosaur wrote on 7/1/2020, 1:13 AM

Is it in the same folder as your Vegas ofx plugins?

You can always just rename the extension until you need it.

I have Vegas Pro 14 and Resolve. No such issue here.

I did that but that's a silly solution to have to do repeatedly when you want to use either software.

 

Musicvid wrote on 7/1/2020, 9:48 AM

Please list the folder path to your Vegas OFX Plugins.

Please list the exact folder path to your offending plugin. Are there other plugins in that folder that also try to load in Vegas, once you have disabled the offending plugin? Do they cause a crash at startup? Are there others you do not recognize showing in this window?

Contrary to your impression, rogue third-party plugins happen all the time. Vegas is not always able to trap them before the fact. Your best bet is to make a detailed problem report -- and submit it to the developers of that third party plugin.

I suspect you have it installed in a Common Files folder that Vegas scans at startup. until then, you can try reinstalling it in a different, dedicated folder, or renaming as you are doing now.