MIDI Triggers from KeystepPro

[Anouk_music]

Hello people,

I have some trouble triggering pads on bitbox micro with my KeystepPro.
The error first occured after I rearranged my rack. I connected MIDI Out 1 on KSP with MIDI In on BBM and tried triggering pads with KSPs drum sequencer but it didn't work. Triggering the pads manually (touch) works. KSPs CV drum gates are working just fine and MCC shows MIDI data when triggering a key.

The MIDI settings were the following:

KSP:
Utility>MIDI Channels>Drum output>10
Utility>Drum Map>Config>Chrom>0

BBM:
Tools>MIDI Pads>Omni

What I've tried so far:

using MIDI out 2
setting MIDI Pads to Ch 10
setting KSPs Drum out and BBMs MIDI Pads to the same channel, other than 10
setting KSPs Drum Map to 54, MCC shows MIDI value 36 for the first key ( BBM receives MIDI values from 36 to 43)
setting BBMs MIDI Pads to channels 1-4 (KSP sends Track 1-4 on these channels), didn't trigger the pads either
doing a factory reset on KSP
upgrading both firmwares to the latest

Btw KSP doesn't send any Gate/Pitch/Vel values from their dedicated CV out either. (has worked perfectly so far). So something is definitely wrong with my KSP.

If anyone has any clues, please help, I'm kinda worried.

Cheers

[Steve]

setting BBMs MIDI Pads to channels 1-4 (KSP sends Track 1-4 on these channels), didn't trigger the pads either

Check this. The Micro pads only respond to these specific notes when you use MIDI Pads in the Tools settings. If you set each pad to a unique channel your results will vary.

KSP set to Drum Ouput Ch 10. The bottom 8 keys do trigger the pads when using MIDI Pads

[Anouk_music]

Check this. The Micro pads only respond to these specific notes when you use MIDI Pads in the Tools settings. If you set each pad to a unique channel your results will vary.

KSP set to Drum Ouput Ch 10. The bottom 8 keys do trigger the pads when using MIDI Pads

That's exactly what I was doing. Setting the MIDI Pads under Tools settings to either ch. 1,2,3 or 4 and triggering the eqivalent channel on KSP.
Since the firmware upgrade there's no option anymore to change the MIDI channel of a specific pad.
And yes, setting MIDI Pads to Ch 10 should result in triggers from KSPs Drum out, but it doesn't. MCC shows, KSP is sending MIDI triggers but BBM doesn't receive them.

I've also checked the MIDI cable and adapter, all connections are intact.

[Steve]

That's exactly what I was doing. Setting the MIDI Pads under Tools settings to either ch. 1,2,3 or 4 and triggering the eqivalent channel on KSP.
Since the firmware upgrade there's no option anymore to change the MIDI channel of a specific pad.
And yes, setting MIDI Pads to Ch 10 should result in triggers from KSPs Drum out, but it doesn't. MCC shows, KSP is sending MIDI triggers but BBM doesn't receive them.

I've also checked the MIDI cable and adapter, all connections are intact.

I confirmed that my settings work using (several) bitbox modules and a KSP. Try using the default config on the KSP. There is separate behavior for MIDI Out 2 on KSP. I used Out 1. You might consider sharing a video of your setup, settings (very important), connections, and process.

Since the firmware upgrade there's no option anymore to change the MIDI channel of a specific pad.

are you referring to the bitbox? Please always share firmware as a number. "Latest" is ambiguous for support purposes. You don't want pad-level MIDI for this.

[kattefjaes]

That's exactly what I was doing. Setting the MIDI Pads under Tools settings to either ch. 1,2,3 or 4 and triggering the eqivalent channel on KSP.
Since the firmware upgrade there's no option anymore to change the MIDI channel of a specific pad.
And yes, setting MIDI Pads to Ch 10 should result in triggers from KSPs Drum out, but it doesn't. MCC shows, KSP is sending MIDI triggers but BBM doesn't receive them.

I've also checked the MIDI cable and adapter, all connections are intact.

The manual is just inadequate and incorrect on this point, it doesn't explain how to map a MIDI channel to a pad correctly. It says:

To Play Notes and Use Common MIDI Modulation Signals with a Specific Pad or Pads:
You can also configure a specific pad to respond to MIDI notes on a specific channel by
assigning a MIDI channel to the pad on the pad’s parameters screen. How the pad
responds will depend on the Pad mode.
1.
Push HOME, and select the pad you want to control with the MIDI Device.
2.
Push the right arrow button twice to see the Pad Parameter screen, and then
use the top knob to scroll down to see the MIDI related parameters.
3.
Set the MIDI In parameter to assign a specific channel to this pad and now
your MIDI device transmitting on this channel will play this pad. If the pad is in
sample (single), granular or clip mode, each MIDI note will play the pad pitch
shifted in the same way the Keys screen works. If the pad is a Slicer, each
MIDI note will play a slice of the file in the same way it works on the Keys
screen. If the pad is using multi-sample, the notes will trigger the appropriate
sample based on root note or sample mapping.

The bit that is incorrect/incomplete/badly written is point 2- "Push the right arrow button twice to see the Pad Parameter screen, and then
use the top knob to scroll down to see the MIDI related parameters". This is only half the story.

The MIDI channel isn't there, scrolling will avail you nought. Everything isn't in a big scrolly list. To get at the MIDI parameters, you need to use the button with five little circles, near the top left of the screen, from the pad parameter screen. Then you need to go to the "config" section. Essentially, the pad parameter screen has five layers or subsections, accessible from that "little circle button".

That bit of the manual badly needs updating, I lost hours trying to solve this problem, checking back with old project files that use mapped channels, to check that it does still work and see if I could expose the UI to control it. Much swearing ensued

Anyway- I hope that by explaining it here I not only save you some frustration, but that I'll remember it the next time that I need it. Once you can actually get at the right interface, mapping a channel to a pad is fast and easy. Until then, it's a menu-diving frustration at the hands of a misleading manual.

[Steve]

The manual is in need of updating. We are small but are working on this - and other manuals. Thanks for the feedback and your continued patience.

[GregIcky]

I'm having this same issue on the micro Bitbox micro release version 2.2.7

When I set up any pad to midi ch 10 ALL of the pads are triggered by every key. They are not restrained to the "First 8 keys on the asp"

I get every sample playing AND they play in different pitches up the keyboard.

I use MIDI out 1 on the KSP
I use MIDI ch 10 on the KSP

I set MIDI on PAD1 (kick) to MIDI Ch 10 on BBM
I set MIDI Pads to MIDI ch 10 on the BBM

Every key I play on KSP triggers the kick.... going up the keyboard makes it go up in pitch
and
If I set ANY other pad to ch10 it is also triggered on every key - the first 24 that KSP uses for "MIDI drums"

[GregIcky]

I'm having this same issue on the micro Bitbox micro release version 2.2.7

When I set up any pad to midi ch 10 ALL of the pads are triggered by every key. They are not restrained to the "First 8 keys on the asp"

I get every sample playing AND they play in different pitches up the keyboard.

I use MIDI out 1 on the KSP
I use MIDI ch 10 on the KSP

I set MIDI on PAD1 (kick) to MIDI Ch 10 on BBM
I set MIDI Pads to MIDI ch 10 on the BBM

Every key I play on KSP triggers the kick.... going up the keyboard makes it go up in pitch
and
If I set ANY other pad to ch10 it is also triggered on every key - the first 24 that KSP uses for "MIDI drums"

I finally solved this issue!

On the Keystep Pro I had to set the "drum map" to custom. It was set to "chromatic" and that's why it was triggering everyone and causing problems.
Whew!