Skip to content
Snippets Groups Projects
Forked from Jonathan Wilkes / purr-data
Loading
README.md 14.28 KiB

Pure Data L2ork

maintainer: Ivica Bukvic ico@vt.edu

maintainer: Jonathan Wilkes jancsika@yahoo.com

One Paragraph Overview

Pure Data (aka Pd) is a visual programming language. That means you can use it to create software graphically by drawing diagrams instead of writing lines of code. These diagrams show how data flows through the software, displaying on the screen what text-based languages require you to piece together in your mind.

Flavors of Pure Data

There are currently three main distributions of Pure Data:

  1. Pd-l2ork. Version used by Ivica Bukvic for his laptop orchestra. This guide is for Pd-l2ork.
  2. Pure Data "Vanilla". Miller Puckette's personal version which he hosts on his website and maintains. It doesn't include external libraries like objects for doing graphics, video, etc.
  3. Pure Data Extended. A monolithic distribution which ships with lots of external libraries. As of August 2015 it hasn't been updated since January 2014.

Three Paragraph Overview

Pd has been designed with an emphasis on generating sound, video, 2D/3D graphics, and connecting through sensors, input devices, and MIDI as well as OSC devices.

Pd has a special emphasis on generating audio and/or video in real time, with low latency. Much of its design focuses on receiving, manipulating, and delivering high-quality audio signals. Specifically, the software addresses the problem of how to do this efficiently and reliably on general purpose operating systems like OSX, Windows, Debian, etc.-- i.e., systems designed mainly for multi-tasking.

Pd can easily work over local and remote networks. It can be used to integrate wearable technology, motor systems, lighting rigs, and other equipment. Pd is also suitable for learning basic multimedia processing and visual programming methods, as well as for realizing complex systems for large-scale projects.

Goals

Pd-l2ork has the following goals:

  1. Documentation. We like documentation. It's like code, except friendly.
  2. Be reliable. Binary releases must be usable for performances and installations. The git repo must always be in a workable state that can be compiled. Regressions must be fixed quickly.
  3. Be discoverable. Undocumented features are buggy. Missing help files are bugs. Patches for new functionality that lack documentation are spam.
  4. Be consistent. Consistent interfaces are themselves a kind of documentation. We like documentation, so it follows that we like consistent interface.s

Installation Guide

To install using a pre-compiled binary, follow these instructions: http://l2ork.music.vt.edu/main/?page_id=56

To set up a development environment, first make sure you have the following package dependencies listed here: http://l2ork.music.vt.edu/main/?page_id=56

Then follow the steps outlined here: http://l2ork.music.vt.edu/main/?page_id=56#install-dev