Re: Class library translation to Python

El vie., 31 jul. 2020 a las 21:31, Lucas Samaruga (<[email protected]>)
escribió:

> Hi Christof
>
>> > There are many undecided things yet, I'm trying a different approach
>> > for patterns now because event and event streams are less practical in
>> > Python.
>> What's the problem with Python coroutines?
>> https://docs.python.org/3/library/asyncio-task.html
>>
>
> The problem is that SuperCollider's concept of coroutines is different in
> essential aspects. SuperCollider's (co)routines are Python's generators
> with a special scheduling model. Asyncio coroutines wait on objects while
> SuperCollider's Routine reschedules constantly, it waits only on time not
> actions or states. Then there are Condition and FlowVar (currently broken
> in sc3) that implements what asyncio does by default. Also there is a
> problem with it having its own scheduler as mentioned in the previous email.
>

For the sake of clarity, note that I get this far with patterns the
SuperCollider way:

```
from sc3.all import *

s.boot()

@synthdef
def ping(freq=440, amp=0.05):
    sig = SinOsc(freq) * amp
    env = EnvGen.kr(Env.perc(0.2), done_action=Done.FREE_SELF)
    Out(0, (sig * env).dup())

p = Pbind({
    'instrument': 'ping',
    'freq': Pseq([440, Pseq([880, 1100], repeats=2), 770], repeats=5),
    'amp': 0.01,
    'dur': 0.2
})

# p.play()
```
I will not discard that, but do feel that the implementation of patterns
could be different in a more affordable way, especially when things get
complicated regarding resource management.