Page 1 of 1

Naming conflict with multiple megadrums into one computer

PostPosted: Sat Jan 09, 2016 5:13 pm
by mbira
Hi,
I have one megadrum with a USB output and then another megadrum that is actually two 56 channel megadrums with one slaved to the other with a USB output.

Both of those are going into a USB hub and then into my Mac. Both devices are recognized and working well, however when I am using Ableton, I have one Megadrum going to one track and another megadrum going to another track. These just show up as Megadrum #1 and Megadrum #2. The order of these seems arbitrary and often I have to manually flip which is going to which track asAbleton doesn't seem to see any difference between the two.

Also I feed one of the Megadrums into Midipipe. When I have both megadrums connected to the computer before I open up Midipipe, then the program gets confused about which one to load as they both simply show up as "Megadrum". Luckily I built the 112 channel Megadrum with a power switch on the front of the enclosure so I can have it turned off and then open Midipipe and it will recognize the correct device and then I power up the second megadrum, but this is not ideal in high pressure stage setups where things get forgotten.

I have the Sysex Chain ID set to 0 for the first box and 1 for the second box but that doesn't seem to make a difference. Is there some other setting I can change so the computer recognises these as two different devices? Thanks.

Re: Naming conflict with multiple megadrums into one compute

PostPosted: Sat Jan 09, 2016 6:15 pm
by dmitri
mbira wrote:I have the Sysex Chain ID set to 0 for the first box and 1 for the second box but that doesn't seem to make a difference.

Sysex Chain ID is only useful for configuring multiple MegaDrum devices chained over standard MIDI ports.
Is there some other setting I can change so the computer recognises these as two different devices?

I believe it can only be done by making USB stack in MegaDrum configurable (names, PIDs/VIDs) but if configured from a PC it will present a "chicken and egg" problem.

Re: Naming conflict with multiple megadrums into one compute

PostPosted: Sat Jan 09, 2016 7:37 pm
by mbira
Hi Dmitri,
So it sounds like having one turned off first before starting the programs is the best solution then?

Re: Naming conflict with multiple megadrums into one compute

PostPosted: Sat Jan 09, 2016 10:39 pm
by dmitri
At the moment it is possibly the best option. It's not very common to connect more than one MegaDrum to the same PC.

Re: Naming conflict with multiple megadrums into one compute

PostPosted: Sat Jan 09, 2016 10:49 pm
by mbira
Right on. Thanks for the reply. We are definitely not doing anything very common. I am triggering synth sounds and video projection with three different marimbas.

Re: Naming conflict with multiple megadrums into one compute

PostPosted: Sun Jan 10, 2016 9:19 am
by airflamesred
mbira wrote: I am triggering synth sounds and video projection with three different marimbas.

Now this,I would like to see.

Re: Naming conflict with multiple megadrums into one compute

PostPosted: Fri Jan 15, 2016 6:19 am
by mbira
I won't post a link here, but you can google the band Rattletree...that's us.

Re: Naming conflict with multiple megadrums into one compute

PostPosted: Sat Jan 16, 2016 2:24 pm
by airflamesred
That looks like a lot of fun Joel.
Have you checked out Soniccouture, they have marimba and mbira. The marimba is second to none.