poly note vs midinote

Sounds like the midinote lookup system is a dictionary lookup.

message: midinote X Y [z, ...]

When Y > 0 poly~ seems to store an active-state in a dictionary whose key is X

activeVoices = {}; // some dictionary

activeVoices = 
{   
  X:  getInactiveInstance()  // X = 60, getInactiveInstance() would return the first inactive instance of a mutemap lookup
}

where getInactiveInstance() would look at the mute map and return the first instance whose busystate is free (I can't remember if 0 means free or 1 means free, but whatever)
and then assigns that value. i.e.

midinote 60 127 ...

activeVoices = 
{   
  60:  1,
}

and routes the full message 60 127 ... to instance #1

when receiving midinote 60 0 it does
getActiveInstanceByNote(60)

function getActiveInstanceByNote(note) {

return activeInstances[note]; // 1

}

and relays the message 60 0 ... to that internal instance, i.e. with max messages to poly~
target {getActiveInstanceByNote(note)}, 60 0 ...

The voice busy-state will be determined by any messaging sent to thispoly~ which often has its inlet connected to an outlet from adsr~ that sends mute messages, or can also do its detection via envelope (averaged~ rms) signal inputs directly to thispoly~ as well.

So if one had to write some voice-allocation & lookup mechanisms... it isn't crazy.

But if we fuck around and look a bit, the poly object with no tilde already implies the wrapping of most of these mechanisms with most of the lookup value stuff I'm describing exposed as returned values from its outlets.

So you could use poly (no tilde) to not have to write that stuff I mentioned in javascript or dict objects or whatever else might be leveraged logic-wise.

Thanks for this thread btw, cheers