How does plugdata relate to Pure Data and Max?

Updated

plugdata is a modern fork of Pure Data, not a separate language or a Max clone. It keeps Pure Data's patching model and object ecosystem while adding a redesigned interface, DAW plugin export (VST3, AU, CLAP, LV2), code export, and bundled libraries. If you already know Pure Data, your patches and habits transfer directly. If you come from Max, the included Cyclone library is there to make you feel at home. If you know neither, plugdata is a visual environment where you build audio systems by dropping blocks onto a canvas and connecting them with cables rather than writing code.

The three-way relationship at a glance

Pure Data Max plugdata
Core model Visual patching Visual patching Visual patching (fork of Pure Data)
Relationship Original lineage Separate commercial lineage Fork of Pure Data
Interface Older, utilitarian Polished Reimagined, modern
Bundled libraries Core + externals you add Max objects + packages ELSE, Cyclone, Gem in the box
Plugin export Not built in Not the same workflow VST3, AU, CLAP, LV2
Code/hardware export Via external tools Limited Built-in Heavy/hvcc toolchain
Platforms Desktop Desktop macOS, Windows, Linux, iOS, BSD

The key takeaway: plugdata sits downstream of Pure Data, and Cyclone is the bridge that makes Max users comfortable.

plugdata vs. Pure Data

plugdata is Pure Data under the hood, reimagined. The site describes it as "a free, open-source patching environment based on Pure Data. Reimagined with a modern interface, DAW plugin version, code export and a curated set of objects."

What that means in practice:

  • Same patching paradigm. You still build with blocks and cables, and hear the result instantly. Skills and patches carry over.
  • Modern interface. The visual environment is redesigned rather than inherited.
  • Plugin export. You can load the same patch as a VST3, AU, CLAP, or LV2 plugin and automate it with MIDI like any other instrument.
  • Code and hardware export. A built-in Heavy/hvcc toolchain exports C/C++ code, flashes to an Electro-Smith Daisy, or produces real audio plugins.
  • Curated objects. It ships with ELSE for high-level abstractions on top of Pure Data, plus Cyclone and Gem.

So the difference is not the language — it's the packaging, tooling, and targets around it.

plugdata vs. Max

plugdata is not a fork of Max, and Max is a separate commercial product. The connection is compatibility of feel: plugdata bundles the Cyclone library specifically "so Max users feel right at home."

If you're a Max user evaluating plugdata, the relevant points are:

  • Cyclone gives you Max-style objects inside a Pure Data–based environment.
  • You gain plugin export (VST3, AU, CLAP, LV2) and code/hardware export as first-class features.
  • You move to a free, open-source, GPL-3.0 tool with no account required.

If your work depends on Max-specific objects or Max's own ecosystem, Cyclone covers familiarity, not full parity — treat it as a bridge, not a drop-in replacement.

What this means for choosing

  • Coming from Pure Data: adopt plugdata for the modern interface, plugin export, and bundled libraries without relearning patching.
  • Coming from Max: try plugdata if you want an open-source path with Cyclone-style objects and plugin/hardware export; verify the specific objects your patches rely on first.
  • New to patching: plugdata is a self-contained starting point — visual building, instant audio, and a curated object set, with no code required.

Where patches can run

The same patch can target several destinations:

  • Standalone — a native desktop app on macOS, Windows, and Linux.
  • Mobile — a native iOS app for iPad or iPhone, available in the App Store.
  • Plugin — VST3, AU, CLAP, or LV2 inside your DAW.
  • Hardware — compiled via Heavy/hvcc to C/C++, flashed to an Electro-Smith Daisy, or exported as a real audio plugin.

plugdata is free and open source under GPL-3.0, with no account required.