Crashing Troubleshooting

John-Vere wrote on 4/16/2024, 12:51 PM

As I said in my other post I have always had trouble with Movie Studio 17 crashing and now I had Vegas crash once. I found the location of the dump files in User\Me\ App Data\local\crash dumps and the few that were there all are labeled sfvstserver.exe. I opened the dumps in WinDbg and it seems sfvstserver is a VST wrapper used by Vegas and MS17.

OK, fine. I don't need VST's as all my audio is already mastered in Sonar. But here seems to be the cause of a crash even though I'm not using any VST plug ins? Is it due to scanning them?

Further investigation shows there was only one scan path for VST under preferences and those are all Magix plug ins. I have unchecked all but the Compressor and limiter. Are these what are causing the crashes???

In the add effects dialogue VST tab it shows just those 2.

When I open the add effects dialogue it shows stuff that is obviously in Cakewalks folders but those are DX plug ins. But the Cakewalk folder is not in a scan path so how did they get there?

The question is this. Does Vegas only support DX plug ins natively and then use this Wrapper that crashes for VST's? If so no big deal.

Thank you. John.

Comments

rraud wrote on 4/17/2024, 9:42 AM

DX plug-ins do not need to have the (search) folder selected by the user. I am not aware of a VST 'wrapper;, The last time a recall needing an optional VST 'wrapper' was with Sound Forge 6 many moons ago.
Vegas currently supports 32 & 64 bit VST 2 and VST 3 effects plug-ins.

John-Vere wrote on 4/17/2024, 4:51 PM

Thanks for the info, It's definitely this wrapper that was crashing, I think It might have come with installing Music Maker or Sound Forge via MS 17. Magix it terrible about installing garbage along with the software. LIke the generic asio driver. I'll see if I can clean stuff up. Might have to completely uninstall everything and then only install Vegas.