[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[sc-users] limiting the randomness of frecuency paths
- To: sc-users@xxxxxxxxxxxxxxxx
- Subject: [sc-users] limiting the randomness of frecuency paths
- From: pikku yokoi <pikku.yokoi@xxxxxxxxx>
- Date: Sun, 19 Sep 2010 13:59:35 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=3XVUWuZnRXt2alYLUk7sRPTMygKWiywjvmHlGh3VeYo=; b=p7lW3Jqe9XQmG8QZOMbay1oHdnD/F2FhtDVusQcgJKez4YAuZrVJgl77hH5kcsu5SC kfj6i1MlmoFtJDA4xnbpqlekRG6HA5Zgpa7+a2c7/5/gCoTaPryDmvFm6fc2HwjeuzmY EXsZ+c6HmtY6o9EUOBo1TOwFl9Ebm2ioAvR3k=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=a1YkfZXcpLN9GZPxNTC6Qaqj5LxNgTe1bibTWmnMdhWeoiXWmWXEFcahBJ4G5GlYxI 748zlH0+89Fph4ixJZZgop83MN0m8ZJYMkxrYPJFYnpN84PxbaiJfH3XHsYms+dFAhqD FasncFrV44+mqAVx9dN/452y1q/o9fmUyYI5M=
- List-id: SuperCollider users mailing list <sc-users.create.ucsb.edu>
- Reply-to: sc-users@xxxxxxxxxxxxxxxx
- Sender: owner-sc-users@xxxxxxxxxxxxxxxx
hello everybody, today i came with this idea while i was
experimenting with sc3, maybe somebody thought about this and i can
get some feedback.
I been creating synthdefs that use random envelopes to define the path
of the frecuency of that sound it produces.
Im using something like:
env_freq = EnvGen.ar(Env.new([(Rand.new(0.0, 20.0) ), Rand.new(0.0,
20.0) , Rand.new(0.0, 20.0) , Rand.new(0.0, 20.0) , Rand.new(0.0,
20.0) ], [2, 3, 1, 4], [0, 3, -3, -1]) );
so if i create 10 synths at the same time they are going to have
diferent random frequency paths.
I was thinking that instead of making this , making that the
randomness of each synth are limited by some rule and in relation
with the other synths.
So one envelope is limited by the envelopes f the others following
some kind of rule, maybe musical rules, like scales?
So that global behaivor would not be random but with a more
structured behaivor.
I was thinking which approaches would be for making this.
Do anybody thought or made something like this? would approaches would be?
any idea would be very approacited
thanks!
Pikku
_______________________________________________
sc-users mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/