TX16Wx 3.7 beta now public. Including native Linux support (updated 2024-11-23)

[graffesmusic]

Does not work in Ubuntu 22.04LTS (Ardour, Waveform)

[elcallio]

@graffesmusic - could you be a little more specific on how the error manifests?

[graffesmusic]

Ubuntu 22.04LTS xorg.
-Ardour: vst3 plugin shows black screen. no error in log. VST2 is OK. (by default, vst2 are concealed if same plugin is present as vst3. i didn't notice the vst2 at first)

-Waveform 13: vst2 is ok, but vst3 gives error.

7 Sep 2024 18:39:33 ----- Launched Plugin Scan Process
7 Sep 2024 18:39:33 No plugins found in: /usr/lib/vst3/TX16Wx.vst3
7 Sep 2024 18:39:33 ----- Ended Plugin Scan
7 Sep 2024 18:39:34 ----- Launched Plugin Scan Process
7 Sep 2024 18:39:34 Added VST: TX16Wx.vst [40 ms]
7 Sep 2024 18:39:34 ----- Ended Plugin Scan

Tracktion pluginval tool:
~/pluginval$ ./pluginval /usr/lib/vst3/TX16Wx.vst3
Started validating: /usr/lib/vst3/TX16Wx.vst3
Random seed: 0x13bfcb4
Validation started
Strictness level: 5
-----------------------------------------------------------------
Starting tests in: pluginval / Scan for plugins located in: /usr/lib/vst3/TX16Wx.vst3...
Num plugins found: 0
!!! Test 1 failed: No types found. This usually means the plugin binary is missing or damaged, an incompatible format or that it is an AU that isn't found by macOS so can't be created.
FAILED!! 1 test failed, out of a total of 1
*** FAILED

Aren't vst3 plugins (on Linux) supposed to have this kind of directory structure? (i have never seen otherwise)
:~/.vst3/plugdata.vst3$ tree
.
└── Contents
├── Resources
│   └── moduleinfo.json
└── x86_64-linux
└── plugdata.so

3 directories, 2 files

[elcallio]

Yes and no. The last SDK does indeed suggest the bundle structure for VST3, but it also suggests this for Windows, on which the format has instead been monolithic shared library. Until last (or so) SDK version, the assumed format for Linux was the same.

[elcallio]

The ardour problem is due to missing this patch: https://github.com/Ardour/ardour/commit ... 08cd778cf4
This fixes Ardours VST3 init to match the (intended) steinberg flow of providing the host pointer to factory _before_ plugin creation.
Without it, TX runs without a X11 poll object -> no UI updates whatsoever.

Note also that due to ardours distro model (shipping all dependencies in a "lib" dir), you will need to modify the startup scripts to add system lib path first to the invocation, as the version of glib used there is to old vs. the libraries used in Ubuntu 22.04 and higher (dependency via libsecret).

[masterheavy]

@elcallio any changelog or whats new for this release ?

[elcallio]

I've upped a new build. This moved VST3 support to SDK v3.7 level, i.e. plugin is now "bundle" on Linux and Windows as well.
Note: Ardour 8.7 was released, which fixes the VST3 X11 rendering issue - they fixed their init code. However, Traction Waveform seems to suffer from the same problem (or worse).

[toecuttr]

AUTO-ADMIN: Non-MP3, WAV, OGG, SoundCloud, YouTube, Vimeo, Twitter and Facebook links in this post have been protected automatically. Once the member reaches 5 posts the links will function as normal.

Hi there, downloaded the most recent beta build of the Linux version, and it is causing Reaper to crash when I try and open it. I'm using Linux Mint 21.3 Cinnamon and Reaper 7.22.

Here is the terminal output:

lv2: /usr/lib/lv2/sfizz.lv2/ http://sfztools.github.io/sfizz (http://sfztools.github.io/sfizz) - patch specified with unsupported type http://lv2plug.in/ns/ext/atom#String (http://lv2plug.in/ns/ext/atom#String)
lv2: /usr/lib/lv2/sfizz.lv2/ http://sfztools.github.io/sfizz-multi (http://sfztools.github.io/sfizz-multi) - patch specified with unsupported type http://lv2plug.in/ns/ext/atom#String (http://lv2plug.in/ns/ext/atom#String)
jack: created client
jack: setting TIME_CRITICAL = 4
jack: activated client
Segmentation fault (core dumped)

Not sure what's going on here. Also worth mentioning that only the CLAP version of the plugin shows up in the plug in scan, even though I have Reaper set to show duplicates.

[elcallio]

Can you tell me the exact version, and can you provide the core dump generated?
As for visible plug-ins: REAPER does not by default include /usr/lib/vst and /usr/lib/vst3 (steinberg designated global plug-in paths) in its search path. You need to add it. Or softlink to your ~/.vst[3].

[toecuttr]

The version of the sampler I tried to use was 3.7.0beta 7202.963. I tried to get a more verbose terminal output and all I could get was "Segmentation fault (core dumped)". Is there another way to maybe get you a little more info?

Also manually added those vst paths, and Reaper still did not scan them for some reason.

[elcallio]

ulimit -c unlimited, this will allow core files being generated. If you then provoke the crash you should get a core file (can be quite large). Please send it to me (wetransfer or similar).

[audiojunkie]

While the problem may indeed come from the beta, from personal experience, this error also often happens with low memory as well. Have you (toecuttr) set your realtime privileges and memlimits?

If you are using Pipewire, try this:

https://gitlab.freedesktop.org/pipewire ... pFLHLqs6cW

Real-time priority limits are usually stored in /etc/security/limits.conf and /etc/security/limits.d/. The best option is to add a new file 95-pipewire.conf in /etc/security/limits.d/ with this content:

# Default limits for users of pipewire
@pipewire - rtprio 95
@pipewire - nice -19
@pipewire - memlock unlimited

Then add your user to the PipeWire group so that you can use these priorities.

sudo usermod -a -G pipewire username

(Replace the word, "username" with your own username)

It is probably a good idea to do this, even if the problem turns out to be from the beta. It will eventually get you at some point if you don't. But remember, this is for Pipewire users.

Best of luck!

[Kott]

I've tried 3.7.0beta 7202.963 rpm on openSUSE TW and it crashes. I can provide a backtrace here or within PM,

[Kott]

The version of the sampler I tried to use was 3.7.0beta 7202.963. I tried to get a more verbose terminal output and all I could get was "Segmentation fault (core dumped)". Is there another way to maybe get you a little more info?

Also manually added those vst paths, and Reaper still did not scan them for some reason.

If you have Carla installed, then you can run it inside GDB (with the jackd started already):

Code: Select all

gdb -ar /usr/lib64/carla/carla-bridge-native vst /path/to/TX16Wx.vst.so 0

your carla-bridge-native path may also differ

[elcallio]

A backtrace may not help much as the install binaries do not contain debug info. You will need to send the full core for me to make much sense out of them.