eDRUMin version 1.4 BETA now available

[Dadwrshpdrum]

See attached screenshot for a pedal editor error. A VH10 controller is pedal input 1, and an Alesis RealHat controller is pedal input 2. I had my VH10 set up correctly, and a BOSS FS-6 as the second Footswitch. However, I switched out the FS-6 for the RealHat controller. The auto sense knew the RealHat controller was a HH pedal, but I didn't want that. So I shut off auto sense and manually selected a switch. I left the VH10 alone. I was using the eDRUMin stand alone (no app) after this and all worked well. Last night I opened up the app and noticed that pedal 2 had a weird indication of bank "44" plus the Min and Max had switched from 1 to 2, to 1 to 4. However, when I operated the pedal the banks still worked 1 to 2. So I called it a display error and told myself I'll take a screenshot the next day. This morning when I went to take the screenshot the following happened:

I powered on the eDRUMin10 and connected to the app. Pedal 1 switched from a HH controller (auto sense is off) and had the weird "44" display error. Pedal 2 did not have the error. The link between VH10 cymbal and the HH controller was lost. I took the screenshot, and then manually selected HH pedal for pedal 1. All of my settings came back, relinked with the VH10 cymbal. All is well. I tried to reproduce a couple times just now. I haven't been able to, but I only tried for a couple minutes.

I understand that in the morning, the VH-10 was set to footswitch and 'sense' was off. Was 'sense' on for the VH-10 before?

I can’t remember. The screenshot shows that it was off and I didn’t touch it. I can only remember specifically turning it off on pedal 2 a couple days back when I switched from the FS-6 to RealHat pedal.

[flaphead]

Think I've found a bug in 1.4.14: HH pedal controller values and notes are sent on channel 1, regardless of what is configured. Just reverted back to 1.3 to check and everything is fine there.

Best, Florian

[Rob]

Hi Florian,

Confirmed bug. If the device is 'standard' mode, adjusting the the hihat pedal MIDI parameters have no effect. The workaround is use 'advanced' mode. I'll fix it for the next build. Thank-you!

Rob

[Rob]

Changes in build 16

• Fixed an issue with changing hihat MIDI assignments in 'standard' mode.

PC
https://www.audiofront.net/eDRUMin_Cont ... 4.0.16.zip

macOS
https://www.audiofront.net/eDRUMin_Cont ... 4.0.16.zip

[MWJT42]

Bug Report: unexpected behaviour

Hi-Hat plays flawlessly in standard mode (well done), but when the advanced button is clicked, I'm unable to trigger a closed articulation. Foot 'chicks' work fine, but as when pedal depressed at 127, hitting the hat triggers an open sound.

Switching back the standard mode remedies the behaviour

[MWJT42]

Feature request: longer hi-hat decay option for open articulations.

It stands to reason that for most players, repeated open HH sounds will be fairly spaced apart (like a crash cymbal), whereas closed, we may play some very fast doubles etc..

Dialling in the decay (for a moving double metal cymbal setup, on a stand, where when closed, its held tight against the lower cymbal) is really tricky.

Setting this high enough to prevent unwanted triggers when the cymbal is loose, is a compromise for when the HH is closed tight shut, and it may not recognise fast doubles.

Proposal: in advanced mode, add a multiplier knob for increasing decay time for open articulations (cc04 < 50), to prevent unwanted vibration triggers for when cymbals are loose - or just a check box like the fast stepping fix, if there's a standard multiplier that works for majority of cases.

Thanks!

[Rob]

Bug Report: unexpected behaviour

Hi-Hat plays flawlessly in standard mode (well done), but when the advanced button is clicked, I'm unable to trigger a closed articulation. Foot 'chicks' work fine, but as when pedal depressed at 127, hitting the hat triggers an open sound.

Switching back the standard mode remedies the behaviour

I don't see an issue. I suspect that you aren't realizing that the note bank is changing when you are in advanced mode. In standard mode, the device will always use the first bank, regardless of which bank was selected when the device was placed in standard mode. In advanced mode however, the device will use whichever bank is currently selected.

Does that make sense?

Regards,
Rob

[Dadwrshpdrum]

Crash report for 1.4.17. I was changing a MIDI note for a rack tom. Advanced setting was on, and I think it was the rimshot note for Bank 1.

[Rob]

Thank-you. Crashed deep inside some macOS code. I'll try to reproduce the issue. Thanks.

[dsteinschneider]

Hi Rob,

I upgraded to 1.4.0.17 and the hi-hat pedal was bouncing up and down by itself. I tried my usual set of steps:

1. Change pedal type to another and then back to hi-hat
2. Click from Advanced mode to Standard
3. Power cycle the E10
4. Try another Hall effect sensor unit (my build in a Polycase) that I know works
5. Click the Reset Pedal
6. Downgrade back to 1.4.0.12

The last step is the scary part. It's doing it after I downgraded the firmware!

At this point I pulled out my E4 Blue I'm keeping for these types of situations and upgraded it to 1.4.0.12 and the pedal is working fine with it.

I just plugged it into the USB host port on the E10

So luckily I can carry on by plugging my PCY135 and Hall effect pedal into the E4