This project has moved. For the latest updates, please go here.
1

Closed

Opening Shell Assemblies

description

i have problems to open a dll which contains a lot of plugins. is there a way to list the plugins in the .dll and then open a specific one?

i have seen in the code that:
//case effShellGetNextPlugin:
/*{
System::String^ str;
result = _commandStub->GetNextPlugin(str);
TypeConverter::StringToChar(str, (char*)ptr, kVstMaxProductStrLen);
}*/
//break;
is commented out, was it working once? plugin shells report
effect->getCategory () == kPlugCategShell
it would be nice if we could catch that case. here is an example code from the vst SDK:

http://ygrabit.steinberg.de/~ygrabit/public_html/vstsdk/OnlineDoc/vstsdk2.3/html/plug/2.0/AudioEffectX.html#getNextSchellPlugin

greets!
Closed Sep 13, 2014 at 12:56 PM by obiwanjacobi

comments

obiwanjacobi wrote Dec 25, 2013 at 6:37 AM

VST.NET never supported ShellPlugins.

But I think we can do so now. Seems simple enough.

tebjan wrote Dec 25, 2013 at 9:14 PM

thanks for the reply, it would be great to have this option. if you load a vst and have the possibility to check whether its a shell plugin and then react accordingly with GetNextPlugin.

obiwanjacobi wrote Dec 26, 2013 at 11:50 AM

I have checked in an initial implementation that supports shell plugins in the Host-interop. Note that building shell plugins with VST.NET is still not possible - may do this later.

I have searched all my plugins but apparently none of them is a shell plugin (I don't own too many ;-)

I would appreciate it if you could get the latest source code and rebuild the VST.NET assemblies locally and give it a quick test run.

Thanx, Marc

wrote Sep 13, 2014 at 12:55 PM

wrote Sep 13, 2014 at 12:56 PM

Resolved with changeset 75412: Release 1.1 check in. Build script changes.