[chuck] time signature durations

[Philip Davidson]

You can spork new shred with a function call, which
will launch a function of your choice.

spork ~ myfunction ( args, args, args );


Any globals declared before that function is
defined are available to subsequently sporked shreds -

check out powerup.ck , or spork.ck, in examples

spork away!


On Tuesday, September 7, 2004, at 09:07  PM, Michael Heuer wrote:

>
> That would be quite helpful.
>
> Is it possible to share data across shreds?  With this I could fully
> implement what I had in mind, say create several shreds for various
> `instruments' and then having a controller shred that could vary the 
> BPM
> of what all of the instrument shreds were doing.
>
>    michael
>
>
>
> On Tue, 7 Sep 2004, Perry R Cook wrote:
>
>> Gary and I have talked about this.  Actually coming up with a
>> semantic to assign new types relative to others, and having
>> them automatically update when the root types are changed.
>> Something like:
>>
>> 100 ms => dur quarter;
>> 4*quarter => dur =whole;  // some semantic i forgot now
>>
>> 50 ms => quarter;
>>
>> would automatically cause =whole to change.
>>
>> PRC
>>
>> On Tue, 7 Sep 2004, Michael Heuer wrote:
>>
>>> Hello,
>>>
>>> Is there built-in support for time signatures, or should I just be 
>>> doing
>>> something like
>>>
>>> 400::ms => dur q;
>>> 4::q => dur w;
>>>
>>> 2::w => now;
>>> while (true)
>>> {
>>>   q => now;
>>>   ...
>>> }
>>>
>>> It would be nice to be able to write a file or shred using 
>>> time-signature
>>> based durations and be able to change the values of those durations 
>>> from
>>> somewhere else, effectively changing the BPM of everything you may 
>>> have
>>> running simultaneously.
>>>
>>>    michael
>>>
>>> _______________________________________________
>>> chuck mailing list
>>> chuck at lists.cs.princeton.edu
>>> https://lists.cs.princeton.edu/mailman/listinfo/chuck
>>>
>> _______________________________________________
>> chuck mailing list
>> chuck at lists.cs.princeton.edu
>> https://lists.cs.princeton.edu/mailman/listinfo/chuck
>>
>
> _______________________________________________
> chuck mailing list
> chuck at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck