eDRUMin version 1.4 BETA now available

[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

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

A little more troubleshooting. Nothing to do with note banks.
The calibration for the pedal is not carried over from the standard mode to advanced (and presumably back again) as far as I can tell. I had to calibrate once for standard and once again for advanced.

[Rob]

A little more troubleshooting. Nothing to do with note banks.
The calibration for the pedal is not carried over from the standard mode to advanced (and presumably back again) as far as I can tell. I had to calibrate once for standard and once again for advanced.

I'm using build 17 and was not able to reproduce with a VH-10, Hall Effect Sensor, or Yamaha HH-65.

Please also note that if your hihat is setup to use 'impact' method, it is only available when the device is in 'advanced' mode. If you have 'impact' method turned on and then you switch to 'standard' mode, the device will go back to using 'pedal' method of triggering closed pedal notes. I can see that there is a bug however, because when switching between 'advanced' and 'standard', the UI doesn't reflect this fact.

[Rob]

Fixed for build 18

[Rob]

Do you think I should reverse course on this and make 'impact' method available in 'standard' mode?

And while we're at it, should I make 'advanced' mode default for anyone updating from version 1.3?

[MWJT42]

Do you think I should reverse course on this and make 'impact' method available in 'standard' mode?

And while we're at it, should I make 'advanced' mode default for anyone updating from version 1.3?

I personally see no need for either of these changes. Seems right the way it is.

Defaulting advanced is not ideal for new users IMO, and people wanting advanced will be willing to explore the option. Trying to keep this software 'simple', whilst allowing for the massive amount of functionality it has is always going to be a tough balance!

[MWJT42]

I was under the impression that the curve UI indicator had made it through to the 1.4 beta, but I'm not seeing it. Has it been included yet?

[Dadwrshpdrum]

Do you think I should reverse course on this and make 'impact' method available in 'standard' mode?

And while we're at it, should I make 'advanced' mode default for anyone updating from version 1.3?

I personally see no need for either of these changes. Seems right the way it is.

Defaulting advanced is not ideal for new users IMO, and people wanting advanced will be willing to explore the option. Trying to keep this software 'simple', whilst allowing for the massive amount of functionality it has is always going to be a tough balance!

I agree. I’m a new user and I started using advanced features, but only after being comfortable with the simple stuff. Then I read the manual and researched on this forum. I think that would be best for most newbies.

[monospace]

Random crash in Build 16. Was just playing along with Control App open, not interacting with it.

[monospace]

Re: standard vs advanced mode on startup. I reckon a majority of users are moving up from a commercial drum module and are using the triggers/pads that came with it. Standard mode should be fine for that. Advanced mode would seem suitable for those with hybrid and custom configurations. But maybe you should do a user survey to determine that for sure.

[Mylo]

In version 17 my hi-hat controllers have quit sending CC. Downgraded back to 16 and everything is back to normal.

All I do is upgrade, no changing of settings or anything. CCs are just not sent. No matter how I press the pedal the hi-hats always play open.

I have VH-11 type controllers.

I played around with build 17 a little. It doesn’t seem to recognize my controller in controller input 2. I click on Calibrate and press the pedal and nothing happens. The green bar doesn’t adjust at all and the pedal numbers don’t change, it just sits at 0.

My controllers are plugged into the device hosted by another eDRUMin10.