LFO fade bug?

seenfromspace · 2013-09-25T14:35:38.000Z

The LFO fade doesn’t work as expected.Is this a known bug? I don’t know how to check my OS version BTW!

Description:

Moving the fade value from zero has no effect, not until it’s set to a very high (and unusable) value.

Then reducing the value doesn’t reduce the effective delay until you reach zero. It then reverts to zero again. I can’t set it to a small, subtle value.

This makes the parameter unusable and greatly diminishes the creative scope of the LFOs

Noisebuddy · 2013-09-25T14:51:24.000Z

The lfo has to be triggered not free running iirc

avantronica · 2013-09-25T15:59:10.000Z

os is shown bottom right as you boot up - - i agree the sweet spot of lfo fade out is very narrow - outwith +20>40 it is pointless (it does seem to only work as expected when mode is trg too ! (works once in free but won’t fade a second time) - my hunch is that this is not as desired ! fade in is a bit more usable

seenfromspace · 2013-09-26T12:48:00.000Z

@Noisebuddy - hadn’t thought of that at all. I’ll give that a try.

namnibor · 2013-09-26T20:32:49.000Z

""Noisebuddy"":

The lfo has to be triggered not free running iirc

THANKS~! I thought I was losing my mind as I am quite used to free-running, more malleable LFO’s and do not recall ever reading this in A4 manual. So do I understand correctly that unless an LFO is in one’s modulation routing, it simply cannot be brought-in manually to affect a sound? Thanks again!

seenfromspace · 2013-09-26T22:29:20.000Z

It wasn’t in the manual? Surely!!! <>

I tried reading the OS version in the splash screen as described. Too quick! Couldn’t read it. Powered it down and tried again - nope. I’m too old obviously.

Think I’ll just download the OS and install it anyway, see what happens.