Should I re-install?

[irpacynot]

Here in the past few days, Tracktion (12 -- still haven't updated to 12.5 yet) rejects all plugins I've installed when scanning for plugins. Even stuff like Voxengo, companies I've other plugins from. It even gave me some type of Windows error regarding "data thread" or something of that nature. I know I have enough HD space, so I don't think it's that.

I wanna re-install, but I'm afraid of losing all of my project/existing plugin data in the process. Anyone done this before?

[jabe]

I've only reinstalled when getting a new machine.

Waveform 12 (and all versions from 8 or 9 onwards) have only had built-in support for 64-bit plug-ins. It rejects any that are 32-bit. Is there any chance that the ones you've tried are 32-bit? There is a way round it, which I haven't tried, but others have, and that is to use a bridging program. The usual choice appears to be JBridge.

[irpacynot]

I've only reinstalled when getting a new machine.

Waveform 12 (and all versions from 8 or 9 onwards) have only had built-in support for 64-bit plug-ins. It rejects any that are 32-bit. Is there any chance that the ones you've tried are 32-bit? There is a way round it, which I haven't tried, but others have, and that is to use a bridging program. The usual choice appears to be JBridge.

No, I purposely ignore any 32-bit plugins because I remember reading that when I first installed the software.

But I'll check out your recommendation.

[jabe]

Perhaps try the scan again and get some screenshots to post. Hopefully it'll be something someone recognises.

[pough]

I would try other things before re-installing Waveform. The plugin validator that is included in Waveform is also available as a standalone application with extra options.

https://github.com/Tracktion/pluginval

It's a handy way to test and investigate plugins.

[irpacynot]

Perhaps try the scan again and get some screenshots to post. Hopefully it'll be something someone recognises.

Will try to that and post back in a bit.

I would try other things before re-installing Waveform. The plugin validator that is included in Waveform is also available as a standalone application with extra options.

https://github.com/Tracktion/pluginval

It's a handy way to test and investigate plugins.

That does sound handy, thanks.

In the meantime, I ran an SFC scan in CMD. It did say it found and corrected errors. I tried reinstalling a couple of plugins, and scanned 'em. It didn't give me any error messages, but it also didn't show them in the plugins search.

Will try to install a completely new plugin and back to you guys.

[irpacynot]

This is the error I always receive.

[lmv]

Try this:
- Close Waveform.
- Open the folder where the settings are kept. I don't use Windows, but I think it's C:\Users\<username>\AppData\Roaming\Tracktion\Waveform
- Open the knownPluginList64.settings file with any text editor.
- Look for "BLACKLISTED id" probably at the end of the file.
- Delete all BLACKLISTED items you think you should.
- Open Waveform and rescan.

[pough]

Could it be the plugins? I downloaded wolf-shaper and it crashes pluginval.

UPDATE: I installed wolf-shaper and Waveform scans it okay. I added it to an Edit and that seemed fine. Note that I have Waveform set up to not open a plugin's UI automatically. When I tried to open it, there were several minutes of spinning torus and then surprisingly it did finally open. Closed it and tried to open it again; it takes several minutes to open and Waveform is completely unresponsive while it's trying to load.

I have a few other DAWs installed and it's useful to check out how they handle problematic plugins. I'm trying wolf-shaper in Reaper now... Same thing; takes several minutes to load.

[lmv]

Now I see wolf-shaper is a vst3 plugin. I hadn't even paid attention to the name of the plugin.

Is there any reason why you're running that instead of the vst2 version? I avoid vst3 and intend to avoid it for the next 10 years.

I had never heard of wolf-shaper and installed it. I run Linux, but I can (and I absolutely do) run Windows plugins thanks to linvst. Wolf-shaper vst2 loads and runs fine on Linux Waveform. The GUI loads instantly when I click it.

There is a separate linvst3 which also loads and runs vst3 wolf-shaper, but then I don't hear any changes to the sound - which I do with the vst2 dll.

Funny fact: there is a native Linux version, but it won't run on my system, probably because my distro is old, which I refuse to upgrade because I would lose things like I have lost before in previous distro upgrades. This is exactly why I prefer to use Windows plugins on Linux. Windows plugins never expire, even on Linux.

[pough]

Is there any reason why you're running that instead of the vst2 version?

Why VST3.png

I was trying to replicate your the problem.

[lmv]

It's not my problem, I'm not the original poster, and my question was directed at him.

[pough]

It's not my problem, I'm not the original poster, and my question was directed at him.

That explains why more than just my vision felt fuzzy as I was reading your post.

[irpacynot]

Try this:
- Close Waveform.
- Open the folder where the settings are kept. I don't use Windows, but I think it's C:\Users\<username>\AppData\Roaming\Tracktion\Waveform
- Open the knownPluginList64.settings file with any text editor.
- Look for "BLACKLISTED id" probably at the end of the file.
- Delete all BLACKLISTED items you think you should.
- Open Waveform and rescan.

I tried hunting down the file you referred to, but no luck I'm sad to say.

EDIT:

I was able to suss out how to show the hidden folders/files and delete those items and re-scan. However, I received these two errors, and nothing, it seems was added to the plugins:

[dellboy]

I downloaded wolfshaper, extracted it, and dropped just the VST3 into the VST3 folder. Started up Studio One Pro 6 and opened the VST. It completely crashed Studio One. Its a bad VST.