[Pierre-Olivier Langlois]

Almost 5 years later; I’m still wishing for some Octobans !

Intel i7-3820 (LGA2011 ftw), Win 8.1, Saffire Pro 24, Sonar Studio

[Pierre-Olivier Langlois]

Without changing the way libraries are recorded.. I wonder if SD2 could somehow “blend” the two samples (snare edge and center, for example) proportionally to the CC value received, in order to simulate the in-between sound you get on a real head ? I wonder if it would sound good / real enough.
There could probably be some selectable non-linear curves (akin to the hi-hat correction curves) that you could use to tailor the response.

Intel i7-3820 (LGA2011 ftw), Win 8.1, Saffire Pro 24, Sonar Studio

[Pierre-Olivier Langlois]

I only have one TD-20 module, but before purchasing SD2 I did take into consideration the possibility of getting a second module (more pads and cymbals) so I evaluated the possibilities in regards to SD2.
I think it is definitely feasible.
SD2 has 16 stereo outs, which you can consider as 32 mono outs (out 1 Left, out 1 Right, out 2 Left, out 2 Right, etc. each hard panned left or right) if you do the mixing outside of SD2. In that scenario, each drum pad in SD2 would be routed to one of the 32 outs (all leveled equally in SD2) and mixed in the DAW alongside the 4 analog mics. So basically in that case, SD2’s mixer is acting like a pass-thru.

In Cakewalk Sonar for example you would insert SD2 as a Soft Synth by selecting “All Synth Audio Outputs: Mono”, after that you will see all 16 “stereo” outs from SD2 appear as 32 separate mono outs in your DAW’s user interface.

As for the mapping of the 2 modules, you will need to either :
– leave the Midi note settings inside each module to Roland’s default, then set them to a different midi channel to send each module to its own midi track, then assign each midi track to its own custom drum map that will redirect everything to the proper SD2 midi input note;
OR
– leave one module’s Midi mapping to the default and tweak the other Module’s so that they don’t overlap, set them to the same midi channel to one single midi track, then either make one custom drum map or adjust all mapping inside SD2 directly.

It’s been a month since your OP but I hope that helps.

Intel i7-3820 (LGA2011 ftw), Win 8.1, Saffire Pro 24, Sonar Studio

[Pierre-Olivier Langlois]

Thanks Rogue for your input.

FYI the TD20’s brain will be kept to default settings. Also I was already using the e-drum preset and “More Closed Curve 2”.

Before anything else, I would appreciate your opinion on the questions below from my original post, as I think it would help me figure out a few things :
– Metal Foundry and Avatar (and possibly other SDXs too) seeming to not have the same default note mappings;
– e-drum preset vs default MF and Avatar mappings;
– availabilty of a visual, keyboard-type map of the e-drum preset.

I understand your suggestion on the second instance of SD2. With that in mind, it means for any given project I would be facing one of the 4 scenarios below:
a) “main” kit, comprised of 2 instances of SD2: the main instance with the base MF kit, a bunch of Xdrums and sticks. And the second instance with an Avatar kit and brushes;
b) any Metal Foundry kit on its own (1 instance);
c) any Avatar kit on its own (1 instance);
d) any kit from an SDX I might purchase in the future (1 instance).

Maybe I wasn’t so clear about my goal. I guess I’m looking for strategies to building ONE DAw-level drum-map for the “main” instance with the X-drums (lets forget about the secondary instance & DAW-level drum-map for the moment) plus ONE “do-it-all” SD2-level midi-map preset so that my worklflow when creating new projects is simple, robust and has a future-proofing quality to it, i.e. it will work independently of the chosen scenario (out of the 4 above).
I understand it might not be perfect in the sense that it might not work 100% with any future SDX that will ever be made… but if it can cover my current needs and I can build upon it and make it work in the future with just a little tweaking, without re-doing it all (as I did in the past)… I’ll be happy!

I guess it all comes down to how much mapping should be covered at the DAW/drum map level, and how much at SD2’s level ?
I’m thinking I should use the DAW-level map mostly as a translator in between the TD20 at default settings and either SD2’s edrum midi-preset (extended with the X-drums’ assignments) or SD2’s default kit-level mapping (which again, differ between MF and Avatar)… It could even prove handy if I ever want to use a another drum VST than SD2 for a particular project.
Starting from there, X-drums shall be added and have notes assigned in a way that doesn’t interfere with the default instruments notes of MF, Avatar and other SDXsk, and mapped as “pass-through” on the DAW-level drum-map.
BTW for me having a drum map loaded in Sonar is a must. Even if notes are not re-assigned and passed as is, being able to see the actual instruments names that the notes are pointing to makes track editing much easier.

Lastly, I’ve haven’t updated SD2 in while and while searching I saw something about “improved mapping for high-end edrums” in one of 2.xx updates that I’ve yet to install. What’s that all about?

Sorry if I might be overthinking it again here.. Being an aerospace engineer sure doesn’t help in that regard 🙂

Intel i7-3820 (LGA2011 ftw), Win 8.1, Saffire Pro 24, Sonar Studio

[Pierre-Olivier Langlois]

I sincerly hope there are some octoban and percussion coming!! I need to run a 2nd drum samplers just to add octobans to the kit and my CPU ain’t liking it (too many VSTs running already!!!).

Intel i7-3820 (LGA2011 ftw), Win 8.1, Saffire Pro 24, Sonar Studio

[Author]

Replies