We do implement it for VST3. I believe he is pointing out that we don't react to VST2 audioMasterIOChanged and saying "in that case what makes you think they would react to VST3 ioChanged?"
In VST2 we don't react to that call because we check VST2 IO and latency on every process call. The simple solution to your issue is for us to also check VST3 latency on every process call, so we will add that. The Voxengo latency changed warning will probably still flash momentarily.
FIXED (REAPER 5.01)
This topic was last updated 180 days ago, and thus it was archived. Replying is disabled for this topic.