Notifications
Clear all

Triggering various midi drum patterns from midi keyboard keys

11 Posts
5 Users
1 Reactions
926 Views
(@craigr68)
Member
Joined: 4 years ago
Posts: 210
Topic starter  

I want to layout drum patterns across my midi keyboard like this:

Key C1 -> triggers pattern1.mid

Key C#1 -> triggers pattern2.mid

Key D1 -> triggers pattern3.mid, and so on

I've successfully created a Midibox Stack and have assigned Macro8 to switch the patterns (Screenshot).  That much works great.  However, is there a way instead to assign the midi patterns to keys on the keyboard?  If so, please elaborate. 

I see that Spitfire "ABE LABORIEL JR DRUMS" new original does this where there's a different pattern on each key.  I tried stacking multiple layers of XO drum plugin, but after adding just a few layers, it takes too long to load.  Loading multiple copies of XO is unnecessary overkill anyway.  Whereas, loading multiple midi clips with one instance of XO should be quick to load.

 


   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4435
 
Posted by: @craigr68

is there a way instead to assign the midi patterns to keys on the keyboard?

At the moment, no. It's on the to-do list.


   
ReplyQuote
(@glenjdiamond)
Estimable Member
Joined: 3 years ago
Posts: 106
 

If you only have three midi files in the stack.  You could program two knobs.  Each one would only be programmed to select one of the midi stack tracks at its lowest position, and an alternative of one of the other two tracks at its highest position. 

A/B , A/C

Twiddling those knobs quickly full left then full right will select the stack track you need. 

The height of the horizontal straight line height on the curve will represent the stack track you need.  Just over half way across the curve should be a straight line downwards.  To the left of the curve the line will be on the bottom horizontal.   When fully left will always pick one of the stack tracks (A) but fully right will only pick the one you are interested in.


   
ReplyQuote
(@courtjestr)
Eminent Member
Joined: 2 years ago
Posts: 17
 

I was dreaming about doing this last night. This would be such an awesome feature to add. 


   
ReplyQuote
(@craigr68)
Member
Joined: 4 years ago
Posts: 210
Topic starter  

@glenjdiamond 

Thanks for the suggestion but I don't see where that connects the action to midi keys.  Unless I'm missing something, manually twiddling knobs is what I'm trying to avoid.  Meanwhile, I have a working solution.  It first starts with a 10 pattern XO midi stack in Midibox linked to Macro3 which is assigned to CC3.  Then I have a script that has 2 parts.  One part senses what midi key is pressed.  Depending on what midi key is pressed, a corresponding CC3 value is sent using sendmidi.  The macro control then moves the appropriate amount and the pattern is switched. 


   
ReplyQuote
(@courtjestr)
Eminent Member
Joined: 2 years ago
Posts: 17
 

@craigr68 This is a great idea. I had just simulated what you had done using Unify in KushView Element, and using midiNotesToCC from the PizMIDI collection. I haven't done any Unify scripting yet, but I would be interested in seeing what you came up with. Care to share your scripts?


   
Robert.P reacted
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4435
 

@craigr

If you want to use a plug-in like MidiNotesToCC, you will need to put it as a MIDI effect on an INST layer, where the instrument is an embedded Unify. That way, the CC events output by the plug-in will be interpreted by the embedded Unify to control its macro knobs.

There is no way to direct the output of a MIDI-effect plug-in to the macro knobs of the Unify instance that contains the MIDI-effect plug-in itself.


   
ReplyQuote
(@craigr68)
Member
Joined: 4 years ago
Posts: 210
Topic starter  

When I saw Spitfire "ABE LABORIEL JR DRUMS" is when I got onto this idea.  Only, I wanted to simulate that with XO and Addictive Drums.  I'm getting discouraged trying to do this with Midibox.  Basically, I want each midi key to trigger a particular drum loop - the pattern, the tempo, the time signature (4/4, 6/8, etc), and the samples.

So I'm thinking maybe I ought to use audio loops instead.  I'm sure that's what Spitfire is doing.  XO is great for exporting audio clips.  Then I could assign the individual audio loops to a key.  Any sampler you'd recommend for this?

Anyway, here's my Autohotkey script that I'll probably put on the side for now.  The routine there that captures midi can be adapted to various situations.  Sendmidi is on github.

This post was modified 2 years ago 2 times by craigr68

   
ReplyQuote
(@craigr68)
Member
Joined: 4 years ago
Posts: 210
Topic starter  

Hey guys, thanks for the heads up on the PizMIDI collection.  I wasn't aware of these plugins.  I haven't checked them out yet, but that's probably a better way to go since you could include them right in the unify patch.


   
ReplyQuote
Robert.P
(@robert-p)
Reputable Member
Joined: 4 years ago
Posts: 293
 
Posted by: @craigr68

Hey guys, thanks for the heads up on the PizMIDI collection.  I wasn't aware of these plugins.  I haven't checked them out yet, but that's probably a better way to go since you could include them right in the unify patch.

I also use PizMIDI plugins, usually I place them inside the ComboBox to add some more magic to Unify.


   
ReplyQuote
(@courtjestr)
Eminent Member
Joined: 2 years ago
Posts: 17
 
Posted by: @getdunne

@craigr

If you want to use a plug-in like MidiNotesToCC, you will need to put it as a MIDI effect on an INST layer, where the instrument is an embedded Unify. That way, the CC events output by the plug-in will be interpreted by the embedded Unify to control its macro knobs.

There is no way to direct the output of a MIDI-effect plug-in to the macro knobs of the Unify instance that contains the MIDI-effect plug-in itself.

Good idea. That is the reason I used Kushview Element, to direct the output of midiNotesToCC to a Unify macro knob. But using an embedded Unify is way more elegent.

Just tried it and it seems to work well. I need to figure out some triggering issues. It is working slightly different than when I was using Kushview Element. More info to come.

This post was modified 2 years ago by DougR

   
ReplyQuote
Share: