This is a bit of a strange one I've noticed for a while
If I automate a parameter using the the CV Input (via the Automation), it acts as though a small amount of voltage is present even when something isn't patched into the CV Input.
Eg, I "override step value" with CV1, and even with nothing patched into CV1 the pattern will often return to the top before finishing, and sometimes get stuck around step 1 for little periods of time.
I've had my Nerdseq in multiple eurorack cases where this happens, so it's not a dodgy power supply or anything.
This happens with all 4 CV inputs.
If the CV Input is automating the "CV" value (ie an oscillator's pitch), it's not noticable
I wonder if there's never *truly* 0V in the system, so maybe it's responding to tiny little bits of residual voltage or something? Perhaps there could be some sort of threshold so that it ignores anything too close to 0V?
Video to demonstrate : https://youtu.be/dVTIJXakstU (happens at start and around 30 sec mark)
If I automate a parameter using the the CV Input (via the Automation), it acts as though a small amount of voltage is present even when something isn't patched into the CV Input.
Eg, I "override step value" with CV1, and even with nothing patched into CV1 the pattern will often return to the top before finishing, and sometimes get stuck around step 1 for little periods of time.
I've had my Nerdseq in multiple eurorack cases where this happens, so it's not a dodgy power supply or anything.
This happens with all 4 CV inputs.
If the CV Input is automating the "CV" value (ie an oscillator's pitch), it's not noticable
I wonder if there's never *truly* 0V in the system, so maybe it's responding to tiny little bits of residual voltage or something? Perhaps there could be some sort of threshold so that it ignores anything too close to 0V?
Video to demonstrate : https://youtu.be/dVTIJXakstU (happens at start and around 30 sec mark)