eDRUMin version 2 BETA

[Rob]

I don't think anything has changed in the firmware that would cause that problem. I'm away for a few days, so won't be able to test until I get back.

No, there is no room for a slider. I could probably add a knob / meter for adjusting the sensitivity a bit, but it shouldn't be needed.

[klatho]

I found a strange behavior on my snare. When I change the hold time and save the value (doesn´t matter if auto/manually) then the hold time jumps to a different value when I trigger a Rimshot. Same behavior when I click on RS or SS. I thought the scan settings are set for all articulations.

I use 2.0.1.6 (windows) but same on 2.0.1.5. I hadn't observed this with 1.6.2.6.

[MWJT42]

I don't think anything has changed in the firmware that would cause that problem. I'm away for a few days, so won't be able to test until I get back.

No, there is no room for a slider. I could probably add a knob / meter for adjusting the sensitivity a bit, but it shouldn't be needed.

Thanks Rob.

A knob would be great, thanks!

[dsteinschneider]

Well I'm relieved that that is sorted out. It was probably the result of some leftover settings from earlier BETAs. As for the the "You have unsaved changes", you probably don't have 'auto save' turned on for your ED4. And if you are using a pedal to change banks, the settings for the device will be dirty and so it will warn you.

Hi Rob,

I realized that the drum maps weren't quite right in my setup. I reset the eDRUMin and then the missing icons appeared. Then I searched the help files and saw the recommendation at the time the maps were rolled out to reset the device. It did have something to do with having previously an ED4 but now an ED10.

Doug

[Rob]

When I change the hold time and save the value (doesn´t matter if auto/manually) then the hold time jumps to a different value when I trigger a Rimshot

This is because of the way that hold time is calculated and the limited amount of resolution that the control has. The result is that small changes might not cause a real change in the value. I should be able to better reflect this is the UI. I'll take a look at it today.

Update: The hold time is stored as an integer, so any changes less than 1ms won't update the stored value, and then due to rounding what looks a change of 1ms (like in your case), might actually be slightly less. Fixing this properly would improve the resolution to about 0.4ms, but would involve a significant amount of work and the potential for bugs that might follow from it.

[thedrumdoctor]

Much kudos for porting to Linux. I'm hoping there'll be advances in running VSTs on Linux as well.

[Rob]

When I change the hold time and save the value (doesn´t matter if auto/manually) then the hold time jumps to a different value when I trigger a Rimshot

This is handled properly version 2.0.2. The control now has a resolution of 0.4 ms. This will not provide for an better triggering, but UI values will stick properly.