no, i'm getting the same error, but it's only on the one vsti. let me try replacing the vsti, then...