Forums > MaxMSP

binding pattr to objects higher in heirarchy

January 24, 2007 | 2:36 pm

is this possible? i can see how to bind to objects at lower levels, but i want my pattr objects encapsulated so i can hide away the workings of my patch, and have a gui on the top level bound to the encapsulated pattr’s


January 24, 2007 | 2:45 pm

@bindto parent::parent::parent::parent::mmmwah

jb

Am 24.01.2007 um 14:36 schrieb bin ray:

>
> is this possible? i can see how to bind to objects at lower levels,
> but i want my pattr objects encapsulated so i can hide away the
> workings of my patch, and have a gui on the top level bound to the
> encapsulated pattr’s
>
>
> –
> http://www.myspace.com/binray


January 24, 2007 | 3:05 pm

bind to them using pattrmarker or the ::parent:: property?
what you’re doing sounds awfully complicated. i’d suggest taking
another look at the architecture. or using pattrforward. it’s hard
to understand why you need poly~ in this case.

best
evan

On Jan 24, 2007, at 2:36 PM, bin ray wrote:

>
> is this possible? i can see how to bind to objects at lower levels,
> but i want my pattr objects encapsulated so i can hide away the
> workings of my patch, and have a gui on the top level bound to the
> encapsulated pattr’s
>
>
> –
> http://www.myspace.com/binray


January 24, 2007 | 4:49 pm

Quote: lists@lowfrequency.or wrote on Wed, 24 January 2007 15:05
—————————————————-
> bind to them using pattrmarker or the ::parent:: property?
> what you’re doing sounds awfully complicated. i’d suggest taking
> another look at the architecture. or using pattrforward. it’s hard
> to understand why you need poly~ in this case.

i have about 200 knobs and sliders in max with which i want to control 200 paramter values of an outboard synth

basically i dont want to have to connect each knob individually to the parameter outs and parameter ins, as my patch will be incomprehensibly messy. i’d rather have the knobs linked to the pattr system and work with the data away from the gui.

all i need to do is map the parameters coming in from sysex or ctlin to the pattr data, and map pattr data out to sysex. i’d like to know how to do this without hundreds of cables!


January 24, 2007 | 5:05 pm

As has been suggested already twice, you should use an autopattr
object in conjunction with the dials. If the dials are already named,
you don’t need to do anything — autopattr will connect to them
automatically. If they are unnamed, using the @autoname attribute of
autopattr with name them automatically, and then connect to them.

The autopattr will reveal ALL of the knobs to a pattrstorage object
at the same patcher level as the autopattr object or higher.

If you need to get the data being managed by pattrstorage out to
other parts of your patch, may I suggest the @outputmode of
pattrstorage.

The following sections of the manuals might be really helpful, more
helpful than sending the same request for help with well-documented
topics multiple times.

autopattr:
Max46ReferenceManual.pdf, p.60-62
Max46Tutorials.pdf, Chapter 53, p.354-360

pattrstorage:
Max46ReferenceManual.pdf p.417-428
Max46Tutorials.pdf, Chapter 53, p.354-360

How To Ask Questions The Smart Way:

http://www.catb.org/~esr/faqs/smart-questions.html

jb

Am 24.01.2007 um 16:49 schrieb bin ray:

>
> Quote: lists@lowfrequency.or wrote on Wed, 24 January 2007 15:05
> —————————————————-
>> bind to them using pattrmarker or the ::parent:: property?
>> what you’re doing sounds awfully complicated. i’d suggest taking
>> another look at the architecture. or using pattrforward. it’s hard
>> to understand why you need poly~ in this case.
>
> i have about 200 knobs and sliders in max with which i want to
> control 200 paramter values of an outboard synth
>
> basically i dont want to have to connect each knob individually to
> the parameter outs and parameter ins, as my patch will be
> incomprehensibly messy. i’d rather have the knobs linked to the
> pattr system and work with the data away from the gui.
>
> all i need to do is map the parameters coming in from sysex or
> ctlin to the pattr data, and map pattr data out to sysex. i’d like
> to know how to do this without hundreds of cables!
> –
> http://www.myspace.com/binray


January 24, 2007 | 5:28 pm

> i have about 200 knobs and sliders in max with which i want to
> control 200 paramter values of an outboard synth

This is NOT hard.

1. For every dial you want to work with, select
Name… from the Object menu, and enter a name
[this allows you to figure out what dial is
what if you do the naming functionally]. You only
have to do this once. Got anything in a subpatch?
name it, too.

2. Drop a pattrstorage object into your patch.

3. Deop an autopattr object into your patch.

That’s it. Every bloody knob in the same
patcher lever or higher as the autopattr
object is there.

If you’re feeling too lazy to name your knobs
in a functional manner, take a look at the
autoname attribute of the autopattr object, but
don’t come crying to me when you can’t figure
out what dial[97] does. :-)

Those tutorials are pretty useful. This is the
basic bonehead approach which works in some
incredibly large percentage of situations, but
pattr as a system is waay beyond this.


January 24, 2007 | 5:47 pm

believe it or not i read the tutorials/ help files first, but its hard to absorb everything in the 2 days ive been using pattr.

and you’re right i actually didnt know what question to ask, as i didnt fully understand the pattr concept.

i understand how to use autopattr to name and add objects to the pattr system, (though i have named them all anyway). the problem was that i didnt know you could get data out of pattrstorage with @outputmode, so i was messing with hundreds of pattr objects

know i know! thankyou
….no more dreadlock patches…


January 24, 2007 | 5:54 pm

>How To Ask Questions The Smart Way:
>http://www.catb.org/~esr/faqs/smart-questions.html

"Some people assert that many hackers have a mild form of autism or Asperger’s Syndrome, and are actually missing some of the brain circuitry that lubricates ?normal? human social interaction. This may or may not be true. If you are not a hacker yourself, it may help you cope with our eccentricities if you think of us as being brain-damaged."

heh
.


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