The plan for Phase I

[averwhy]

I think it makes the most sense to tackle this project in phases. We have to build up a foundation before getting into the more complicated features. First, for our audio Engine- test if CoreAudio can handle our needs for this. It needs to be as low latency as possible. I'd love to avoid creating a custom audio engine for this since I think that would be really tricky. Once that's out of the way, this is what will get tackled next:

• Basic UI (ugly sliders and buttons just for testing the audio engine)
• Proof of concept MIDI integration (just testing if we can send and receive signals, maybe play/pause from an external app)
• Two audio tracks with pitch control

After we have these basics in place, we can start thinking about:

• Multiple audio tracks (6 maximum I think- I don't see any reason to go beyond that)
• Basic mixing (EQ and crossfader)
• Audio routing (the options part of the app would start here too)
• Cue and seeking?

Once we get all of these features working smoothly, we'll talk about phase II.

[averwhy]

source