Audiofront

Product: eDRUMin 10
Firmware: 2.3.1.35

Hello

This is my 2nd eDRUMin 10. It arrived today.
I am running it daisy-chained to the first module.

I have 2x of these:
Lemon 15 inch Dual Zone Crash

Both work perfectly on the 1st module.

Cymbal 1 is OK after moving it to the 2nd module.
However cymbal 2 only triggers the edge zone on soft hits. Any moderate or hard hits trigger the bow sensor.

I have tried another port on the module, but still the problem is there.
I have tried another cable as well.

If I move the cymbal back to the 1st eDRUMin module, it works fine again.
However, the plan is that I move all cymbals to the 2nd module.

The firmware was running 2.3.2.[something] and I downgraded it to the current production firmware to match the original module I have.

I also saw this error message when moving to a different port:
Compatibility issue: 0.23, 87

Any ideas?

The latest production firmware is 2.3.2.30, but 2.3.1 should also work just fine. I don't know what the issue is, but given that one cymbal works fine and the other does not implies something is up with the cymbal itself. Is the compatibility detection disabled on your 1st ED10? It will be hard to tell using version 2.3.1 because that version has a bug where the control application will not correctly display if the compatibility check has been disabled. You can still use it to enable / disable the setting, but it will always look like it's off when you go back to the firmware section of the control application. Maybe try disabling it for the second ED10. After you disabled it, wait a few seconds for the eDRUMin to save its setting and the power cycle the second ED10.

Hello Rob

I have tried another Lemon cymbal - with the same result.

It is port 4 that is the problem.

I have tried ports 1 to 5. Not tried the bottom row ports.

Port 1: OK
Port 2: OK
Port 3: OK
Port 4: faulty
Port 5: OK

I have tried disabling the compatibility check - that does not fix the issue.

I have also updated the firmware on this new 2nd unit to 2.3.2.30.

Still the problem persists on port 4 - soft hits detect the edge, anything moderate to hard switches the edge to bow detection and the edge cannot be detected.

Is this a faulty module?

Thanks

Further testing.

Port 6: OK
Port 7: OK
Port 8: OK
Port 9: faulty
Port 10: OK

It's ports 4 and 9 that are the problem.

With compatibility check enabled, port 9 was also issuing an error.
Needed to switch it off to get it (partially) working.

Do ports 4 and 9 work properly with a dual piezo pad?

Hello Rob

I will try a dual zone tom tomorrow and let you know.

I have just tried the cymbal again, on port 4 and 9, before I planned to plug in a mesh based tom.

The problem is no longer there. Edge detection works on hard strikes.

Yesterday, it was reproduceable every single time on ports 4 & 9.
i.e. it was not an intermittent problem.

I updated the original 1st unit to the latest firmware. Wonder if that has solved the problem?

The 2nd unit with the issue has never been connected directly to the laptop - it has only ever been daisy chained to the 1st unit I purchased.

Spoke too soon

I shutdown the laptop and powered up again.

The problem is back again.

Going to try a mesh tom on the port.

I realise I have been describing the ports incorrectly - I thought the top row was 1 to 5.

So the ports that have a problem with the cymbals are 7 and 8 (4th left on top row, 4th left on bottom row).

A dual zone mesh pad (14" floor tom) seems to function perfectly fine on ports 7 and 8.

I have also tried this module connected directly to the laptop, but the cymbal issue is still there.

If you contact me via technical support, we'll capture some data from your cymbal to figure out what's wrong. Send me an email to support at audiofront dot net.