Why won't TX16Wx plugin load?

Getting Stuff Done How do I .... ?
#1

I was successfully using a very old version of the TX16Wx plugin, but when its GUI started displaying gibberish, I decided to update it. After uninstalling and deleting all traces of TX16Wx, I installed the latest version. In Ardour, after removing stale plugins and re-scanning for plugins, the Plugin Manager and Plugin Selector each showed three TX16Wx plugins, with no indications of any errors.

I tried adding each of them to a MIDI track, and they all failed with the exact same error (except for the times), reporting this in the Log:

[ERROR]: VST: cannot load module from "V:\VST_plugins\VST2\TX16Wx.dll

I noticed that the VST3 plugins were trying to load from a VST2 dll, so in the Plugin Manager I checked the ā€œIgā€ (ignore) flag for the VST2 plugin. This removed the VST2 plugin from the Plugin Selector. I tried again to load the two VST3 plugins, but they failed with these dialogs:

The plugin "TX16Wx could not be loaded | See the Log window for more details (maybe)

The plugin "TX16Wx (legacy id) could not be loaded | See the Log window for more details (maybe)

This time there was no additional info in the Log.

I also looked at the TX16Wx plugins using OwlPlug, which found them without reporting any errors.

Iā€™ve seen in this forum that other people have been able to use TX16Wx successfully.
Does anyone have any idea why the latest version isnā€™t working for me?

Iā€™m running Ardour version 8.12.0 (rev 8.12) Intel 64-bit under Windows 10.0.19045.4291.
The TX16Wx version is 3.7.0n (x64).

Thank you!

ā€“ Ed

Some additional info:

Here is some of the detail info for the VST2 plugin from the Plugin Manager:

Callback opcode = 16 (ignored)
Callback opcode = 17 (ignored)
Found Plugin: '61XT' TX16Wx
VST2Cache
	binary="V:\VST_plugins\VST2\TX16Wx.dll" 
	arch="x86_64"
	id="1415065910"
	name="TX16Wx"		creator="CWITEC"		category="Instrument"
	version="" 
	n_inputs="2"			n_outputs="24"
	n_midi_inputs="1"		n_midi_outputs="1"
	is_instrument="1"		can_process_replace="1"		has_editor="1"

Here is some of the detail info for the two VST3 plugins from the Plugin Manager (they both have exactly the same info):

Class: 0 'TX16Wx' 'Audio Module Class'
Class: 1 'TX16Wx (legacy id)' 'Audio Module Class'
Found Plugin: TX16Wx
Found Plugin: TX16Wx (legacy id)
VST3Cache  
	bundle="V:\VST_plugins\VST3\TX16Wx.vst3" 
	module="V:\VST_plugins\VST3\TX16Wx.vst3\Contents\x86_64-win\TX16Wx.vst3"
	VST3Info
		uid="C4D8BD1A074B1188285DC2AA09B619A4" 
		name="TX16Wx"		vendor="CWITEC"		category="Instrument|Synth" 
		version="3.7.0n 7587.1313"		sdk-version="VST 3.7.14"
		n_inputs="0"			n_outputs="24" 
		n_aux_inputs="2"		n_aux_outputs="0" 
		n_midi_inputs="1"		n_midi_outputs="1"
	VST3Info
		(same info as previous VST3Info, except...)
		uid="C4D8BD1A1188074BAAC25D28A419B609"
1 Like
#2

Iā€™ve had a similar nightmarish headache with TX16Wx as of late as wellā€¦
-And Iā€™m on macOS Mojave.

Whether itā€™s the latest version of TX16wx, or some older ones Iā€™ve tried, eventually my Ardour projects literally fail to loadā€¦ -until I delete the plugin from my computer, and then Ardour will open, warn me, and simply replace the missing instances of it with a blank ā€˜stubā€™.

I would guess that itā€™s probably something to do with TX16wx itself, so for now, Iā€™m just going to abandon it, and perhaps alert its creators to this issue.

It sucks to have to do this thoughā€¦ Because it seems to be a really sweet/capable pluginā€¦

:confused:
-J

[Edit/Update: I just submitted a post/report here about it: https://www.kvraudio.com/forum/viewtopic.php?t=626262]