www.megadrum.info

I just bought a yamaha pcy-155, when I try to configure it in the ride input as a 3way trigger it cuts out my Roland cy-8 crash cymbal, the bow and edge will not trigger but it sees aftertouch messages still. The ride when configured as dual zone "yes" works fine to trigger the bow and bell and the crash cymbal works fine again, change the ride to dual zone "3way" and the I get bow and bell out of the pcy-155 but the bell sometimes triggers the crash edge as well as the proper bell note. I was messing around last and without the ride plugged into the ride input I configured it as a 3way again then I tap on my Roland cy-8 crash cymbal, there is no notes sent like before, I hit no other pads and changed the ride input back to dual zone "yes" and the megadrum send a midi on off signal from the crash edge without even touching it, it's like a stored event from tapping it before when the ride was configured for 3 way triggering. All of the inputs work fine when setup as dual zone "yes". I thought maybe there is an issue with the ride input so I plugged it into Aux5, when configured as a 3way I get the same outcome, I get bow and bell but no edge out of the pcy155, I'm noticing now that bell is now triggering Aux6 rim. I don't know if this is related but sometimes when I mess with the contrast my screen starts pulsating a little and then it sends a midi signal is shown in the led and resets itself while I'm trying to adjust settings, screen goes blank shows copyright page flashing blank till finally the midi led lights up and megadrum stabilizes back to the copyright screen. If I try to start megadrum while pressing the right button down while powering the megadrum up my contrast on my screen goes dark and after 1 min or so it send a midi led lights up and it resets back to my saved configuration 1 were the lcd screen looks fine. I'm sorry guys, I'm finding it hard to explain the problem here but I hope this makes sense. Thanks Kurt

I admit and maybe confusing but this is what Documentation says about DualHead setting:

For Head/Bow inputs: Can be set to No, Yes or 3Way.
If set to No, Head/Bow and Rim/Edge inputs are treated as separate pads.
If set to Yes, Head/Bow and Rim/Edge inputs are treated as parts of the same dual zone pad or as parts of the same 3 zone pad, e.g. Yamaha style 3 zone cymbals.

I.e. for Yamaha 3 zone cymbals you need to set DualHead to Yes and look at BNote and BThreshold.

Well that makes sense on whats happening with my crash cymbal note being triggered from the ride input. I have had it set to dual head "yes" and I was getting good bell and bow triggering but I wasn't getting an edge hit out of it or aftertouch to choke, I was using the default bnote and bthreshold settings so I'm assumming thats why I'm not getting any edge triggering? I'm not sure whats happening with the lcd issue though, I noticed that when I rolled the firmware back to the 0729 version, before the lcd contrast change, the lcd screen refreshes clearly while scrolling through the menus, with the latest firmware it is a little bit blurry/not as crisp while scolling through the menus. I notice that when I adjust the contrast darker and leave it without saving turn off megadrum and back on again the contrast is still dark, is this normal? I have also had a few instances were I have made an adjustment change in contrast and started making pad setting changes then screen starts flickering/pulsing slightly, goes blank, midi led flashes and megadrum resets itself to the last saved configuration.

You may have a corrupted EEPROM. Start with fresh settings booting with right KEY pressed.

When I restart with with the right button held (which is my encoder switch) and reset to default, the screen contrast goes dark like the sendsysex screen does and I have to adjust the contrast lighter, is that the way it should be? I'm asking this because when I load the latest firmware the screen contrast is perfect. Thanks, Kurt

Edit: does this mean that my atmega is no good and I need to buy a new one if this keeps happening? I have notice that the settings do get reset to default when I reset with right key pressed but the lcd screen is dark like described above, is the this what you think is causing my megadrum to reset itself while making config changes.

By default LCD contrast in newer firmware versions is lower than it used to be and this is ok. This is a result of widening LCD's contrast range which I introduced to a couple firmware versions back.
EEPROM content can get corrupted for various reasons, e.g. due to a power spike during EEPROM write operation.

So I just got home from an AC/DC concert, it was sold out at BC place stadium in Vancouver BC. All I can say is "WOW", they still put on a fantastic show, Angus is a machine and he must be like 60!!! Thanks for your help dmitri and sorry for not searching a little harder on the Yamaha cymbal, its getting all 3 notes now and sending 3 aftertouch messages as it should. I'm not sure though on one little thing which is, when making a contrast change on the lcd display, lets say lighter and I turn megadrum off without saving configuration should it automatically keep the contrast to were I set it before when I turn it back on? Also, as far as the auto reseting goes, it seems to not be doing it anymore but I did notice that I had midiox open for midi monitoring but I created a loop so I was getting midi confliction issues there, maybe related or possibly that I had it configured as a 3way input but was running the yammy in it causing instabilty issues? Synthex programmed this atmega644 so I'm sure it's something other than a programming fault, if it is the eeprom thats faulty. I have been messing about quite a bit inside of my megadrum lately with the daughter board expansion and the addition of the encoders/switches so who knows what I did, I guess a little more time will tell.

kurtus420 wrote:Thanks for your help dmitri and sorry for not searching a little harder on the Yamaha cymbal, its getting all 3 notes now and sending 3 aftertouch messages as it should. I'm not sure though on one little thing which is, when making a contrast change on the lcd display, lets say lighter and I turn megadrum off without saving configuration should it automatically keep the contrast to were I set it before when I turn it back on?

The LCD contrast setting is automatically saved in EEPROM when exiting the menu and automatically loaded on powering up.

Also, as far as the auto reseting goes, it seems to not be doing it anymore but I did notice that I had midiox open for midi monitoring but I created a loop so I was getting midi confliction issues there, maybe related or possibly that I had it configured as a 3way input but was running the yammy in it causing instabilty issues?

MIDI loop is a sure way to confuse MegaDrum and even to cause it to reset.

Sweet, I'd have to say then that all is working as it should then. Thanks for your time dmitri. Later, Kurt.

kurtus420 wrote:Well that makes sense on whats happening with my crash cymbal note being triggered from the ride input. I have had it set to dual head "yes" and I was getting good bell and bow triggering but I wasn't getting an edge hit out of it or aftertouch to choke, I was using the default bnote and bthreshold settings so I'm assumming thats why I'm not getting any edge triggering?

How did you fix that?
I have the same problem...

RideB:
Note: 53
Dual head: yes

RideE:
Note 51
Type: Switch

RideE:
BNote: 52
BThreshold: 30

(the rest is default)
I get 53 and 52, but never 51...