Vienna Symphonic Library Forum
Forum Statistics

182,294 users have contributed to 42,217 threads and 254,749 posts.

In the past 24 hours, we have 3 new thread(s), 18 new post(s) and 41 new user(s).

  • Drum Map Key Switch - Cbb

    Drum Map Key Switch - Cakewalk by Bandlab

    Seeking vid tutorials on how to organize sample libraries, create a template, and use Key Switches to control articulations. I' have found 1 for Cakewalk but still don't quite get how DM work to actualy change the articulations without placing a midi keyswitch note on the same track as the midi music.

    It looks like Drum Maps can be used to Map Articulations but I'm not sure how to use it.

    I'm open to learn different ways to record articulations besides KS.


  • last edited
    last edited

    Drum Maps is about assigning drum sounds to notes.
    The typical ones a drums vi use are General Midi, for example C1 kick drum, D1 snare plain hit, D#1 drag, E1 half edge snare, F1 rim shot; G# for pedal stomp hihat etc... then cymbals, and for a whole kit tends to cover several octaves range. (I use Cubase with the Yahama numbering ("-2" in BFD3) so these so far are C0 etc, and in the range of most of my keyswitches; EXCEPT this falls in the play range of certain bass instruments, and this is out the window completely now.)...
    and as such have no particular relation to where you'd want to organize your keyswitches through itself. You'd be going through a process which is unnecessary as you're going to have to make decisions anyway.

    "how DM work to actualy change the articulations without placing a midi keyswitch note on the same track as the midi music." they don't, I didn't understand the question.

    - nothing that isn't assigned to the MIDI channel the instrument receives data on communicates with it. But you have no good reason to be thinking about drum maps as a go-between, it would be a waste of time.


    VSL is pretty consistent with the factory matrices; for example a short and long notes matrice has the lowest KS staccato, then portato short, medium and a sus. For eg., bass flute they start at Roland # C1, Yamaha C0*.
    VSL uses the former, there is a way to set it to use the latter or any other known basis in General Settings, the gear icon. The lowest pitch in the play range is *Bb (2 or) 1, an octave and 10 semitones above the low KS, ie., there's no conflict up to there.

    So you could take that as a model for organization, it's coherent. I tend to, but I make my own rather ad hoc
    rather more


  • last edited
    last edited

    Thanks for taking time to explain.

    DM (Drum Maps) in Cakewalk are not just for drums the name is misleading, it allows a way to see the articulation names instead of the virtual keyboard keys.
    Trying to set Key Switch data on a different track to control when articulation changes occour.

    Instead of having KS midi data on the same track as midi music notes

    Keyswitch

    Drum Map


  • Ok, that is interesting. My drum maps from BFD3 import to Cubase in a way to show exactly what the note numbers trigger, I suppose I could make one do that, never thought to.


    "how DM work to actualy change the articulations without placing a midi keyswitch note on the same track as the midi music." 

    Just so long as it's on the right channel.  I don't get why having it on the same track is a big problem, I guess. I definitely want it on the MIDI track instead of having to refer to someting else. 
    I meant same channel, it can be on a different *track* on that same channel.

    I don't know what the question was except 'VE Pro templates' for third party instruments. I wouldn't know. The Kontakt Factory Library VSL Demos follow the usual as I described, in that limited scope of the thing.


  • You have a picture of the drum map going to VE Pro Port 5 channel 5 and a picture of Kontakt assigned to channel 2. 

    Port in VE Pro is meaningful when you have more than one specified in Preferences. If you do not use the VST 3 VE Pro or one of the workarounds for Logic or other hosts, you have one port, Port 1. It looks like the Kontakt Cello is Port 1 Channel 2 (there appears no Port designation); so if you intend the KS from the Drum Map thingy to communicate to that instance that's your target.


  • last edited
    last edited

    Looking for info more up to date but at least found 3 videos, two are 9 years old and one in Russian.

    1. EWQLSO Keyswitch Map Template in Sonar, Part 1

    2. EWQLSO Keyswitch Map Template in Sonar, Part 2

    3. Cakewalk Articulations


  • The business end of the first video, as per drum maps functionality is that it uses the paradigm of Input for the Keyswitch naming and the Output to the instrument; "I/O". Drum maps traditionally can re-map the input - with no alteration - to whatever note name by specifying that in the 'O'. This is probably why drum maps are employed for this, at least as a beginning.