@whale-av Is the only way of using connect with the number of the object? I could see it would be tricky to count correctly for larger sets of objects.

I guess I can connect it all up by hand then look in the saved pd file with a text editor.

@whale-av Oh wow, dynamic object creation. I had no idea that was possible. My mind is blown. Thank you. I've only been learning PD for a week. I think I'll wait for another week before I start using that for real!

Here's a quick test patch I made just to see how the obj and connect messages work.

dynamic-object-creation2.pd

@whale-av Thanks for your speedy help today!
Ah ok, so [loadbang] and anything it triggers isn't running at creation time, it's actually running after that at "load" time.

I'm writing vanilla PD patches for the Bela so I was wanting to keep everything like memory as small as possible but your answer prompted me to go and check on the Bela's specs. It's got 512MB of RAM, so I've probably been worrying unnecessarily.

In abstractions I've been using the following to provide default values for creation arguments that aren't specified:

[loadbang]
|
[list $1]
|
[select 0]
|        |
[7(      |
|        |
+--------+
|
[...\

Where "7" would be a default value. (That seems to work well unless I want to explicitly set the creation argument to 0).

But what if I'm using $1 to set the length of a delay:

[delwrite~ $0-del $1]

How can I set a default value for the $1 in the [delwrite~...] if my abstraction is created without a $1 creation argument?

@whale-av ah, thanks!

The [*~] object can take either an audio or control input on its right inlet.

I want to create an abstraction that does something similar and can take either type on its right inlet. How do I do that?