From 491d6920d2167707c1676503b8720d3588ec23e1 Mon Sep 17 00:00:00 2001 From: Guenter Geiger Date: Mon, 17 Feb 2003 09:32:27 +0000 Subject: This commit was generated by cvs2svn to compensate for changes in r403, which included commits to RCS files with non-trunk default branches. svn path=/trunk/; revision=404 --- htdocs/index.html | 227 +++++++++++++++++++++++++++++++++++++++++ htdocs/pd.css | 88 ++++++++++++++++ htdocs/pure-data.htm | 76 ++++++++++++++ htdocs/subprojects.html | 266 ++++++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 657 insertions(+) create mode 100644 htdocs/index.html create mode 100644 htdocs/pd.css create mode 100644 htdocs/pure-data.htm create mode 100644 htdocs/subprojects.html (limited to 'htdocs') diff --git a/htdocs/index.html b/htdocs/index.html new file mode 100644 index 00000000..a83b158a --- /dev/null +++ b/htdocs/index.html @@ -0,0 +1,227 @@ + + + +Pure Data External Repository + + + + + + + +

Pure Data External Repository

+ +

+I think it is certainly true that the open-source movement is a very powerful +source toward higher-quality software, and I would turn the question around and +ask if open-source music wouldn t also be a very good thing. +
MSP + + +

Introduction

+ +The Pure Data external repository is meant to be a place where developers of +externals for the Pure Data computer music system can put their code. For +information about PD, look at the Pure Data +website. +

+ +PD has a huge user base and we all enjoy working with PD. A lot of externals +are being written and published on the web. As a consequence, it has become +increasingly hard to have an overview of all the externals. A central code +repository will offer this, as well as many other advantages. It will be easier +to manage the code, update orphaned externals, distribute compiled versions for +different systems, avoid duplication of effort, collaborate on improving the +same external, and finally the users have the advantage of being able to +download it from one single place. +

+ +I could go on listing the advantages, but there is one big disadvantage. We +have to work on it in order to make it a success. We have to learn CVS and we +have to import our projects into the repository. I think it is worth this work, +because you gain a lot too. If you don´t have the time to get into this, but +still agree that your external becomes part of the repository, just send an email with the information how to +download your code. +

+ +Another drawback is that your code has to be GPL'd. If this is a problem for +you, let us know. + +

Projects at the Pure Data Repository

+There is a list with short descriptions of the Externals currently in the Repository + +

Accessing the Externals via CVS

+ +You have to install cvs. On most Linux systems this is already installed, on +Windows or Mac OS/X you will have to download it from the net. Then, if you have cvs +installed (this example is assuming the commandline version) use the following +line to login into the CVS server: +

+% cvs -d:pserver:anonymous@cvs.pure-data.sourceforge.net:/cvsroot/pure-data login 
+

+ +Hit return when you are asked for a password. In order to get the source: +

+% cvs -z3 -d:pserver:anonymous@cvs.pure-data.sourceforge.net:/cvsroot/pure-data co externals
+

+ +This will give you a local copy of the externals-directory in the repository. +After some time, if you want to get all the latest additions and updates, type +(in the externals directory): +

+% cvs -d:pserver:anonymous@cvs.pure-data.sourceforge.net:/cvsroot/pure-data update -d
+

+ +Without the -d only existing directories on your local copy get updated. +

+ +Currently building the externals works to same way it did before, just cd into +the external directory (e.g. cd vst) and read through the compilation +instructions. Later this process will be automated and you can build al the +externals in one go, or even download a precompiled archive for your system. +

+Some other modules in the repository include Pd abstractions or the developers +version of Pd. You can check these out by replacing the modulename with the +respective modulename. +

+For example check out the abstractions with: +

+% cvs -z3 -d:pserver:anonymous@cvs.pure-data.sourceforge.net:/cvsroot/pure-data co abstractions
+

+or Pd with + +

+% cvs -z3 -d:pserver:anonymous@cvs.pure-data.sourceforge.net:/cvsroot/pure-data co pd
+

+To check out the current developers' branch, which is tagged with "devel_0_36", use +

+% cvs -z3 -d:pserver:anonymous@cvs.pure-data.sourceforge.net:/cvsroot/pure-data co -r devel_0_36 pd
+

+You can find out the available branches in the pulldown menu on the project's +CVS-page +(or use "cvs -T ..."). +Browsing CVS +is a good way to see what else is in the repository anyway. +

+If you absoluetly cannot use CVS, there are nightly CVS-tarballs +of the whole project tree available (around 15 MB currently). +

Putting Your Externals in the Repository

+ +This description is mainly about Linux, if you are working with Windows, you +might try the procedure described in this tutorial. Let +us know if it works. +

+ +To contribute your pd externals to the repository you'll first have to register +yourself at sourceforge (making you an official developer of the project). Go +to sourceforge.net and click on the "new user" link on the upper left corner. +Then send an email with the user you +created and Guenter will add you to the pure-data developer list. +

+ +At the project page you +can see if you are already listed as a developer. The next step is to "import" +your source code. First make sure that your code is in a directory, and remove +everything from that directory that you don´t want to put under CVS. Compiled +code, for example, is not normally put into CVS. +

+ +Make sure you are in this directory and issue the command: +

+% export CVS_RSH=ssh
+% cvs -z3 -d:ext: developername@cvs.pure-data.sourceforge.net:/cvsroot/pure-data 
+  import externals/dirname developername source-dist
+

+ +Exchange "developername" with your sourceforge accountname and "dirname" with +the name of your externals directory. You have to import the source only +once for your external(s). +

+ +If all of this went well, move away your external directory (keep it as a +backup) and checkout the code with: +

+% cvs -z3 -d:ext:developername@cvs.pure-data.sourceforge.net:/cvsroot/pure-data 
+  co externals
+

+ +From this point on, if you are working in your externals directory, and want to +commit your changes to the server you just have to do +

+% cvs commit
+

+ +or +

+% cvs update
+

+ +to take a look at what you have changed. +

+ +All the information about where the repository is, the loginname etc, is in the +"CVS" directory, that should be part of your external directory now. +

+ +If you are still unsure about the workings, take a look at this introduction about using +CVS. + +

Contact

+ +All questions, suggestions should go to the PD Developer +mailing list. (Except if you want to ask to be added to the developer list on sourceforge). + +
+
+ + + +
+

+ + + +

+ + diff --git a/htdocs/pd.css b/htdocs/pd.css new file mode 100644 index 00000000..b6b5e233 --- /dev/null +++ b/htdocs/pd.css @@ -0,0 +1,88 @@ + +HTML { + background: #ffffff; + color: #000; + font-family: Verdana, Helvetica, Arial, Tahoma, sans-serif; + font-size: 8pt; +} + +BODY{ + padding: 5px; + font-family: Verdana, Helvetica, Arial, Tahoma, sans-serif; + font-size: 8pt; +} + +.footer { + background:#EEEEEE; + width: 650px; +} + +.bordered { + padding: 5px; +} + + +H1 { + color: #600; + border: solid 1px; + font-family: monospace; + padding: 5px; + background:#EEEEEE; +} + +H2 { + font-family: Courier, monospace; + border: solid 1px; + color: #000; + padding: 4px; +} + +H3 { + font-family: Courier, monospace; + border: solid 1px; + color: #000; + padding: 4px; +} + +pre { + color: #333333; + padding: 3px; + background:#EEEEEE; +} + +A { + text-decoration: none; +/* background: #FFFFFF; */ + color: #b00; +} + +A:hover { + text-decoration: underline; + /* background: #FFFFFF; */ + color: #003300 ; +} + +A.nonexistent { + background: #EEE; + color: #CC6600; +} + + + + +HR { + height:1px; + width: 75%; + /* background:#eeaa00; */ + background:#eee; + color:#000; +} + +P.small { + font-size: xx-small; + background:#fff; + text-align: right; + /*border: dotted 1px;*/ + padding: 5px; +} + diff --git a/htdocs/pure-data.htm b/htdocs/pure-data.htm new file mode 100644 index 00000000..36514141 --- /dev/null +++ b/htdocs/pure-data.htm @@ -0,0 +1,76 @@ + + +Pure Data External Repository + + + +

Pure Data External Repository

+ +

Introduction

+The Pure Data external reopsitory is meant to be a place where developers of externals +for the Pure Data computer music system can put their code. For information about PD, +look at the Pure Data website. + +

How to download the PD externals

+ +ANN:This is preliminary information, later it will be just downloading a source tarball or +the precompiled binary distributions. +

+You have to install cvs. On most Linux system this is already install, on Windows or MACOS/X +you will have to download it from the net (TODO: add link). +

+Then, if you have cvs install (this example is assuming the commandline version) use the following line +to login into the CVS server: +

+cvs -d:pserver:anonymous@cvs.pure-data.sourceforge.net:/cvsroot/pure-data login +

+hit return when you are asked for a password. +In order to get the source: +

+cvs -z3 -d:pserver:anonymous@cvs.pure-data.sourceforge.net:/cvsroot/pure-data co externals +

How to put your externals in the repository

+ +

Why you should care

+PD has a huge user base, we are all enjoying to work with PD. But sometimes when you do a big project +there are some things that you want to do, but it is not possible to do it by patching only. +Thats why so many different people wrote lots of externals for PD, and most of them (I hope so at least) +are putting them on the web for free download. +

+It has become increasingly hard to have the overview over all these externals, thats why we started this +external repository, where developers can add their externals. This way it will be easier to manage the +externals, update orphaned externals, distribute compiled versions for different systems, avoid duplication +of effort, and finally the users have the advantage of beeing able to download it from one single place. +

+I could go on listing advantages of this system, but there is one big disadvantage. We have to work +on it inorder to make it a sucess. We have to learn CVS, we have to import our projects into the +repository. I think it is worth this work, because you gain a lot too. If you don´t have the time to +get into this, but still agree that your external becomes part of the repository, just write me an email +(ANN: link to email). +

The procedure

+To contribute your pd externals to the repository you have to register yourself at sourceforge first. +(You will be a official developer of the project then). Go to sourceforge.net and click on the "new +user" link on the upper left corner. Then send me an email and tell me the user you created, I will add +you to the pure-data developer list then. +

+You can see at the +project page if you are already listed as +a developer. The next step is to "import" your source code. First make sure that your code is in a +directory, and remove everything from that directory that you don´t want to put under CVS. +Compiled code, for example, is not put into CVS, normally. +

+Make sure you are in this directory and issue the command:
+cvs -z3 -d:ext:developername@cvs.pure-data.sourceforge.net:/cvsroot/pure-data import externals/dirname developername source
+If all of this went well, move away your external directory (keep it as a backup) and checkout the code +with:
+ cvs -z3 -d:ext:developername@cvs.pure-data.sourceforge.net:/cvsroot/pure-data co externals + + + + + + diff --git a/htdocs/subprojects.html b/htdocs/subprojects.html new file mode 100644 index 00000000..3adca578 --- /dev/null +++ b/htdocs/subprojects.html @@ -0,0 +1,266 @@ + + + +Pure Data External Repository + + + + + + + +

Pure Data External Repository

+ +

sorry for the constant upheaval, at some point I'll get it right...
MSP + +

Projects at the Pure Data Ext. Repository

The following projects already have put their sources inside the Pure Data +External Repository: +

+	externals
+	|-- OSCx
+	|-- aenv~
+	|-- ann
+	|-- arraysize
+	|-- chaos
+	|-- creb
+	|-- cxc
+	|-- debian
+	|-- ext13
+	|-- footils
+	|-- ggee
+	|-- grill
+	|   |-- deljoin  
+	|   |-- delsplit  
+	|   |-- flext
+	|   |-- pguitest  
+	|   |-- idelay  
+	|   |-- namedobjs 
+	|   |-- pool
+	|   |-- prepend
+	|   |-- py
+	|   |-- vasp 
+	|   `-- xsample
+	|-- maxlib
+	|-- pdogg
+	|-- plugin~
+	|-- rhythm_estimator
+	|-- sprinkler
+	|-- susloop~
+	|-- svf~
+	|-- vbap
+	|-- vst
+	|-- zexy
+	`-- zhzxh~
+

+You also can browse the Repository contents at the projects CVS-Page. +

Missing externals

There are externals missing, I know. Please mail your descriptions to +fbar@footils.org. Thank you for your attention. + + +

OSCx

+OSC, OpenSoundControl for pd +
by jdl at xdv.org +

aenv~

+aenv~: asymptotic ADSR envelope generator; The output value approaches the +target values as asymptotes. +
(c) Ben Saylor +

ann

+/* ...this is an externals for comouting Aritficial Neural Networks... +
thikn aboiut this +
+
0201:forum::für::umläute:2001 +
*/ + +

arraysize

arraysize -- report the size of an array + +

chaos

+"Chaos PD Externals" a set of objects for PD which +calculate various "Chaotic Attractors"; including, Lorenz, Rossler, Henon +and Ikeda. Hopefully more will be on their way. +
Copyright Ben Bogart 2002 +

creb

+This is a collection of pd externals. No fancy stuff, just my +personal bag of (ahem) tricks... +
(c)Tom Schouten +

cxc

+-------------------------- +
cxc pd eternals library +
powered by zt0ln d4ta +
-------------------------- +
many useful externals. +

debian

+From the README.Debian: +
<possible notes regarding this package - if none, delete this file> ;) +

Debian users can check out all externals and build a Debian package of +most in one command. +

ext13

this ist ext13, another highly useful collection of externals for pd + +

footils

+externals for classic synthesis techniques like fm, granular, soundfont, ... +
flext-iiwu | rx7 | shabby | syncgrain +

ggee

+Your host's Guenther Geiger's ggee externals collection. They serve different +purposes, ranging from objects for building a simple User interface for pd +patches, to objects interfacing Perry Cooks STK, streaming audio over the LAN, +Filter implementations and other. +

grill

+Various externals, libraries and development tools by Thomas Grill (xovo@gmx.net). Synched to +www.parasitaere-kapazitaeten.net/ext. +Please see the following descriptions: + +

deljoin

join a list with delimiter + +

delsplit

split a delimited list-in-a-symbol +

flext

+flext - C++ layer for Max/MSP and pd (pure data) externals +
+This package seeks to encourage the development of open source software +for the pd and Max/MSP platforms. + + +

guitest

Experimental wrapper for writing GUI externals. + +

idelay

Interpolating delay line + +

namedobjs

retrieve named objects in a patcher +

pool

+pool - a hierarchical storage object for PD and Max/MSP + + +

prepend

prepend - just like in MaxMSP +

py

+py/pyext - python script objects for PD (and MaxMSP... once, under MacOSX and Windows) + +

vasp

VASP modular - vector assembling signal processor +

GOALS/FEATURES +
=============== +

+VASP is a package for PD or MaxMSP consisting of a number of externals extending +these systems with functions for non-realtime array-based audio data processing. +VASP is capable of working in the background, therefore not influencing eventual +dsp signal processing. + + +

xsample

+xsample - extended sample objects for Max/MSP and pd (pure data) + + +

maxlib

+maxlib - music analysis extensions library +

The objects can be very useful to analyse any musical performance. Some +of the objects are 'borrowed' from Max (they are not ported but +rewritten for Pd - cheap immitations). +maxib has recently been extended by objects of more general use and some +which can be use for composition purposes. See +http://www.akustische-kunst.org/puredata/maxlib/ +
(c) 2002 by Olaf Matthes +

pdogg

+Superior open source audio compression with OGG Vorbis has come to Pd. +
(c) 2002 by Olaf Matthes +

plugin~

LADSPA and VST plug-in hosting for Pd +

+This is a Pd tilde object for hosting LADSPA and VST audio plug-ins on Linux +and Windows systems, respectively. The LADSPA plug-in interface is supported +completely on Linux, while the VST 1.0 audio processing plug-in interface +(without plug-in graphics) is supported on Windows. +
Jarno Seppänen, jams@cs.tut.fi +

rhythm_estimator

This is a collection of Pd objects for doing rhythm (quantum) +estimation. +
Jarno Seppänen jams@cs.tut.fi and Piotr Majdak p.majdak@bigfoot.com + +

sprinkler

+'sprinkler' objects do dynamic control-message dissemination. +
+Given a list as input, a 'sprinkler' object interprets the initial +list element as the name of a 'receive' object, and [send]s the +rest of the list to that object. +
Bryan Jurish <moocow@ling.uni-potsdam.de> + +

susloop~

sample player with various loop methods (ping-pong, ... ) think tracker. + +

svf~

This is a signal-controlled port of Steve Harris' state variable filter LADSPA plugin
By Ben Saylor, http://www.macalester.edu/~bsaylor + +

vbap

Vector Based Amplitude Panning. Use, if you need to control sound locations +in space. + +

vst

VST 2.0 support external. It supports the "string" interface for +parameters as well as providing access to the graphical interface supplied by +the plugin's creator. VSTi's can have midi information supplied to them and +export automation data. All in all it provides a very flexable mechanism to use +VST plugins outside of the Cubase environment. This download is the compiled +external DLL and PDF help file. + +

zexy

the zexy external +

+general::
the zexy external is a collection of externals. Including matrix +operations. +

zhzxh~

by Ben Saylor http://www.macalester.edu/~bsaylor +Turns the input signal into a staticky, distorted mess. Comes with tone +control. + +

+ +
+ + +

+ + +

+ + -- cgit v1.2.1