Dec 10, 2009 at 8:06 AM
Edited Dec 10, 2009 at 8:42 AM
Absolute newbee, trying to get a feel for the VST.NET library by setting up the sourceprojects, looking through the samples and trying to get the meaning of it all.
I Think that I now understand the relation between the host (in my case Cubase), the (renamed) interop and the plugin itself. As I understand it, the interop is a decoupling of the lowlevel connectivity with the host, so that the host "sees" this
as the plugin, never knowing that it is just a "facade" to the vst.net plugin. (correct me if I'm wrong).
Everything compiles nicely and I have made the sugested post-compile scripts, renaming/copying the interop to a folder along with individual plugin assemblies. So far so good.
To get an idea about the implementation of the plug-ins created using VST.NET I copied the newbuild (and renamed) .dlls (specifically Jacobi.Vst.Samples.Delay.dll and Jacobi.Vst.Samples.Delay.net.dll) to the vst-plugins dir of my host (Cubase SX3)
when starting up Cubase after this it "sees" the plugins, but never loads them. They stay in the "brown" group of unloaded plugs in the plugin-information dialog in Cubase and are inaccessible.
I am not really sure if it is correctly understood, but I guessed that the host.exe (in the vst.net samples) would be a simulation of a vst-host, alowing you to try to load the plugins in a "friendly environment", thus exploring the exposed
parameters and so on. Having this idea, I tried to load them here, but never got that far. I got a stackoverflow error from within the vst.core (which I cannot debug) on the OpenPlugin method (host's mainform) when it tries to create the plugincontext
for the plugin.
I tried (both in Cubase and the host.exe) with both my own compilation of the samples and with the allready compiled samples from the download, but with the exact same results.
What am I missing here ?
PS.: I have tried compilng, using both .NET 2, 3.5 and 4 but with the same results.