Predicting results of coin

[Paul Jones]

   Hello list

I am writing some generative algorithms. In which I'm using coin to create possible out comes. I would like to be able to predict the result before it is used in the Tdef. For example

Tdef(\beat1 , {inf.do{ |i| ~probtest =if(i%3==1,0.5.coin,{Tdef(\pain).play});
                                     
                                      if(~probtest==true,{Synth(\kick)});

if in this case I would be "missing" a kick drum I would like to impart some kind of accent on the preceding hit, i.e longer envelope, distortion, and whatever else , but knowing when to do this depends on knowing the outcome of ~probtest before it has happened. i.e if ~probtest == true but next ~probtest == faulse then do a big kick with some reverb distortion and fire off an acid line. Or something like that.

Thanks in advance for any ideas

   Paul

[andrea valle-3]

Maybe you can take a look at the randomSeed help file

Best

-a-

On 23 Sep 2008, at 22:28, Paul Jones wrote:

   Hello list

I am writing some generative algorithms. In which I'm using coin to create

possible out comes. I would like to be able to predict the result before it

is used in the Tdef. For example 

Tdef(\beat1 , {inf.do{ |i| ~probtest

=if(i%3==1,0.5.coin,{Tdef(\pain).play});

                                      if(~probtest==true,{Synth(\kick)}); 

if in this case I would be "missing" a kick drum I would like to impart some

kind of accent on the preceding hit, i.e longer envelope, distortion, and

whatever else , but knowing when to do this depends on knowing the outcome

of ~probtest before it has happened. i.e if ~probtest == true but next

~probtest == faulse then do a big kick with some reverb distortion and fire

off an acid line. Or something like that.

Thanks in advance for any ideas

   Paul

-- 

View this message in context: http://www.nabble.com/Predicting-results-of-coin-tp19636294p19636294.html

Sent from the Supercollider - User mailing list archive at Nabble.com.

_______________________________________________

sc-users mailing list

info (subscribe and unsubscribe): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml

archive: http://www.listarc.bham.ac.uk/marchives/sc-users/

search: http://www.listarc.bham.ac.uk/lists/sc-users/search/

--------------------------------------------------

Andrea Valle

--------------------------------------------------

CIRMA - DAMS

Università degli Studi di Torino

--> http://www.cirma.unito.it/andrea/

--> http://www.myspace.com/andreavalle

--> andrea.valle@...

--------------------------------------------------

"

Think of it as seasoning

. noise [salt] is boring

. F(blah) [food without salt] can be boring

. F(noise, blah) can be really tasty

"

(Ken Perlin on noise)

[Dan Stowell]

Could you do something inside the loop like

~thiscoin = ~nextcoin ?? {0.5.coin}; // the coin here only used on
first iteration
~nextcoin = 0.5.coin; // this is where most of the coins come from
if(~thiscoin){
  if(~nextcoin){
    // normal kick
  }{
    // biiiiiiig kick
  }
}{
  // no kick
}



2008/9/23 Paul Jones <pauljones_mds@...>:

>
>   Hello list
>
> I am writing some generative algorithms. In which I'm using coin to create
> possible out comes. I would like to be able to predict the result before it
> is used in the Tdef. For example
>
> Tdef(\beat1 , {inf.do{ |i| ~probtest
> =if(i%3==1,0.5.coin,{Tdef(\pain).play});
>
>                                      if(~probtest==true,{Synth(\kick)});
>
> if in this case I would be "missing" a kick drum I would like to impart some
> kind of accent on the preceding hit, i.e longer envelope, distortion, and
> whatever else , but knowing when to do this depends on knowing the outcome
> of ~probtest before it has happened. i.e if ~probtest == true but next
> ~probtest == faulse then do a big kick with some reverb distortion and fire
> off an acid line. Or something like that.
>
> Thanks in advance for any ideas
>
>   Paul
> --
> View this message in context: http://www.nabble.com/Predicting-results-of-coin-tp19636294p19636294.html
> Sent from the Supercollider - User mailing list archive at Nabble.com.
>
>
> _______________________________________________
> sc-users mailing list
>
> info (subscribe and unsubscribe): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
>

--
http://www.mcld.co.uk

_______________________________________________
sc-users mailing list

info (subscribe and unsubscribe): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/

[James Harkins-2]

Or, turn the problem upside down - you could generate an accent
according to some rule, and pass that information forward to determine
whether or not to leave out the kick drum.

In my work, I'm moving much more toward having higher-level agents
that control "player" processes, to coordinate larger gestures among
multiple processes. Here, you might have a higher level entity decide
to do the "big accent + acid line" gesture at some particular time and
influence the players to realize the behavior. I don't have time right
now (still in the office) to be much more specific but maybe that will
give you some ideas.

hjh


On Tue, Sep 23, 2008 at 4:28 PM, Paul Jones <pauljones_mds@...> wrote:

>
>   Hello list
>
> I am writing some generative algorithms. In which I'm using coin to create
> possible out comes. I would like to be able to predict the result before it
> is used in the Tdef. For example
>
> Tdef(\beat1 , {inf.do{ |i| ~probtest
> =if(i%3==1,0.5.coin,{Tdef(\pain).play});
>
>                                      if(~probtest==true,{Synth(\kick)});
>
> if in this case I would be "missing" a kick drum I would like to impart some
> kind of accent on the preceding hit, i.e longer envelope, distortion, and
> whatever else , but knowing when to do this depends on knowing the outcome
> of ~probtest before it has happened. i.e if ~probtest == true but next
> ~probtest == faulse then do a big kick with some reverb distortion and fire
> off an acid line. Or something like that.
>
> Thanks in advance for any ideas

--
James Harkins /// dewdrop world
jamshark70@...
http://www.dewdrop-world.net

"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman

_______________________________________________
sc-users mailing list

info (subscribe and unsubscribe): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
search: http://www.listarc.bham.ac.uk/lists/sc-users/search/