Hi,
so what's the question ?
What do you need to achieve this ?
You could maybe use 2 MTMs or a PM16 Roland (for 16 pads
connections ?) ... or whatever ...
But after resolving the problem of connecting all the pads to a brain
sending some midi notes & midi channels.
you'll probably have to get a midi patch so you could avoid delays
between different modules (if cascaded via "midi thru"). the patch
would have 8 midi out for example.
So your midi interface would be the master , & your Simmons & alesis
module would be the slaves... via a midi patch to distribute midi
notes at the right time.
If you get an SDSV, 7, 8 or even some of the SDS1000 you'll probably
need a midi to trigger interface (MTM or whatever) to midify the old
units so they could respond to your midi system.
hope I could be clear & that it helps...
Good luck,
Patrice.
Le 8 avr. 09 à 14:13, p_k_daniels a écrit :
> Ok I have SDS1000/2000/9 and a multimallet, as well as an alessis
> D4. (I hope to get a V soon fingers crossed that the other ebay
> bidder has exceeded his budget!but thats besides the point!)
>
> I have a fifteen pad simmons rackmounted kit and I want to be able
> to midi all the above together so that I can access all the sounds
> from the one set of pads. The plan is to use all the simmons brains
> as various drum sounds, the allessis for cymbal sounds and the
> multimallet for occasional other sounds.
>
> I have no experience at all of midi but understand its done as a
> daisy chain bus. I assume something has to be master and others
> slaves. Do i need to add a laptop? how the hell would I program
> this? how do you go about saving and recalling different midi kit
> setups? Does the fact that some pads are connected to one brain and
> another to a seperate brain complicate matters?
>
> Basically I would like to have 20-25 different kit layouts available
> at the touch of a button/turn of a knob
>
> oh how I wish i could as the manuals suggest "call simmons technical
> advise line for detailed midi help" ho hum
>
> oh and it needs to be robust and repeatable as its going to Gig!
>
>
>
[Non-text portions of this message have been removed]