![marching drum step sequencer marching drum step sequencer](https://usa.yamaha.com/files/C6BE3B61CC0148BCB37AE79453CF9EE1_12074_240x413_717933b112917c17665f49c23f0009a9.jpg)
Well it can be just routed to the synth and in the case of hardware it is. Why do simple instrument tracks need both and audio and Midi track? Why can't it just be a midi track with the output routed to the synth? Try writing a map from scratch rather than loading a preset, you'll see what I mean. Just a shame its so awkward and unintuitive to use.
![marching drum step sequencer marching drum step sequencer](https://www.musicalbin.com/wp-content/uploads/2019/12/51soTags0ZL.jpg)
In its simpler use as in this case it just translates the note names to drum names for you, but can be used in a far more powerful way if required. You can create a drum map from many different drum sources if you wish "mapping" each note on your controller to a different note on any drum synth you wish. antiquated as the drum map interface is in principle it is still a very handy and powerful tool. This is the part of the drum map that tells it what synth to play.Īs er. One of the fields in the drum manager is the "Out port". How does the track know what synth to play if you don't map the output of the track to a synth? As it is this option isn't available for soft synths.
![marching drum step sequencer marching drum step sequencer](https://www.promusicaustralia.com.au/assets/thumbL/BERD8.png)
If it were hardware you could write an Instrument definition (ins file) if one hasn't already been written to "translate" the note names to drum names. Session Drummer 3 for example does the drum names for you. In the case of the CW Studio instruments it seems that it translates as notes rather than individual kit names. How the synth handles the note names is down to the individual synth. When you route the output to itself, I assume you mean "SI drumkit" the MIDI track is going directly to the synth. what was it doing when I routed the the output to itself