Using a Roland TD 50 I can control two note choices (head & rim) from the module. IN SD 3 I can map each individually. With the rim midi note I can assign to rimshot or “rim only” in SD3.. one or another. So this limits the use of sounds and playing considerably. Seems the Roland does internal processing to determine that two notes occurred nearly the same time and fires off the rimshot sound versus just a rim sound if it sees it separate versus combined with center enough. A little simple AI. But there is no midi channel for this out from the module after the AI. You only get Center and Rim note and impact info. So the AI that occurs in the module to fire a Rimshot does not also routed to a midi out. Therefore, the only way to achieve this would be to add some simple logic to the software you’re sending to (i.e. Toontrack SD).
So… is there a way in SD 3 to map a combined note pattern (based on timeframe to each other and velocity) for the same tom to a trigger like a rimshota and keep the rim separate if the center wasn’t determined a hit within the timeframe. So if rim and center come in strong right next to each other a mapping can be made to rimshot to rigger more realistically? Again, I’m talking about combined notes that map to another note under center circumstances. I am certainly understanding how to map what I have and am doing so just fine. Just stuck with choosing rim versus rim shot and I’d REALLY like to have the ability to trigger both. The realism would significantly improve.
If your software can’t do this, can you please consider for an update? Seems the software could be made to do that by evaluating what came in and combining two notes that meet criteria like this (rough concept idea):
IF both RIM note and center happen with 0.1 timeframe (or whatever pseudo-real-time designation makes sense) THEN check impacts of each trigger for what sound bank to trigger:
If (RIM note >20 impact and center > 20 impact) THEN route together as one RIMSHOT note (user hit both rim and head – so rimshot sound!)
IF (RIM note 20) then CENTER only (user didn’t intend for rim sound – or play rim sound along with it at low volume, but not rimshot sound
IF (RIM note >20 and CENTER <20) then RIM only. (the user is clearly trying to get a cool rim snap - let him hear it!)
So you use simple AI logic to evaluate two incoming notes and their relation to each other to map to sound. Clearly this is what is happening in the modules like the Roland TD50.
I think it would be easy enough to program and if needed I would gladly help do this for you guys!
Something like this and maybe the variables can be user defined would make for a killer midi trigger configuration ability way beyond just the rimshot!
Just seems that aded logic would propell the relaism of your software into realms only modules once dared to dwell! 🙂
Thanks for considering!
Bryan
Looks like the Perl Mimic Pro and Steven Slate Drums does this internally and offers a midi out for center, rim and rimshot even when use two trigger pads. Clever. Just wish this algorithm capability was in Toontrack SD as well. This is so close to spectacular. Please add this feature!
Thanks for the ideas. To add AI, or smart algorithms, to the e-drum section of SD3 is a good idea, one that we have discussed before. I’ll add this to our lists of what to do in future updates!
Henrik Ekblom - User Experience Designer
Toontrack
Struggling with the same problem – no MIDI channel in TD-50X for rimshots. Has anything useful been implemented in SD3 in the meantime?
Please log in to read and reply to this topic.
No products in the cart.
Get all the latest on new releases,
updates and offers directly to your inbox.
Note: By clicking the 'I WANT IN' button, you will not be creating a Toontrack user account. You will only sign up to get our newsletters, offers and promotions to your inbox. You can unsubscribe at any time from a link at the bottom of each email. If you want to learn more about our privacy policy, please find detailed information here.