> > i'm convinced it's better to design one system that works > > for event-only as well as audio-only plugins and allows for > > the mixed case, too. everything else is an arbitrary > > limitation of the system's capabilities. > > So, you want our real time synth + effect API to also be a full-blown > off-line music editing plugin API? Do you realize the complexity > consequences of such a design choice?
Umm, I want that. I have little need for the RT features, myself. I want to use this API in a FruityLoops like host, where the user is not bothered with making wiring decisions or RT/non-RT behavior. I want to use it to develop tracks in the studio. So far, I don't see anything preventing that. My host, as it evolves in my mind, will allow things that you won't. You can load a new instrument at run time. It might glitch. So what. It will certainly be usable live, but that is not the primary goal. As for time vs. time debates, my original idea was that each block was based on musical time (1/100th of a quarter note or something). I've been convinced that sample-accurate events are good. That doesn't mean I need to change the tick-size, I think. Tim