AAS Tassman 32-bit crash

[kporkka]

Thanks for giving yabridge a shot!

• [X] I read through both the troubleshooting and the known issues sections, and my issue wasn't listed there

Problem description

After installing WineHQ and yabridge, and installing AAS Tassman 4.1 32bit (legit copy), and running TAssman the first time, it worked without problems.

However, upon reboot, the Tassman plugin loads and can be played in Bitwig (latest), but does not open the plugin editor window and audio engine crashes soon after. Reaper hard crashes immediately on loading Tassman.

What did you expect to happen?

Tassman to work as during first boot

What actually happened?

Plugin loads, does not open it's control window/editor, audio engine crashes (Bitwig)

Made all the changes proposes in the README file

Operating system

Pop!_OS 22.04

How did you install yabridge?

Directl from the release page, as per instructions

yabridge version

Latest

yabridgectl version

Latest

Wine version

wine 7.11

Plugin

AAS Tassman 4.1

Plugin type

VST2

Plugin architecture

32-bit

Host

Bitwig 4.2.5

Desktop environment or WM

Gnome

GPU model

NVIDIA Quadro RTX 3000 Mobile / Max-Q

GPU drivers and kernel

Latest

Debug log

yabridge.log

Anything else?

My understanding is that Tassman is a 32-bit plugin. However:

kporkka@pop-os:~/Downloads/sspi$ yabridgectl status yabridge path: VST2 location: '/home/kporkka/.vst/yabridge' VST3 location: '/home/kporkka/.vst3/yabridge'

libyabridge-chainloader-vst2.so: '/home/kporkka/.local/share/yabridge/libyabridge-chainloader-vst2.so' (64-bit) libyabridge-chainloader-vst3.so: '/home/kporkka/.local/share/yabridge/libyabridge-chainloader-vst3.so' (64-bit)

yabridge-host.exe: '/home/kporkka/.local/share/yabridge/yabridge-host.exe' yabridge-host-32.exe: '/home/kporkka/.local/share/yabridge/yabridge-host-32.exe'

/home/kporkka/.wine/drive_c/Program Files/AAS/VSTplugins/ Tassman4Vst_Effect.dll :: VST2, 64-bit, synced Tassman4Vst_Synth.dll :: VST2, 64-bit, synced

[robbert-vdh]

The plugin is indeed 64-bit. If you take a look at the log, you'll notice the following lines when the plugin's editor is being opened:

18:11:51 [Tassman4Vst_Synth-6Dacefhq] [Wine STDERR] 00c4:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 18:11:51 [Tassman4Vst_Synth-6Dacefhq] [Wine STDERR] 00c4:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."

Which sounds like there's something very wrong with your system. Are you using Wayland? If so, switch to Xorg and check if Wine can create windows there.

[kporkka]

Thank you for the quick comment.

Standard Pop!_OS 22.04 install, no wayland. We re-install everything, just trying to find a way to uninstall wine and yabridge.

[robbert-vdh]

You'll also want to use Wine Staging, rather than the non-staging Wine you're using now.

[kporkka]

Perhaps you could update the WineHQ link to the Wine staging page, if that is preferred. All and all, the instructions are excellent.

Your comment got me thinking about an issue with the NVDIA graphics card drivers (I have the latest ones). Switched to integrated GPU (thus disabling NVDIA) and now everything works. And incredibly well I must say, with a very low latency. Perhaps this is good to know for other (rare) users with laptop NVIDIA cards (mine is ThinkPad P15)

Thanks for making this happen. TBH, had serious doubts this would ever work :)

[robbert-vdh]

The is mentioned in the readme at the very start of the usage section:

Users of Debian, Ubuntu, Linux Mint and Pop!_OS should install Wine Staging from the WineHQ repositories as the Wine versions provided by those distro's repositories may be too old to be used with yabridge.

But great to hear you got it working in the end!