[chuck] time signature durations
gewang at CS.Princeton.EDU
Tue Sep 7 21:41:13 EDT 2004
On Sep 7, 2004, at 9:07 PM, Michael Heuer wrote:
> That would be quite helpful.
I think Perry and I came up with the syntax of:
100::ms => dur quarter;
4::<quarter> => dur whole;
changing quarter would also affect whole.
This is currently not implemented. It is (now)
a high priority.
> Is it possible to share data across shreds?
So far, it is possible only for shreds in the same source
file to share global data. (see examples/wind2,
mand-o-matic, moogie, or grep for 'spork')
Soon (in the next major release), there will much more
freedom in sharing data, using both global value maps,
as well as static data of classes/namespaces/shreds.
This is a very high priority.
Most of this should be available later this month.
> 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.
>> On Tue, 7 Sep 2004, Michael Heuer wrote:
>>> Is there built-in support for time signatures, or should I just be
>>> 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
>>> based durations and be able to change the values of those durations
>>> somewhere else, effectively changing the BPM of everything you may
>>> running simultaneously.
>>> chuck mailing list
>>> chuck at lists.cs.princeton.edu
>> chuck mailing list
>> chuck at lists.cs.princeton.edu
> chuck mailing list
> chuck at lists.cs.princeton.edu
More information about the chuck