Page 1 of 2

Input failure...

PostPosted: Mon Dec 31, 2012 10:31 pm
by ibanman555
Hey everyone,

I just had an input on my MD fail, just programming and tweeking, I've been playing it all day. Just randomly, Input 7 (Aux 1) stopped working. I swapped it to another input and it was working fine there. I tried to connect multiple triggers to that input just to verify, but none of them worked.

I find this strange and everything is stationary and I can't imagine something came loose inside. I then reloaded the firmware thinking something weird happened software-wise, but it didn't help. I feel taking it apart to investigate is a lost cause, as my MD was built by Dmitri himself, I trust his work...

Has anyone else experienced any input failures on your modules?

Re: Input failure...

PostPosted: Tue Jan 01, 2013 10:29 am
by angr77
This is a dual input, right?

I would check if both ports have stopped e.g head/rim...if so...i am guessing some real type of errors have occured. If only one port have stopped...i would suspect the soldering.

Angr77

Re: Input failure...

PostPosted: Tue Jan 01, 2013 4:48 pm
by Maylord.war
Do you use a Roland 3zone pad?

Because this type of pad require 2stereo jack (es. ride and AUX ) , if you setted one channel in this type automatically the next input is associated with the previous to read only the piezo message of the previus and the pressed switch in both jack's.

At last, save your configuration in .Mds file with Megadrum Manager, reboot the Megadrum with left button pressed and load the settings from .mds file, i'm sure that can hope to "unbrick" this problem.

Re: Input failure...

PostPosted: Tue Jan 01, 2013 6:23 pm
by ibanman555
Yes this is a stereo input, and I am using my custom made pads. Now they only have one piezo in them, attached to the tip. I tested both tip and ring using two other pads and both are out. I'm beginning to think it is a software issue, because I had MD freeze up with some really weird display crap happening, weird characters on the LCD. It stopped working and needed to be rebooted. I will try a save and hard reset. Hope I can fix it.

Re: Input failure...

PostPosted: Wed Jan 02, 2013 9:59 pm
by ibanman555
Maylord.war wrote:At last, save your configuration in .Mds file with Megadrum Manager, reboot the Megadrum with left button pressed and load the settings from .mds file, i'm sure that can hope to "unbrick" this problem.



I'm not sure I understand what process to follow here... I cannot load settings with an .mds file while booting up Megadrum holding the left button. My understanding is that this is for firmware upgrades only.

Re: Input failure...

PostPosted: Wed Jan 02, 2013 10:21 pm
by Maylord.war
I'm sorry. The left button is for bootloader start upgrade. The right button is to load default settings.

BEFORE DOING THIS save your pad configurations into a mds file with megadrum manager.

Connect the Megadrum on your pc

Open MdManager and click "open midi"

click to "get all"

Go up to " Main, all setting, save to file" and save.

click to "open midi" to close the midi connection

Disconnect megadrum

Power up Megadrum with RIGHT key pressed and try to connect your pad to AUX 1 ( when you have the problem)

If works reload your previous mds file to reload your personal configurations with MdManager

Re: Input failure...

PostPosted: Thu Jan 03, 2013 3:18 am
by ibanman555
Alright... I followed those steps:

Restarted Megadrum while holding down the right control knob, and it appeared that everything restarted in Default. Unfortunately the input (Aux 1) still does not work, both tip and ring of that input. Don't know what else to do, but I find it very strange.

For the mean time, I've just patched my drum pad to the next available input...

Re: Input failure...

PostPosted: Thu Jan 03, 2013 8:58 am
by dmitri
Do Aux 2, 3, 4 ... and so on inputs work? Did you change MaxInputs from its default value?

Re: Input failure...

PostPosted: Thu Jan 03, 2013 5:43 pm
by ibanman555
dmitri wrote:Do Aux 2, 3, 4 ... and so on inputs work? Did you change MaxInputs from its default value?


No. No I didn't... It's amazing how easily it is to overlook these things...

However, the pad did work until I reloaded my .mds file into MD. No midi info down that channel. I decided not to "send all" pad info to MD and then sent the data one pad at a time. It's still working. Looks like a bug of some sort and I can't quite pinpoint what caused it. If I avoid sending mass info from MDM to MD, all appears normal. Thanks Dmitri! Now I feel better it not broken!

Re: Input failure...

PostPosted: Thu Jan 03, 2013 6:29 pm
by Maylord.war
So the problem was in the setting of "Max input"? :)