Anthony Palomba

I have been doing some experimenting with the global transport 

and the new timing features of phasor. I want to be able to 

construct rhythms by randomly selecting note divisions (1n, 2n, 

4n, etc.) each time there is a new phasor cycle. But for some 

reason the chain gets broken when the note division is is 

set to 64nt. Any ideas why it might be doing that?

I have been doing some experimenting with the global transport 
and the new timing features of phasor. I want to be able to 
construct rhythms by randomly selecting note divisions (1n, 2n, 
4n, etc.) each time there is a new phasor cycle. But for some 
reason the chain gets broken when the note division is is 
set to 64nt. Any ideas why it might be doing that?

rhythm-experiment

I didn't test your patch at all, but just from looking at it- it could be that when phasor~ is running that fast it never goes above 0.995 before it jumps back down to 0. Maybe instead of using >~, try using delta~

Instead of having it change when the phasor is about to get to the top of its ramp, you should have it change when it restarts at the bottom. In other words, change your >=~ 0.995 to 

Looking through the table of ticks and meter values in

file:///Applications/Max5/Cycling%20'74/docs/vignettes/core/maxtime_syntax.maxvig.xml

I noticed a while ago that 64nt is omitted. Also, trying to type in 64nt into the inspector for a metro objects' interval returns to 0. when entered.

I assume that 64nt is not included in permissible divisions, though why not does make me curious. I hazard a guess that it would be 20 ticks, so 'omission due to fractional amount of ticks' isn;t it!

If I'm wrong on that some one please correct me..

Quote: Anthony Palomba wrote on Thu, 04 September 2008 17:40

----------------------------------------------------

> I have been doing some experimenting with the global transport 

> and the new timing features of phasor. I want to be able to 

> construct rhythms by randomly selecting note divisions (1n, 2n, 

> 4n, etc.) each time there is a new phasor cycle. But for some 

> reason the chain gets broken when the note division is is 

> set to 64nt. Any ideas why it might be doing that?

Hi there,
Just a thought....
Looking through the table of ticks and meter values in 

I noticed a while ago that 64nt is omitted. Also, trying to type in 64nt into the inspector for a metro objects' interval returns to 0. when entered.
I assume that 64nt is not included in permissible divisions, though why not does make me curious. I hazard a guess that it would be 20 ticks, so 'omission due to fractional amount of ticks' isn;t it!
If I'm wrong on that some one please correct me..

Quote: Anthony Palomba wrote on Thu, 04 September 2008 17:40
----------------------------------------------------
> I have been doing some experimenting with the global transport 
> and the new timing features of phasor. I want to be able to 
> construct rhythms by randomly selecting note divisions (1n, 2n, 
> 4n, etc.) each time there is a new phasor cycle. But for some 
> reason the chain gets broken when the note division is is 
> set to 64nt. Any ideas why it might be doing that?
>
>
> Thanks,
> Anthony
>
>
>
>
>
----------------------------------------------------


> I noticed a while ago that 64nt is omitted. Also, trying to type in 64nt into the inspector for a metro objects' interval returns to 0. when entered.

>
> I noticed a while ago that 64nt is omitted. Also, trying to type in 64nt into the inspector for a metro objects' interval returns to 0. when entered.

Thanks Nick, your way is much more accurate. But every now and 

then it will stop, it tends to stop on either 64nt or 

128nt. Could this be a bug? Here is the corrected patcher...

Thanks Nick, your way is much more accurate. But every now and 
then it will stop, it tends to stop on either 64nt or 
128nt. Could this be a bug? Here is the corrected patcher...

Symbols such as 4n are just a convenient shorthand for numerical tick values, which I would suggest are a more general and flexible way to specify tempo-relative time. Note that numerical tick values can also be fractional. The set of symbols built-in into the system was never supposed to be anything other than a basic set. I feel a little uncomfortable about these symbols since they are not "computational" and thus represent a bit of an exception to a general Max design principle which is to try to specify as much as possible using numerical spaces. However, given that they are just a shorthand for numbers, you need not use them and you shouldn't complain if your favorite metrical grouping is not represented.

There never was a value assigned to the symbol 64nt, and if this is listed in the documentation or in a help file, it is an error and we should remove it.

Will it appears that I can not manually set a phasor to 

64nt or 128nt. I am not sure where I got that original ubumenu,

RabidRaj, I like your solution to this problem. Using the raw

Now that we have solved this problem, I was wondering if anyone

had any interesting ideas as to concatenating rhythmic intervals.

Prob is the first thing that comes to mind. But I was hoping 

someone could spark my interest with some other ideas.

I am also very interested in representing the note divisions in

some non linear way, like say for example a matrix. Where the x-axis is length and y-axis is swing. Or maybe convert that to 

polar coordinates and gave some Lissajous function pass through it.

Will it appears that I can not manually set a phasor to 
64nt or 128nt. I am not sure where I got that original ubumenu,
I think from a previous example.

RabidRaj, I like your solution to this problem. Using the raw
tick count is a good alternate way.

Now that we have solved this problem, I was wondering if anyone
had any interesting ideas as to concatenating rhythmic intervals.
Prob is the first thing that comes to mind. But I was hoping 
someone could spark my interest with some other ideas.
I am also very interested in representing the note divisions in
some non linear way, like say for example a matrix. Where the x-axis is length and y-axis is swing. Or maybe convert that to 
polar coordinates and gave some Lissajous function pass through it. 

rhythm experiment...