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.
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.