eDRUMin 1.6 BETA

[Dadwrshpdrum]

using Beta 1.6 b9, with Roland hardware, two eDRUMin10’s and SD3, I have two questions:

I have a question about tweaking for the lowest possible threshold for the BT-1 and PD-125 snare combo - using inputs 2&3. Using the Xtalk/Link mode - it works well. But…when using ‘lighter or lightest’ tapping on the BT-1, the eDRUMin app will register spikes in the THRESH box, but only trigger above some value amount - regardless - of changing both or either the xtalk setting (shown at 15 in attachment) down to ‘0’, or the THRESH (shown as 0.4) down to ‘0’. Am I missing some other parameter to adjust to try to get these lowest hits to trigger? Velocity curve doesn’t make a difference either, that I’ve noticed.

I’ve noticed the same thing, and recently switched back to sensor mode instead of xtalk mode. I believe while In XTALK mode the eDRUMin app will display the piezo signals, but will not trigger a sound until the switch is closed. So light taps won’t close the switch. I noticed about a velocity of 30 to 50 was the lowest I could get, and it wasn’t very reliable. Sometime slightly firmer than light would get a sound, but then I might miss a couple hits later in groove. So I switched to sensor mode. Raised xtalk on the BT1 and threshold. I didn’t need to touch my PD125 settings at all is well. Much happier with the play.

[Rob]

Am I missing some other parameter to adjust to try to get these lowest hits to trigger?

That's expected behavior in crosstalk mode. As Dadwrshpdrum notes, the switch inside the BT-1 has to be activated in order for it to register a note.

Also I noticed that I can’t link across two eDRUMin10’s for the BT-1 link

Yes, that's a limitation and it's not going to change--not because I'm lazy, but because it would require a significant amount of communication between the devices over the USB connection, which is very slow and inefficient for this sort of thing.

[hang12]

I’ve noticed the same thing, and recently switched back to sensor mode instead of xtalk mode. I believe while In XTALK mode the eDRUMin app will display the piezo signals, but will not trigger a sound until the switch is closed. So light taps won’t close the switch. I noticed about a velocity of 30 to 50 was the lowest I could get, and it wasn’t very reliable. Sometime slightly firmer than light would get a sound, but then I might miss a couple hits later in groove. So I switched to sensor mode. Raised xtalk on the BT1 and threshold. I didn’t need to touch my PD125 settings at all is well. Much happier with the play.

Thanks this is helpful and I considered doing this, but sorry I'm not understanding the BT-1 piezo and switch situ.
(possibly this is all explained in another thread)
Can't a piezo (or any other type of generated) peak trigger a note via the eDRUMin?
It's registering a signal, so can't the switch be ignored and the eDRUMin generate the note if the BT-1 can't quite do it, due to a low hardware threshold detection, or...whatever?
Can't say I'm a great fan of the BT-1 but it physically replaced some ancient KAT Pole bars that the rubber eventually failed on, and they were quite sensitive at lower levels. Could even do a decent quick and snappy ride cymbal pattern on the Kat - not even close to possible (for me) on the BT-1.
I definitely appreciate the Xtalk mode, thanks.

[Dadwrshpdrum]

There are some vdrum forum links that go into the finer points. Basically using a BT1 with a compatible Roland module you can use trigger set up presets to use the BT1 in it’s normal mode, which is intended for heavy xtalk environments such as mounted on the snare or Tom rim, or you can select “sensor” mode. Sensor mode is when the switch is ignored and the pad is basically a mono signal. However, the key thing to remember with a BT1, it is “like” a mono pad when in sensor mode, but is actually not a mono pad. The BT1 requires a stereo connection. A compatible Roland module uses software to use the piezo signal. Otherwise if you plug a BT1 into a non compatible module the default is always xtalk mode, which requires the switch to close before the piezo signal makes it to the module. Unless you split the signal, and then you can bypass the switch.

What eDRUMin has done is make the control app work like a BT1 compatible Roland module. So you can select sensor or xtalk mode without needing a splitter. And eDRUMin goes a step further (or multiple steps further) by allowing you to link BT1 to the xtalk input. I think it improved xtalk actually, but I never did a comparison between my TD-17 and eDRUMin, by the time I got a BT1 I had already fully committed to eDRUMin. So…eDRUMin implementation is just like a modern, BT1 compatible Roland drum module, but better (in my opinion).

I’m happy with sensor mode and I don’t see any xtalk issues. I have xtalk on BT1 cranked to 34 (I think) and threshold around 2.4 (I think, away from kit today). But when I play (not at a professional level, just a basement drummer enjoying playing) I can’t find any missed ghost notes on BT1 in a groove, and no xtalk from max velocity head and rim hits on PD125. Likewise I have no xtalk on PD125, and I think that xtalk is 10????

[hang12]

Great synopsis on the BT-1.
I don't have any modern Roland drum modules to plug the BT-1 into for comparison either.
The eDRUMin is where it's at!
thanks!

(edit) ok, I tried sensor mode for the BT-1 and PD-125 tandem - it's definitely better. yay!

[hang12]

Great work, it works great on my CY-15RMG,I used the bow tip and bow shank in the core library and the bow tip 1 and bow tip 2 in death.

I agree that the technology part of it works great, but sound wise, in the Core Library, using it to switch between tip and shank sounds and feels terrible and wrong to me, so I ended up disabling Cymbal PS for now. Using a plain old Velocity Gate works much better.

None of the currently available SDXs sound appealing to me, so hopefully a future SD3 Core update will make this feature worth enabling again for me.

OK, Sorry but what am I’m missing here with 1.6, regarding cymbal positioning and with SD3? OK, there’s bell sensing, for up to 3 articulations per cymbal. But how do I assign other available cymbal articulations from SD3 via positioning? I can’t find anything in this thread (or the most recent manual) to explain how it’s (possibly) employed. Velocity gating sounds like a good alternative too. Thanks.

[Dadwrshpdrum]

crash report. I was just playing. No interruption to my playing. When I was done I went to the computer, and I had a crash report.

[Dadwrshpdrum]

another crash report

[Rob]

It's a very obscure crash deep in apple code. In version 1.6.1 I'm going to be changing how data packets are processed by the UI. Hopefully that'll take care of the issue. Busy working on MIDI Expression for the next couple of weeks, but I'll shift my focus back to eDRUMin after that.

[digiface]

Hi Rob, I'm on an imac with an apple magic mouse https://www.apple.com/uk/shop/product/M ... agic-mouse and the sensitivity of the mouse with the midi note mappings is too sensitive. Often when I switch back to the eDrumin app the settings will get messed up just by whatever drum was in focus and the slight movement on the mouse. Thanks for adding Abbey road, just trying it out