Personal tools
You are here: Home development Google Summer of Code PluggoPD
Views

Usecase

Pluggo is an application of Max/MSP that allows it to be run as a VST or Audio Unit plugin in any software that supports such extensions. It allows users of the software to rely upon the solid framework of their professionally crafted and solid DAW, in tandem with the versatility of using an open software environment to extend their creative efforts if needs be.

The user should be able to run one master app (a DAW like Cubase, Ardour, Ableton Live, or Digital Performer) and have all auxiliary Pd instruments loaded from there, so that they don't have to spend 30 mins of configuring and opening corresponding files and settings, stored in directories across the computer, as is the current state of this interoperability.

It's a known pain in the Pd community for users to have to adjust and load setting after setting. when it could instead all be saved in a nice project file in a professional sequencer application as with VST and Audio Unit plugins.

For those users who like what Pd has to offer as a bus insert, midi filter or general audio swiss army knife, it is undesirable to deal with multiples of files that are stored all over the place in different spots. This is a serious damper to the spontaneous real-time creativity that Pd promises to its user base.

A desirable outcome of this project would be to have a nice compact project space (i.e. the DAW project file) that contains all of the details of audio and midi routing between it and Pd in an intuitive way (i.e. such as VST and Audio Units provide). Being able save everything so that a user can open the project back up again exactly how it was saved in the DAW; including all automation and Pd devices. This would help to honor the general Pd promise of a touch-and-go, dive-right-in extendability, coupled with minimal headache on dealing with object persistence, midi loopbacks and bus names, sluggish graphical interfaces, and general confusion.

Managing automation in Pd has not been a quick and dirty thing for many of its users, who would prefer to leave that task to previously existing sequencing software. Having a custom synth, effect, midi chain filter or integrated graphics show work seamlessly from a standard DAW upon loading a single project file is the holy grail for the impulsive musician who wants to track their automation history and edit it with the cut and paste style that is the common idiom of sound design in our world today.

Having 5 programs open and trying to wrangle the routing between them for a half hour to get a song playing is less than ideal. A Pluggo for Pd would help minimize the time and frustration of this by compressing it all into one file that references a bank of subordinate plugins.

Implementation Issues

To support several plugin backends (vst, ladspa) the plugin wrapper naspro should be used (see http://sourceforge.net/projects/naspro/).

ATM Naspro is in early development, therefore it's probably a good idea to join the Naspro development where it's usefull, in order do avoid duplicate work.


comments:

Clam bindings --sunji, Tue, 17 Apr 2007 08:35:11 +0200 reply
it's possible that getting PD to interface with clam (http://clam.iua.upf.edu/wikis/clam/index.php/Main_Page) would have much the same effect as a pluggo type package. I only found Clam reading about Naspro earlier this evening, it's a pretty slick api- It's similar to gstreamer.



Powered by IEM Powered by Plone Section 508 WCAG Valid XHTML Valid CSS Usable in any browser