Bug when using Voxengo plugins - Can anyone confirm?

I took advantage of the Voxengo Spatifier introductory price, and tested it out yesterday. But I noticed some strange behavior when using it in the FX bin. I then played with the Voxengo Voxformer plugin and saw the same behavior. It doesn't reproduce with non-Voxengo plugins so I assume it must be a Voxengo specific issue.
 
Basically, when you click the bypass button on the plugin in the FX bin, then click it again to enable it, it is still not enabled properly. You have to toggle the enable button again to make it come back into the signal flow.
 
Steps:

1. Insert a VST3 Voxengo plugin into an FX bin.
2. Start playback and ensure you can hear the effect.
3. In the FX bin, click the bypass button on the plugin to disable it.
4. In the FX bin, click the bypass button on the effect to enable it.

 
Result:

• The effect is still bypassed after step 4, even though it shows as active in the FX bin.

 
Expected result:

• The effect should be enabled after step 4.

 
Workaround:

• Repeat steps 3 and 4, after which the effect will be enabled again.

 
Note that the bypass button mentioned in the steps is the one in the FX bin, not the one on the plugin property page. The one on the plugin property page works properly.
 
Can anyone confirm this behavior?
 
EDIT: Note that this is with the VST3 versions of the Voxengo plugins. I have not tried the VST2 versions.

I have not tried Span, will try that when I get a few minutes and see whether that reproduces for me.

At work so can't help until I get home.
 
Are you using 32 bitor 64 bit version?

SF_Green
At work so can't help until I get home.
 
Are you using 32 bitor 64 bit version?

I'm using 64-bit.
 
In contact with Voxengo, and it seems it might be related to VST3 plugins that support an automatable bypass (the bypass button on the plugin property page isn't grayed out). Unfortunately the only VST3 plugins I have that support bypass are those from Voxengo, so I'm no longer sure this is a Voxengo specific issue.
 
Does anyone else have non-Voxengo VST3 plugins that support bypass?

I tested this with a handful of non-Voxengo VST3 plugs and could not reproduce. I tested Ozone 5 components (and the UI actually has a bypass button which took SONAR's prompt), a few of the free Melda plugs, Focusrite's Red EQ, and the FX version of CA-2A (these three went on/off with no indication on the UI, but bypassed).

So far it only reproduced with Voxformer and Spacifier, so maybe it is limited to those plugins. Voxengo has confirmed that they can reproduce it with Voxformer so it isn't limited to my system.

Not sure if related, but I opened up a couple old projects which already had FX bypassed and had to click them twice to enable them. This has only occurred after first opening a project though, and after initially enabled (with two clicks), they then go on/off as expected. I am not sure if this is related to the OP, but I have noticed this on non-Voxengo plugs.

I've noticed this behavior with the gliss eq.