LFO slow clock bit rate

[verifiedpersonae]

When trying to use really slow lfo settings I noticed that the "slow" clock setting is quite low bit rate, taking 16 separate steps to complete a full cycle without any smooth movement at all. I seem to remember a couple of firmware versions ago (the last time I used the slow clock setting) it was able to produce fairly smooth lfo movement at slow rates. Am I remembering incorrectly? Is there a setting to improve this at all?

I find myself using the Nerdseq as a modulation source quite often and would love a smoother lfo function at slow settings.

[mgd]

Just a possibly stupid idea:
You don't have it accidentially set to "pattern" (instead of "slow") and your pattern length is 16?

[XORadmin]

When trying to use really slow lfo settings I noticed that the "slow" clock setting is quite low bit rate, taking 16 separate steps to complete a full cycle without any smooth movement at all. I seem to remember a couple of firmware versions ago (the last time I used the slow clock setting) it was able to produce fairly smooth lfo movement at slow rates. Am I remembering incorrectly? Is there a setting to improve this at all?

I find myself using the Nerdseq as a modulation source quite often and would love a smoother lfo function at slow settings.

I just checked it and indeed there is an issue. I am not sure if it was ever like this.

But fixed it now and the speed goes now from the lowest normal speed (if clock is set to free with speed 1) to 4095 times slower than that. And that on it's smoothest. It goes from 90 seconds to 368550 seconds (or like 4 days, 6 hours, 22 minutes and 30 seconds). Should be enough for every drone in the world

Will be in the coming version.

[fadeddata]

Hah, this is likely what was affecting my bouncing ball effect.