I've been seeing a few troubling issues with vMix recent. The most troubling is that I am getting this protected/corrupt memory error with some regularity when opening bundled presets. I have seen this memory error on 5 different machines. It is not a memory issue. I think it has to be some kind of bug with vMix accessing files where ever it is storing bundled preset assets.

Typically when this error pops up vMix will quit immediately afterwards. Sometimes vMix will open the preset but all the assets will show up off line. Then later the preset will open just fine.

The other issue I am seeing with some regularity is my Waves plug-in licenses deactivating themselves. If I open a vMix preset that uses a Waves plug-in, I'll see an error about each plug-in not being licensed. Then the next time I open the preset I'll get another error about GUID and characters which appears to be vMix looking for the license. Then vMix will quit. After I re-activate the Waves licenses all is fine.

Anyone else seeing this? Again, I've encountered both of these issues on multiple machines including both local and AWS instances.

Thanks,

Greg

IMG_9555.jpg (2,119kb) downloaded 0 time(s).

After talking to vMix Support and to Waves I've come to the conclusion this problem is caused by a recent update to Waves VST plugins. Waves recently updated to v14. All of my plugins got updated on my account in Waves Central but my not on any of my computers. The issue is this update wiped out all of the previous versions of my Waves plugins along with the licenses. So all of my vMix presets are looking for Waves plugins that not longer exist on the computer. I have to manually reinstall the v14 plugins on each vMix instance. Once I do that all is right with the world. The first time or two you open a preset that has an old plugin saved, vMix very well may throw off an error and even quit. Restart the preset a time or two and it should drop the old plugin and you can install the updated one.

Hope this makes sense.