;; this sound was generated with the following code. see profile.

\[
	\[
		.15 coin \[0] \[
			\[(1 100 xrand 0 urand lfpulse) (1 40 xrand 0 urand lfpulse 0 8k rand * 20 2k xrand +) *] 3X +/ = freq
			freq 0 .5 lfpulse 4m 8c xrand * .5 hpf2 0 3 rand lfnoise0 .8 * 4m lag pan2  .1 .35 rand aa 3 combl
		] if
	] 6 1 4 2 oltx
] = data-space
data-space 56 4 fadeout conormalize "data space" >sfo

Data Space 2

/////   Ecosystemic electroacoustic music   /////


I'm a drummer, composer, programmer living in Milan, Italy. 
My recent work revolves around real-time ecosystemic composition practices: creating situated sonic ecosystems that are in deep dialogue with their host space. Adaptive systems that can auto-regulate (or semi-autoregulate) and shape a dynamic sound form emerging from interactions between the space and a digital system (pure electronic or electroacoustic). 
Usually involved are:

	if indoor
- acoustic drums and percussions + digital signal processing (improvisation or with score)
- digital signal processing of the results of excitation carried out on the surfaces/structures/furniture/inhabiting objects of the host space, via actuators and other means 

	if outdoor
-the sounds autochtonous to a particular soundscape I’m in at the moment (currently running the newborn project "The Ecosystemic Camper")


/////   I ask space how to generate sound   /////

This account contains examples from a programming language for audio.
This language is still very experimental and is not available. 

WHAT

This programming language is called:

"A tool for the expression of sound as pure form."

It is an interpreter for a language for creating and transforming sound. The
language is mostly functional, stack based and uses postfix notation similar to
FORTH. It represents audio and control events using lazy, possibly infinite
sequences. It intends to do for lazy sequences what APL does for arrays: provide
very high level functions with pervasive automatic mapping, scanning, and
reduction operators. This makes for a language where short programs can achieve
results out of proportion to their size. Because nearly all of the programmer
accessible data types are immutable, the language can easily run multiple
threads without deadlock or corruption.

WHY

Other languages that inspired this one:
    APL, Joy[1], Haskell, Piccola[2], Nyquist[3], SuperCollider[4].

APL and FORTH (from which Joy derives) are both widely derided for being
write-only languages. Nevertheless, there has yet to be a language of such
concise expressive power as APL or its descendants. APL is powerful not because
of its bizarre symbols or syntax, but due to the way it automatically maps
operations over arrays and allows iterations at depth within arrays. This means
one almost never needs to write a loop or think about operations one-at-a-time.
Instead one can think about operations on whole structures.

Here is a great quote from Alan Perlis[5] on APL, which that also reflects my
interest in this way of programming :
"What attracted me, then, to APL was a feeling that perhaps through APL one
might begin to acquire some of the dimensions in programming that we revere in
natural language — some of the pleasures of composition; of saying things
elegantly; of being brief, poetic, artistic, that makes our natural languages
so precious to us."

The Joy language introduced concatenative functional programming. This generally
means a stack based virtual machine, and a program consisting of words which are
functions taking an input stack and returning an output stack. The natural
syntax that results is postfix. Over a very long time I have come to feel that
syntax gets in between me and the power in a language. Postfix is the least
syntax possible.

There are several reasons I like the concatenative style of programming:
    Function composition is concatenation. 
    Pipelining values through functions to get new values is the most natural
        idiom.
    Functions are applied from left to right instead of inside out. 
    Support for multiple return values comes for free. 
    No need for operator precedence. 
    Fewer delimiters are required: 
        Parentheses are not needed to control operator precedence.
        Semicolons are not needed to separate statements.
        Commas are not needed to separate arguments.


When I am programming interactively, I most often find myself in the situation
where I have a value and I want to transform it to something else. The thing to
do is apply a function with some parameters. With concatenative programming this
is very natural. You string along several words and get a new value.


REFERENCES    

1. http://www.kevinalbrecht.com/code/joy-mirror/joy.html

2. http://scg.unibe.ch/research/piccola

3. http://www.cs.cmu.edu/~music/nyquist/

4. http://supercollider.sourceforge.net

5. http://www.jsoftware.com/papers/perlis78.htm


Acá subo arte sonoro y likeo cumbias pa la peda. 
#UnConejoPerdidoEnLoVirtual

