some hihat sounds not matching SSD5

[Ralph @ Rayzoon]

Okay, here is what happened. When you recorded the MIDI output from Jamstix, you recorded drum set AND Jamcussion notes onto the same track.
When you feed that back into SSD5, you will get unwanted Jamcussion notes getting played by SSD5.

Solution is to export to MIDI file rather than recording because that will only export the active brain mode (drum set OR Jamcussion).

Another way would be to set the MIDI channel for Jamcussion to something other than the drum set channel (PERC mode, KIT window, KIT menu, Send To MIDI Channel) so you can filter them out in the DAW by channel.

[Jae.Thomas]

Jamstix outputs MIDI CC #4 controller data to control SSD5 hihat opening level. You can watch it by previewing a bar in JS4 with a closed hat while having the "Kit Mapping" window open in SSD5. Turn the 'Open' knob on the hihat note in JS4 and watch as different notes get triggered red in SSD5 through all 5 open stages supported by SSD5.

that makes sense!!! sorry!

[W_Michael_F]

I tried both suggestions without success.

When I export the midi file, it is exporting both Jamcussion and drum set (even with only 'drums' selected). If it matters, I'm doing this as a vst inside of Cubase. I could try it in standalone and see if that makes a difference.

I tried setting the Jamcussion and drum set to different midi channels and recording ... setting up separate tracks for each. Even though I told Cubase to only receive on specific channels, it was getting all of the information on each track. And exporting the track as a midi file didn't retain that information either.

I've already built the song with a Jamcussion part ... but is there a way to delete the Jamcussion after the song has been built? That would seem to be the simplest solution ... then I could save two diff song versions.

While I'd love to see the product do this, if we're spending too much time on it, I'll just try some other method.

By the way, back to what I was doing, I assumed when I didn't check the 'keep percussion' option on the mapping page, that was going to ignore the percussion parts ... apparently, it doesn't work that way.

Michael

[Ralph @ Rayzoon]

When I export the midi file, it is exporting both Jamcussion and drum set (even with only 'drums' selected).

That is odd. Whether I drag or export to file, I only get the MIDI for the active mode (DRUMS or PERC).

but is there a way to delete the Jamcussion after the song has been built? That would seem to be the simplest solution ... then I could save two diff song versions.

You can disable Jamcussion by toggling the speaker icon next to PERC. It won't be in any MIDI export nor will it be in the MIDI if you record it from the output.

By the way, back to what I was doing, I assumed when I didn't check the 'keep percussion' option on the mapping page

That option is about keeping the percussive parts of the drum set (chimes, jam blocks etc.).

[W_Michael_F]

OK ... this morning's update.

Now I'm not sure if what I said about the methods for file transfer not working is true ... here's why. (And, as a caveat, I did mute the Jamcussion speaker and was getting the same issue.) I was basing my comments on the fact that the annoying hand clap was still present when I did each of the paths you suggested ... since it was still there, I was assuming the various methods just weren't working.

This morning I manually stripped out the percussion parts of the Jamstix song measure by measure ... so there was NO percussion part in the song. I exported both a JS4 version and a SSD5 midi version. I will send you the files in a separate email.

The issue comes back to the fact that the E4 note is 'oddly mapped' or 'mis-mapped'. When you open the 'drum kit' midi files concurrently, it becomes more easy for me to see what's re-mapped and to where (and, not re-mapped, obviously by toggling b/n the tracks). The E4 is NOT re-mapped. Based on my analysis (for this song), every other note appears to be appropriate. I A/B'd various notes/kit sounds and all the other mapping makes sense (taking in consideration the different kits).

So, I still believe there's an issue with the SSD5 re-map but at least I've convinced myself that it's only one kit piece (one note) and I can manually address that. Again, the E4 in Jamstix sounds like a highly muted hi-hat or muted cymbal ... in SSD5, it's the hand clap from hell.

Anyway, I'll go back and test some of the other methods for transfer that you've suggested in later songs ... I appreciate the tips ... but I really need to get moving forward with this song.

Let me know your thoughts, please ...

Thanks,

Michael

[Ralph @ Rayzoon]

I've looked into this. For me, the annoying clap sound shows as E5 (#76). If you open Kit->Kit Menu->Show Key Map, you can see that #76 is mapped to the 'Shaker', which you have active in the drum kit as a Jamstix sound.

So, if you record/export the MIDI, you will be sending those notes to SSD5 instead of Jamstix, causing the issue.

In other words, you have 3 targets for MIDI notes in your project: a) SSD5 drum set b) Jamstix drum set percusssion (i.e. Shaker) and c) Jamcussion, which makes things a bit tricky.

What I would do is have SSD5 driven only by the Jamstix output. I would then record the full MIDI as you've done, send it on a MIDI track to Jamstix. set Jamstix to 'MIDI Playback' mode and make sure that the MIDI icon in the kit editor is checked (or use 'No MIDI output for internal sounds' in the kit menu).

This will cause Jamstix to play all non-SSD5 notes (shaker, Jamcussion etc.) but only send the rest to SSD5 via MIDI output.

Just make sure the toggle is off whenever you export/record MIDI from Jamstix.

[W_Michael_F]

Your reply reminded me that Cubase has its midi note names shifted by one. There's a whole set of threads in their forum about 'why does Cubase call middle C C3 instead of C4'. And they seem to have killed the preference option to display midi note numbers on the editors ... ugh.

Anyway, your explanation makes sense with regards to what is happening ... and at least we're to the bottom of it. I'll try to deploy your process later today ... now that I know what's happening, I think I can manage a 'manual' process if I'm not smart enough to make your process work.

Thanks for your time ...

Michael