MegaDrum configuration hints & tips

[angr77]

Hi. I have been playing around with MegaDrum Manager (latest ver) to configure my Megadrum Module 32. I am running this in windows 7 together with the app Vsthosts which is hosting Addictive drums.

In MegaDrum Manager you are configuring which midi ports megadrum should communicate with and you have two port choices when running it over USB. MegaDrum midi (Usb) and megadrum midi 2(usb)

In my case i will be able to run MegaDrum Manager at the same time as addicitve drums, to be able to configure it in proper way...online.

If i setup mega drum manage to communicate on midi port 1...(in) and setting out to midiport 2...Addictive is able to play the drum sounds...but there is alot of strange things happen...

I have tested the midi thru function...but it does not feel like the right way to do it.

How do others setup their test environment? What is the story about the two different usb based midiports on MegaDrum?

This is maybe something mentioned about this on the forum...but i can't find it. It is not mentioned in the documentation.

Last - when things have been properly configured and stored into MegaDrum Module...it works and is solid as a rock against vsthost/addictive drums.

Anders

[dmitri]

Two USB MIDI ports is a feature which allows to control MegaDrum using MegaDrum Manager and use it with any other MIDI software at the same time. In MDM you should use the same MegaDrum MIDI port for MIDI In and MIDI Out. In Vsthosts you should use another MegaDrum MIDI port.

[angr77]

Thanks Dmitri,
Is the megadrum module sending the same midi information on both ports?

Best regards

Anders

[dmitri]

Yes. Both ports are identical.

[angr77]

Hi again!

I took a real journey into the MegaDrum module/MDM...yesterday.

I am using the lastest firmware/MDM...i have created a MDM config file which I send to the MegaDrum Module. So far no problem. But if i do the function get config from md module...most of the settings comes back as I originally set them i MDM....except the hihat foot pedal settings. I am using footcontrol...but when getting the data from the MD module it shows up "pot" instead. I think i have red somewhere that there was problems reading sysex files for hihat foot controller on the forum...should this work?

I have still problems with MDM which freeses or hangs real hard occasionally...quite often...running it inline with VSTHost app.
mdm uses Midi usb port 1 and VSThost midi usb port 2. I am using default speed and latency on the Megadrum module.

Running them stand alone seems to work better. I am going to try another system to see if the problems disapper.

Best Regards

Anders

[dmitri]

I am using the lastest firmware/MDM...i have created a MDM config file which I send to the MegaDrum Module. So far no problem. But if i do the function get config from md module...most of the settings comes back as I originally set them i MDM....except the hihat foot pedal settings. I am using footcontrol...but when getting the data from the MD module it shows up "pot" instead. I think i have red somewhere that there was problems reading sysex files for hihat foot controller on the forum...should this work?

Does anybody else experience the same problem?

[talrusher]

yop.... mdm hangs up or dont change settings... the foot pedal settings arent read anyway.

[angr77]

Hi!

i have not been able to test it again with another computer because of vacations...
But did any body else experince problems?

[cschlipp]

I'm sorry that I wake up the dead...


...but I'm facing this problem too.
The configuration read out by the MDM differs from the configuration MD shows on its LCD.
Changes made in MDM do not have any effect.

Has there been any solution?

It seems all a bit strange and as I'm new to MD, it's hard to realize whats going on.
If I connect ezdrummer to my MD, e.g. suddenly all notes are set, no matter what was selected before...

[dmitri]

There have been a number of changes in MDM since the last post, including those addressing mismatches in settings between MDM and MegaDrum, so you will need to describe your setup and your problem in details.