I'm away till 23rd of September

[kurtus420]

[/quote]
So, are you having the problem when it is set to No or to Yes?

My issues come when inputpriority is set to yes. Triggers as it used to before this new firmware with inputspriority set to no.


[/quote]
Do you mean you get random crashes/funny lcd/etc in normal operation or after firmware upgrades and trying loading configs saved with a previous firmware version?[/quote]

It has happened on nearly all the firmwares that I have installed. I get the crashes in normal operation while trying to make normal configuration changes (pad adjustments), these crashes are random as I have not been able to duplicate the cause. What is the best way to get your saved configs back after doing a firmware update? I have loaded a new firmware in the past and just used the default settings with that firmware and still get the crash occasionally this way while making all of my pad adjustments causing me to lose all the configs I've made. I noticed with this new firmware that when I loaded it the config setting that was saved in slot 1 before became the default with this firmware on startup, is this right or should I have to load it from slot 1 before it should load?

Edit: I just realized that I may have set it to autoload yes out of habit because my hihat pedal wont respond until I do that.

[dmitri]

Can you reformat your last post so that I understood which question you are answering?

[kurtus420]

"Do you mean that when you enable InputsPriority it becomes noticeably harder to trigger edges/bells on piezo/switch pads/cymbals?"

When I enable inputspriority to yes I no longer get consistent bell and edge triggering.


"Do you mean you get random crashes/funny lcd/etc in normal operation or after firmware upgrades and trying loading configs saved with a previous firmware version?"

normal operation.

[dmitri]

"Do you mean that when you enable InputsPriority it becomes noticeably harder to trigger edges/bells on piezo/switch pads/cymbals?"

When I enable inputspriority to yes I no longer get consistent bell and edge triggering.

I'll have a look at this.

"Do you mean you get random crashes/funny lcd/etc in normal operation or after firmware upgrades and trying loading configs saved with a previous firmware version?"

normal operation.

If it happens with any firmware version with a fresh config, i.e. not trying to load a config saved with a previous version, than it looks like you have a hardware issue.

[kurtus420]

Should I try and reflash the atmega or get a new one? Is it normal that my hihat pedal wont respond when I load new firmware until I flick the impedance switch to off the back to low again?

[dmitri]

Should I try and reflash the atmega or get a new one?

When you update a firmware you are in fact reflashing Atmega, so it won't help.

Is it normal that my hihat pedal wont respond when I load new firmware until I flick the impedance switch to off the back to low again?

No, it is not normal. It should work fine without toggling the high/low impedance switch.

[kurtus420]

Do you think this might be a flux issue possibly around the atmega circuitry, I was just playing around and changed to the bigvu screen and after pressing the hihat pedal a couple of times and then letting it sit for a few seconds megadrum reset itself again, I put it back to bigvu meter again and it's fine for now. Any thoughts were I should start looking? Thanks for your help.

[dmitri]

You may have a bad contact somewhere or an intermittent short. Due to the intermittent nature it might be difficult to find the cause. Of course it could be due to residual flux. You may also have an intermittent problem in the USB cable.

[kurtus420]

Any idea were to start with the hihat pedal?

[dmitri]

Any idea were to start with the hihat pedal?

Start with describing the problem in more details in a separate topic.