these are great ideas to explore! this collection of devices isn’t meant to box in, but to provide a framework for folks to build their own unique use cases
i’d say just rip into this! you’ll want to go through the druid studies to get a handle of the syntax and go through the [crow] object’s help patcher in Max to see how to apply that syntax inside of Max’s visual coding environment. I cannot recommend Matt Wright’s Kadenze course highly enough. you will walk away with a full understanding of how to program in Max, for free
you can ping here for help if you run into any specific questions or hurdles, and you can share any helpful snippets you land on here: ^^ recipes: max / m4l snippets for crow
yes, though depending on how much traffic you’re sending you may find that you can only do 3-4 channels.
1 command center per crow. you can load as many of those m4l devices to speak to one crow as you’d like (or until things get unstable, depending on how much stuff you’re slamming into the stream), which all route through a single command center.
…this is pretty much already possible using other MIDI-generating/affecting M4L devices ahead of 6 jf_vox devices each set to speak to a different JF channel! it’s totally valid to build a group of jf_vox’s and set them to receive from the same MIDI track and throw a few of Live’s MIDI Effects ahead of the incoming MIDI on each channel:
this sorta stuff extends the crow devices so much – i always have a Random ahead of my jf_vox’s
hope this helps! let us know where you get to!!