Nerdseq's Gate arrive too early, I think

[Friend of Dogs]

On all the channels I'm sending the cv info to from the nerdseq, (bitbox, ER301, Basimilus etc) If im triggering changing timbre's (drum slices) it plays a "hic" of the previous sample first.

Are you clocking externally by any chance? With internal clocking I use my nerdseq to trigger an external sampler (akai s950) using a Doepfer 192-2 (cv-midi)... the Doepfer module is very picky about the gate and cv arriving coincidentally and I've had no issues using the nerdseq with it!

I dont think so. If you mean clocking the bitbox, other modules, with the nerdseq's clock out, not yet. Not until I get my songs straight.   If you mean clocking the nerdseq with the computers midi clock send, also no. 

I have an easier time writing music on the computer, and then converting it to nerdseq later. Now that I think about it, i dont know if this problem exists when using the nerdseq regularly, but it certainly does when I use it as a midi to cv converter. 

Thanks.

---

are you able to post videos as attachments?, i just tried and it didnt work.

i mean is there a video format that works.

[XORadmin]

On all the channels I'm sending the cv info to from the nerdseq, (bitbox, ER301, Basimilus etc) If im triggering changing timbre's (drum slices) it plays a "hic" of the previous sample first.

Are you clocking externally by any chance? With internal clocking I use my nerdseq to trigger an external sampler (akai s950) using a Doepfer 192-2 (cv-midi)... the Doepfer module is very picky about the gate and cv arriving coincidentally and I've had no issues using the nerdseq with it!

I dont think so. If you mean clocking the bitbox, other modules, with the nerdseq's clock out, not yet. Not until I get my songs straight.   If you mean clocking the nerdseq with the computers midi clock send, also no. 

I have an easier time writing music on the computer, and then converting it to nerdseq later. Now that I think about it, i dont know if this problem exists when using the nerdseq regularly, but it certainly does when I use it as a midi to cv converter. 

Thanks.

---

are you able to post videos as attachments?, i just tried and it didnt work.

i mean is there a video format that works.

I will for sure make a scope picture tomorrow to see the gate compared to the CV change. I didn't have the time yet to do it. But i assume it to be the same as if it was sequenced by the NerdSEQ.

For the video, you can add Videos from other platforms here, when using the reply and not the quick reply you can choose to add a video from different sources. Direct upload is not possible.

[XORadmin]

I just measured with a scope and i can assure you the gate comes after the CV.

My measuring is on one channel CV + Trigger output.
So i had a note 2 octaves lower, pressing a key on the Midi keyboard 2 octaves higher. The result is that the CV voltage will go to it's intended voltage and approx 1 uS later (this is microseconds not milliseconds) the Gate starts to rise. Given the normal threshold when a gate/trigger should be detected of around 2 Volt, the Gate is 3.5 uS behind the new stable CV value (after it's rise which takes ca. 1.5 uS).
And again, i am talking microseconds. So the gate comes definitely after the CV voltage.
Just to compare this 3 uS to like a normal Midi Note message. To transfer one Midi note it takes at least 960 uS (microseconds) , around 1 mS (millisecond).
So i think there might be another problem there. And for sure not a problem in the milliseconds.

[Friend of Dogs]

I just measured with a scope and i can assure you the gate comes after the CV.

My measuring is on one channel CV + Trigger output.
So i had a note 2 octaves lower, pressing a key on the Midi keyboard 2 octaves higher. The result is that the CV voltage will go to it's intended voltage and approx 1 uS later (this is microseconds not milliseconds) the Gate starts to rise. Given the normal threshold when a gate/trigger should be detected of around 2 Volt, the Gate is 3.5 uS behind the new stable CV value (after it's rise which takes ca. 1.5 uS).
And again, i am talking microseconds. So the gate comes definitely after the CV voltage.
Just to compare this 3 uS to like a normal Midi Note message.  To transfer one Midi note it takes at least 960 uS (microseconds) , around 1 mS (millisecond).
So i think there might be another problem there. And for sure not a problem in the milliseconds.

huh, well thats good news that its arriving properly, but then the problem is still there somewhere..  
Maybe its reason's midi as a program....
Im going to email you the video of the bitbox's reaction.

---

thanks by the way for going through all the trouble

[pascalm]

seems to be more like an issue inside bitbox :
https://forum.1010music.com/forum/produc...modulation

the proposed solution is to trigger bitbox by midi (unfortunately) or to further delay your gate trigger...

[XORadmin]

There seem to be issues with other samplers as well.
The NerdSEQ is setting the gates well after the voltage is stable and this seems to be more an issue that the samplers trigger/CV sampling is not fast enough.
While triggers might be sampled digitally, the CV values are sampled analogue and this might take longer. (But thats only my educated guess)
A delayed gate might be a possibility, but the NerdSEQ can't make a delayed gate from Midi right now. Only from the sequencer. I probably plan to add a setup setting to be able to change the delay of a gate (and here also not in the milliseconds range as i think this shouldn't be audible).

In the end, i want them all to work well with the NerdSEQ.