Ever since starting that course at the university I keep coming up new ideas for my application. Integration with MAX/MSP and VST, using Phidgets and other sensors to control things like volume, RFID to select instrument patches… The list is long. I have to prioritize. In a way I have two separate paths for the conch. One is gallery life, which is the first priority. Then there is the afterlife, further development and making the software accessible to home users. Also, I have a demonstration coming up at the Guthman Musical Instrument Competition, and I still haven’t fixed all the things I need to fix for that. So here is a list of priorities:
Demonstration:
1. User profiles. Save and load. When I fix this I can rehearse in advance of the demo and just load my profile as I set up.
2. Bug fixing. I’m sure there are many I have not found. Like interrupting training.
Gallery:
1. Solve the sensor connectivity issue. How do you fit the headset properly if you only have an audio interface?
2. Visualization of pitch, a dot of light on the wall rising and falling perhaps. This can be done with a servo and Phidgets. Or a screen on the wall with graphics.
3. Funding and building the sculpture.
4. New voice audio (using speech synthesizer today).
Further development:
1. MIDI out.
2. UDP out (both raw and processed braid wave data).
3. Audio BUS.
4. Other sensor input.
5. Include detection of facial expressions.
6. Design a nicer GUI.
With MIDI out and UDP it can be used in conjunction with other software, like MAX to make a more complex synthesizer than the one that is programmed in the conch. This opens up opportunities for using the technology in live performances.