If you do a forum search using keywords such as 'Waves plugins', you'll find quite a few forum posts over the years about Waves plugin problems in Vegas Pro, particularly after Waves ceased support for Vegas Pro with the last VP supported version apparently being 9.6. If I remember correctly, that's when Waves went VST3 only at a when Vegas Pro was VST2 only. But even after Vegas Pro introduced VST3, there have still been quite a few forum posts about problems with Waves plugins in Vegas Pro.

From Waves website, ProTools, Abelton Live and Davinci Resolve are all listed as supported hosts for Waves plugins - but Vegas Pro is not listed.

 If this was the good old days, I'd call Curt Palmer up and ask him WTF

I think that Curt Palmer was involved with Sonic Foundry.

 

 If this was the good old days, I'd call Curt Palmer up and ask him WTF

I think that Curt Palmer was involved with Sonic Foundry.

Yes. I was intimately involved with the development team of the original Vegas at Sonic Foundry, and Curt (RIP) was a dear friend of mine, along with Peter Haller, Chris Moulios, and the team of geniuses there. Interesting factoid. Vegas was first launched as an audio-only platform, but there was a boot up variable that turned on the entire video portion that was under development.

Another interesting factoid: If you reported a crash bug to Curt, he's call you up and demand you show him how to reproduce it. He was a monster of programming, ex-Microsoft. Truly an icon. Anyway...

Unfortunately, the failsafes that allowed boot-up bypasses seems to have disappeared. Or I am not remembering how to engage them.

So far as Vegas support within Waves, I'm also closely involved there. They had to drop official support owing to the problems Sony introduced after Haller's departure from that team. He was the last man standing who knew the code like the back of his hand.

I'm just trying to determine if Vegas is functional at this point, so I can decide whether to re-license. So far, not promising. Are you involved on a level where you know who I might contact to determine what is going on with Waves support? If I could get to the bypass mechanism, I'd go through the usual routine. But I don't know what has happened with the code since I had to stop using it last time.

One place to look is C:\Program Files\Common Files\OFX\Plugins. Copy everything from that folder to a folder on your desktop. Then remove the plugin folders leaving Plugins empty. Start Vegas and see if it gets past the plugin scan. If it does, then add each plugin folder from your desktop to the OFX Plugins folder. Start Vegas, etc..

That is if the issue is loading a plugin. What plugins do you have installed?

You can also reset Vegas by following the instructions HERE.

Thanks. I'll give that a go. The usual post stuff in audio plugins...complete Waves suite and whatever installs natively with Pro Tools, along with an assortment of mainstream stuff. All work flawlessly with PT, Ableton, Resolve, and Cakewalk/Sonar, so...not sure why Vegas is horking. It was once the most solid app of any. I'll try the reset. I have a feeling it's trying to pick up somewhere it left off, since the plugin scan shows 75% the moment it hits the screen. Maybe I can see where it chokes once I reset.

NEW CLUE: I reset. It appears to hork while "loading .net runtime" is on the screen. If I recall the way it usually worked back in the day, it was the NEXT thing that loads...after the last thing you see...that is the crash point.

Does anyone know what that is?

EDIT: I updated my .net runtime to the latest version, so that's not it I guess. It must be the NEXT THING, as I remember.

Unfortunately, the failsafes that allowed boot-up bypasses seems to have disappeared. Or I am not remembering how to engage them.

@Bruce_Richardson I have a memo about VEGAS Pro Troubleshooting: https://zzzzzz9125.github.io/VegTips/ / https://vegtips.netlify.app/

I've recorded here all the useful solutions that I've come across.

Q: VEGAS hangs/crashes/freezes at the "Scanning VST plug-ins..." step during startup?

A: Try disabling VST scanning on startup. Right-click the VEGAS shortcut -> Properties. In the "Target" field, add " /NOVSTGROVEL" at the end (note the space before the slash). Then run VEGAS using this shortcut. Once it starts normally, you can move problematic plugins from the VST paths, store them separately, etc.

 

Q: VEGAS hangs/crashes/freezes at the "Initializing DirectX plug-ins..." step during startup?

A: Similarly, try disabling DirectX plugin scanning on startup using the command " /NODXGROVEL".

EDIT: I updated my .net runtime to the latest version, so that's not it I guess. It must be the NEXT THING, as I remember.

@Bruce_Richardson For VEGAS Pro, you should install .NET Framework Runtime instead of .NET Runtime. They look similar but are actually different. The former is an old thing that is only compatible with Windows, while the latter is cross-platform.

You can try the .NET Framework Repair Tool: https://support.microsoft.com/topic/942a01e3-5b8b-7abb-c166-c34a2f4b612a

Same problem. Sony Vegas 23. Opens, looks like when loading windows then crashes out.

C:\Program Files\Common Files\OFX\Plugins The version of 23 the ofx files are not listed there, i do not have that file its named differently under Vegas. Not sure exactly what to do about it. Tried uninstalling and re-installing, same issue. Just crashes every time.

Sony Vegas 23

@richard-eustace "Sony Vegas 23" not exists. See: https://www.vegascreativesoftware.info/us/forum/sony-vegas-vs-vegas--119881/

Furthermore, your question might be different from that of the op. It would be best to create a new thread to provide a detailed explanation.

And if you see "ntdll.dll" in the error message, you might want to take a look at this post: https://www.vegascreativesoftware.info/us/forum/warning-ms-vc-14-50-v145-kill-vegas-permanently--150332/

The crash caused by MSVC1450 is also mentioned in my troubleshooting guide, if you take a closer look.

sorry VegasPro 23.

I have already tried your steps 1-6

EDIT: I updated my .net runtime to the latest version, so that's not it I guess. It must be the NEXT THING, as I remember.

@Bruce_Richardson For VEGAS Pro, you should install .NET Framework Runtime instead of .NET Runtime. They look similar but are actually different. The former is an old thing that is only compatible with Windows, while the latter is cross-platform.

You can try the .NET Framework Repair Tool: https://support.microsoft.com/topic/942a01e3-5b8b-7abb-c166-c34a2f4b612a

None of this helped. I had installed the .net Framework (to update), and I ran the troubleshooter and reinstalled it.

Unless the logic of the startup has changed, I am 100% positive that the thing on the screen is the previous item that loaded successfully, and that the NEXT element that instantiates is always the cause of the crash.

When you are troubleshooting which plugin is causing a crash, you know it's the next one to have been scanned after whatever was on the startup screen when it disappears.

I remember all of that detail like it was yesterday. I was on team alpha when Vegas originated.

If I had a development team contact, I imagine we could resolve this quickly. Do you know one? I know no original Sonic Foundry guys are around, but maybe there are still a couple of Sony guys in the mix? I have no idea. I'm just trying to get into some project and mixes that I need to reopen for a licensing deal. I can't imagine what would be going on in my system that would be problematic. Everything runs like a top on all music platforms.

I guess I could go through the pain of reinstalling and sitting and clicking the endless components. Does anyone know if Vegas creates a startup log?

sorry VegasPro 23.

@richard-eustace ​​​​​​From my troubleshooting guide:

Q: Clicking Render As (called Render in VP23+) to open the template list causes error/crash?

 

A: If there's an error pop-up, first try Disabling Error Reporting.

 

If that fails, try temporarily moving all folders from the codec path "...<VEGAS install path>\FileIO Plug-Ins\", restart VEGAS, insert a text event, and see if clicking Render As still crashes. If not, gradually move codecs back, restarting VEGAS and testing Render As after each to identify the problematic codec. Once found, avoid using that codec by not placing its folder back. This may prevent VEGAS from importing/rendering certain formats. (Prioritize checking mxavcaacplug.)

In summary, you need to identify the codec mentioned in your error message ("appleprores.dll") and try to block it.

None of this helped. I had installed the .net Framework (to update), and I ran the troubleshooter and reinstalled it.

@Bruce_Richardson If the .NET Framework repair tool doesn't work, I'm not sure what the problem might be. You can try looking at my troubleshooting guide to get some possible ideas.