eDRUMin 2.4 BETA

[CodaClef]

Uh-oh, after quitting and restarting my ED the window not looks like this, not showing the 2 ED 10's anymore.
What do I do?

EDIT: I downloaded 2.3.2.31 and same thing, shows like an ED4 and doesn't show the 2nd at all. Tried updating firmware and it hangs and fails.

Screenshot 2025-03-28 210907.png (253.97 KiB) Viewed 113 times

[Rob]

Just power cycle the devices. They should work fine.

[CodaClef]

Just power cycle the devices. They should work fine.

Yeah they came back and updated fine after that. Thanks!

Might have found a bug in the minimize button, haven't seen this before, and it wasn't like this at first...

Screenshot 2025-03-28 233320.png (67.76 KiB) Viewed 106 times

Screenshot 2025-03-28 233331.png (91.68 KiB) Viewed 106 times

[mrmbira]

Is the midi channel function working as it should? It seems to always show global but when I click on it it shows the non-global channel that I set it too. Why does it not show my setting without clicking on it?

[Rob]

When it says GC, it's using the global channe,l which can be set in the options page (cog icon in the side bar on the left of the UI). When you click on the chan label, you can set a different channel for that particular input.

[CodaClef]

Just power cycle the devices. They should work fine.

Yes everything came back! Thanks!

[Rob]

I posted build 1.

• Added a 'note velocity' device setting to change the way note velocities are calculated, removing the need for extremely velocity curve settings.
• Reworked sense controls for dual peizo pads so that all the control can fit nicely again.
• Fixed awkwardness using mouse wheel on rimshot range control.
• Fixed a regression bug when trying to turn on/off expression curves.

Here's an exert from the manual about the Note Velocity setting:

Note Velocity
There is no standard way to translate transient magnitudes to note velocities. Prior to version 2.4, the eDRUMin linearly mapped the magnitude of hits (force) directly to note velocities (linear force).

As of version 2.4, you can now change this to ‘linear velocity’ (new default), which is more similar to how a keyboard measures velocity, where velocity is a measure of how fast a keyboard key is moving downward.

When set to ‘linear velocity’, the eDRUMin translates the magnitude of transients to something resembling the downward speed of your drumstick. This removes the need for extreme velocity curves to get a natural velocity response in many applications.

[frankzappa]

Looking forward to the velocity mapping Rob, sorry for bugging you about it

[Gemini8026]

"Improve cross-stick performance on ATV snare with cross-stick bracket (and possibly other snares)."

- ATV snare user here and can report cross stick is working good for me. Much improved as before it wasnt very good.

[Rob]

Looking forward to the velocity mapping Rob, sorry for bugging you about it

I actually think the 'linear force' method is the correct implementation. By converting the force measurements to velocity just so that software applications can convert it right back to force again results in a drop in fidelity. But considering a large number of people are triggering drum software with keyboards, that's not going to change.

eDRUMin natively measures force, so I'm going to stick to 'linear force' and use the curve to compensate as I always have. That preserves the highest resolution.