eDRUMin 1.3 BETA now available (again)

[lalo]

Does using input no. 1 (for anything non-HH) have any particular significance that could be causing issues?

(if the HH is linked correctly elsewhere...)

I have my snare on input 1 and my hihat on input 10 and it works fine

[Rob]

Does using input no. 1 (for anything non-HH) have any particular significance that could be causing issues?
(if the HH is linked correctly elsewhere...)

There's nothing special about input 1. Are you on ED4 or ED10?

[MWJT42]

Does using input no. 1 (for anything non-HH) have any particular significance that could be causing issues?
(if the HH is linked correctly elsewhere...)

There's nothing special about input 1. Are you on ED4 or ED10?

ED10.

It's quite possibly user error, as it's happened before after an update that the HH became linked to 1 (instead of 3 in my case).

[monospace]

One tricky thing that was counterintuitive to me at first in SD3 is that Projects are different from User Presets. I'm mostly playing the Premier Genista kit, and have set it as my startup configuration, but when I make changes to it it's not enough to save the User Preset, I must also change it as a new Deafult Startup Project. Also, avoid making changes to MIDI mappings on the Project/Preset level. Those are best made (and saved!) in your User Mappings in the Midi In/Edrum settings panel.

[MWJT42]

One tricky thing that was counterintuitive to me at first in SD3 is that Projects are different from User Presets. I'm mostly playing the Premier Genista kit, and have set it as my startup configuration, but when I make changes to it it's not enough to save the User Preset, I must also change it as a new Deafult Startup Project. Also, avoid making changes to MIDI mappings on the Project/Preset level. Those are best made (and saved!) in your User Mappings in the Midi In/Edrum settings panel.

I now leave MIDI mapping as default, and make the note changes in edrumin. Any reason to alter it in SD3 instead?

[Mylo]

One tricky thing that was counterintuitive to me at first in SD3 is that Projects are different from User Presets. I'm mostly playing the Premier Genista kit, and have set it as my startup configuration, but when I make changes to it it's not enough to save the User Preset, I must also change it as a new Deafult Startup Project. Also, avoid making changes to MIDI mappings on the Project/Preset level. Those are best made (and saved!) in your User Mappings in the Midi In/Edrum settings panel.

I now leave MIDI mapping as default, and make the note changes in edrumin. Any reason to alter it in SD3 instead?

That’s what I do. The less I touch SD3 the better off I seem to be. One of the major things I do in SD3 is turn off articulations I’m not using. This decreases load time. If you are never going to trigger your bell on the crash then turn off that articulation in SD3.

[monospace]

I now leave MIDI mapping as default, and make the note changes in edrumin. Any reason to alter it in SD3 instead?

I should clarify I'm not altering the standard note mappings, but I did create an "eDrumIn" user preset in the MIDI In/Edrum settings for tweaking hihat CC mapping and positional sensing CC mapping. And it's also where I assign note numbers for any X-Drums I might be using.

[MWJT42]

tweaking hihat CC mapping and positional sensing CC mapping

Ok, do you do this per snare drum, or do you just prefer this interface to eDRUMin's?

I do find this is the one area where SD3 is more visually intuitive than eDRUMin, but even still, I keep SD3 as default and make my alterations in the eDRUMin control panel in case I ever lose the SD3 map, and want to play back my recorded MIDI accurately. Using velocity (position?) curves for the HH is quite nice too, although I'm not sure my playing actually requires more than open/close!

Rob, is a change to the positional sensing UI on the road map at all?

[monospace]

Ok, do you do this per snare drum, or do you just prefer this interface to eDRUMin's?

It's a two-step process as far as I'm concerned. I start by enabling Positional Sensing on the eDrumIn and adjusting the zones slider so that the CC values it sends out are optimized for my snare pad. I might then slightly tweak the way Superior Drummer translates those CC values into specific snare articulations. The default is good but I like having the option.

You can only do this globally though (as part of your preset in the MIDI in/EDrum settings.) I can see how it could potentially be useful to edit it for individual snare drums, the way you can with the hihat.

[dsteinschneider]

MWJT42 wrote:
Does using input no. 1 (for anything non-HH) have any particular significance that could be causing issues?
(if the HH is linked correctly elsewhere...)

No input has any special purpose - you can plug in whatever you like. I was just pointing out that I was missing random kick triggers when I first installed 1.3.0.7 because I failed to point the Link button for the pedal input* to the input(3) I was using for the hi-hat cymbal.

Also I didn't adjust the hi-hat pedal cross talk so the pedal cross talk was suppressing the kick trigger once in a while.

*pedal one - same situation - doesn't matter which pedal input you use for the hi-hat.