Exit Only

ok. I am probably going to be asking a lot of questions about transport, first because it is AMAZING. Also because the syntax for a number of objects is a lot different now and I'm still coming to terms with that.

In the 'Objects that Support Time Values' page, it lists line~ as one of the object that can handle tempo-relative times. However the help file for line~ doesn't mention them at all. Does line really support them?

Also, my main question is whether or not I can do a line-like message but substitute a tempo relative number for the ramp time.

I would like to do something like change [0., 1. 200] to 

[0., 1. 480 ticks] but that doesn't seem to work.

I realize that I can use translate for the conversion but it would be cool if it was built right in... or maybe it would be more of a hassle. In any case I'd like to know! 

ok. I am probably going to be asking a lot of questions about transport, first because it is AMAZING. Also because the syntax for a number of objects is a lot different now and I'm still coming to terms with that. 

Also, my main question is whether or not I can do a line-like message but substitute a tempo relative number for the ramp time. 

I would like to do something like change [0., 1. 200] to 
[0., 1. 480 ticks] but that doesn't seem to work.  

I realize that I can use translate for the conversion but it would be cool if it was built right in... or maybe it would be more of a hassle. In any case I'd like to know! 


more-transport-questions

On Apr 23, 2008, at 11:18 PM, Nick Inhofe wrote:

> Also, my main question is whether or not I can do a line-like 

> message but substitute a tempo relative number for the ramp time.

You could cobble something together using "translate."

On Apr 23, 2008, at 11:18 PM, Nick Inhofe wrote:
> Also, my main question is whether or not I can do a line-like  
> message but substitute a tempo relative number for the ramp time.

Chris Muir
cbm@well.com	
http://www.xfade.com

On 2008 Apr 24, at 1:18 AM, Nick Inhofe wrote:

> ok. I am probably going to be asking a lot of questions about 

> transport, first because it is AMAZING. Also because the syntax for 

> a number of objects is a lot different now and I'm still coming to 

> In the 'Objects that Support Time Values' page, it lists line~ as 

> one of the object that can handle tempo-relative times. However the 

> help file for line~ doesn't mention them at all. Does line really 

> I would like to do something like change [0., 1. 200] to

> [0., 1. 480 ticks] but that doesn't seem to work.

> I realize that I can use translate for the conversion but it would 

> be cool if it was built right in... or maybe it would be more of a 

In order to maintain backward compatibility we couldn't reasonably 

change the format of the lists accepted by objects such as line~. 

That means that time values must be represented for objects like these 

in a single item in the list. "480 ticks" is two list items. 

However, there are many ways to represent this value as a single list 

Presuming 480 ticks to a quarter note, you can use 4n.

You could also express the value as bars/beats/units -- because the 

units part of that is a number of ticks. So this means you could say 

Tap.Tools - Objects for Max, MSP, and Jitter

On 2008 Apr 24, at 1:18 AM, Nick Inhofe wrote:
>
> ok. I am probably going to be asking a lot of questions about  
> transport, first because it is AMAZING. Also because the syntax for  
> a number of objects is a lot different now and I'm still coming to  
> terms with that.
>
> In the 'Objects that Support Time Values' page, it lists line~ as  
> one of the object that can handle tempo-relative times. However the  
> help file for line~ doesn't mention them at all. Does line really  
> support them?
>
> Also, my main question is whether or not I can do a line-like  
> message but substitute a tempo relative number for the ramp time.
>
> I would like to do something like change [0., 1. 200] to
> [0., 1. 480 ticks] but that doesn't seem to work.
>
> I realize that I can use translate for the conversion but it would  
> be cool if it was built right in... or maybe it would be more of a  
> hassle. In any case I'd like to know!

In order to maintain backward compatibility we couldn't reasonably  
change the format of the lists accepted by objects such as line~.   
That means that time values must be represented for objects like these  
in a single item in the list.  "480 ticks" is two list items.   
However, there are many ways to represent this value as a single list  
item.

You could also express the value as bars/beats/units -- because the  
units part of that is a number of ticks.  So this means you could say  
0.0.480.

I hope that helps,
   Tim
____________________________________
Tap.Tools - Objects for Max, MSP, and Jitter
http://electrotap.com/taptoolsmax/


more transport questions