Help with Max Msp, saving and recalling LISTS?

Jan 20, 2009 at 12:48am

Help with Max Msp, saving and recalling LISTS?

Hey,

i have been working on my own sequencer and have really got into Max Msp 5.

i have made a 16 step sequencer its not amazing but its my own and i can load my samples in and stuff.

i am using the matrixctrl and i really want a way to save and load the patterns i have entered in the matrix. i just cant figure a way of doing it.

#41849
Jan 20, 2009 at 1:00am

The [preset] object is a good one to start with, it’s fairly simple, if you want something a little more intelligent then have a look at the tutorials for the [pattr] family of objects.

lh

#149323
Jan 20, 2009 at 1:46am

if you wanted to save to a text file so that app’s other than max can
read write the patterns look at [coll] or [text] – bit of messing
around to get going, but might be worth it in the long run – as your
sequencer develops so will you save file format…

2009/1/20 Darren :
>
> Hey,
>
> i have been working on my own sequencer and have really got into Max Msp 5.
>
> i have made a 16 step sequencer its not amazing but its my own and i can load my samples in and stuff.
>
> i am using the matrixctrl and i really want a way to save and load the patterns i have entered in the matrix. i just cant figure a way of doing it.
>

#149324
Jan 20, 2009 at 1:58am

On Jan 19, 2009, at 4:48 PM, Darren wrote:

> i am using the matrixctrl and i really want a way to save and load
> the patterns i have entered in the matrix. i just cant figure a way
> of doing it.

I suggest getting started with the pattr world. I have a simple
example file, called PattrKitty, on my examples page: http://xfade.com/max/examples/

For the use you mention, pattr is almost certainly what you will end
up with after you try all of Max’s various ways of storing data.

- C

Chris Muir
cbm@well.com

http://www.xfade.com

#149325
Jan 20, 2009 at 2:18am

One vote for [pattr].
J-F.

>
> The [preset] object is a good one to start with, it’s fairly simple, if you
> want something a little more intelligent then have a look at the tutorials for
> the [pattr] family of objects.
>
> lh

#149326
Jan 20, 2009 at 4:24am

pattr may seem intimidating but it really is nothing too complex. it allows for really easy pattern saving and recalling, plus you can interpolate between presets which is awesome.

#149327
Jan 20, 2009 at 4:45am

also awesome is the ability to interpolate between presets, even if
they aren’t adjacent, with a recallmulti message sent to pattrstorage.
There’s a recent thread about this topic…

–SN

Sam Nichols
samuelnichols@earthlink.net

http://samnichols.net/

On Jan 19, 2009, at 8:24 PM, Kyle Kaplan wrote:

>
> pattr may seem intimidating but it really is nothing too complex. it
> allows for really easy pattern saving and recalling, plus you can
> interpolate between presets which is awesome.
> –
> -k.

#149328
Jan 20, 2009 at 4:53am

[preset] will get you started, [pattr] is a bit more in-depth (but simple to implement) and should be experimented with to really “get” it. pattr does everything a preset does and lots more. To combine the two, once you have your pattr going, use a preset for *that* by setting the pattr attribute name in the preset. Then you’ve got a quick GUI for working with it.

Lots of other objects, but not all, can be saved in pattr, and you can use the @greedy attribute to work with pattrs in subpatches, among lots of other goodies built-in.

#149329
Jan 20, 2009 at 8:52am

hi,

saving a matrix with [pattr]&[pattrstorage] is not very easy.
i personally give a name to my matrixctrl object and use the [autopattr]
object to have it stored in the [pattrstorage].

g.

2009/1/20 Seejay James

>
> [preset] will get you started, [pattr] is a bit more in-depth (but simple
> to implement) and should be experimented with to really “get” it. pattr does
> everything a preset does and lots more. To combine the two, once you have
> your pattr going, use a preset for *that* by setting the pattr attribute
> name in the preset. Then you’ve got a quick GUI for working with it.
>
> Lots of other objects, but not all, can be saved in pattr, and you can use
> the @greedy attribute to work with pattrs in subpatches, among lots of other
> goodies built-in.
> –
> Interactive Media :: Concepts | Creation | Learning
> http://www.third-space-mind.com/
>

#149330
Jan 20, 2009 at 9:46am

Thank you everyone for the advice, i think i will crack on ASAP( after a cup of coffee) this morning

thanks again.

#149331
Jan 20, 2009 at 1:19pm

i read up on [pattr]&[pattrstorage] and [autopattr] but i am still slightly confussed by it.

how do i name my matrixctrl so that autopattr will see it ?

i also read the exccellent PattrKitty example but i am unsure how to connect it to the matrixctrl.

#149332
Jan 20, 2009 at 1:51pm

You can give the [matrixctrl] object a scripting name in the inspector under the “hint” tab. This will allow [autopattr] to see it and then you can use [pattrstroage] to save and load your presets.

lh

#149333
Jan 20, 2009 at 2:40pm

Well, I would say that’s the standard way of using the pattr system.
You usually do pattr tutorial 1 “pattr basics” for pleasure, then you do
tutorial 2 “autopattr bindings and storage” for real life, and use just
[autopattr] and [pattrstorage]. You can always go back to the other pattr
objects later, for more advanced use if needed.

> saving a matrix with [pattr]&[pattrstorage] is not very easy.
> i personally give a name to my matrixctrl object and use the [autopattr]
> object to have it stored in the [pattrstorage].
>
> g.

#149334
Jan 20, 2009 at 2:58pm

In Max, 2 tutorials about “pattr”, especially the 2nd one.
To expose the parameters of a UI object to autopattr, just name your object,
meaning give it a scripting name. If you open the object’s inspector, you
will see a scripting name: give it a name, close the inspector, open the
pattrstorage’s clientwindow, you should see the parameter(s).
J-F.
> i read up on [pattr]&[pattrstorage] and [autopattr] but i am still slightly
> confussed by it.
>
> how do i name my matrixctrl so that autopattr will see it ?

#149335
Jan 20, 2009 at 5:36pm

Quote: fader12 wrote on Tue, 20 January 2009 07:19
—————————————————-
> i read up on [pattr]&[pattrstorage] and [autopattr] but i am still slightly confussed by it.
>
> how do i name my matrixctrl so that autopattr will see it ?
>
> i also read the exccellent PattrKitty example but i am unsure how to connect it to the matrixctrl.
>
>
>
>
>
—————————————————-

It’s simple to connect a [pattr] (middle outlet) to your matrixctrl. Then your pattrstorage will see it. It will be called something like “matrixctrl[1]“. If you give it a scripting name in the Inspector, then that will be the new name.

BTW, once it has a scripting name, you can then do a lot of other fun stuff: move, show/hide, make clickable or not, and change the size (and in this case, extend/contract the dimensions of it) using scripting messages to thispatcher (check help file for thispatcher). Some of these commands can be very useful for some functions—I particularly like show/hide if you have a “basic” and “advanced” mode of interaction, for example.

#149336
Jan 20, 2009 at 6:07pm

On Jan 20, 2009, at 5:19 AM, Darren wrote:

> i also read the exccellent PattrKitty example but i am unsure how to
> connect it to the matrixctrl.

All you really need to do to incorporate a matrixctrl into a patch
that is set up to use autopattr, is to give the matrixctl a scripting
name.

- C

Chris Muir
cbm@well.com

http://www.xfade.com

#149337
Jan 20, 2009 at 7:41pm

I just want to say thank you all very very much i have now got it working.

was it really that easy.

sorry lol

thanks again

#149338
Jan 24, 2009 at 8:36am

#149339

You must be logged in to reply to this topic.