Unable to load the vst3 version into LightHost
Avnsx opened this issue · 5 comments
LightHost is a great open source repo to apply vst plugins system wide.
In my case I'm even using it with VoiceMeeter Banana to seperate system audio into tracks.
This works perfectly fine with every other vst plugin I've used, but unfortunately I'm encountering an issue with yours
For some reason the vst3 version of your plugin, doesn't let me use it in lighthost, it just unloads itsself or does not get initialised or whatever. It initally gets detected and then it's just gone
but the normal vst version is loaded and works fine, idk why
Where do you place VST2 and VST3 plugins? Because I cannot get LightHost to see any plugins I have, I'm placing plugins in C:\Program Files\Common Files\VST2
, C:\Program Files\Steinberg\VSTPlugins
, and C:\Program Files\Common Files\VST3
.
Just place them in the default paths that lighthost just pre-selected (or click on set custom path, up to you), you've to go to the bottom of the available plugins tab and then there's a options button. Once you click it it'll say scan for vst3 plugins and pretty sure after you're done scanning it'll initially find the vst3 plugin, but afterwards when you're supposed to left click and turn it active (in the system tray), the option is just not there and if you try to see if the vst3 plugin is still shown in the LightHost available plugins tab, it's not there either anymore. But then with your normal vst version, it's executed just fine and can be used with LightHost
This guy explains, the correct initialisation progress for LightHost and any VST Plugin: https://youtu.be/AyzQZScP2Sw?t=228
You need to left click on the lighthost tray icon to even get this menu
Anyway, yeah, my plugin disappears
I mean I would appreciate it, if you could fix this somehow, since it seems your plugin is initially compatible with LightHost and as you may know VST3 plugins, only consume CPU resources when the plugin is in use, so I am really looking forward to only have the plugin active when I am using my microphone and not all the time as it's taking resources constantly otherwise. Also I feel like LightHost is the easiest way to apply system wide vst plugins, so I guess it would increase the user reach of your vst plugin in general (or help people that can otherwise not initialise your plugin - I saw the other premiere pro issue ticket), as it offers a new platform everyone can use then (windows, macos, etc)
But obviously it's up to you, if you think this is worth your time go for it ☺
Also I recommend setting up sponsorships for this repo (through repo settings), I'm sure people will donate.
LightHost for some reason expects plugin to have stereo channels by default. Which is weird since vst3 allows dynamically specify channel configuration. Is it a quirk of an old JUCE LightHost is using? Or LightHost itself is mistaken here? Who knows.
I'd suggest using Equalizer APO as an up to date open-source host for plugins.