hey mnb, i just downloaded the patches and gave them a listen, really really like them, nice work. I'll have a quick check through them just to make sure that everything that needs it has the $0 arguments and then I'll get them up and running.
if it will run on the atom then it should be fine to run on the server. I'll test it out first like I have been with lead's patches and let you know if there are any issues, thanks for helping out. I'll ping you an email so you have my address, i realise that it isn't so obvious on my website heh.
Maelstrom, I was wondering if there might be something like that but hadn't found it for some reason. thankyou for pointing it out to me, I'm testing it out now. will take a bit of rejigging as i realise the namecanvas would have to be in the top layer and cant be in a subpatch or abstraction. pretty sure i've got it tho.
currently the $0 argument of the patchComs abstraction is already being sent to the main patch as this is how the audio is routed between the patches. there are a set of send objects in the patchComs called $0-l and $0-r, python receives the $0 value and then sends messages to the master patch which sets a pair of receive objects to get their audio from those sends. means that i can do the crossfading in the main patch and not have to send too many control messages to the loaded patches.
hopefully I can have this working in the next couple of days.
audiolemon, i figured it was a picture of an old timey radio. i quite like it tbh heh.