cleetus

Hey, was just wondering if anyone could help me convert a PD patch into a working max version. I've done most of it but I'm stuck on a few minor details, such as where there is a message box that starts with a ";" that seems to be sending data elsewhere.

If anyone could help me with this predicament then I'd be most grateful.

pd-to-max-conversion

> I'm stuck on a few minor details, such as where there is a message box that starts with a ";" that seems to be sending data elsewhere.

From Max documentation ("Message" chapter):

"A semicolon (;) sends a message to a receive object. The 1st item 

following a semicolon is the name of the receive object. The rest of the 

message is sent to that object, rather than out the outlet..."

Dominic wrote:
> I'm stuck on a few minor details, such as where there is a message box that starts with a ";" that seems to be sending data elsewhere.
>

Hi.
 From Max documentation ("Message" chapter):

"A semicolon (;) sends a message to a receive object. The 1st item 
following a semicolon is the name of the receive object. The rest of the 
message is sent to that object, rather than out the outlet..."

Well it all seems fine to me now...can't figure out why it's still not working the same as the in PD patch.

I'll upload the max patch just incase anyone feels like having a skwizz

Could someone please explain this: Inside the "Mycircle" sub patcher it starts off with "r $1" but max doesn't understand this and reports an error stating: "$" variable out of range.

So although the sound is coming through ok, the selector section that is providing the modulation isn't working properly.

there's really no difference between max and Pd in this regard, this 

technique is older than both Max or Pd, it dates back to prehistoric 

> Hey, was just wondering if anyone could help me convert a PD patch 

> into a working max version. I've done most of it but I'm stuck on a 

> few minor details, such as where there is a message box that starts 

> with a ";" that seems to be sending data elsewhere.

> If anyone could help me with this predicament then I'd be most 

there's really no difference between max and Pd in this regard, this  
technique is older than both Max or Pd, it dates back to prehistoric  
MaxFTS days...

> Hey, was just wondering if anyone could help me convert a PD patch  
> into a working max version. I've done most of it but I'm stuck on a  
> few minor details, such as where there is a message box that starts  
> with a ";" that seems to be sending data elsewhere.
>
> If anyone could help me with this predicament then I'd be most  
> grateful.

1st of all, in your pd patch, [mycircle one], [mycircle two], ... are 

abstractions, not subpatchers, so we couldn't see what was inside as you 

didn't provide them with the main patch...

You did convert them into patchers in the max patch so, I could have a 

A big difference between Max and PD is how they deal with patcher 

So, if an *abstraction* in Max called [mycircle one] contains a [r #1] 

object, it will become [r one] as soon as the abstraction is created 

(because "one" is the first creation argument of the abstraction).

In PD, in an *abstraction* called [mycircle one], a [r $1] object will 

In your max patch, you are using these "r $1" as messages, they should 

be objects and they should receive informations from these [;one ...( 

And if you still wanna use the creation arguments, you should convert 

all [p mycircle...] patchers to abstractions, and change [r $1] to [r #1].

(Another solution would be to name [r #1] -> [r one] in [p mycircle 

one], [r #1] -> [r two] in [p mycircle two] and so on...).

1st of all, in your pd patch, [mycircle one], [mycircle two], ... are 
abstractions, not subpatchers, so we couldn't see what was inside as you 
didn't provide them with the main patch...

You did convert them into patchers in the max patch so, I could have a 
look and found some mistakes.

A big difference between Max and PD is how they deal with patcher 
creation arguments.
Max will use "#1", PD will use "$1".
So, if an *abstraction* in Max called [mycircle one] contains a [r #1] 
object, it will become [r one] as soon as the abstraction is created 
(because "one" is the first creation argument of the abstraction).
In PD, in an *abstraction* called [mycircle one], a [r $1] object will 
become [r one], and so on...

In your max patch, you are using these "r $1" as messages, they should 
be objects and they should receive informations from these [;one ...( 
messages we talked about.
And if you still wanna use the creation arguments, you should convert 
all [p mycircle...] patchers to abstractions, and change [r $1] to [r #1].
(Another solution would be to name [r #1] -> [r one] in [p mycircle 
one], [r #1] -> [r two] in [p mycircle two] and so on...).

> Could someone please explain this: Inside the "Mycircle" sub patcher 

> it starts off with "r $1" but max doesn't understand this and 

> reports an error stating: "$" variable out of range.

> So although the sound is coming through ok, the selector section 

> that is providing the modulation isn't working properly.

I don't have any errors, but I dodn't try much to get some.

there are 2 [p mycircle one] in your patch (one is hidden behind 

another patcher), one is correct but not the other one because:

you probably want the object [r ], not the message r. You should have 

It is possible to create abstractions in Max, which is much more handy 

than having 6 identical [p mycircle]. You then have to learn stuff 

The [line~] object should probably be triggered when hit is received, 

as its output stays at 0. 2 seconds after create is sent.

Centre de Recherches et de Formation Musicales de Wallonie asbl

> Could someone please explain this: Inside the "Mycircle" sub patcher  
> it starts off with "r $1" but max doesn't understand this and  
> reports an error stating: "$" variable out of range.
>
> So although the sound is coming through ok, the selector section  
> that is providing the modulation isn't working properly.

there are 2 [p mycircle one] in your patch (one is hidden behind  
another patcher), one is correct but not the other one because:
you probably want the object [r ], not the message r. You should have  
a look at [patcherargs].
It is possible to create abstractions in Max, which is much more handy  
than having 6 identical [p mycircle]. You then have to learn stuff  
like [r #1].

The [line~] object should probably be triggered when hit is received,  
as its output stays at 0. 2 seconds after create is sent.

_____________________________
Patrick Delges

Centre de Recherches et de Formation Musicales de Wallonie asbl
http://www.crfmw.be/max


Those last few nuggets of information were invaluable to me.

> I'll upload the max patch just incase anyone feels like having a

You need to save the [p mycircle ...] as a subpatcher, and replace the 

message [r $1] with and object [r #1]. Then it will load them with 

appropriate parameters and create the receive object... You could also 

just create an input to these patchers and connect them instead of these 

Its good to understand the functionality in general if you do such a 

port, then its easy to find out why it doesn't work... ;-)

The tutorials in Max and in Pd are both pretty good now (Pd gained a lot 

of documentation in the past, but with Max 5 cycling is again pretty 

Dominic schrieb:
> I'll upload the max patch just incase anyone feels like having a
> skwizz

You need to save the [p mycircle ...] as a subpatcher, and replace the 
message [r $1] with and object [r #1]. Then it will load them with 
appropriate parameters and create the receive object... You could also 
just create an input to these patchers and connect them instead of these 
send/receive constructions....

Its good to understand the functionality in general if you do such a 
port, then its easy to find out why it doesn't work... ;-)

The tutorials in Max and in Pd are both pretty good now (Pd gained a lot 
of documentation in the past, but with Max 5 cycling is again pretty 
much ahead... ;-)

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


PD to Max conversion