On 08/01/2008, mike clemow wrote:

Okay... affine spaces. I'm going to have to wikipedia that one, i'm afraid (high school math ain't doin' it for me here ;-) I understand the analogy of vectors and point, though--I think that lends some credence to the idea that Chuck is already on the right path as far how the dur and time types work.

I see the analogy and I think it has a lot of merit. I'm also, at the same time, sticking to my older point that ChucK is already muddying the waters and is in fact getting quite a bit of use from that, for example "now - (now % T) => now;", I find that line very beautiful, extremely useful and in direct opposition to looking at time objects are pure references to instances. I still have a few questions. The first is for Kassen: Why do you

want to know the VM start time?

To quote Nick Cave; "I can't see for the smoke so I poke around, I poke around"(etc) At some moment I just tried it as the units are the same, it didn't work so I tried some more related stuff. I want to learn so I'm asking questions. ChucK is a great tool to put some bangin' beats on the proverbial floor and it's a nice experiment in syntax. I like both aspects a lot. At the core of ChucK's syntax is time and timing so any questions and -possible- incoherency's in working with those are quite interesting. I can find the birth of the VM and half a minuted after I found out how to I shared this with the list so now we all can, but I think some questions remain. I don't know about you but so far I have used "time" as a data type only rarely and I didn't know that much about it, I think we all know a bit more now. In a way there is a certain philosophical beauty to only being able to define time in relation to the "now" but as this can lead to some decidedly odd expressions I wonder if that's intentional and proper. As for actual use, I could imagine that referring to absolute moments in time could become useful when writing a score, especially with some sort of sorting, Csound style. Maybe there are other better uses, maybe it's all quite academic? I'm already enthusiastic there are people that have a position on this too.

I'm just thinking out loud...

So was and am I. It's the ultimate in open-source! "thinking out loud" strikes me as a excelent slogan for a musical programing language. Yours, Kas.

OK, I'm not a math wiz or even a audio/dsp wiz, and certainly not a ChucK wiz. What exactly does this mean: now - (now % T) => now;

In this context, T is a duration to which to synchronize, like a beat. minute/140 => dur beat; the expression (now % beat) is the remainder after dividing the current time into uniform beats, the amount of time that hangs over the last beat. Usually, the next step for me is: beat - (now % beat) which indicates the time left until the next beat. Chucking it to now wakes up the current shred exactly on the next beat / period. beat - (now % beat) => now; But as far as your expression now - (now % T) => now; if T is a duration, then the right hand expression would be the current shred time (a time) minus that that hangs over the duration (a duration), which would be a time in the past, which seems to throw a NegativeTimeException in the VM. Graham

Thanx Graham; this makes sense, and is chuckin cool! Gees, even I can understand it! Woohoo! -- Rich ----- Original Message ----- From: "Graham Coleman" To: "ChucK Users Mailing List" Sent: Thursday, January 10, 2008 6:44 AM Subject: Re: [chuck-users] cast dur to time?

OK, I'm not a math wiz or even a audio/dsp wiz, and certainly not a ChucK wiz. What exactly does this mean: now - (now % T) => now;

In this context, T is a duration to which to synchronize, like a beat. minute/140 => dur beat; the expression (now % beat) is the remainder after dividing the current time into uniform beats, the amount of time that hangs over the last beat. Usually, the next step for me is: beat - (now % beat) which indicates the time left until the next beat. Chucking it to now wakes up the current shred exactly on the next beat / period. beat - (now % beat) => now; But as far as your expression now - (now % T) => now; if T is a duration, then the right hand expression would be the current shred time (a time) minus that that hangs over the duration (a duration), which would be a time in the past, which seems to throw a NegativeTimeException in the VM. Graham _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

Glad to help, Rich. Indeed, the _p - (now % p)_ pattern comes up so much, it could even have its own operator... now %- dur => now; //sync to period and for ints: beatnum %- 4 => int notesel; //reverse sawtooth pattern, 4, 3, 2, 1, 4, 3, 2, 1 thought it might be nice if it subtracted from the highest value, ie: 3 - (beatnum % 4) => now; //zero-based reverse sawtooth, 3, 2, 1, 0, 3, 2, 1, 0 Graham On Jan 10, 2008 6:16 PM, Rich Caloggero wrote:

Thanx Graham; this makes sense, and is chuckin cool! Gees, even I can understand it! Woohoo! -- Rich

ons 2008-01-09 klockan 01:34 +0100 skrev Kassen:

On 08/01/2008, mike clemow wrote: [snip]

I still have a few questions. The first is for Kassen: Why do you want to know the VM start time?

To quote Nick Cave; "I can't see for the smoke so I poke around, I poke around"(etc)

Agreed. [snip]

I'm just thinking out loud...

So was and am I. It's the ultimate in open-source! "thinking out loud" strikes me as a excelent slogan for a musical programing language.

Very nice! Like it a lot! You should put it on the Toplap slogan page =) Gasten