It turns out this seems to be a bug in unicode handling in the vamp 2.3 hostsdk. The attached patch (also committed to trunk) fixes the bug. I'm submitting this upstream to the VAMP folks.
It turns out this seems to be a bug in unicode handling in the vamp 2.3 hostsdk. The attached patch (also committed to trunk) fixes the bug. I'm submitting this upstream to the VAMP folks.