Building VST Plugins
I’m still a bit confused.
is it possible right now to build vst plugins for win and osx with Max/MSP 5, and what do i need?
here’s what confuses me (first sentence, well and the second one, if they’re in max and they work like in the past, then why don’t they work with the first release? maybe i’m just stupid…):
in the changelist it doesn’t mention that vst building has been fixed: http://www.cycling74.com/version/version_5_0_4.html
and another question, do vst plugins also require the microsoft c runtime library? or can they be distributed normally.
i have another question:
did i get it correct, that pluggo plugins are basically VST/AU Plugins with additional features.
I can build normal VST Plugins with Max/MSP and they don’t require the user to install anything additional.
I can build pluggo VST Plugins with enhanced features like bus sending, the user will have to install the pluggo runtime.
also, is midi output possible when building a vst plugin?
> did i get it correct, that pluggo plugins are basically VST/AU
> Plugins with additional features.
No, there are two uses for the name Pluggo: One is a collection of
plug-ins (originaly exactly 74) made by cycling which can be bought
completely independent of Max (the can be hosted by VST/AU/RTAS/.
(Cyclings web site is more specific)
The other use is for building your own plug-ins with Max. This works
momentarily only in Max 4.x. If you have purchased Max 5, and want to
build your own plug-ins in Max, either download Max 4.6.3 and bulid them
in Max 4 or wait till the Max 5 compatible version of pluggo is out.
(There is no date announced yet…) If you never got into plug-in
building, its maybe wise to use the time till release with learning
> I can build normal VST Plugins with Max/MSP and they don’t require
> the user to install anything additional.
> I can build pluggo VST Plugins with enhanced features like bus
> sending, the user will have to install the pluggo runtime. correct?
No, you always have to install the pluggo runtime. They come also in a
small collection of free pluggos which install the runtime from cycling.
Look at it as a little advertisement for the full collection, its quite
usefull to have them in your plug-in folder anyway…
> also, is midi output possible when building a vst plugin?
This seems to depend on the host, some allow it, some don’t. One way to
get around host limitations is to use OSC instead of Midi…
There is a seperate list for dealing with all sorts of Pluggo issues btw…
Thanks for your reply, Stefan
ok, i got confused by the sentence "If you want to tweak your own plug-ins, you might want to consider Max/MSP, which includes everything you need to develop your own plug-ins."
but i missed the
"And the Pluggo Runtime Installer allows you to give your own plug-ins to everyone, regardless of whether they own Pluggo or not."
so i thought i can build plugins with max only. but i see the pluggo runtime is always required. hmm.
so one last question, is it possible to include/bundle the runtime next to the vst file so the user doesn’t even have to run the installer for the runtime? making it look like a "regular" plugin?
Sure – if you build your own installer we don’t mind if you include the Pluggo components in it.
Download and try the demo version of my Major Malfunction plugin – it
shows (for Mac anyway), how I bundled the Pluggo Runtime installer
within my own plugin’s installer, for a pretty seamless end user
experience. It also launches the AudioUnit Scan application once
At 8:56 AM -0700 7/31/08, Andrew Pask wrote:
>Sure – if you build your own installer we don’t mind if you include
>the Pluggo components in it.
202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X / Major
ok i get it now, thanks for the replies.
i was hoping the runtime could simply reside in the same directory as the plugin file. the problem is, that my software uses a fixed installer: download files > put in subdirectory.
so unfortunately this won’t work for me.