TX16Wx or sforzando (native Linux versions) in Waveform for Linux

[talby]

I am trying to use TX16Wx or sforzando (their native Linux versions) in Waveform (newest 13.5.n) for Linux, running WF13.5 on Debian13 with its KDE 6.3.6 (Wayland).

TX16Wx:
- VST opens with a usable GUI.
- VST3 version opens with a plane white canvas only, nothing else becomes visualized.

soforzando:
- VST3 version opens with a plane white canvas only, nothing else becomes visualized.

Other VST3 plugins:
- usually displaying their GUI fine.

Do you got the VST3 version of either of these plugins to show its GUI properly? If so, which Linux configuration are you using? Anything special which you have had to install extra or to set up manually?

[Kott]

Looks like a problem with JUCE and plugins built with a plain VST3 SDK GUI. The same problem with MT-PowerDrumKit 2 native Linux Version.

[talby]

If understanding you correctly then this isn't an issue which could be solved by Waveform, right? It will have to be reported to the support channel of the particular plugin developer, right?

[edrickblade]

It also happens with Sfizz Vst3, only a white background gui, many bugs in WF version 13+, I hope Tracktion team fix all those bugs in V13.5.21 or V14.0.0

[Kott]

If understanding you correctly then this isn't an issue which could be solved by Waveform, right? It will have to be reported to the support channel of the particular plugin developer, right?

It has to be reported here, I think: https://github.com/juce-framework/JUCE/issues

[talby]

Looks like a problem with JUCE and plugins built with a plain VST3 SDK GUI. The same problem with MT-PowerDrumKit 2 native Linux Version.

It has to be reported here, I think: https://github.com/juce-framework/JUCE/issues

Interestingly a user reports in another thread (viewtopic.php?p=9176182#p9176182) that for the VST3 version of MT-PowerDrumKit 2 the GUI of it isn't shown in Waveform but in Reaper.

I reported it to Tracktion, for now. If they would answer that they cannot fix it because the problem is caused in the plugin code, then I will see if I can reach out to the third parties.

[talby]

The TX16Wx developer found the cause of the issue, at least concerning his instrument plugin, describing it here:
viewtopic.php?p=9176855#p9176855

[pough]

Ooh, a rare explicit example of "plugin has bug in Waveform because Waveform actually follows the spec". I've seen a few tacit ones in the past but it's interesting to see a plugin developer spell it out.

And this is not to say that Waveform is never the problem. It absolutely is sometimes. But it seems like people are skeptical that the above could ever be the case when a plugin works just fine in Cubase/Reaper/whatever and only bugs out in Waveform.

Here's me hoping that one day my Voxengo VST3 plugins will no longer mishandle MIDI CC data in Waveform. The same "must be Waveform not me" problem went away for Auburn Sounds and Boz Digital plugins...

[pough]

Has anyone used pluginval on Linux to see what it reports about these plugins?

https://github.com/Tracktion/pluginval

I sometimes use it to inspect plugins. Waveform has a simplified version built in, but the full standalone has a lot more options.

[talby]

Pluginval does not open the GUI of TX16Wx, and then is actually not testing anything. There isn't any verbose output. But it still logs "ALL TESTS PASSED", which is obviously a misbehavior of Pluginval to report this, after it didn't perform any tests.
The only hint that something could be wrong with this plugin is, that Pluginval crashes when testing this plugin with option "Validate in Process" being activated.

[talby]

Interestingly, Pluginval does open the GUI of the Sforzando plugin, while WF is not, and then passes all important tests. It only fails on a detail where even plugins of Tracktion fail to pass if running tests in "randomised" mode.

I am not sure if running a test in Pluginval is actually testing the plugin, or the plugin is testing Pluginval to run stable. Pluginval crashes often, even when the tested plugin never fails in the DAW. And running it newly on a plugin, not the option to repeat tests, sometimes reports that a plugin passed all tests, and sometimes Pluginval crashes.

[pough]

Sometimes pluginval is helpful and sometimes it isn't. Thanks for giving it a try.

[edrickblade]

Tracktion Team had been investigating this with the JUCE Team and it seems to be the result of those plugins not correctly returning the value of their XEMBED_MAPPED state.
As posted in the JUCE Forum here, and they have a fix for this bug issue in the next update and the will release it very soon.