As exporting plug-ins is not currently available for Max 5, we will look at another alternative in this article based on a new feature of the poly~ object, which allows you to dynamically load new abstractions without recompiling the DSP. To help users explore this new alternative, we will demonstrate different ways to convert a Pluggo-ready patch made with MaxMSP 4.6 into a patch that you can load as a poly~ abstraction.
In an earlier article, Andrew Benson and Ben Bracken went through the process of connecting a guitar to a Max-based processing system, and creating a few guitar-oriented effects patches. In this series of articles, I will be building a Max-based guitar processing "rig", and will give you the opportunity to look over my shoulder as I design and implement this system.
This folder contains a number of extra externals which we use in the various Pluggo based plug-in packages. These externals are unsupported, contain features which may change at any point, and may not be maintained with regard to backwards compatibility. However, plug-in developers may find some of them useful, and you are free to include and distribute them with your plugs. In this article, I'd like to introduce a few of them, explain a little about how they work, and also demonstrate a couple of the tools we use to make our lives easier managing all of our plug-in packages.