@RT5000 Any object (all objects) can have a $ variable as one of its arguments.... you don't need to use a [float] to define it.... it will be translated as the abstraction is opened.
So you can use $ variables as part of a symbol in the OSC address.... [oscformat /EnvATT_$3] will become [oscformat /EnvAtt_1] if the value of $3 for the abstraction is "1".
A $ variable in a message acts differently.... taking its value from an incoming message.

GUI's can be told to change their send and receive addresses by sending them a message, so they can be dynamically changed within an abstraction.
And those addresses can contain $ variables anyway.
The same for e.g. [send message_$1] because it is an object.

[route] and [select] can also be changed (for a single argument) through their right inlet.... but again... they are objets so you could put a [route $3 $1 $2] if you wish.
So you do have a few options.

Knowing that it is not easy, I had a go at explaining this a while ago...
https://forum.pdpatchrepo.info/topic/9774/pure-data-noob/4
David.

@RT5000 $ variables are translated as a patch opens, so the "mother patch" arguments will be translated to $ variables for abstractions.
Which means that you need a "super mother patch" that opens the "mother patch" with all the variables that you will want to use for the abstractions.
You could otherwise use a counter and dynamic patching to create the abstractions with an incremented argument (or more) like this.... dynamic.zip
David.

@impression There could well be messages in the Pd console in red "cannot create".
If so then use Deken ( Help.. Find externals ... from the Pd top menu.)
It needs a fairly recent Pd version with the [file] object.
Please let me know which externals were needed as I would like to make it pure vanilla.

Ahh... ! .... I think it needs [count]....... which is a vanilla abstraction.
I have just added it to the zip file..... cart-5-vanilla.zip
David.

@impression To play files from a folder this might help...... cart-5-vanilla.zip .... although I am not certain that it is 100% vanilla.
As you will know the paths to your folders you will not need all of it, and probably not the random part either.
Otherwise I think the else library has an external for listing folder contents.
David.

@porres I cannot remember to tell the truth as it was a long time ago. Yes, I believe what started my "investigation" (learning session) was finding that a list could be distributed across the inlets....which surprised me for this object.
Maybe that could be described as a bug, as I cannot see that anyone would ever have used it for any purpose, and it can cause problems.
David.

@gentleclockdivider This might help...... tag.zip
Try things out with pd-selector.pd
I called the [route] problem a "bug" in the zip, but that is not the case. It is awkward to deal with though.
It was work in progress a while ago.
[rawprint] is one of my "must have" externals. It prints detail of the atoms comprising a message.

You will see in that patch at the bottom left that a message [list me 10 woof( will not behave as you might expect ....... because the first atom in the list (me) is a symbol.... so [list] is sometimes necessary... as @porres says in the previous post...
David.

@gentleclockdivider Put a [list] before your [set $1 $2 $3 $4 $5(
David.

@kazeko I did a bit more work on it here....... https://forum.pdpatchrepo.info/topic/14240/pure-data-and-pi4-with-usb-audio-interface/12
As so often, it might be hard to remember how it works, but I think I designed it to select an interface automatically (by name rather than the position in the Pd Media tab list) as a patch was opened.... but it needs the external [audiosettings] from the mediasettings library.
It seems that the librarywas available for the RPI4.
David.

@jbaker Just leaving it here it will be found, but if you can give it a good title and description (which will help people to find it when they are trying to accomplish something similar) you could post it under the "patch" section that you will see on the home page for this forum.
Well done....!
David.

@jbaker Just a little more info that might help, although you might already have everything that you need.
Anything in the string /x/y/z/etc is part of the osc header.... the address.
The data that follows..... that is then sent to that address.... /x/y/z <space> data ..... is the part that needs to be specified as i, f, s, b

The address string should always be comprised of symbols (even though parts may "seem" to be integers or floats) and problems can arise using vanilla [oscparse] when they are not..... so [fudiparse] and [fudiformat] can solve that problem as demonstrated here...... vanilla_bug_oscparse_solution.pd

Unfortunately quite a few devices send malformed osc headers.
MrPeach objects don't care.
David.