Jamstix 4.4.0 & MODODRUM

Post by **Ralph @ Rayzoon** » Wed Aug 28, 2019 4:50 pm

Starting with version 4.4.0 Beta 3, Jamstix supports the just released MODODRUM from IK Multimedia with input and output mappings but also with snare and tom head positioning.

For the latter to work, you need to enable snare and tom positioning in MODODRUM and set the MIDI controllers to 14 (Snare) and 15 (Tom). Now load a MODODRUM output mapping in Jamstix and Jamstix will automatically send positioning info to MODODRUM via MIDI.
You can control the random fluctuations as well as the head offset for L/R hits via new menu items in the kit menu.

Please note that you must enable CC #15 [b:39e6e6abde]for each tom[/b:39e6e6abde] in MODODRUM.

Let us know what you think!

apesma_1 · Post by **apesma_1** » Wed Aug 28, 2019 11:33 pm

I see MODO listed on the Mac version 4.4.0 Beta 1 as well. Is this ready to test as well?

Post by **Ralph @ Rayzoon** » Thu Aug 29, 2019 7:47 am

We're still working on the next macOS Beta for MODODRUM positioning logic but the mappings will work.

El Taube · Post by **El Taube** » Sun Sep 01, 2019 5:59 am

Hi Ralph,

thank you for the update. With regards to thr hihat, should I enable CC4 in MODODRUMS?

Ralph [RZ] wrote:Starting with version 4.4.0 Beta 3, Jamstix supports the just released MODODRUM from IK Multimedia with input and output mappings but also with snare and tom head positioning.

For the latter to work, you need to enable snare and tom positioning in MODODRUM and set the MIDI controllers to 14 (Snare) and 15 (Tom). Now load a MODODRUM output mapping in Jamstix and Jamstix will automatically send positioning info to MODODRUM via MIDI.
You can control the random fluctuations as well as the head offset for L/R hits via new menu items in the kit menu.

Let us know what you think!

Post by **Ralph @ Rayzoon** » Sun Sep 01, 2019 9:32 am

Yes, Jamstix sends hihat opening data via MIDI CC #4 data to MODODRUM by default.

Post by **Ralph @ Rayzoon** » Wed Sep 04, 2019 3:26 pm

Just a quick note that MODODRUM has tom positioning separate for each tom so you need to assign #15 to each tom.

jimgue_77 · Post by **jimgue_77** » Thu Apr 09, 2020 4:34 pm

Is anybody using MODO DRUMS? Considering getting it but wanting opinions on sound (realistic or not) and if anyone is using JS4 with it does it have advantages over sample libraries, like SSD 5.5?

d_steinschneider · Post by **d_steinschneider** » Sun May 10, 2020 9:57 am

I've done a deep dive on edrumming the past year. There was a discussion on vdrums.com about Modo Drums with links to other website threads that got into detail.

My summary is from memory but the consensus was that it's a really promising drum modeling VST that already sounds very good but not as quite as real sounding as sample based drum VST's. There were comparisons to Roland's latest drum modules which means they sound very good but slightly synthetic. That's something you don't hear once they're in a mix. What everyone liked was that there is infinite variety such as what you get when sending cc16 to the snare for positional variations.

IK was having a sale recently and I bought the Studio Max bundle which unfortunately didn't include Modo Drums but it did include Modo Bass which is the best sounding electric bass VST I've used.

dayvy_g · Post by **dayvy_g** » Sat Jun 13, 2020 8:05 am

I get inconsistent hi-hat mapping between Jamstix and Modo drums. I have CC4 enabled on the hi-hat and have had to select the invert button in mapping to get it to play the proper hits. However, sometimes it just seems to ignore the open hats and play closed hats instead. The open hits are not being replaced in the sequencer by the brain either. It still shows an open hit.

Any ideas?

Thanks.
d.

Post by **Ralph @ Rayzoon** » Sun Jun 14, 2020 1:06 pm

dayvy_g wrote:I get inconsistent hi-hat mapping between Jamstix and Modo drums. I have CC4 enabled on the hi-hat and have had to select the invert button in mapping to get it to play the proper hits.

Please do a "Save Song" of this situation and send me the resulting file so we can look into this.