v097pba8@ubvmsd.cc.buffalo.edu (Ken F Morton) (04/15/91)
I'm revisiting my idea of using an Apple II computer as dedicated MIDI processor to run in tandem with my GS running Master Tracks Pro. Here's how I'm thinking of working it now: MIDI out of the GS runs to the MIDI in of the AppleII (e probably). What the apple IIe would do is process the data coming from the GS to preform certain tasks the GS cannot do with MTpro. For example, controlling patch volumes on a multi-timbral synth that cannot be done by any way but SysEx. The II would take controller messages in realtime or sequenced into MTpro and convert them to sysex. In that way one could still use the graphical editing of MTpro. I'd also like to be able to digitize fader (or other input devices) to send MIDI data in real time. The possibilites are staggering. What I'm concerned about is MIDI delay and speed problems. A nice feature of the above system is that I can take MIDI data out *before* the II processor if I wish, via the multiple GS MIDI outs. Drums and such would benefit from not having to be delayed any more than they are already. Also using multiple MIDI cards in the IIe I can further parallel-ize the MIDI data flow reducing delays. The problem is that there is only one link between the GS and the IIe through which all data must flow. Perhaps an accelerator card on the IIe will minimize problems. Apple IIgs MIDI: out out out in <----------------------------out Merger | \ in in | \____________> To MIDI instruments | | | / \__< Instruments MIDI: in out out out(special) / \ \ \__________________________________/ \ \_________> MIDI instruments \____________> MIDI instruments Apple IIe The special out is filtered to send only controller or patch change data (or whatever) created by the IIe (with sliders, etc) back to the GS to be sequenced in MTpro as well as being provided to the MIDI instruments. This data would only be sent out through the special out directly - otherwise it would have to go through the GS first to get to the other outs of the IIe. The outs of the IIe would be seperate by the way (more than 16 channels avail). I could create a sequencer in the IIe to directly record the data thereby hastening the MIDI flow by bypassing the GS and Mtpro - but then sequencing would be a pain - two screens to worry about, complicated cut and paste (I'd have to record the IIe midi data onto the GS and then manipulate, and then record back into the IIe to get rid of the MIDI delay...). Perhaps I could work entirely with the GS and MTpro, and then seperate the data before mixdown into the GS and the IIe to gain channels and speed. Hmm... There's more, but I can't think of it now... What do you people think? Ken Morton "A vacant engineer rides on a v097pba8@ubvms.Bitnet train of thought that will not v097pba8@ubvmsd.cc.buffalo.edu lead him home" - Edie Brickell