Custom mapping issue

[Megamix]

Hi Toontrack, I use an Akai MPD 218 for triggering SD3 and I like to create my own custom mappings for kits using the Learn button in the Midi In/E-Drums Settings page. I then save my mapping settings using the Save As function and place the file somewhere in my project. However, if I decide to change kits and I then select my custom mappings file, some of the mappings are lost. It seems to retain Kick, Snare and hats (midi notes 36, 38, 42) but some of the toms and cymbals aren’t as I saved them.

To get round this I have to set up a kit as I want it, then save the project. It would be nice to be able to change kits on the fly and then select my custom mapping file and have all of the articulations mapped to my preferred midi notes. I used to be able to do this in SD2.

Any ideas what’s happening here ? Maybe it’s the case that when you save mappings in SD3 it doesn’t save the custom midi In/Out remapping info ? just the Midi In info ?

Topic

[Henrik Ekblom]

What version of SD3 are you using? The version number is visible in the lower left corner of the interface.

Henrik Ekblom - User Experience Designer
Toontrack

[Megamix]

Hi thanks, I’m using 3.1.1

[Henrik Ekblom]

If you change some settings in MIDI In/E-drums, they are saved with the (.SD3P) project file you save in the File menu of SD3.
Say you change some MIDI in settings so that incoming note 38 is mapped to note 40. You then save the project and name it “Metal”.

You load an old project where you have mapped incoming note 36 to note 80. Those settings are loaded into MIDI In settings, so if you want to always have that incoming note 38 should be mapped to 40, you should do the changes and save the project. The next time you load that project, note 38 will go to 40…

So in summary: each project carries its own MIDI In settings.

Does this make it clearer for you? Does it solve your problem?

Henrik Ekblom - User Experience Designer
Toontrack

[Megamix]

Hi, thanks, I see how it works now.

[Author]

Replies