View on GitHub


Purr Data - Jonathan Wilkes' cross-platform Pd-l2ork version

Jonathan Wilkes’ Purr Data is an improved version of Miller Puckette’s Pd. It is based on Ico Bukvic’s Pd-l2ork, which in turn is a fork of Hans-Christoph Steiner’s Pd-extended.

This repository is a mirror of Wilkes’ original Gitlab repository available at We mainly use this as a one-stop shop to make it easy for you to get your hands on the latest source and the available releases, including pre-built packages for Linux, macOS and Windows.

Here’s a quick shopping list:

There’s also a video up on YouTube of the presentation Meet the Cat: Pd-L2Ork and its New Cross-Platform Version “Purr Data” at the Linux Audio Conference 2017 (Jean MONNET University, Saint-Etienne).

Enjoy your stay!

About Purr Data

Pd (Pure Data) is a graphical data-flow programming environment which is geared towards real-time interactive computer music and multimedia applications. It is a full-featured open-source alternative to its commercial sibling, Cycling74’s Max.

Purr Data serves the same purpose, but offers a new and much improved graphical user interface and includes many 3rd party plug-ins. Like Pd, it runs on Linux, macOS and Windows, and is open-source throughout.

Purr Data running on macOS.

Purr Data also offers some notable advancements over “classic” Pd-l2ork:

Purr Data continues to offer all of Pd-l2ork’s GUI and usability improvements, a help browser giving access to help patches in PDDP (Pd Documentation Project) format, and a large collection of bundled 3rd party externals, while using a recent version of Pd’s tried and proven real-time engine under the hood.

The Name?

Purr Data is the official nickname of the Pd-l2ork 2.x branch. Quite obviously the name is a play on “Pure Data” on which “Purr Data” is ultimately based. It also raises positive connotations of soothing purring sounds, and makes for a nice logo. 😺


The easiest way to get up and running on Mac and Windows is to use one of the available binary packages and installers available from the Github releases page. Generally you can just double-click these packages and go through the usual (platform-dependent) installation process.

Linux users: On OBS we provide the JGU packages for a variety of Linux distributions, see below. If your Linux distro is not among any of these then sorry, you’ll just have to bite the bullet and build Purr Data from source. (It’s not that hard any more once you got all the required dependencies installed, but it may take a little while.)

JGU Packages

This is a collection of ready-made Linux packages for Arch Linux, Fedora, and recent Debian, Raspbian and Ubuntu releases, maintained by Albert Gräf from the Johannes Gutenberg University (JGU) at the OBS (Open Build System). They offer the following advantages:

Please refer to the Installation wiki page for more information and detailed installation instructions.

Building from Source

This is just a brief summary. Please check the Installation page in the wiki for more information.

Purr Data is a big package with many parts and many dependencies, building it from source can take a long time, even on modern hardware. So please be patient! :)

To build Purr Data from source, you’ll have to clone the git repository as follows:

git clone

Or, if you prefer to build straight from Wilke’s upstream repository:

git clone

Make sure that you have all the requisite dependencies installed (Linux, Mac, Windows), then run make in the toplevel source directory:


On Debian/Ubuntu, Mac and Windows this should leave the ready-made package in the toplevel source directory. Install this as usual. On other Linux systems you can run the following command instead (this also works on Debian/Ubuntu, if you prefer this method or if you don’t have the Debian packaging tools installed):

sudo make install

You can uninstall the software again as follows:

sudo make uninstall

Afterwards, to clean the source directory:

make realclean

Note that this puts the source into pristine state again, like after a fresh checkout, so that you can run make from a clean slate again. Also, all build artifacts will be gone, and hence you won’t be able to run make install or make uninstall any more. So you want to do this only after you’ve finished the installation process.

Good luck!