NerdSEQ plus Bitbox Micro (slicer mode)

[Murcia Parker]

Hi:

I'm trying to sequence Bitbox Micro slices with the NerdSEQ. You can see the sequence in the first attached picture.

   

In the other pictures you can see my Bitbox Micro settings (last firmware).

   

   

I'm getting an erratic behaviour. Sometimes the slice isn't triggered, sometimes is triggered but it isn't the right one (the behaviour is more erratic with the PlayThru options enabled, but is erratic in both cases).

I have my Bitbox Micro pad in Slicer Mode, unquantized, slice: Source EXT1/Amount 100%

What am I doing wrong? Anyone else is using this two modules?

I forgot to mention that I tried different trigger delay settings in the Track Setup Menu (NerdSEQ).

[mgd]

I don't have a BitBox, so everything I know about it is from skipping through the manual. That having said:
What happens, when you change the BitBox from Gate mode to Trigger mode and instead of sending Gate On/Gate Off to just a single trigger like e.g. 40? Or put the Gate Off way further down so that playback is longer?
When using gates the BitBox stops when it receives a Gate Off. When your sample has a long/slow lead in it may not play something noticeable.

Just a thought,
Michael

[yrn1]

You could also try to add some trigger delay in the nerdseq track.

[Murcia Parker]

Thanks for your help! I forgot to mention that Bitbox was in Trigger mode. As you said, I tried to send just a single trigger. Everything remains erratic

In fact, when I changed to Gate mode, things got better: everything worked as intented. But I hear a brief gap between slices (when gate is off). I need the Trigger mode.

And yes, I tried to add some trigger delay.

I don't what else I could do.

Any more ideas?

[mgd]

From what you write it appears the Trigger sent by the NerdSEQ is not properly recognized by the BitBox. If that's the case then you could try the following:
- Do you have a scope (e.g. Mordax Data or vpme Zeroscope or Dave Jones Design O'Tool Plus or something similar) available? Try to monitor the trigger on the scope and see what level it is. It should go from 0V to +5V
- Does this work on other modules? Trigger on ADSR modules or whatever
- You could use the MOD output (flip the switch to the right) and manually create your gate there by entering values C-0 and C-A (or 000 and FFE). That will create gates from 0V to +10V

I recently had issues with triggering my 2hp Pluck. I solved that by sending the trigger into a Doepfer A-183-4 and from there into the Pluck.

Maybe one of the above brings you closer to a solution.

[XORadmin]

Thanks for your help! I forgot to mention that Bitbox was in Trigger mode. As you said, I tried to send just a single trigger. Everything remains erratic

In fact, when I changed to Gate mode, things got better: everything worked as intented. But I hear a brief gap between slices (when gate is off). I need the Trigger mode.

And yes, I tried to add some trigger delay.

I don't what else I could do.

Any more ideas?

With the Bitbox in Gate mode you can simply use for example a 01, which generates a delayed gate. If using that instead of the Gate off then you won't have the gap anymore.

Another thing is that you actually create Gates in your sequence but the bitbox might expect triggers only in trigger mode.
In Trigger mode then I would rather try to fill in a 10 for example which is only a short trigger, also without gate off. And together with the delayed trigger settings it should get you the results you need.

[Murcia Parker]

Thanks for your help.


In the end the only thing that worked with Bitbox Micro in trigger mode has been repeated triggers from NerdSEQ. I used "11" triggers (see attached picture). Track setup without trigger delay. Pattern with CV and trigger at the same time.

I'm a bit confused. I don't know why this is the only thing that worked. And I don't know if the slice was triggered repeatedly (ON/OFF/ON/OFF) because it was so fast.

Could someone explain me what happens?

[mgd]

Thanks for your help.


In the end the only thing that worked with Bitbox Micro in trigger mode has been repeated triggers from NerdSEQ. I used "11" triggers (see attached picture). Track setup without trigger delay. Pattern with CV and trigger at the same time.

I'm a bit confused. I don't know why this is the only thing that worked. And I don't know if the slice was triggered repeatedly (ON/OFF/ON/OFF) because it was so fast.

Could someone explain me what happens?

The Bitbox has way to many settings to know that.
To understand guess what might have happened there are a few things yet unknown. Here comes a short and probably incomplete list of questions:
- What are the envelopes set to? (e.g. short Attack/Decay and low Sustain?)
- What happens when you set the trigger to 02 (longer delay, then gate) followed by a gate off?
- Have you tried trigger lengths of e.g. 20 or 40?
- What ranges of trigger delay in the N3rd Menu have you tested?
- What type of sound is it that you try to play? (fast/slow attack, etc.)
- If possible try to look at things with a scope. I find that invaluable.
- What happens when you trigger the Bitbox from another trigger source?
- How do other sound sources react, when you send them the same triggers from the NerdSEQ?

I'm sure there are more...

Kind regards,
Michael

[Murcia Parker]

I haven't had time today to try all of these settings you mention, but tomorrow I'll give them a try and I'll post the results here... Thanks for your help.

[Murcia Parker]

Thanks for your help.


In the end the only thing that worked with Bitbox Micro in trigger mode has been repeated triggers from NerdSEQ. I used "11" triggers (see attached picture). Track setup without trigger delay. Pattern with CV and trigger at the same time.

I'm a bit confused. I don't know why this is the only thing that worked. And I don't know if the slice was triggered repeatedly (ON/OFF/ON/OFF) because it was so fast.

Could someone explain me what happens?

The Bitbox has way to many settings to know that.
To understand guess what might have happened there are a few things yet unknown. Here comes a short and probably incomplete list of questions:
- What are the envelopes set to? (e.g. short Attack/Decay and low Sustain?)
- What happens when you set the trigger to 02 (longer delay, then gate) followed by a gate off?
- Have you tried trigger lengths of e.g. 20 or 40?
- What ranges of trigger delay in the N3rd Menu have you tested?
- What type of sound is it that you try to play? (fast/slow attack, etc.)
- If possible try to look at things with a scope. I find that invaluable.
- What happens when you trigger the Bitbox from another trigger source?
- How do other sound sources react, when you send them the same triggers from the NerdSEQ?

I'm sure there are more...

Kind regards,
Michael

1) What are the envelopes set to? Envelopes are set to default values (Attack: 0.0% / Decay: 0.0% / Sustain: 100% / Release: 20.0%)
2) What happens when you set the trigger to 02 (longer delay, then gate) followed by a gate off? Erratic behavior
3) Have you tried trigger lengths of e.g. 20 or 40? Yes, I've tried these trigger lengths and I've got an erratic behavior
4) What ranges of trigger delay in the N3rd Menu have you tested? I've tested up to a "6A" delay
5) What type of sound is it that you try to play? (fast/slow attack, etc.) The sound of an arpegiatted clean electric guitar
6) If possible try to look at things with a scope. I find that invaluable. Yes, I think my next purchase will be the Mordax DATA. Right now, without it, I'm going crazy.
7) What happens when you trigger the Bitbox from another trigger source? I've tried to trigger the Bitbox from Clank Chaos gate signals and the slices were triggered every two Chaos pulses!! So it seems an odd Bitbox behavior. This explains why "11" triggers from NerdSEQ works well with the Bitbox Micro. So I guess I should address this question in the 1010Music forum. However if anyone here have an explanation and a solution, please, let me know!