Audiofront

An early eDRUMin 2.0 is now available for testing. There are a lot of changes in version 2 and the purpose of this Alpha phase is get feedback about the new features and make the UI as simple and clear as possible.

As with any major update, you can downgrade to version 1.6, but your device will be factory reset in the process. Be sure to save a device preset before updating so you can restore if you need to. There have been a lot of changes under the hood in version 2, so don’t be surprised if you run into a few hiccups. If you are unsure if you want to try the BETA, then don't! If you do check it out, please leave feedback. It's not too late to make changes (manual hasn't been updated yet).

To properly downgrade on macOS, you'll need to delete the eDRUMin control application from the Applications folder and then reinstall version 1.6.
New Features

• Drum Maps / Drum Map Editor
• Pad Functions
• Redesigned Pedal Input Interface
• Velocity curve for pedal notes
• Improved Splash Triggering
• MIDI Monitor

Improvements

• Inverted the hihat pedal graphics
• Improved splash detection
• Note banks support drag and drop.
• Dual Mono inputs can now be properly controlled by the hihat pedal.
• Preset last modification date is now shown in the preset manager.
• Pedal Hits now light up the pedal jack.

BUG Fixes since version 1.6

• Fixed slow UI performance when calibrating pedals.
• Fixed a crash when Clicking ‘Update Firmware’, then canceling, and clicking ‘Update Firmware’ again.
• Fixed issues saving Metadata for presets.
• Fixed an issue that could prevent pedal presets from being saved.
• Applying a device preset will now properly setup Roland 3-Way inputs.
• Fixed an issue that could lead to SS articulation when hitting dual piezo extremely lightly.
• Fixed an issue that could result in some cymbals configured as Yamaha 3-Zone triggering EDGE with hard hits to the BOW.

eDRUMin_Control_PC_2.0.0.23.zip

eDRUMin_Control_OSX_2.0.0.23.zip

Questions and Answers
Can I use version 1 presets with version 2 firmware?
Yes. Version 1 presets will be updated on the fly (actual file is not changed) before it gets sent to the device. If the input a preset is being sent to is setup as a ‘Drum Map Kit Piece’, it will remain setup to use the drum map. You’ll need to change it to ‘Note Banks’ before or after sending the preset to have it use the Notes assigned in the preset.

Here are relevant excerpts from the version 2.0 manual.

Excellent ! Thanks for all of your ongoing hard work with this product, Rob. It really is a game changer. Can't wait to get home to try these updates out.

Rob wrote: ↑

Fri Feb 04, 2022 5:09 am

Editing Drum Maps

When an input is setup as a ‘Drum Map Kit Piece’, editing the note assignments using the note controls will edit the drum map, and not the note bank assignments. If your device isn’t set to auto save, then you will need to click the save icon to make the changes permanent.
The 7 icons at the top of the Kit Piece Selector can have custom images. Right-Click on an image and select the one you want to use.
A kit piece can be dragged and dropped onto another kit piece to copy note assignments.
Note there is only one CHAN setting for the entire drum map.

Nice! First question I have, after a brief look-through, is in dealing with the 'one CHAN setting'.

As is, across two eDRUMin10's, I have sort of a main group of hardware dedicated to a 'main' SD3 instance, and then a sub group of hardware that is dedicated to a second instance of SD3. They are on separate MIDI channels, which is the easiest way to channelize things in any given AU/VST host. I would treat this the same way when switching a Drum Mapping to a hardware setup of a TD-20 and a TD-10, which would probably be channelized just like SD3 instances, but not necessarily...

How do I deal with recalling Drum Maps with what may be arbitrarily (or fluidly) channel assigned pieces across the two devices? thanks!

two crash reports. I think they are the same (and I could have more but I didn't attach them all). I updated ED10R1 first (ED4 was disconnected from powered HUB). No issues, but as I have noticed the past couple updates I have to power cycle ED10 first before it will update. Anyways. After a successful update I then unplugged ED10 and plugged the ED4R2 directly into the laptop. I ran the update and at the conclusion of the update the control app crashed. That is the first crash report. Every time I tried to reopen the app it crashed. I did not save these reports. Then I plugged the ED4R2 back into powered hub, and plugged the ED10R1 back into the laptop. App opened just fine. When I select the ED4R2 on the app the app crashes. That is the second crash report I sent. I checked. The ED4R2 seems to be functioning just fine. I can trigger notes and it works. However when I turn auto select on and hit a pad connected to ED4R2 the app crashes.

Thank-you. Fixed, and I updated the download link to build 4. Looks like this is caused by an issue when updating ED4 device settings. I think you'll find that the first input on your ED4 is assigned to the second hihat pedal (which doesn't exist). Anyways, I've fixed the crash and the bug with updating the device settings.

slight graphic bug...
When I did a factory reset in v1.6x and re-loaded my 1.6 device preset, the cymbal icon for the HH shows as a cymbal and not the HH icon. The pedal is still linked to that input, and to get the HH icon back, must click to unlink, and then re-link, then the HH icon is displayed.

single channel?
Rob - I sort of asked earlier, above, but... is the v2 Drum Map function currently only capable of recalling all note assignments only on one MIDI channel? I definitely will be using at least two MIDI channels, because the situations on the receiving end pretty much demand it.
Unless I re-think and re-did a whole lot of things, the trade-off of having to go in the direction of being limited to one MIDI channel would not at all be worth using a single channel Drum Map for me. I have 22 inputs, with multiple articulations on 95% of them - including 3 articulations per cymbal. It's just too much to chess board spread out in the 128 notes of any default kit layout - it is -so- much easier to map out on two channels for two instances of default plug-in layouts (using default mapping as well on another channel).

Single channel Drum Maps will be just fine for others and I think it is a very useful direction, but it would not be a full implementation of what I had in mind (basically -> snapshots of all of the input's trigger MIDI channel/MIDI note/MIDI CC (where applicable) per articulation assignments - as per the right side box info). That's my version of an ideal drum map where MIDI channel is a given per note, not a global. thanks.

I think the best way to deal with your request is to have a checkbox that disables the drum map MIDI channel from the Drum Map Editor. If the map MIDI channel is disabled, inputs can use the MIDI channel associated with the Note Bank--allowing each input to have its own channel setting. Would that work for you?

Rob wrote: ↑

Fri Feb 04, 2022 11:17 pm

I think the best way to deal with your request is to have a checkbox that disables the drum map MIDI channel from the Drum Map Editor. If the map MIDI channel is disabled, inputs can use the MIDI channel associated with the Note Bank--allowing each input to have its own channel setting. Would that work for you?

Let's try it! sounds like it might work

Added 'disabled channel map' in build 5. Download links updated.

I’m blown away. Around midday I downloaded the first beta version, reported a crash, that was fixed in build 4 and now there is a build 5. I haven’t even had time to go back to my kit to download the fix to the crash!!!!