Need help diagnosing possible hardware faults in MD

[bcslaam]

Well I have taken a few days off after more than 2 weeks of troubleshooting MD and read more of the forums and documentation. There has been much discussion about some issues in this thread
viewtopic.php?f=3&t=2626&start=20

but the scope has gone wider and Dmitri and I are in disagreement.

At first it appeared as though cold resetting the unit solved some of my issues but they have all come back.

1) Load Rom Map freezing, save config freezing occurs after some time. I reset, it no longer freezes then it starts freezing again after a few hours. Whilst in menus on the panel multiple VU bars (not moving) appear over the parameter text. After cold resetting hitting hhat on 2/3 lights up sensors 8/9. and I am aware of hh input settings or dual/triple head setting affecting sensor order. I have sifted through the forums and really tried to solve this assuming the unit is not faulty and its user error,

2) MDM sysex init and timeout errors frequently. I end up mainly using the panel now because of this. I have double checked USB leads, uninstalled copperlan, rtpMIDI virtual patchbays and gone direct from MD to PC/MDM with a short tested cable no other programs running. The unit will only hold green lights in MDM until I do a get-all or send-all or move a parameter to much as to apparently overflow the midi buffer (I have tried different buffer settings in MDM options), then a MIDI sysex timeout occurs followed by init errors. Only way out is to turn off MD, close all programs on PC, reset all midi drivers then reboot MD

3) Same settings for a 3zone cymbal that worked for a while no longer do now. After double checking manually and loading from file from when they did work. I cant get them to work anymore.

4) "AltEncoders" never stays off no matter how many times I switch it to no. Right hand encoder often cant toggle stably between yes and no, like it may be faulty but TBH I think its software related aswell.

5) I have powered it only from charger and used MIDI only. As soon as anything is plugged into the MIDI out it behaves strangely. I cannot use it as a simple midi device either.

6) MIDI light remains on, MD totally freezes requiring re-boot.

7) Intermittently turning on MD it will freeze on the copyright dialog.

8) In MDM pedal notes from bow semi open down to the bottom changes the wrong parameter in ipad commander, ie MDM"bow semi open" changes commander" "edge semi closed" and so on.

I am convinced there is something wrong with this unit. I have exhausted every possibility, with the assistance of a friend to keep my methods in check today. I really want to be able to use Megadrum in my studio Dmitri and I need your support as manufacturer. I feel like we are working against each other and I've never had this experience from a manufacturer before. I do know how to trouble shoot. I have a complex digital studio that I have built and maintained successfully for years. Should I make another video? What more do you want me to do? Why are you so reluctant to accept this could be a bad unit? Should we skype so you can see it live?

I guess I had to say this here on the forum before I go to PM with Dmitri because maybe someone else can help...? Has any of the above points happen to you?

I have truly tried, systematically, every possibility. I disagree with Dmitri's comment of it's "due to the wrong approach to configuration". After more than 2 weeks of trouble shooting MD I would not be randomly and manically going at it without a method. I'm often stopping and regrouping my thoughts, and step by step going thru a particular problem. It is just that the behavior is so hard to put my finger on, even Dmitri admitted that. His comment "I believe it is counterproductive to try address many things at the same time" is true in one context but it is ignoring that I have to describe a number of weird behaviors that are causing multiple problems.

One may ask what is it I want..simple

1) I want to use Megadrum (I dont give up easy), besides as I've said it has unique possibilities, I respect that.

2) I would like to return this unit and for it to be tested and another sent in its place if it is found to be faulty. I'd like to do this with the minimal amount of downtime because I have pressing sessions requiring edrums.

3) In fact what would be ideal is that - Dmitri sent me another tomorrow and I send this one back tomorrow or when the new one arrives. For that I would be grateful.

Thanks
Ben

[dmitri]

Please PM me to go forward.

[angr77]

Hi!

I have been following this thread for some time and I have been looking on the videos. It does not look right...MD is a though bastard...but not as though as you have been facing. I have three different MDs...but when moving to the ARM based version a couple of years ago...most strange behaviors disappeared. I have been following the forum for many years...and I can just recall one case where the MD was really broken.

One scenario which I am afraid could start creating errors is if using a fixed amount of inputs (e.g 32) and try to load the rom maps which are defined for 56..,

I would suggest that you do a reset as described before.

Forget about the rom maps and rom kits for a while.

Just load the CY-15R config from my library on the actual two channels. My config will include everything you need for the CY-15R using the MegaDRUM Advanced setting in AD2.

Do you get the same kind of behavior now?

You talk about the iPad commander in the thread...if this the MegaDRUM commander...I would be very careful if trying to change any parameters from the app against the MD. (It is really old...and the MD has many new functions not supported by the iPad app)

Best regards

Angr77

[bcslaam]

Hi angr77, thanks for the suggestion. I had urgent business last couple of days but held off sending MD back to try your cy15r setup files.
No luck unfortunately. Tried resetting, testing the leads that came with cy15r. Swapped them round. If those settings are working for everyone else +- snall adjustmebt thats convinced me that there is something wrong with my machine.

All i was getting was bell and bow if i changed all thresholds down to like 5 or so. Edge never showed up. If i had the thresholds setvaround 20 as you did i would get mainly bell with bow if i tapped really lightly on the bow. Between the coms failures of MDM and the freezing up of MD Ive decided to ship it back tomorrow.

Dmitri has agreed to test and grant me my wishes mentioned earlier. If it is indeed user error, which I have done all i can to ascertain it isnt, then i will not be getting the machine back. I did suggest that and now it has become official and non reversable.

Either way i will post back with the outcome. Buy for now.

[airflamesred]

What was the outcome on this?

[bcslaam]

What was the outcome on this?

Dmitri has kindly tested my machine thoroughly and found no faults. I have asked him if I could give it another go and he accepted. I paid for all postage. Machine has been on its way back from UK for 2 weeks now and still hasn't arrived.

I really don't know what I was doing wrong yet. It's possible my go edrum hhat controller has unusual wiring or my pads may need cooling down. In the next weeks I will update.

So I'm afraid the megadrum community hasn't seen the last of me. I aim to contribute more in the future however.

[airflamesred]

Good news for all then.

[bcslaam]

Received yesterday just after I posted previously. Now after initial tests:

First thing thats come up is I have to have my hihat pedal jack pulled halfway out for it to work. But it does seems to work normally after that.

I have managed to get the Goedrum cymbal for hihat working with 3 zones. Could be better edge response. A bit inconsistent . But moving on for now. Hihat and pedal working roughly as should apart from edge inconsistency.

Mesh snare is now in the ball park but PS response is still a little inconsistent. Often it will stick in one zone or the other. If I wait a little after a hit has dissipated then hit the other zone it will track but if I roll 8ths or faster then move from centre to outer or other way around it will stick on the initial zone. I checked if that was a setting in SD2 but it seems to be how cc16 is outputted ie MD behaviour.

1) Does MD have a mask time internally for when it will send cc16 or not?

Toms seem a little too hot and are double triggering a lot. Rim piezo inconsistent.
I have bought some 50k pots and will try putting them inline.
2) Should I use one for centre cone piezo and one for rim?
3) Should I move the foam cone sensor to the opposite side to the rim sensor, closer to the edge since I am not using PS with the toms yet (hope I can one day)

CY15R not working yet after loading files from angr77 site.
4) Why does one config for the same cymbal work for some people and not others? The only variable I can think of if cable length.

PCY135 I cannot get the edge to trigger much at all. Have managed to get reasonable consistency between bell and bow however. I have tried varying the trim pot underneath, started with the PCY150 files from angr77 site.

Tomorrow I am going away for a few days and will resume when I get back. I will still have internet to discuss however.

[dmitri]

1) Does MD have a mask time internally for when it will send cc16 or not?

Yes. It will stick with the same PS value if a hit is within NoteOff Delay of a previous hit. Reduce it.

CY15R not working yet after loading files from angr77 site.
4) Why does one config for the same cymbal work for some people and not others? The only variable I can think of if cable length.

Please, create a separate topic, post settings screenshot and describe what is not working.

PCY135 I cannot get the edge to trigger much at all. Have managed to get reasonable consistency between bell and bow however. I have tried varying the trim pot underneath, started with the PCY150 files from angr77 site.

As per a PM when I was testing the module:

4. Loaded Angr77's PCY150 settings into inputs 2/3. As far as I can see they're not right, at least not for PCY135. This is the screenshot of settings after I adjusted them for PCY135:

You can see my settings screenshot in the PM from 31st October but here it is again:

pcy135.png

Anyway, please, create a separate topic, post settings screenshot and describe what is not working.

[airflamesred]

First thing thats come up is I have to have my hihat pedal jack pulled halfway out for it to work.

Has it occured to you that something is not wired correctly?

I have managed to get the Goedrum cymbal for hihat working with 3 zones. Could be better edge response. A bit inconsistent .

Have you set this up correctly?

I checked if that was a setting in SD2 but it seems to be how cc16 is outputted ie MD behaviour.

MD only converts the information it recieves from the piezo.

Toms seem a little too hot and are double triggering a lot. Rim piezo inconsistent.
2) Should I use one for centre cone piezo and one for rim?
3) Should I move the foam cone sensor to the opposite side to the rim sensor, closer to the edge since I am not using PS with the toms yet (hope I can one day)

These are all questions regarding the build of a DIY e drum and, as Dmitri points out, should have their own topic.