Bitbox with the BeatStepPro - a great control surface for the BitBox

[Angstrom]

Hi, I thought I'd share my usage strategy here. I use the Bitbox Micro with the BSP, which is not only a fun table top sequencer to use in addition to a more complete sequencer - but it has the advantage of a mode called "control" where the 16 rotary encoders and the 32 pads temporarily become a midi control surface.

So, the MIDI out from the BSP can go to the MIDI in of the BitBox (it needs an A to B TRS MIDI adapter ;-) ) and then I use the rotaries on the BSP to control the mixer of the BitBox. It's very quick to set up on stage or in studio as it's one TRS cable. All the other esoteric modulation and such can then come in from the rack via the usual routes.

I thought I'd pass this idea along as although it's obvious, it's also sometime easy to overlook the obvious things!

[NaemAurum]

Hi, I thought I'd share my usage strategy here. I use the Bitbox Micro with the BSP, which is not only a fun table top sequencer to use in addition to a more complete sequencer - but it has the advantage of a mode called "control" where the 16 rotary encoders and the 32 pads temporarily become a midi control surface.

So, the MIDI out from the BSP can go to the MIDI in of the BitBox (it needs an A to B TRS MIDI adapter ;-) ) and then I use the rotaries on the BSP to control the mixer of the BitBox. It's very quick to set up on stage or in studio as it's one TRS cable. All the other esoteric modulation and such can then come in from the rack via the usual routes.

I thought I'd pass this idea along as although it's obvious, it's also sometime easy to overlook the obvious things!

This is dope! Would love to see photos or vids of it in use. I'm in the market for a sequencer and I'm trying to decide if I want to go euro or controller

[g.r.u.m]

and then I use the rotaries on the BSP to control the mixer of the BitBox.

I'd also love to know how you control the Bitbox Micro mixer with MIDI as I can't find anything in the manual to explain how to set this up and there is no MIDI learn command on the mixer screen. Which CCs and channels are you using?

[Steve]

Map the external controller to the Level parameter. Decrease the Level to apx -50dB.

[Angstrom]

Someone asked how to set it up, here's a terrible video.

https://www.youtube.com/watch?v=rC581yoMslE

[tries.tracts-0r]

Never used the control mode, but the BSP drum pads + midi is a killer combo for the Micro. I love it.

[g.r.u.m]

Map the external controller to the Level parameter. Decrease the Level to apx -50dB.

Thanks, this works well so I've set up a preset to use as a template. However when a new sample is loaded into a pad, all the mappings are reset to default (i.e. VEL, MVOL and MPAN) and I have to relearn the CC for that pad.

This becomes very tedious, very quickly when experimenting with different samples so I'm hoping that I've missed something! So exactly how do I get my template preset to remember the MIDI mappings?

EDIT: after a bit more experimenting, it appears that the mappings are remembered when the sample is recognised/loaded as a clip but they are reset when it's a sample (i.e. one-shot). So is this a bug or intentional?

[Steve]

When you load a different type, some settings will change. This is intentional to help set you up based on the meta data in the wav file.

[g.r.u.m]

When you load a different type, some settings will change. This is intentional to help set you up based on the meta data in the wav file.

When the sample type is changed from Clip to Sample or vice versa, the only settings that change are Levels > Modulation targets, which is not very helpful when trying to set up an external controller.

Steve, if this is intentional, I don't understand how it is helpful. Should I create a new Wishlist topic or is it actually a bug?

(n.b. other mod targets such as Pitch, Filter etc retain their settings when changing sample type, which is the behaviour I would expect for the Level parameter too)

[Steve]

This is not a bug, and it definitely exists on the wishlist. The underlying issue is that the sampler reads metadata to determine whether the wav file is a Clip (sync, beat count, etc.) or has markers for slices. This is meant to be helpful though we hear the requests for altering this behavior. We looked at this when we were working on version 3, but there was no clear path to making it happen, given the other things we were working on. I get it seems an easy modification, but everything in the box is interconnected in some way.