+- XOR Userforum (https://forum.xor.eu)
+-- Forum: Products (https://forum.xor.eu/forumdisplay.php?fid=3)
+--- Forum: NerdSEQ (https://forum.xor.eu/forumdisplay.php?fid=6)
+---- Forum: General Questions (https://forum.xor.eu/forumdisplay.php?fid=17)
+---- Thread: Assigning Pad Note on BitBox Micro (/showthread.php?tid=2084)
Assigning Pad Note on BitBox Micro - heyitsme - 03-20-2026
So I have the Bitbox Micro connected to my NerdSeq via MIDI, MIDI Pads on the Bitbox listens to Channel 10, see picture 1 and 2. When a pad’s MIDI In is set to None, Root note to None and Pad Note to Default, the NerdSeq troggers the Pad as expected starting from Note C-3.
However, when I try to assign a specific note to a Pad, it doesn’t trigger the pad. When I change that specific pad to listen to MIDI In channel 10, all notes that are played trigger that pad, I’ve also tried setting the Root Note to be the same as the Pad Note but that doesn’t help either. What am I missing here?
I want to assign a specific note to a specific pad as my plan is to get a second BitBox micro, in order to have more samples available from the same MIDI track.
More specifically, here is my setup:
NerdSeq1 + 2hp MIDI connected to NerdSeq2 + 2hp MID
NerdSeq1 connected to the Bitbox Micro1 MIDI In.
This already consumes both MIDI outs on the NerdSeq 1, so the plan is to use the MIDI through on NerdSeq2’s 2HP MIDI expander and connect it to the Bitbox Micro2, but I want to make sure that assigning MIDI notes to pads does work and that this setup using the MIDI through on the second NerdSeq to the second Bitbox Micro will work before pulling the trigger.
What am I missing not being able to assign specific note values to specific pads? Also, would appreciate some pointers about the setup with MIDI through, will it work?
RE: Assigning Pad Note on BitBox Micro - XORadmin - 03-20-2026
I think that is one of the things people use the bitbox for. I am pretty sure you can define a specific note to a pad. But that is a question for bitbox users/manual or for the bitbox groups.
As for your NerdSEQ strategy they are multiple options:
NerdSEQ1 2HP Out -> Bitbox1
NerdSEQ1 2HP Out2-> NerdSEQ2 -> Bitbox2
Here you would have one or multiple tracks on both controlling NS1->BB1 and NS2->BB2 but you can keep sync between NS1 and NS2.
And of course they are more options, and some are better than others.
Did you think of using the drummatrix instead of a Midi track? There you can define up to 16 midi-drums per track and you could even control both bitboxes independently.
Sorry for the low sample quality. It's not a bitbox or a full fledged sampler and was never meant to be :-)
RE: Assigning Pad Note on BitBox Micro - heyitsme - 03-20-2026
Yes, I’m already using the Trigger 16 to trigger my modular drums, I have 3 trigger outs left on it which I plan to use on my second Bitbox, and the rest of the pads on the second bitbox to mostly trigger some samples. My first bitbox is also occupied with sample triggering so that’s why I want to get a second one.
The reason I don’t want to control the second bitbox from my second nerdseq is basically to save a channel for modulation, but also to reduce cognitive load as the system is already really complex, so keeping all midi triggering on one NerdSeq saves me some brain RAM lol.
In any case, I found the issue: it turns out Bitbox and NerdSeq uses different octave referencing, C#0 on the NerdSeq corresponds to C#1 on the Bitbox. I figured it out by using all the midi columns and added all the notes until pads were triggered.
About the sampling on the NerdSeq, I think it’s just a bonus having sampling, however even when using firmware 3.01RC and using a sample rate of 44.1khz, noticable noise were present in some, but not all of my samples, which was odd.
RE: Assigning Pad Note on BitBox Micro - XORadmin - 03-20-2026
(03-20-2026, 11:09 PM)philosopherstone Wrote: Yes, I’m already using the Trigger 16 to trigger my modular drums, I have 3 trigger outs left on it which I plan to use on my second Bitbox, and the rest of the pads on the second bitbox to mostly trigger some samples. My first bitbox is also occupied with sample triggering so that’s why I want to get a second one.
The reason I don’t want to control the second bitbox from my second nerdseq is basically to save a channel for modulation, but also to reduce cognitive load as the system is already really complex, so keeping all midi triggering on one NerdSeq saves me some brain RAM lol.
In any case, I found the issue: it turns out Bitbox and NerdSeq uses different octave referencing, C#0 on the NerdSeq corresponds to C#1 on the Bitbox. I figured it out by using all the midi columns and added all the notes until pads were triggered.
About the sampling on the NerdSeq, I think it’s just a bonus having sampling, however even when using firmware 3.01RC and using a sample rate of 44.1khz, noticable noise were present in some, but not all of my samples, which was odd.
Yes sampling is 8bit and there is no way to change that. That adds the noise on lower volumes.
You know you can use the drummatrix also with Midi and with a thru you can connect both bitboxes?! No trigger16 involved.
Also without a thru you could merge the signal on the 2nd NerdSEQ and pass that to both bitboxes with the double out. But that adds a slight latency caused by the merging. Mainly not noticeable though.
RE: Assigning Pad Note on BitBox Micro - heyitsme - 03-22-2026
(03-20-2026, 11:43 PM)XORadmin Wrote:(03-20-2026, 11:09 PM)philosopherstone Wrote: Yes, I’m already using the Trigger 16 to trigger my modular drums, I have 3 trigger outs left on it which I plan to use on my second Bitbox, and the rest of the pads on the second bitbox to mostly trigger some samples. My first bitbox is also occupied with sample triggering so that’s why I want to get a second one.
The reason I don’t want to control the second bitbox from my second nerdseq is basically to save a channel for modulation, but also to reduce cognitive load as the system is already really complex, so keeping all midi triggering on one NerdSeq saves me some brain RAM lol.
In any case, I found the issue: it turns out Bitbox and NerdSeq uses different octave referencing, C#0 on the NerdSeq corresponds to C#1 on the Bitbox. I figured it out by using all the midi columns and added all the notes until pads were triggered.
About the sampling on the NerdSeq, I think it’s just a bonus having sampling, however even when using firmware 3.01RC and using a sample rate of 44.1khz, noticable noise were present in some, but not all of my samples, which was odd.
Yes sampling is 8bit and there is no way to change that. That adds the noise on lower volumes.
You know you can use the drummatrix also with Midi and with a thru you can connect both bitboxes?! No trigger16 involved.
Also without a thru you could merge the signal on the 2nd NerdSEQ and pass that to both bitboxes with the double out. But that adds a slight latency caused by the merging. Mainly not noticeable though.
I’ve read that you need to assign a MIDI channel and then go to the last page, but I can’t find the drum martrix by doing that and I I’m not sure how to map notes to Pads with the drum matrix.
In any case, I have 5 analog drums do I would need to use the trigger 16 anyway
RE: Assigning Pad Note on BitBox Micro - XORadmin - 03-22-2026
(03-22-2026, 08:43 PM)heyitsme Wrote:(03-20-2026, 11:43 PM)XORadmin Wrote:(03-20-2026, 11:09 PM)philosopherstone Wrote: Yes, I’m already using the Trigger 16 to trigger my modular drums, I have 3 trigger outs left on it which I plan to use on my second Bitbox, and the rest of the pads on the second bitbox to mostly trigger some samples. My first bitbox is also occupied with sample triggering so that’s why I want to get a second one.
The reason I don’t want to control the second bitbox from my second nerdseq is basically to save a channel for modulation, but also to reduce cognitive load as the system is already really complex, so keeping all midi triggering on one NerdSeq saves me some brain RAM lol.
In any case, I found the issue: it turns out Bitbox and NerdSeq uses different octave referencing, C#0 on the NerdSeq corresponds to C#1 on the Bitbox. I figured it out by using all the midi columns and added all the notes until pads were triggered.
About the sampling on the NerdSeq, I think it’s just a bonus having sampling, however even when using firmware 3.01RC and using a sample rate of 44.1khz, noticable noise were present in some, but not all of my samples, which was odd.
Yes sampling is 8bit and there is no way to change that. That adds the noise on lower volumes.
You know you can use the drummatrix also with Midi and with a thru you can connect both bitboxes?! No trigger16 involved.
Also without a thru you could merge the signal on the 2nd NerdSEQ and pass that to both bitboxes with the double out. But that adds a slight latency caused by the merging. Mainly not noticeable though.
I’ve read that you need to assign a MIDI channel and then go to the last page, but I can’t find the drum martrix by doing that and I I’m not sure how to map notes to Pads with the drum matrix.
In any case, I have 5 analog drums do I would need to use the trigger 16 anyway
You do that with the multifunction/I2c track. There you can assign many different things to the drummatrix columns. Also the triggers.
RE: Assigning Pad Note on BitBox Micro - heyitsme - 03-22-2026
Okay, I think I tried with that type of track as well, will try again tomorrow and see if I find it this time.
So I found the drum marrix in the multi/i2c track, but I don't know how to assign them to triggers or MIDI notes, how do I do that?
RE: Assigning Pad Note on BitBox Micro - XORadmin - 03-26-2026
(03-22-2026, 10:12 PM)heyitsme Wrote: Okay, I think I tried with that type of track as well, will try again tomorrow and see if I find it this time.
So I found the drum marrix in the multi/i2c track, but I don't know how to assign them to triggers or MIDI notes, how do I do that?
In the Track Setup.
Manual Page 98