Review, question/suggestion on mapping and MIDI controller.

Yep! The old-school drum-kit sampler Drumkv1 is a hit.

Rui has done a great job on another fine piece of software.

BRAVO!

I have been creating soundfonts with Swami to load into Qsynth
with custom drum kit samples, it's tedious but works.

The main reason and problem to solve was always having to load
the same soundfont numerous times so individual drum sounds can
be panned without appling the pan in the actual .wav sample.

The MIDI spec does not really take drum kit notes into consideration
for continous controllers like pan, pitch etc just an overall
track setting that is applied to all events on the track. The
drum notes can be split into individual tracks and audio panning
used once the individual track audio is recorded back in but it's
also tedious and time consuming. Cubase solves this with VST but
it's not available on Linux and not always the easiest thing to use.
Qtractor may already do this too and I just have not found it.

With Drumkv1 the pan setting actually operates on the individual
drum note (drum sample) so cymbals, toms or any sample can all be
panned individually from the loaded kit. The MIDI drum track can
now stay together. I was hoping to find somthing that could do just
this and Drumkv1 has it.

It's really easy. Sample some drum sounds or download some free
ones and start building kits. No need to create a soundfont, no
multiple instances of the soundfont just simple .wav files loaded
into a logical drum kit.

The phaser effect brings back some fond memories.

Couple of thoughts :

When adding samples and saving the kit it would be nice if a separate
file could be attached with a user defined drum map. One drum sound name
for each of the notes that map the custom drum kits to the standard 0-127
MIDI notes. Basically, custom kits rarely line up with the standard
GM/GS defined naming. Nothing fancy needed just a user defined note
name to the actual MIDI note number.

MIDI automation comes to mind. I have not tried this yet but it could
be usefull if Qtractor MIDI controller messages could set some of the
parameters on the drum kit or effects.

If controller messages are handled then a really nice one to handle
would be the CC#4 (foot controller). Most electronic kits today send
CC#4 for the hi-hat pedal. With the CC#4 value between 0 and 127 and
a little mapping the hi-hat could trigger more than the standard 3 sounds.
With 0 being fully open and 127 fully closed a set of ranges could be
used to map a different hh-hat sound based upon the foot controller.
Then samples like : (closed tip, 1/4 open tip, 1/2 open tip, 3/4 open tip,
open tip, closed edge, 1/4 open edge, 1/2 open edge, 3/4 open edge,
open edge and pedal chic) could be trigged by 2 midi notes and the
value of the foot controller.

Today I preprocess the .mid files as described above and actually create
the correct hi-hat MIDI note-on/off events (base on CC#4 value) to map with
a set of custom hi-hat samples. The CC#4 events are also removed
during the process since the new events usually need to be tightened
up in the mix.

I would say Drumkv1 covers 90% of what I need in order to create
easy nice sounding custom drum kits .

Thank You Rui!