Re: [PD] Pd monosymphonia

2011-06-30 Thread Andrew Faraday

That's a fair enough comment, I could do quite a lot more to sweeten the sound, 
too (it's just a simple sine oscillator atm, as I was concentrating on the 
score building process.

The idea is one of the central things in a lot of these styles, sometimes it's 
placed above the actual realization of the piece. Although it is nice to craft 
as much of your sound as possible. 

 Subject: RE: [PD] Pd monosymphonia
 From: ro...@dds.nl
 To: jbtur...@hotmail.com
 Date: Thu, 30 Jun 2011 00:05:17 +0200
 
 On Tue, 2011-06-28 at 22:01 +0100, Andrew Faraday wrote: 
  That was one thing I wasn't sure about, although it does help with the
  kind of 'passive listening' part, something like Cage or Glass, where
  there is a huge amount of repetition and the value of the piece is
  discovered over time, almost as a meditative process. It's not for
  everyone, but it does lend itself to computer music
  
 
 from Cage i don't know about repetative music/scores, 
 but a.o. terry riley and steve reich did a lot with repetition and
 shifting patterns.
 i still love to listen to some of these old pieces like 'rainbows in
 curved air' (riley) or 'drumming' (reich).
 there's also composition nr.7 (1961) of La Monte Young: to play BF# for
 a long time. in certain circumstances with a number of participating
 musicians/voices this can be a wunderfull experience.
 
 maybe you know all this already.
 
 so to cut it short:
 for me your present soundscape is not yet interesting enough,
 where the patch cq the concept can be a good starting point.
 
 c'est tout.
 
 rolf
 
 
 
 
 
  ___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Pd monosymphonia

2011-06-28 Thread IOhannes m zmoelnig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2011-06-27 23:56, Andrew Faraday wrote:
 
 This is probably because I created it on the mac, there may be a syntax issue 
 with other operating systems...
 Usually the sends to create dynamic objects is titled pd-*Whatever's in the 
 title bar* it could be that in ubuntu or windows it's pd-BuildGen instead of 
 pd-BuildGen.pd ... 

unlikely.
it's Pd that does the dynamic creation not your operating system.

one of the big advantages of Pd is, that the patches are cross-platform.

you will have a hard time creating a _patch_ that runs on one platform
but not on another (and is not host-specific, e.g. doesn't use hardcoded
paths to the user's data disk E:\).
obviously things are a bit different when using externals that make use
of system specific capcabilities, but dynamic patching does not belong
into this realm.

fgmadsr
IOhannes
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4Jf4UACgkQkX2Xpv6ydvS9/QCg7DXytT1PsHUxNXHrZND9bljH
J9EAmgIhX0Y66NmAtgHxgckfUtswBE2j
=/gUp
-END PGP SIGNATURE-



smime.p7s
Description: S/MIME Cryptographic Signature
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Pd monosymphonia

2011-06-28 Thread Andrew Faraday

That was one thing I wasn't sure about, although it does help with the kind of 
'passive listening' part, something like Cage or Glass, where there is a huge 
amount of repetition and the value of the piece is discovered over time, almost 
as a meditative process. It's not for everyone, but it does lend itself to 
computer music

 Subject: Re: [PD] Pd monosymphonia
 From: ro...@dds.nl
 To: pd-list@iem.at
 CC: jbtur...@hotmail.com
 Date: Tue, 28 Jun 2011 01:04:45 +0200
 
 On Tue, 2011-06-28 at 00:16 +0200, pd-list-requ...@iem.at wrote:
  jbtur...@hotmail.com
 This is probably because I created it on the mac, there may be a syntax
 issue with other operating systems...
 [cut]
 'it's just in the name'
 i copied the patch from the text attachment and gave it just a name.
 but it does a SEND to itself called buildGen, alas..
 
 so it worked.
 i find the concept interesting,
 this specific soundscape less.
 i guess because for hearing the development the waiting for the 'new'
 part gets everytime longer, while being obliged to sit through the 'old'
 parts again and again and again.
 
 rolf
 
 
 
 
  ___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Pd monosymphonia

2011-06-27 Thread Andy Farnell


Hi Andrew,

That was very interesting to listen to to. Thanks
for sharing it. 

A couple of thoughts, though I may be missing
some important point; since you only keep a scope 
of the last 3 notes you could use float boxes
instead of creating tables on the fly. Also, 
the concept seems to be a base N counter, so
approaching this starting with an up-down counter
might simplify it.

Also [range] seems to be missing for me but easily
fixed with a multiply and an add.

best
andy.

On Sun, 26 Jun 2011 00:32:27 +0100
Andrew Faraday jbtur...@hotmail.com wrote:

 
 Hey Pders
 I've been messing with the idea of combining dynamic patching and generative 
 music. And after a few hours of work I've come up with a patch (attached) 
 which uses some rules to build a randomly generated piece of music who's 
 result I'm rather fond of. 
 On opening the patch, a 4-number array is generated, with a choice of 1 
 single note to choose from. It's played by a simple sine oscillator, then a 
 second iteration generates a second array, choosing from 2 notes (adding one 
 a semitone above), plays the two arrays in order, then generates a third, 
 with 3 notes to choose from, and so on. 
 As the piece progresses, the choice of notes playing through a sequence 
 that's always a low drone, expanding out to a more tangible mid-range, 
 usually coming up with melodic fragments, and then starting to use some 
 higher-pitched sounds. And all the time the feedback on a delay unit on the 
 output, of the system. 
 When the range of notes reaches 127, the feedback jumps from 60% to 90%, 
 changing the mood of the piece significantly, building to a harsh climax, 
 each frequency range of notes lasting into the next and gains more 
 significance. Like the perceived voices vying for position. 
 Eventually, when a note above midi 127 is played, the synth stops, and the 
 delay tail gradually fades out. 
 I've found this to be an unusually structured and dramatic piece of 
 generative patching. Initially a low drone, which pushes out and explores 
 into melodies, building ideas, and being repeatedly pushed back to it's 
 initial form. Then building into a repeating and expanding set of phases. 
 getting louder and busier. Then a change brings this to a head, and signifies 
 to the audience that the piece could end on any phase, building excitment to 
 an inevitable but always unexpected end. 
 
 
 Sorry, I've written quite a lot about this, but I thought the PD list might 
 be interested... If anyone could spare about 15 minutes to listen to the 
 patch in action, I'd love to hear what you think of the artistic result.
 
 Thanks in advance.
 Andrew 
 P.S. I do realize that I could clean this up a great deal. The addition of 
 [table] objects could just as easily be a single expanding array, I could 
 hide modules away in sub patches and the sliders used for visualization could 
 be more efficiently done with gem.   

-- 
Andy Farnell padawa...@obiwannabe.co.uk

___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Pd monosymphonia

2011-06-27 Thread Frank Barknecht
On Sun, Jun 26, 2011 at 12:32:27AM +0100, Andrew Faraday wrote:
 P.S. I do realize that I could clean this up a great deal. The addition of
 [table] objects could just as easily be a single expanding array, I could
 hide modules away in sub patches and the sliders used for visualization could
 be more efficiently done with gem.  

Regarding subpatches: I would do this kind of dynamic object generation in a
subpatch anyway instead of putting the new objects into the main patch. That
way, you can easily start with a fresh subpatch by sending clean to [s
pd-subpatchname] instead of having to manually delete the created
tables/objects.

Ciao
-- 
 Frank BarknechtDo You RjDj.me?  _ __footils.org__

___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Pd monosymphonia

2011-06-27 Thread rolf meesters
hi
i would like to listen to it, but:
i'm with pd-extended 42.5 on windows xp and/or ubuntu 9.10
i get error messages:

error: tab-1: no such object
print: table 1: 30 30 30 30
error: : no such array
... you might be able to track this down from the Find menu.
error: : no such array
error: : no such array
error: tab-2: no such object
print: table 2: 31 31 31 31
error: tab-1: no such array
error: tab-1: no such array
error: tab-1: no such array
error: tab-1: no such array

what's wrong?

gr,rolf
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Pd monosymphonia

2011-06-27 Thread Andrew Faraday

This is probably because I created it on the mac, there may be a syntax issue 
with other operating systems...
Usually the sends to create dynamic objects is titled pd-*Whatever's in the 
title bar* it could be that in ubuntu or windows it's pd-BuildGen instead of 
pd-BuildGen.pd ... 
This means it's not creating the object [table tab-1] to place the four notes 
into. Try changing that (towards the bottom right of the patch) When you get it 
right you should see the [table] objects start to appear in the top left of the 
patch, and, of course, start hearing music.


Date: Mon, 27 Jun 2011 11:16:48 +0200
From: rolfmeest...@gmail.com
To: pd-list@iem.at
Subject: Re: [PD] Pd monosymphonia

hi 
i would like to listen to it, but:
i'm with pd-extended 42.5 on windows xp and/or ubuntu 9.10
i get error messages:

error: tab-1: no such object
print: table 1: 30 30 30 30
error: : no such array

... you might be able to track this down from the Find menu.
error: : no such array
error: : no such array
error: tab-2: no such object
print: table 2: 31 31 31 31
error: tab-1: no such array
error: tab-1: no such array

error: tab-1: no such array
error: tab-1: no such array

what's wrong?

gr,rolf



___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list 
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Pd monosymphonia

2011-06-27 Thread Andrew Faraday

As I say, I could neaten this in a number of ways, I was considering some form 
of [loadbang] triggered script to delete the objects on creation, then use a 
delay to initialize the generative patch. Which would also solve the problem.

 Date: Mon, 27 Jun 2011 10:00:40 +0200
 From: f...@footils.org
 To: pd-list@iem.at
 Subject: Re: [PD] Pd monosymphonia
 
 On Sun, Jun 26, 2011 at 12:32:27AM +0100, Andrew Faraday wrote:
  P.S. I do realize that I could clean this up a great deal. The addition of
  [table] objects could just as easily be a single expanding array, I could
  hide modules away in sub patches and the sliders used for visualization 
  could
  be more efficiently done with gem.  

 
 Regarding subpatches: I would do this kind of dynamic object generation in a
 subpatch anyway instead of putting the new objects into the main patch. That
 way, you can easily start with a fresh subpatch by sending clean to [s
 pd-subpatchname] instead of having to manually delete the created
 tables/objects.
 
 Ciao
 -- 
  Frank BarknechtDo You RjDj.me?  _ __footils.org__
 
 ___
 Pd-list@iem.at mailing list
 UNSUBSCRIBE and account-management - 
 http://lists.puredata.info/listinfo/pd-list
  ___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Pd monosymphonia

2011-06-27 Thread Andrew Faraday

[range] is one of those objects I don't strictly need, but use for screen 
real-estate and speedy coding. It is cheating a little, mind.
All the generated notes are kept, so they do have to be stored somewhere, I do 
realize that this could be a single, expanding array. 
And yes, I did mostly share this because I felt it was quite an interesting bit 
of generative work... Now I just need somewhere to exhibit it. 

 Date: Mon, 27 Jun 2011 07:50:43 +0100
 From: padawa...@obiwannabe.co.uk
 To: pd-list@iem.at
 Subject: Re: [PD] Pd monosymphonia
 
 
 
 Hi Andrew,
 
 That was very interesting to listen to to. Thanks
 for sharing it. 
 
 A couple of thoughts, though I may be missing
 some important point; since you only keep a scope 
 of the last 3 notes you could use float boxes
 instead of creating tables on the fly. Also, 
 the concept seems to be a base N counter, so
 approaching this starting with an up-down counter
 might simplify it.
 
 Also [range] seems to be missing for me but easily
 fixed with a multiply and an add.
 
 best
 andy.
 
 On Sun, 26 Jun 2011 00:32:27 +0100
 Andrew Faraday jbtur...@hotmail.com wrote:
 
  
  Hey Pders
  I've been messing with the idea of combining dynamic patching and 
  generative music. And after a few hours of work I've come up with a patch 
  (attached) which uses some rules to build a randomly generated piece of 
  music who's result I'm rather fond of. 
  On opening the patch, a 4-number array is generated, with a choice of 1 
  single note to choose from. It's played by a simple sine oscillator, then a 
  second iteration generates a second array, choosing from 2 notes (adding 
  one a semitone above), plays the two arrays in order, then generates a 
  third, with 3 notes to choose from, and so on. 
  As the piece progresses, the choice of notes playing through a sequence 
  that's always a low drone, expanding out to a more tangible mid-range, 
  usually coming up with melodic fragments, and then starting to use some 
  higher-pitched sounds. And all the time the feedback on a delay unit on the 
  output, of the system. 
  When the range of notes reaches 127, the feedback jumps from 60% to 90%, 
  changing the mood of the piece significantly, building to a harsh climax, 
  each frequency range of notes lasting into the next and gains more 
  significance. Like the perceived voices vying for position. 
  Eventually, when a note above midi 127 is played, the synth stops, and the 
  delay tail gradually fades out. 
  I've found this to be an unusually structured and dramatic piece of 
  generative patching. Initially a low drone, which pushes out and explores 
  into melodies, building ideas, and being repeatedly pushed back to it's 
  initial form. Then building into a repeating and expanding set of phases. 
  getting louder and busier. Then a change brings this to a head, and 
  signifies to the audience that the piece could end on any phase, building 
  excitment to an inevitable but always unexpected end. 
  
  
  Sorry, I've written quite a lot about this, but I thought the PD list might 
  be interested... If anyone could spare about 15 minutes to listen to the 
  patch in action, I'd love to hear what you think of the artistic result.
  
  Thanks in advance.
  Andrew 
  P.S. I do realize that I could clean this up a great deal. The addition of 
  [table] objects could just as easily be a single expanding array, I could 
  hide modules away in sub patches and the sliders used for visualization 
  could be more efficiently done with gem.
   
 
 -- 
 Andy Farnell padawa...@obiwannabe.co.uk
 
 ___
 Pd-list@iem.at mailing list
 UNSUBSCRIBE and account-management - 
 http://lists.puredata.info/listinfo/pd-list
  ___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list


Re: [PD] Pd monosymphonia

2011-06-27 Thread Tyler Leavitt
I have been working on a generative patch of my own and have been
contemplating different methods of exhibiting it myself. In my school's art
department (of which I am majoring in) there is not much awareness of
computer/sound art, and I was thinking if I could get some other works to
display I could put together a sort of exhibit of Puredata/generative
patching...

I'm not sure how it would look, but I was considering something as simple as
a wall of 4 or 5 headphones on a hook that people could walk up to and
listen to at their leisure (kind of a play on the traditional method of
display for paintings). Maybe a little placard next to it with a blurb by
the artist about their methods/conceptions behind the work. I don't know...
I was going to further contemplate it before I asked the board, but since
you've brought it up...

Any other suggestions on how to exhibit generative patching?

Tyler


On Mon, Jun 27, 2011 at 3:01 PM, Andrew Faraday jbtur...@hotmail.comwrote:

  [range] is one of those objects I don't strictly need, but use for screen
 real-estate and speedy coding. It is cheating a little, mind.

 All the generated notes are kept, so they do have to be stored somewhere, I
 do realize that this could be a single, expanding array.

 And yes, I did mostly share this because I felt it was quite an interesting
 bit of generative work... Now I just need somewhere to exhibit it.


  Date: Mon, 27 Jun 2011 07:50:43 +0100
  From: padawa...@obiwannabe.co.uk

  To: pd-list@iem.at
  Subject: Re: [PD] Pd monosymphonia
 
 
 
  Hi Andrew,
 
  That was very interesting to listen to to. Thanks
  for sharing it.
 
  A couple of thoughts, though I may be missing
  some important point; since you only keep a scope
  of the last 3 notes you could use float boxes
  instead of creating tables on the fly. Also,
  the concept seems to be a base N counter, so
  approaching this starting with an up-down counter
  might simplify it.
 
  Also [range] seems to be missing for me but easily
  fixed with a multiply and an add.
 
  best
  andy.
 
  On Sun, 26 Jun 2011 00:32:27 +0100
  Andrew Faraday jbtur...@hotmail.com wrote:
 
  
   Hey Pders
   I've been messing with the idea of combining dynamic patching and
 generative music. And after a few hours of work I've come up with a patch
 (attached) which uses some rules to build a randomly generated piece of
 music who's result I'm rather fond of.
   On opening the patch, a 4-number array is generated, with a choice of 1
 single note to choose from. It's played by a simple sine oscillator, then a
 second iteration generates a second array, choosing from 2 notes (adding one
 a semitone above), plays the two arrays in order, then generates a third,
 with 3 notes to choose from, and so on.
   As the piece progresses, the choice of notes playing through a sequence
 that's always a low drone, expanding out to a more tangible mid-range,
 usually coming up with melodic fragments, and then starting to use some
 higher-pitched sounds. And all the time the feedback on a delay unit on the
 output, of the system.
   When the range of notes reaches 127, the feedback jumps from 60% to
 90%, changing the mood of the piece significantly, building to a harsh
 climax, each frequency range of notes lasting into the next and gains more
 significance. Like the perceived voices vying for position.
   Eventually, when a note above midi 127 is played, the synth stops, and
 the delay tail gradually fades out.
   I've found this to be an unusually structured and dramatic piece of
 generative patching. Initially a low drone, which pushes out and explores
 into melodies, building ideas, and being repeatedly pushed back to it's
 initial form. Then building into a repeating and expanding set of phases.
 getting louder and busier. Then a change brings this to a head, and
 signifies to the audience that the piece could end on any phase, building
 excitment to an inevitable but always unexpected end.
  
  
   Sorry, I've written quite a lot about this, but I thought the PD list
 might be interested... If anyone could spare about 15 minutes to listen to
 the patch in action, I'd love to hear what you think of the artistic result.
  
   Thanks in advance.
   Andrew
   P.S. I do realize that I could clean this up a great deal. The addition
 of [table] objects could just as easily be a single expanding array, I could
 hide modules away in sub patches and the sliders used for visualization
 could be more efficiently done with gem.
 
  --
  Andy Farnell padawa...@obiwannabe.co.uk
 
  ___
  Pd-list@iem.at mailing list
  UNSUBSCRIBE and account-management -
 http://lists.puredata.info/listinfo/pd-list

 ___
 Pd-list@iem.at mailing list
 UNSUBSCRIBE and account-management -
 http://lists.puredata.info/listinfo/pd-list


___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management

Re: [PD] Pd monosymphonia

2011-06-27 Thread Cuong Do Kien
Hi Andrew,

I am using PD on win 7. I could open your builGen.pd. I can watch it
running, but no sound.
Do you have any idea?

Anyway, thanks for sharing.

Best,

Cuong

On Tue, Jun 28, 2011 at 5:55 AM, Tyler Leavitt thecryofl...@gmail.comwrote:

 I have been working on a generative patch of my own and have been
 contemplating different methods of exhibiting it myself. In my school's art
 department (of which I am majoring in) there is not much awareness of
 computer/sound art, and I was thinking if I could get some other works to
 display I could put together a sort of exhibit of Puredata/generative
 patching...

 I'm not sure how it would look, but I was considering something as simple
 as a wall of 4 or 5 headphones on a hook that people could walk up to and
 listen to at their leisure (kind of a play on the traditional method of
 display for paintings). Maybe a little placard next to it with a blurb by
 the artist about their methods/conceptions behind the work. I don't know...
 I was going to further contemplate it before I asked the board, but since
 you've brought it up...

 Any other suggestions on how to exhibit generative patching?

 Tyler



 On Mon, Jun 27, 2011 at 3:01 PM, Andrew Faraday jbtur...@hotmail.comwrote:

  [range] is one of those objects I don't strictly need, but use for screen
 real-estate and speedy coding. It is cheating a little, mind.

 All the generated notes are kept, so they do have to be stored somewhere,
 I do realize that this could be a single, expanding array.

 And yes, I did mostly share this because I felt it was quite an
 interesting bit of generative work... Now I just need somewhere to exhibit
 it.


  Date: Mon, 27 Jun 2011 07:50:43 +0100
  From: padawa...@obiwannabe.co.uk

  To: pd-list@iem.at
  Subject: Re: [PD] Pd monosymphonia
 
 
 
  Hi Andrew,
 
  That was very interesting to listen to to. Thanks
  for sharing it.
 
  A couple of thoughts, though I may be missing
  some important point; since you only keep a scope
  of the last 3 notes you could use float boxes
  instead of creating tables on the fly. Also,
  the concept seems to be a base N counter, so
  approaching this starting with an up-down counter
  might simplify it.
 
  Also [range] seems to be missing for me but easily
  fixed with a multiply and an add.
 
  best
  andy.
 
  On Sun, 26 Jun 2011 00:32:27 +0100
  Andrew Faraday jbtur...@hotmail.com wrote:
 
  
   Hey Pders
   I've been messing with the idea of combining dynamic patching and
 generative music. And after a few hours of work I've come up with a patch
 (attached) which uses some rules to build a randomly generated piece of
 music who's result I'm rather fond of.
   On opening the patch, a 4-number array is generated, with a choice of
 1 single note to choose from. It's played by a simple sine oscillator, then
 a second iteration generates a second array, choosing from 2 notes (adding
 one a semitone above), plays the two arrays in order, then generates a
 third, with 3 notes to choose from, and so on.
   As the piece progresses, the choice of notes playing through a
 sequence that's always a low drone, expanding out to a more tangible
 mid-range, usually coming up with melodic fragments, and then starting to
 use some higher-pitched sounds. And all the time the feedback on a delay
 unit on the output, of the system.
   When the range of notes reaches 127, the feedback jumps from 60% to
 90%, changing the mood of the piece significantly, building to a harsh
 climax, each frequency range of notes lasting into the next and gains more
 significance. Like the perceived voices vying for position.
   Eventually, when a note above midi 127 is played, the synth stops, and
 the delay tail gradually fades out.
   I've found this to be an unusually structured and dramatic piece of
 generative patching. Initially a low drone, which pushes out and explores
 into melodies, building ideas, and being repeatedly pushed back to it's
 initial form. Then building into a repeating and expanding set of phases.
 getting louder and busier. Then a change brings this to a head, and
 signifies to the audience that the piece could end on any phase, building
 excitment to an inevitable but always unexpected end.
  
  
   Sorry, I've written quite a lot about this, but I thought the PD list
 might be interested... If anyone could spare about 15 minutes to listen to
 the patch in action, I'd love to hear what you think of the artistic result.
  
   Thanks in advance.
   Andrew
   P.S. I do realize that I could clean this up a great deal. The
 addition of [table] objects could just as easily be a single expanding
 array, I could hide modules away in sub patches and the sliders used for
 visualization could be more efficiently done with gem.
 
  --
  Andy Farnell padawa...@obiwannabe.co.uk
 
  ___
  Pd-list@iem.at mailing list
  UNSUBSCRIBE and account-management -
 http://lists.puredata.info/listinfo/pd-list

[PD] Pd monosymphonia

2011-06-25 Thread Andrew Faraday

Hey Pders
I've been messing with the idea of combining dynamic patching and generative 
music. And after a few hours of work I've come up with a patch (attached) which 
uses some rules to build a randomly generated piece of music who's result I'm 
rather fond of. 
On opening the patch, a 4-number array is generated, with a choice of 1 single 
note to choose from. It's played by a simple sine oscillator, then a second 
iteration generates a second array, choosing from 2 notes (adding one a 
semitone above), plays the two arrays in order, then generates a third, with 3 
notes to choose from, and so on. 
As the piece progresses, the choice of notes playing through a sequence that's 
always a low drone, expanding out to a more tangible mid-range, usually coming 
up with melodic fragments, and then starting to use some higher-pitched sounds. 
And all the time the feedback on a delay unit on the output, of the system. 
When the range of notes reaches 127, the feedback jumps from 60% to 90%, 
changing the mood of the piece significantly, building to a harsh climax, each 
frequency range of notes lasting into the next and gains more significance. 
Like the perceived voices vying for position. 
Eventually, when a note above midi 127 is played, the synth stops, and the 
delay tail gradually fades out. 
I've found this to be an unusually structured and dramatic piece of generative 
patching. Initially a low drone, which pushes out and explores into melodies, 
building ideas, and being repeatedly pushed back to it's initial form. Then 
building into a repeating and expanding set of phases. getting louder and 
busier. Then a change brings this to a head, and signifies to the audience that 
the piece could end on any phase, building excitment to an inevitable but 
always unexpected end. 


Sorry, I've written quite a lot about this, but I thought the PD list might be 
interested... If anyone could spare about 15 minutes to listen to the patch in 
action, I'd love to hear what you think of the artistic result.

Thanks in advance.
Andrew 
P.S. I do realize that I could clean this up a great deal. The addition of 
[table] objects could just as easily be a single expanding array, I could hide 
modules away in sub patches and the sliders used for visualization could be 
more efficiently done with gem. 

buildGen.pd
Description: Binary data
___
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management - 
http://lists.puredata.info/listinfo/pd-list