nick rothwell | project cassiel

Try this: open transport.maxhelp, and then stop and start the 

transport a few times. On most restarts I'm seeing the quantized metro 

drop a 1/480th bar tick - the units come out as 479 (with the previous 

Max 5.0.5/36423, OS X 10.5.5, MacBook Pro.

Try this: open transport.maxhelp, and then stop and start the  
transport a few times. On most restarts I'm seeing the quantized metro  
drop a 1/480th bar tick - the units come out as 479 (with the previous  
beat), then 478, then ...

Nick Rothwell / Cassiel.com Limited
www.cassiel.com
www.myspace.com/cassieldotcom
www.last.fm/music/cassiel
www.reverbnation.com/cassiel
www.linkedin.com/in/cassiel
www.loadbang.net


quantized-metro-drifts

I'm not sure that timing is affected though

Quote: nick rothwell / cassiel wrote on Wed, 26 November 2008 11:07

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

> Try this: open transport.maxhelp, and then stop and start the 

> transport a few times. On most restarts I'm seeing the quantized metro 

> drop a 1/480th bar tick - the units come out as 479 (with the previous 

> Max 5.0.5/36423, OS X 10.5.5, MacBook Pro.

I have also noticed that changing the timesig has a similar effect.

Quote: nick rothwell / cassiel wrote on Wed, 26 November 2008 11:07
----------------------------------------------------
> Try this: open transport.maxhelp, and then stop and start the  
> transport a few times. On most restarts I'm seeing the quantized metro  
> drop a 1/480th bar tick - the units come out as 479 (with the previous  
> beat), then 478, then ...
>
> Max 5.0.5/36423, OS X 10.5.5, MacBook Pro.
>

I have also noticed that changing the timesig has a similar effect.


On 26 Nov 2008, at 20:10, Andrew Pask wrote:

> I'm not sure that timing is affected though

here's the odd thing: the raw tick count output appears fine, it's 

just the bar/beat/tick outputs that drift.

here's the odd thing: the raw tick count output appears fine, it's  
just the bar/beat/tick outputs that drift.

We're doing a lot of work on ITM and transport related functionality at the moment, so if any of you have niggles or patches which don't work right or anything else to report, feel free to get in touch with me offline or here.

this is just for myself (and other acronym-honks):

On 26 Nov 2008, at 23:00, Andrew Pask wrote:

> We're doing a lot of work on ITM and transport related functionality 

> at the moment, so if any of you have niggles or patches which don't 

> work right or anything else to report, feel free to get in touch 

Something of an aside, but: what's the story (or is there one) on 

allowing metrical time to tapout~? I realise that it's not one of the 

two use cases (fixed, non-smooth millisecs or signal-input) so might 

be tricky in a world of changing transport tempo, but the fact that 

metrical time is not allowed might surprise newcomers. (On the other 

hand, when teaching, it shows a useful application of [translate]...)

> We're doing a lot of work on ITM and transport related functionality  
> at the moment, so if any of you have niggles or patches which don't  
> work right or anything else to report, feel free to get in touch  
> with me offline or here.

Something of an aside, but: what's the story (or is there one) on  
allowing metrical time to tapout~? I realise that it's not one of the  
two use cases (fixed, non-smooth millisecs or signal-input) so might  
be tricky in a world of changing transport tempo, but the fact that  
metrical time is not allowed might surprise newcomers. (On the other  
hand, when teaching, it shows a useful application of [translate]...)

> (On the other hand, when teaching, it shows a useful 

Nick, could you elaborate, please? Do i not understand [translate] because it is an object not present in 4.63?

Or is it, that English doesn't translate to German too well or vice versa?

> (On the other hand, when teaching, it shows a useful 
> application of [translate]...)

jrp
p.s. was a serious quest, nevertheless.


ITM is a new feature of Max 5. So there's no translate object in Max 

>> (On the other hand, when teaching, it shows a useful

> Nick, could you elaborate, please? Do i not understand [translate] 

> because it is an object not present in 4.63?

> Or is it, that English doesn't translate to German too well or vice 

> p.s. was a serious quest, nevertheless.

ITM is a new feature of Max 5. So there's no translate object in Max  
4.6.

>
>> (On the other hand, when teaching, it shows a useful
>> application of [translate]...)
>
> Nick, could you elaborate, please? Do i not understand [translate]  
> because it is an object not present in 4.63?
>
> Or is it, that English doesn't translate to German too well or vice  
> versa?
>
> :)
>
> jrp
> p.s. was a serious quest, nevertheless.
> --
> ---
> fiction-induced heat
> in too many places to name.
> mood description: audiotic.


translate is part of the suite of objects supporting Max 5's beat- 

https://cycling74.com/docs/max5/refpages/max-ref/translate.html

> Nick, could you elaborate, please? Do i not understand [translate]  
> because it is an object not present in 4.63?

translate is part of the suite of objects supporting Max 5's beat- 
based timing machinery:

	https://cycling74.com/docs/max5/refpages/max-ref/translate.html

On 27 Nov 2008, at 17:20, Andrew Pask wrote:

Quantized metro drifts...?