Re: [sc-users] Re: top five sclang pet peeves

[amindfv@xxxxxxxxx]

> 
> If you replace SC's timing model with tidal's, then you lose the ability to
> create all kinds of textural layers where metrical divisions make no sense.
> 
> When Lucas wrote, "That is exactly what comes to my mind when I say that
> pattern interface is clumsy" -- my point was, how, in tidal, would you
> express the idea "start with a randomly chosen time in a given range and,
> for 6-12 events, slow down, and do this repeatedly, and do not coordinate
> the rhythm cycles with the pitch cycles"? Good luck.
> 


I'm getting somewhat off-topic here, but I think tidal is actually able to do most if not all of this. You can generate random values and slow down sections of time and have e.g. a rhythmic pattern be running slower or faster than e.g. a pitch pattern (for the same stream of events).

Agree, though, that tidal and the pattern lib have different strengths and each is going to be a better tool than the other for certain jobs.

Tom
_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/