TX16Wx (free v.3) problems with gig performer

[monkey78]

Hi guys,

actually I tried TX16Wx because I need for live perfomances a sample Player. Live I will use the gig performer.
My problem is that TX16Wx not works in gig performer. The VST3 can be load. I connected like the other plugs. Loading samples - fine. But it happen nothing if I play the midi keyboard or the piano roll in the sampler - there is no sound (and the key dont change the colour when I press them). Also I press the play button in the wave/sample editor - nothings happen.

If I use the TX16Wx in ableton live - all is fine. I have created an own performance - works great. If I load this performance in gig performer - nothing. Have anyone an idea what my mistake is?

Edit: Descriped Problem is only with the VST3. The simple VST works - but this has only one mono Output.

Greetingz Chris

[monkey78]

I have some news.
I had support by the gp developers. The VST3 Version not works. But the VST2 Version works with a MAC. The gp support tested this.
I tested the VST2 too. Well it works but with only one mono output. (Screenshot by gp support - two outputs). in my case, a message came:
warning. unsupported bus mode.
Can anyone help me?

[elcallio]

"gig performer" seems to be slightly broken generate an incompatible init chain. For VST3, it creates several instances of TX and uses the GUI in one, but does audio processing in the other. That does not work. Nor is it required to.
For VST2 it tries to set the input bus mode to an unsupported configuration. Now here I can admit that TX could technically just ignore this and let it have its own interpretation of IO instead of complaining.

[monkey78]

hi, thanks for the answer. are you the developer? but how can I solve this problem?

[elcallio]

Let me rephrase my evaluation after talking to the GP people ever so briefly: The VST3 problem is in the JUCE VST3 host code, which makes some assumptions on how the VST3 factory/component works - albeit true for anything derived from the Steinberg SDK, and really more a result of not very well specified and documented API calls. So we'll treat this as a TX incompatibility.

Fixed in next build.

[elcallio]

If you download 3.0.14a the VST3 version should now load fine in GP.

[elcallio]

Update: I found the issue with VST2 plug-ins. It is again idiosyncrasies in JUCE plug-in hosting that breaks IO setup. JUCE assumes all plug-ins are written in JUCE, and has the same bugs as various versions of that toolkit exhibits.
Will be fixed in a later build.

[elcallio]

VST2 issue fixed in 3.0.14b