Maybe you have : Boris continuum OFX (any version) installed on your system.

Also an issue if you have very old newblue titler 2 OFX left overs in the plugin folder.

I have been chasing the Vegas team, Boris team and hitfilm team for the unability to work together for half a year now.

Vegas post is not compatible with Boris continuum, and is not fixed in the new update of Vegas post (build 387), nor in the new updated (of this week) versions of Vegas image nor Vegas effects...

I have move all the common files' OFX plugin to VEGAS Pro' directory's ofx plugin folder. But VE still often has no response...

It's working fine for me, after disabling the new blue plugin in my ofx folder. I haven't tested since the update to see if I can re-enable that plugin yet. I haven't had a single crash since, though.

It's working fine for me, after disabling the new blue plugin in my ofx folder. I haven't tested since the update to see if I can re-enable that plugin yet. I haven't had a single crash since, though.

Ohh

Oh my god! Always have no response! Why?

None of us are having the issues you are having, so it's hard to help with a problem we cannot reproduce. If you can specify something you can do that makes Vegas Effects crash, that might help us, or if you can post a .vegfx project file that causes a crash, that too might help, but otherwise we're scratching our heads trying to figure out a way to help.

None of us are having the issues you are having, so it's hard to help with a problem we cannot reproduce. If you can specify something you can do that makes Vegas Effects crash, that might help us, or if you can post a .vegfx project file that causes a crash, that too might help, but otherwise we're scratching our heads trying to figure out a way to help.

I will find a time to reinstaller my OS. hope it will solve the problem.

Step 1: disable so4compound.dll

Kinda like hearing "I have a headache" and replying "step one, shoot up some morphine." So4 can and does cause a lot of people a lot of issues, but it works for many as well, and disabling it comes at a cost of removing functionality some of us need, so it should be recommended as one of the later steps, not starting off.

Ian, until you describe to us what is happening when your program malfunctions, which you can learn how to do by reading the information in this thread: (https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/), we can't help you. Just hearing that your software is freezing/crashing isn't enough information to get us started.

alextudm95 wrote on 12/27/2019, 7:14 AM

"I have to agree with this. (People moving AWAY from VEGAS, as per now locked thread) My only suggestion to Magix is to stop making new version of VEGAS Pro, but fully remake the whole system to be more stable & reliable like other NLE.
when VEGAS Pro 17 is being promoted with the new screen capture, it doesnt work till today."

_______________________________^^^ THIS ^^^^ ___________________________________

This is what I've been saying for years, STABILITY FIRST...
All the silly add ons don't add up to a hill of beans versus stablity and an improved, smoother GUI (which is Vegas strength, inherently, but it's only been slightly improved over the years, victim of its own "success??" perhaps.

and although some of the comments on the now "locked" other thread on this subject may not all be spot on, ^^^^THIS ^^^^^ Idea has GOT TO BE REITERATED.... PLEASE PEOPLE, quit focusing on the candy apple paint job and window tint when the engine is blown.

Came here from the other thread on crashing. I am using the latest build for VP17. I had to disable So4 and all has been well for me ever since. I have full Boris Continuum 2020 and it's working so far... ok.

For timeline fast editing, I really like Vegas, but do feel the pain of those who have experienced crashes. VP16 was solid for me. Same as VP15. So I waited for a patch to come out before being an early adopter to VP17, which came with some nice features I was interested in.

So hoping that AMD support and even more stability come with the next update.

As for those that say "stability first", no argument from me! But that is not what sells. And sadly, by the time most bugs are squashed, new people have been turned off and old users start to have wandering eyes. I sat on the sidelines watching all the early posts on VP17 thinking I'll skip it. But I took a chance (a Black Friday Christmas gift to myself). Yes, some stumbling along the way, but I am satisfied with the stability so far.

Step one for headache! LOL.

@lan-mLMC I am not sure we have the same issue, but if it is a case of Vegas effects not launching (or better "not seem to be appearing" to launch, or even briefly visible launching and then disappearing) may be due to OFX, as you already guessed by the suggestion given before. In your post I see that you moved some common OFX to Vegas folders trying to solve the issue, but I do not think this will not work. What does work is finding out which OFX is offending and then temporary re-naming or removing the particular OFX in it's original folder. Eventually this will make Vegas Effects launch (if all incompatible OFX's are renamed or removed), but you will lose the OFX in Vegas (and possibly other NLE's). So until they fix this, it is really choosing between the OFX plugin or Vegas Effects. By the way launching Vegas effects as a stand-alone has the same issue.

Unfortunatly Vegas itself does not crash or indicates what is wrong, however Vegas effects does crash, it is just not visible as there is no feed-back. However you can find which OFX is causing the issue is using the windows tool "event viewer" build in every windows version:

On my system, following files need a rename or remove to make Vegas effects launch successfully.

Obviously, I would loose Boris (and newblue titler pro 2) functionality by doing so, which in case of Boris is unacceptable (I do not care about the old newblue titler)...

C:\Program Files\BorisFX\ContinuumOFX\13\lib\Continuum_OFX_8Bit.dll
C:\Program Files\BorisFX\ContinuumOFX\13\lib\Continuum_OFX_Float.dll
C:\Program Files\Common Files\OFX\Plugins\NewBlueFX\TitlerPro2.ofx.bundle\Contents\Win64\TitlerPro2.ofx

it is just not visible as there is no feed-back. However you can find which OFX is causing the issue is using the windows tool "event viewer" build in every windows version:

 

 

Wow，thanks！It seems to be a excellent solution to find out which ofx to cause the no response！