Glide + Calibration = Freaking Out

[schematicwizard]

Hi !

So I was recalibrating my Nerdseq and kinda freaked out because two of my mod outputs were unresponsive, with values slowly going up/down and not matching the voltage they were supposed to send. After spending two hours trying to figure out why (a.k.a emptying my whole case to check if there was a power issue) the solution was actually pretty dumb: I had a super long Glide modulation on two tracks. And they were still active when I was in the calibration menu. That's all.

So in case it happens to any of you: the calibration menu seems to be sensitive to current values on tracks. Just go through all tracks and double check "Glide Modulate" is 000.

I don't know if it's a feature or a bug so I don't open an actual issue, but maybe it would be an interesting feature to allow the user to disable any custom modulation/output configuration in the calibration menu   (or a warning in the manual maybe? Page 82 on current version)

That's all, thanks

[JX3D]

The Current Values screen is great for troubleshooting this stuff.
From the main window chose the track you want to check and press the PATCH button.

[mgd]

I don't know if it's a feature or a bug so I don't open an actual issue, but maybe it would be an interesting feature to allow the user to disable any custom modulation/output configuration in the calibration menu   (or a warning in the manual maybe? Page 82 on current version)

IMO it clearly is a feature. As they say: "Great power comes with great responsibility"
The NerdSEQ is such a powerful beast

[XORadmin]

Haha sorry. But I also got to say that it probably make sense to calibrate with a fresh project only and without any running stuff. I will see to add that in the manual but probably not fix it in the firmware.