Re: [sc-users] 30 small pieces - one synthdef

[micromoog <micromoog@xxxxxxxxx>]

Thank you!  There's a lot to study here, and so far (day 3) I like what I'm hearing.  For me it's easier to handle them in one big plaintext file, and I've attached it if anyone's interested.

 

Congratulations on sticking to your pact; I'll check out your counterpart's work next!  I'd be interested to hear about self-imposed limits anyone else uses to boost productivity -- I fully understand the feeling of having so many options available in sc that it's easy to get sidetracked.

 

micromoog

 

 

On Thu, Apr 30, 2009 at 1:05 PM, Fredrik Olofsson <f@xxxxxxxxxxxxxxxxxxx> wrote:

dear all,

for april i did 1hour-per-day coding practice.  the results can be found here...

http://www.fredrikolofsson.com/f0blog/?q=node/357

to run the code you'll need to first send the redMond synthdef to the server.

sorry for music quality - varies a lot and most pieces are quite embarrassing.  but they are all coded from scratch during the 1h time limit, and i restrain myself to silly restrictions: to only use one [albeit massive] synthdef, patterns+pdefs, and no randomness allowed.  another excuse is that i often was tired, drunk or on the train going somewhere.

i don't know how you others get things done, but for me these restrictions really helps.  as well as getting faster at coding by rewriting the same structures over and over, it does produce a lot of music material that could be the foundation for a few real tracks.

comments welcome.

_f

  #|

     fredrikolofsson.com     klippav.org     musicalfieldsforever.com

  |#

Attachment: redFrik_200904_pact.zip
Description: Zip archive