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.

Nope - the VST3 version of Span works as expected here.

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

OK I tried Span and it doesn't repro for me either.
 
So speculating here... Span does not modify the audio passing through it, and it also doesn't support the bypass button on the property page since bypassing it makes no audible difference (the bypass button is grayed out on the property page). VST3 plugins can specify whether they support bypass or not. So maybe the bug could be in how the Voxengo plugins that do support this bypass functionality is handling a disable/enable operation from the host.
 
I did file a problem report with Voxengo, so I'm sure they will look into it.

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

Hi,
I had a kind of strange behavior yersterday with Voxengo Deft Compressor,I can't tell exactly,but the GUI would not appear and there was an error message,so,as far as I do not think,I closed Sonar and restart and the problem was more or less solved,..meaning everything seemed to work fine. But I just have to mention that it was the first time I was confronted with this situation,so wait and see,don't know if it comes from Sonar,from Voxengo or from my set-up.
Hope it can help.
All the best.
Olivier.

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?

Voxengo can repro this with Voxformer in Sonar, but not in Cubase 6. They are trying to root cause the issue.
 
In the meantime, be careful when using Voxengo plugins in Sonar since you can't visually tell whether the plugin is in circuit or not. On plugins that create subtle effects, this can be problematic.

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).

Hi,
I tested the Voxengo Elephant (VST 3)and Span here  at 64 bit ,
everything works as expected.
regards