bpjacobsenFor my ride bell, I use a cut out bell from a broken cymbal and a piezo connected to a spare tom port. (was having issues with the bell trigger working right so I gave up and connected a piezo separately to a reg tom port which has worked great in the Alesis Strike)
However, I’m struggling to get SD3 to assign the ride bell sound to it. I go into midi settings, select my added instrument which is a ride cymbal and select the option for the Bell. I hit learn then tap the bell but then all I get is a tom sound and it messes up the bow too. So both the bow and bell make a tom sound.
I have no issues with my cowbell as I do the same process except using the added cowbell instrument.
Seems to me I should be able to teach SD3 which pad I’m using for ride bell but it’s not working so good. The only way I have ever gotten it to work is if I do it directly via the drum page which I was told is not the correct way b/c then it would only apply to that kit/preset and not all which is not at all what I want.
Please help, this is driving me crazay!
pumpkinkingThis can happen if two triggers are assigned the same midi value at the module. Use the midi monitor and hit the bell and tom triggers and see what midi values they produce. If they are different then just map the bell midi value to the bell instrument articulation you want it to use. If they are the same, then you’ll have to change the midi value produced in the module for that trigger.
Midi monitor can really be your friend in these cases.
bpjacobsenThis can happen if two triggers are assigned the same midi value at the module. Use the midi monitor and hit the bell and tom triggers and see what midi values they produce. If they are different then just map the bell midi value to the bell instrument articulation you want it to use. If they are the same, then you’ll have to change the midi value produced in the module for that trigger.
Midi monitor can really be your friend in these cases.
Superior Drummer 3 version: 3.3.6
Operating system: macOS Ventura (13)
OK so I tried to take a video on my phone to demonstrate what I’m seeing:
Seems like the ride bow is showing the same midi note as the bell which intrigues me considering the bell is not even hooked up to the cymbal trigger. It’s hooked up separately to a tom zone and makes a tom sound. Yet none of the toms are using the same midi note. Why would D#2 be registering for both the bell which technically is a tom trigger AND the ride bow? I”m stumped. Hopefully the video is easy enough to follow. Was kinda a challenge to take the video with one hand and hit pads with the other. lol.
Oh and to add, when I mouse click on the pad graphic in the midi settings when the D#2 ride bell is selected, it does make the correct ride bell sound. So why on earth is it making a tom sound when hitting the actual bell? Should it not make the same sound that is in the graphic? So so confusing. Honestly though, I”m probably going to end up re-connecting the ride bell trigger to the 3 zone box and seeing if I can get that working properly again. I would assume that should make the midi mapping a but easier assuming it works. but in case I still have an issue, I would love to figure this out, if not for the learning process. (pun intended)
Thanks for the help.
pumpkinkingHard to follow exactly what is going on, but I will suggest that you look at either the “midi monitor” box in the right side of the main SD3 window (might have to show it in the pulldown), or the midi analyzer at the bottom left of the “Midi in/e-drums” window. That shows you a log of what midi signals are received, not just the last one received. It was hard to see in your video, but it seems like your bell is triggering two notes: 51 (mapped to 30) and 80. Not sure what 80 is but maybe it is causing an undesired sound. This could be due to crosstalk across your kit or something, especially if you’re using various modules for processing that will not cancel crosstalk across the whole kit (eDrumIn modules, even multiples, will do this canceling).
Often times I see weird things in the monitor that I was not expecting but they are not the most recent hit so you have to look into the history a little (this is my I like the monitor box as it has a scrollable history). Also the history grabs things like control change (CC) and aftertouch (AT) that the mapping box will not show you real-time.
You can also bring up the midi layout window (Help->Show MIDI mapping layout) and it will light up triggers real-time as you hit them,. You can see the whole 128 midi assignments in one window and watch them light up as you hit them. You do not see the full names but it is enough usually.
Mark KingHave you tried selecting the bell then removing all notes that are associated with it? Then try and assign the correct note.
SD3 with older sdx,s plus Rooms of Hansa and Death & Darkness. Cubase and wavelab current versions. Roland TD50x using all trigger inputs for triggering SD3 only. Windows 11 computer. Various keyboards and outboard gear as well as VST instruments. Acoustic drums: Yamaha 9000 natural wood and Pearl masters. Various snare drums. RME BabyFace Pro FS and Adam A7X monitors
bpjacobsenHave you tried selecting the bell then removing all notes that are associated with it? Then try and assign the correct note.
funny thing is, I tested earlier today using my cowbell pad. I added a ride cymbal instrument to the kit, then in midi setup, tapped the cowbell, clicked learn, and tapped it again. it played the ride bell. So I know I’m doing it correctly but I have to try again when I re-connect the bell. I may just try connecting it to a different port. I got a few laying on the floor from removing some pads so hopefully that solves my issue for now. eventually, when I get the edrummin boxes, I will have to re-do the mappings anyway, and the trigger settings etc. But at least for now I can keep loading presets I like and modifying and saving. then later when I get the ED, I can just update the mappings again.
bpjacobsenSo I played around a bit more and what I am finding is that, the learn button does not work all the time. If I add the cymbal instrument then go to the midi settings and hit my bell, then just select the ride bell, it works from there. no need to learn.
pumpkinkingSo I played around a bit more and what I am finding is that, the learn button does not work all the time. If I add the cymbal instrument then go to the midi settings and hit my bell, then just select the ride bell, it works from there. no need to learn.
Whenever I’m trying to map ekit midi with accuracy, I do it manually (ie not with “learn”). Using the learn is great for quick tweaks and trying out different ekit mods, but I have found it is not a reliable enough UI for precision mapping – mainly because it is “click then trigger” style UI, as opposed to the manual approach which is “trigger then click” so you know what you’re getting.
No products in the cart.