paths in athenacl are an ordered sequence of pitch collections (multisets), which can be interpreted as pitch space, pitch class, and set class values.
sorry for the delay! i see your question. in short: spaces.
in demo/midi/script03c.py, command-line arguments are being fed to an Interpreter instance.
when using this approach, each string works the same as a command-line string in an interactive session.
so, in an interactive session, you can use a space to delimit multipaths within a path. any syntax that works for a path works here, it just needs to be given all without spaces, and spaces delimit path components.
for example, here i create 1 path with 4 multisets; the first from pitch classes, the second from a xenakis sieve, the third from a set class, and the fourth from pitch space values.
pi{}ti{} :: pin a 3,4 3@7 3-11 f2,f#9
PI a added to PathInstances.
pi{a}ti{} :: piv
PI: a
psPath 3,4 -11,-8,-5,-2,1,4,7,10 0,3,7 -19,66
D#4,E4 C#3,E3,G3,A#3,C#4,E4,G4,A#4 C4,D#4,G4 F2,F#9
pcsPath 3,4 1,4,7,10,1,4,7,10 0,3,7 5,6
scPath 2-1 4-28 3-11A 2-1
durFraction 1(25%) 1(25%) 1(25%) 1(25%)
TI References: none.
in a script feeding strings to an Interpreter, you can provide 'pin a 3,4 3@7 3-11 f2,f#9' to get the same result.
does that answer your question?