RAYZOON

The keymap is already included in JS. Kit tab > Top Left dropdown menu >Load Key Map. The .ini setting is no longer needed.

Robitaille20, here are the pre-3.5 SSD4 mappings:
www.rayzoontech.com/stuff/ssd4mappings.zip

Thank you so much Ralph!

Hmm trying to use SSD4 and Jamstix OSX 3.6 together. I don't see any CC4 events coming through from Jamstix.

I have selected the SSD4 default kit from within Jamstix, which presumably has all the midi mapping stuff in it. The various kit pieces are playing in SSD4 that way, seemingly correct, but I don't see any CC4 events showing up.

I saw old posts about adding the following to jamstix.ini:

[code:1:e8bc743eb3]
[SsdSampler]
CC4=1
CH_15=13
CH_16=14
CH_19=16
CH_22=15
[/code:1:e8bc743eb3]

Is that still neccessary? If not, then what might I be missing to make sure Jamstix generates beautiful CC4 activity?

I took a peak at the actual kit file in SSD4 Default.j2k:

[code:1:e8bc743eb3]
.
.
UseCC=1
ClosedHatSet=
HihatController=4
Flam=-1
CH_15=13
CH_16=14
CH_19=16
CH_22=15
CC4Fluctuations=0
Stereo Width=0
Ambience Dampening=50
Ambience Strength=44
Ambience Strength 0=44
Ambience Strength 1=44
Ambience Shaping=0
Ambience Output #4=0
.
.
[/code:1:e8bc743eb3]

A little confusing because it says use CC1, but then later says cc4, and cc4fluctuations=0. Not sure what all of those mean, but I would sure love to see cc4 variations happening from jamstix.

Let me look into this and get back to you.

I don't know if this is relevant to anyone anymore, but in JS2 I found that the cowbell and shaker werent getting routed to SSDex using the mappings.

I found what I had to do was finalise my drum track, more or less, using a JS2kit, render down just the cowbell track to a new wav file/track, and then run the JS2 through SSD to use the kits there while playing the cowbell alongside.

Ok, so yeah. I've just upgraded to JS3, and the percussion elements of the kit don't go through to SSDex, possibly because those instruments don't exist in it.

any update on the CC4 issue?

Sorry about the delay! We'll definitely get back to you on this tomorrow.