Forums > MaxMSP

combining [transport] with audio

June 4, 2008 | 9:08 pm

File this under "Things I thought was difficult to do in max5":

So I had a transport-based sequencing environment and a phasor~-style
0.- 1. system for audio.

"uuuuh, it’s going to be soo hard to sync those two systems", more than
a bit disappointed that I didn’t have a phasor output from Transport
(like hostsync or whatever)

ahem. [Phasor~ 1n] and then send "0." to the phase inlet, and I am a
very happy chum.

:)

Andreas.


June 4, 2008 | 10:30 pm

can you paste a version of what you are talking about?

I’m still trying to learn about the transport object and this sounds
interesting.

thanks, nick

On Jun 4, 2008, at 5:08 PM, Andreas Wetterberg wrote:

> File this under "Things I thought was difficult to do in max5":
>
> So I had a transport-based sequencing environment and a phasor~-
> style 0.- 1. system for audio.
>
> "uuuuh, it’s going to be soo hard to sync those two systems", more
> than a bit disappointed that I didn’t have a phasor output from
> Transport (like hostsync or whatever)
>
> ahem. [Phasor~ 1n] and then send "0." to the phase inlet, and I am
> a very happy chum.
>
> :)
>
> Andreas.


June 5, 2008 | 12:46 am

On Jun 4, 2008, at 3:45 PM, Nick wrote:

> I’m still trying to learn about the transport object and this sounds
> interesting.

I show a line~ being driven slaved to a transport in my NewThump
example, which can be found on my examples page: http://www.xfade.com/max/examples

-C

Chris Muir
cbm@well.com

http://www.xfade.com


June 5, 2008 | 1:50 am

Here is an example I put together

– Pasted Max Patch, click to expand. –

It still would be nice to have an attribute that locks the phasor to its interval, kind of like a ‘quantize’ attribute.


June 5, 2008 | 2:44 am

On 5 juin 08, at 03:50, Nick Inhofe wrote:

> It still would be nice to have an attribute that locks the phasor to
> its interval, kind of like a ‘quantize’ attribute.

Did you try the lock attribute?

ej

– Pasted Max Patch, click to expand. –

June 5, 2008 | 5:34 am

I was hoping someone would come along and say that!

I’d been staring at the lock attribute since I first got Max 5 but I was afraid to get in there and test it. It would be nice if the reference was a little more clear on exactly what ‘lock 1′ does.

Your example demonstrates it clearly!

Now its time to revise some patches :0


June 5, 2008 | 5:39 am

While we’re on this subject. The lock method is great, but the reference really doesn’t explain it very well at all. This is very odd for Max/MSP.

If the phasor~ gets a float value while lock = 1, then it simply set the phasor frequency to 0. The reference makes it sound like it would simply ignore the float.

However, it does respond to well to time (note?) values. Giving 4n would move it to a quarter note etc. I like this behavior, but it also contradicts there reference since note values can change the frequency while it is locked.

In any case, this is all cleared up for me but I would hope that other people could find this feature more easily because its really great!


Viewing 7 posts - 1 through 7 (of 7 total)