Thoughts about OSC server for Shunt installation

My first post…

Good to see everyone on Thursday. at the meat bar. I have been thinking about the central sever program (MCP) for the Shunt installation.Here are my disorganised thoughts, in part including discussion from thurs:

• MCP_OSC_S – an OSC server which receives OSC messages from Agents. Possible OSC message:
  • x, y position
  • I am percussive, I am melodic, I am stockhausenic
  • note data
  • I am happy, I am drunk
  • Something should happen soon
• MCP_OSC_C – an OSC client which sends OSC messages to Agents, e.g
  • Notes recently played
  • Times of upcoming events
  • Clock
  • IP addreses of nearby agents??
• MCP-Audio – an algorithmic audio mixer which receives 2 channels of audio from each client and mixes them to (4?) channels based on the positions of the agents. Possible mixer rules:
  • Turn down consistently loud agents
  • Filter spectrally noisy agents
  • Power per cycle rule – agents can only output so much energy per cycle. Once energy used, agent is faded out until next cycle
• Agent – MCP Handshake. Agent connects to MCP_OSC_S and registers to receive OSC messages from MCP_OSC_C.
• Agents must  also be OSC servers to receive messages from MCP_OSC_C