hey hey!
i think that good ideas will always capture community attention and folks who can help will jump in
the current pile of m4l devices in the repo are meant to springboard people into creating their own, not serve as a final resting point or closed collection. we’d love PRs, forks, alternatives, etc to help grow the crow m4l ecosystem! i’m trying to keep on top of requests, but i think that together things can go faster and further 
that said…
this should do the trick: ^^trigs.amxd (99.9 KB) nb. please lmk how you get on with it and i’ll add it to the repo!

for the curious, here’s the patch:
basically uses techniques from the [crow] help patcher to match a midi note to execute a pulse message through each of crow’s outputs. if you want midi thru, then connect a [midiout] to the [midiin] 
i will be setting some time aside to explore these (see below), but this would be an excellent way for someone to dip their toes into max + crow. happy to help answer q’s!! otherwise, it’s definitely on the list.
fwiw, crow + Max programming is really nicely approachable because of how much work trent has put into the API – the slowest part is honestly deciding on a final UI that is approachable and immediate, for public release. i was able to spin up a modified version of the jf_synth device that addresses individual outputs in a few minutes. it doesn’t look good (basically just dropped a “voice selector” on top of existing text, lol), but it works!
this sort of “i need it to do the thing it does, but different” is exactly why max for live is so so dope. you can get changes up and running really quickly 
yo, also, addressing multiple jf voices individually is amazing. excited for folks to try this!