eDRUMin version 2.3.2 BETA now available

[Rob]

I posted build 26.

• Linux, fixed issue with updating firmware of devices connected to host port.
• Fixed an issue that could result in changes to the pedal input not being saved.

[pumpkinking]

Hi Rob - using both .19 and .20 builds, I can see the bank changes are working find for trigger inputs, but I'm seeing an issue with the HiHat pedal. For the note bank switch sustain pedal I have Input=ALL, and the hi-hat trigger cycles through the banks fine, but the associated pedal is having an issue with bank 3. The only difference between the banks are channel numbers (banks 1-4 have channel 10-13 across all triggers and pedals). For the hi-hat pedal, the channel number for bank 3 is 1+ that of the hi-hat trigger channel for bank 3 (banks 1, 2, and 4 are fine). I cannot manually override the pedal channel # (probably by design). Let me know if more information would help understand the issue.

Never mind - I kept fiddling with it and then it suddenly started working OK. I'll keep watching it, but for now the issue is gone.

OK I am still seeing an issue here - even with the latest .28 version. Specifically, when I change the channel value for a hi-hat pedal then click away and return to the pedal config, the channel number has increased by 1. I can get what I want by setting it to the value 1 below what I want it to be as the implicit +1 seems to stick. So not catastrophic, but might be a nuisance to users who do not see the pattern.

LMK if you need more details or want a config export. Thanks!

[Rob]

I've seen and fixed this issue before, but obviously my fixes are missing the real source of the problem. I'll look into it today.

[Rob]

It was a firmware issue. It'll be fixed in the next build.

[Rob]

I posted build 29 with the fix.

[mpanzer]

I downloaded and updated my eDrumin 10 and eDrumin 4 firmware to 2.3.2 using a Mac laptop and the eDrumin app on the laptop can see and edit both fine. However, my iPad no longer sees them when I connect them to it. I tried deleting and downloading/installing the eDrumin app again but it didn’t help. Any ideas what I can do to fix this?

[mprinz]

Hi Rob,

I guess my DIY snare pad might by one of the 2%. I am pretty ok with the rimshot range , but I guess, I might be able to squeeze some
more happiness out of this feature. I will see.

This single rotary encoder idea is really neat.
I always was like ... I need a bunch of knobs... I don't.
There are some devices from AKAY & Co. that use encoders but they are bulky.

I think I have at least on free pedal input.
And IT IS EXACTLY as you said... the headphone is always, always to quiet.
Or the MainOut in SD3 to loud.

I still have to figure out, how to config the MIDI data to control the RME Babyface.
My wife needs a single knob, to set the volume of the TotalMix TV input, too.

Out of interest, what are the sorts of issues/uses independent gain control for TIP and RING help with?

I think 98% of pads won't see any benefit as the rinshot range does something similar already. However if a pad has an extremely sensitive rim sensor (like a some Roland PDX-8 pads), manually setting the rim peizo gain can help prevent false cross/side stick/rimshot triggers.

[Rob]

I still have to figure out, how to config the MIDI data to control the RME Babyface.

That's the video I'll do next. It's great that RME has enabled that functionality, although in my opinion, they could have implemented it a bit better.

[mpanzer]

I downloaded and updated my eDrumin 10 and eDrumin 4 firmware to 2.3.2 using a Mac laptop and the eDrumin app on the laptop can see and edit both fine. However, my iPad no longer sees them when I connect them to it. I tried deleting and downloading/installing the eDrumin app again but it didn’t help. Any ideas what I can do to fix this?

Anyone with this issue?
BTW: I’m trying to connect the eDrumin units to my new iPad Air M2. I’m not certain if it’s an issue with connecting to the new iPad or something to do with the firmware update.

[Rob]

It's a known firmware issue. Its fixed already. I'll post a fix tomorrow.