Search results

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.

This series of tutorials first appeared on my CreativeSynth.com website between 2001 and 2002. Due to their popularity (especially amongst new Max users), I have moved them to the Cycling74.com website.

In this interview, Tim Place speaks about his work as a developer and artist, charting the numerous development projects which pooled together to create Hipno.

Even before the Max for Live beta was opened up to the public, a community of testers was hard at work putting Max for Live through its pa...

built with max

This series of tutorials first appeared on my CreativeSynth.com website between 2001 and 2002. Due to their popularity (especially amongst new Max users), I have moved them to the Cycling74.com website.

Since we've changed the way that plug-ins are built, I realized that perhaps it'd be a good idea to find my humble little article and update it for use in the Current Dispensation.

Effective immediately, Cycling ’74 will discontinue sales of prebuilt Max-based audio plug-in packages. This includes Pluggo, Mode, Hipno, and UpMix. We will still continue to support current users as best we can, but there will be no further development on either the plug-in packages or their supporting technology.

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.