charles wrote:have you any programs written for the Atari ever?
Foxie wrote:Some potential advantages of including the MIDI inputs:
charles wrote:im off topic , but do u and i have some shared midi equipment...?
im in (and have been for about 6 years) the process of
writing sysex editors/librarians for the equipment I own
tyk wrote:5. Complex routings between multitimbre MIDI-devices. I have dreamed about 3 separate midi inputs and outputs. There is some mixer like controllers that put sliders to every channel, so there isn't left any channel to keyboards. And there is some rack-synthesizer that use heavy sysex that they really need own midi-cables. So if somebody make hardware, I promise make (maybe ugly and hard to use) routing program.
Atari74user wrote:MIDI ins would be very pleasing for me, if i were to be greedy!
Foxie wrote:This sounds interesting, do you need information about programming MIDI hardware? I know how to program the Soundpool MO4, Friend Chip MM1, C-Lab Export, and the Macman. I've got some information on the Midex and Unitor, although I need to do more work reverse-engineering them. The Log3 and the SMP24/II remain a bit of a mystery to me.
Foxie wrote:I was planning to simply merge all MIDI inputs together in my sequencer. All 16 channels remain independent, but not the individual inputs. However, the hardware I'm designing will probably keep each of the MIDI inputs independent - so you could do some complex routing if programming it directly.
If I do include MIDI inputs, then how many inputs? I was thinking of two, because that requires little extra hardware. I could increase that to six by using an additional MCU. It seems a bit silly to go to that effort if I can't figure out how to support the inputs in Cubase!
One option I have considered is to have a mode which turns it into a merge box. The six inputs would be merged, and sent out the eighth MIDI output. You could then plug that output into the Atari's MIDI input - giving you six MIDI inputs without the extra expense of a merge box.
charles wrote:im sorta loosing my patience foxie , any neat code I can tinker with ?
charles wrote:; Pass dev_struct into MROS IOM. Opcode $14 (undocumented).
; Return with pointer to vars in a5.
is xbios 14
charles wrote:this is fetching the address of the midi buffer ???????
if theres data placed into the midi buffer and you change the interupt priority level
it will out put whats in the buffer.
but by using 512 byte blocks I feel this is using only 4 configurations of 128 bytes
meaning it adds 4 individual outs? a midi buffer is circular and made of 128 bytes..
Users browsing this forum: No registered users and 2 guests