For my own preset system, I'm trying to build up a message which contains a large number of parameters i'm storing. So far this works fine with pack and unpack, but now I'm starting to have so many parameters that there are to many inlets and outlets to those objects. Is there a possibility to split a large message into different smaller messages or lists which I can treat individually (and thereby reducing the number of inlets on 1 large unpack, but having several smaller unpack's)?

What I've attached obviously doesn't work. I hope this makes some sense...

D.

http://www.pdpatchrepo.info/hurleur/message.list.problem.pd

Hi Domien,
you were pretty close. Only pb was unpack type mismatch - you have to define whether unpacking float or symbol.

See attached
ale¨

http://www.pdpatchrepo.info/hurleur/message.list.working.pd

Thanx a lot caucasian. Grrr, lists and symbols and messages always give me headaches. You wouldn't happen to know how to achieve the inverse. That is: a lot of floats going into a couple of pack's and constructing one big message out of it. I think it must have something to do with list and prepend but I just can't get my head around it.

Thx,

D.

[pack] [pack]
| |

The rightmost [pack] gets stored in . Once a list is sent to the left inlet, the stored list gets tacked on to the end of the incoming list. You can then daisy chain them to create long lists out of many separate [pack]s.

. [pack] [pack]
. | |
[pack]

| |

That's great maelstorm. I saw that there's also a list append, which is nice. Now I have just one more question. Is there an option to convert the contents of a list to a message without doing something like this:

|
[set $1 $2 $3 $4 $5 $6 $7(
|
[ ( <-- this will be the final message

D.

Yep.

|
|
[ (

will just attach the word "set" to the beginning of the list, but it also adds the "list" selector. gets rid of the "list" selector, so it becomes an actual message instead of a list whose first element is "set".

Knowing when that list selector gets added and when it does or doesn't matter is something I found very confusing when using Pd's list processing to create messages to send to objects. When in doubt, stick a at the end to make sure it's a message.

Super! Now my preset system is as good as i need it to be and very simple to extend. Thx Maelstorm. However - feeling a bit embarassed now to ask yet another question - would it be easy to write those values to a table, because this would make possible to save presets at runtime, where now i have to make them in compile time?

d.

If you really want to use a table, you could use a [tabwrite] and address a certain index per parameter. If new parameters occur you need to resize the table (and a new index).
But maybe have a look at the [textfile] object..

You can write lists to a table by just sending the list to the table, but you have to prepend the list with the offset index.

(list)
|

<-- 0 for first index
|