I was also having problems with the latest vb3-II crashing, it especially seemed to happen when multiple rackspaces had it running.
Per Joey’s suggestion I’ve been running it inside Blue Cat Audio PatchWork for a few days and so far it is entirely stable. I’ll report back if it starts crashing again, but so far so good!
Do you have a crash report please?
Sorry I didn’t save one, if I get a crash with it running inside patchwork I will post it
Well, a crash inside another host doesnt help. Any chance you can get it to crash directly in GP?
Sorry if my post was unclear -
Vb3-II was crashing, I don’t have a crash report but when I clicked the “what’s in this report link” when it was happening it was reporting an exception just like the one you posted above, pointing to VB3-II.vst3
I’ve since started running VB3-II inside Patchwork and have had no crashes, nor does VB3 seem to be crashing within Patchwork as it is always working.
I was just sharing this as a solution for those folks that want to run VB3-II.
Well scratch all that, VB3 is now dropping out intermittently when using blue cat patchwork.
On the plus side it doesn’t crash gig performer like VB3 was, and seems to restart itself gracefully. Blue cat doesn’t seem to have any log files of its own.
Licensing issue?
You should try it in jBridge instead of Blue Cat Audio PatchWork.
Got nothing to lose…I think it’s only around $15.
You’re on your own if you use jBridge.
It would be far better to get a proper crash report so we can (a) determine exactly what went wrong and (b) get it fixed by us, if a GP bug, or by GSi, if a VB3 bug
VB3 - the neverending story…
It may have been as simple as this. (Insert facepalm)
I went to run it in standalone and it had lost my serial somewhere along the way. It’s not great that the vst3 window doesn’t tell you this. I did a full reinstall with the latest and it is running fine.
I’m going to copy my gig and try running it outside of patchwork again.