[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [sc-users] selfdestroying synth that destroys another synth stored in a variable
- To: sc-users@xxxxxxxxxxxxxxxx
- Subject: Re: [sc-users] selfdestroying synth that destroys another synth stored in a variable
- From: kimm furt <kimm.furt@xxxxxxxxxxxxxx>
- Date: Mon, 20 Sep 2010 09:42:30 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:content-type:mime-version :subject:from:in-reply-to:date:content-transfer-encoding:message-id :references:to:x-mailer; bh=b8Fpzdh+MMCoT0/Jx2i/KgNM5VyQjN2Evo+oVTMQIjc=; b=Jo8PkmMC0iJa9QcSzi+tmIMLw737o1kpX1NBM+ajClUVK41LjTSnUBZeF9hWeqDnEv 8lLDB6ZGjdP5i8vBYDoQcZGPu+F2xdOmxlS1Y56C0SU9bpoEyqUMn8n3WgHuRIzjGleF lPLW3uMLpMq8fXLekH7bWA5AmoyaehCkrzujg=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=fyqP8L7/m/VaExczr8co0gfJRiRmwaegcHIv2/pFb7pz7O9HO1kxn6tOjQD1bPCQCe 4NLm5xDDRGjaPwjrsKR/ilLuQHdVIe1o2jNCqCX1FatJwkrNmDWLZb9vgPW+imcIBnHa VOG3Otmtvhepbi0Wh2LBNZa1ztgfjGi/BvVkQ=
- In-reply-to: <AANLkTikW0pY0eEROdKG-TFf21=6c6AueU=3oys6xX3Jc@xxxxxxxxxxxxxx>
- List-id: SuperCollider users mailing list <sc-users.create.ucsb.edu>
- References: <AANLkTikW0pY0eEROdKG-TFf21=6c6AueU=3oys6xX3Jc@xxxxxxxxxxxxxx>
- Reply-to: sc-users@xxxxxxxxxxxxxxxx
- Sender: owner-sc-users@xxxxxxxxxxxxxxxx
hi,
i had a similar problem recently.
it would be so great having a doneAction sending a osc message!
i ended up doing it this way:
- b pauses itself instead of freeing
- b has an envelope inside that triggers a SendReply.kr
- the OSCresponder getting the message frees both synths...
best, florian
Am 20.09.2010 um 00:49 schrieb ronni montoya:
> Hello dear list, im using task for sequencing behaivors , the task
> have 2 nested "do", when the first do is called it creates a synth an
> stores it in a variable, then when the second "do" is called it
> create another synth that selfdestroys after a while. I want that when
> my second synth selfdestroys also destroy the first synth stored in
> the variable.
> Any idea of how to do this?
>
> here is the code
>
> (
> t = Task({
> inf.do({
>
> 1.do {
> arg i;
> a = Synth(\sound_a );
> (20.rand ).wait;
> };
>
>
> 1.do {
> arg i;
> Synth(\sound_b ); //
> -----------------------------------------------------> when this
> selfdestroys, i want that also destroys variable a
>
> };
>
>
>
> (40.rand * 0.1 ).wait;
> })
> })
> )
>
> t.play
> t.stop
>
>
>
> THANKS!
>
> _______________________________________________
> 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/
_______________________________________________
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/