Dev with VST3 SDK : my plugin is not detected
-
- KVRer
- 4 posts since 1 Feb, 2010
Hi,
I'm quite new with VST SDK and C++. I have only already customized AGain to make an overdrive, added parameters etc...
I wanted to build a new plugin. So I copied AGain project (Visual C++ Express 2008), changed file names, class names, etc, and made my new plugin (a simple tremolo) with it.
It compiles well. The .vst3 file goes where it has to. Fine.
But the problem is : PluginTestHost and Cubase do not detect this plugin. It's like it didn't exist.
What can be the problem, how can I debug that ?
Thanks a lot!
Benoît
I'm quite new with VST SDK and C++. I have only already customized AGain to make an overdrive, added parameters etc...
I wanted to build a new plugin. So I copied AGain project (Visual C++ Express 2008), changed file names, class names, etc, and made my new plugin (a simple tremolo) with it.
It compiles well. The .vst3 file goes where it has to. Fine.
But the problem is : PluginTestHost and Cubase do not detect this plugin. It's like it didn't exist.
What can be the problem, how can I debug that ?
Thanks a lot!
Benoît
-
- KVRAF
- 1940 posts since 16 Aug, 2004 from Vienna, Austria
Did you create a new GUID for it, too?
Regarding debugging: my VSTHost should be able to load your PlugIn, if it really is a valid VST3 PlugIn.
Assuming Visual Studio .NET/2003/2005/2008, simply specifying
X:\whereveryouinstalledit\vsthost.exe
as debugging command with the parameters
/noload /nosave "$(CommonProgramFiles)\VST3\Steinberg\$(ProjectName).vst3"
should be enough. Set breakpoints, press F5.
Regarding debugging: my VSTHost should be able to load your PlugIn, if it really is a valid VST3 PlugIn.
Assuming Visual Studio .NET/2003/2005/2008, simply specifying
X:\whereveryouinstalledit\vsthost.exe
as debugging command with the parameters
/noload /nosave "$(CommonProgramFiles)\VST3\Steinberg\$(ProjectName).vst3"
should be enough. Set breakpoints, press F5.
-
- KVRAF
- 3948 posts since 8 Sep, 2003 from germany
There's also this VST3-Validator inside the SDK which runs a couple of tests with your plugin. It sure helped me to understand a couple of other things VST3 related.
m i d i - v s t (free)
-
- KVRer
- Topic Starter
- 4 posts since 1 Feb, 2010
Thanks too for VSTHost and breakpoints, that's really a basic tool that will be very very useful.
Note : my Tremolo works now
Next step, 50's Delay with a LPF \o/
Note : my Tremolo works now
Next step, 50's Delay with a LPF \o/
-
- KVRAF
- 1940 posts since 16 Aug, 2004 from Vienna, Austria
It may become clearer if you think about the fact that this is an acronym for Globally Unique Identifiertheredled wrote:What's the role of GUIDs ?
Cubase has always been notorious for requesting that each PlugIn has its own identifier.
