Steven,
I'm part of an ongoing discussion in the VST EFFECTS PLUGIN topic; please see my posts starting here:
https://getmusicbee.com/forum/index.php?topic=13022.msg134192#msg134192Specific issues include:
-----------------------------------------------------------------
1. Plugin scanning crashI've installed the VST Effects plugin in MusicBee 3.1. In Preferences, I changed the VST location to my preferred 32-bit VST plugin location.
When I restarted MusicBee, initially (for about 2 seconds) it looked like it was scanning plugins. Then I get the error:
"Runtime Error! Program: C:\Program Files (x86)\MusicBee\MusicBee.exe R6016 -not enough space for thread data"
The error dialogue provides an OK button, but when I click it the same error immediately pops up repeatedly. There is no way to proceed except to crash MusicBee via the Task Manager.
I've tried restarting MusicBee a few times, but the errors occur almost immediately.
I am using high-quality plugins that do not cause any crashes whatsoever in DAWs and several other VST hosts, neither during initial scanning of the entire batch of plugins in those hosts, nor with actual use of the plugins. I have hundreds of VST plugins, so trying to add them one-by-one to figure out which ones are (possibly) problematic would be extremely tedious. Plus, the error MusicBee is providing looks more like a resource overwhelm issue as opposed to a specific plugin issue. I suspect something is wrong with the MusicBee VST scanning process itself, rather than the plugins.
-----------------------------------------------------------------
2. VST Plugin Host doesn't work with my pluginsJust to get around issue #1 above, I've created a unique MusicBee VST folder, set the MusicBee VST plugin to use that folder, and copied just one core monitoring plugin, Sonarworks Reference 4, into the folder.
MusicBee successfully scans the Sonarworks plugin and lists it under "Equaliser and DSP Settings", which is good. I can activate the Sonarworks plugin, launch the plugin interface and make edits. The problem is, anytime I make a change to the plugin, the change is not reflected in the audio output unless I uncheck (deactivate) and recheck (activate) the plugin again in the Equaliser and DSP Settings window. I can literally perform the most audio-mangling changes in the plugin interface, and nothing changes in the actual processing until I uncheck and recheck the plugin. Effectively, it seems like the MusicBee VST plugin just takes a single snapshot of the Sonarworks plugin settings at activation and uses those, regardless of changes, until the plugin is deactivated and reactivated.
I tried another plugin, DMG Audio's TrackControl, and making changes in its interface does nothing to the audio output whatsoever, even after deactivating and reactivating the plugin.
-----------------------------------------------------------------
At this time, it appears the MusicBee VST plugin may be in a fairly broken state. Other users are reporting this issue in the aforementioned thread. The plugin host obviously works with some plugin selections, but it's looking like some of the basic plugins I'd want to use simply don't work through its hosting mechanism.
I'm currently using a workaround combination of Winamp VST Host (
http://www.pcjv.de/applications/winamp ) plus
Blue Cat PatchWork, but I'd rather not rely on the old, non-maintained Winamp VST host. I'd prefer to use the native host you wrote for MusicBee.
I would be glad to test a debug version. Can you help?