My vst3 wont show up....
-
So I have a strange one...
I have a Project - that compiles correctly (well without telling me it has any bugs, and by giving me a .vst3 file).
I load the vst3 into C:/Program Files/Common files/VST3/ChannelRobot/
where all my other vst3s are living, but it wont show up in Reaper. I've double checked its Plugin Code and Bundle identifier, and I see Reaper scanning it when I ask Reaper to rescan my plugin folders, but it never shows up as loadable..
It's an FX plugin.
I cant think of anything else that might be wrong with it..
Any ideas?
-
@Lindon Are you trying to re-open previously saved DAW project and can't the DAW see the plugin?
Or no vst3 recognization at all?
-
@Fortune said in My vst3 wont show up....:
@Lindon Are you trying to re-open previously saved DAW project and can't the DAW see the plugin?
Or no vst3 recognization at all?
I'm opening a previously saved DAW project in which the plugin in question is NOT saved or present, and creating a new track and asking Reaper to add a plugin to the track. Reaper shows me all the plugins on this machine - EXCEPT the one in question...
-
@Lindon You're definitely looking in the VST3 column of Reaper's plugin list and not the VST3i column?
What does pluginval say?
-
@d-healey said in My vst3 wont show up....:
@Lindon You're definitely looking in the VST3 column of Reaper's plugin list and not the VST3i column?
What does pluginval say?
yeah I forgot to run pluginval I should go away and do that.. hang on.
-
@Lindon oh wow - the plugin is crashing pluginval on scan....
-
When I started to test my first plugins in my DAW, I had the problem that the last one wasn't showing up. It turned out the culprit was that 2 different plugins were using the same 'Plugin Code' like (Abcd). Have you checked that?
-
@Frankbeat That's usually only an issue on MacOS (with Logic).
-
@Frankbeat said in My vst3 wont show up....:
When I started to test my first plugins in my DAW, I had the problem that the last one wasn't showing up. It turned out the culprit was that 2 different plugins were using the same 'Plugin Code' like (Abcd). Have you checked that?
read my initial post...
-
@Lindon Firstly, I suggest you change the name and ID of the plugin and re-compile it. As I see you've already done that.
So, are there controls that change the values of the parameters that are
isPluginParameter
enabled? If yes, you should make them alsoisMetaParameter
. Otherwise AU plugin validation fails. Maybe that could be related to VST3 too.Other possibility is compiled custom .dll nodes. If the target value and controller value ranges are different each other, that causes crash in DAW. So make sure that parameter ranges (including the middle points) are the same.