A4 mk2/ hearing lfo modulations even with depth set to 0

This isn’t a recommended way to get official support and in all likelihood this unmonitored ‘news’ account may not see the post

Best ask support or MK2 users here - also look at the manual section on encoder acceleration / snapping etc for newer tips


My suspicion always was that this was a 14bit thing - clearly there’s an oversight in these ‘snap’ values (or it’s in the manual by another method - mk2 uses different encoders)

My suggestion is to go extreme left with the encoder pushed and then keep pushing and it may stick to integer values and land on 0

True Zero will definitely be (0) - so you need to finesse your fine tuning - it’s delicate work even on MK1 so it’s likely to be trickier on MK2

but try full left or right then press to do what happens on MK1 - you skip through bigger steps

only from left or from the right will work due to the distribution of the 14bit depth - not sure which (try left first and see if it snaps to 0

Clearly this will get fixed - it’s an essential shortcut

as another workaround you could send An NRPN message (maybe even just a CC) from your DAW (or whatever) to centre it until the firmware is sorted

I’d make an official report, but haven’t been able to reproduce, so I don’t know what steps I took to trigger this problem in the first place. :frowning:

Update from Elektron support:

Thanks for reporting. This is a known but nasty bug. It has been reported to the developers and will hopefully be fixed with the next update.

:slight_smile:

5 Likes

Sorry if there’s already a thread about bugs but I can’t find one. Got the MK2 a couple of days ago and noticing a few bugs, mainly parameters being affected even when their value is set to zero e.g right now I’m having the issue with the lfo, the amount is set to zero but it’s still affecting the sound, I’ve encountered the same thing with effects sends.

I’m sure I seen someone else post about this issue but can’t seem to find the post.

Anyone else having such issues?

Wrt the LFO: are you sure it’s set to 0, i.e. did you hold Func while turning the knob? Otherwise it might be set to a value less than 1 and greater than 0 which also is displayed as 0.

apparently it doesn’t work yet on MK2s

anytime the envelopes or lfo’s are set to modulate anything, i still get slight modulation even with it set to zero. i’ve noticed there is a range of effect between 0 and 1 on the encoders, most noticable when set to with OSC pitch as a destination. with some extremely delicate fiddling i can occasionally find the true zero setting which is shown as “(0)”. this seems weird and extremely hard to get to with the encoders. is this by design, or a bug? not very intuitive. i spent an hour trying to chase this down thru the many pages of modulation. try it yourself, turn on both osc tuned to same pitch, and put any OSC pitch as a destination on ENV or LFO. turn it up then set it back to zero. then turn the destination knob back to meta:none. you will hear a clear difference. strange that it would be so fiddly.

just use function+encoder to set it back to true zero

amazingly, this doesn’t put it to true zero! more like -+0.1, still takes a bunch of knob feathering to get it to true parenthesis zero “(0)”. if they want to keep it this way, they should show decimal points on the display, like with the filter freq. or better, make the fn+ encoder set it to true zero.

hm, never had a problem setting it back to (0)…
MK1 or MK2?

I had the same with the envelopes (not with LFO though). do a calibration. that fixed it for me…

1 Like

and first doublecheck you dont have a perf macro applied

1 Like

Exactly this for me too. Frustratingly the parenthesis keep flashing so I know I’ve gone past it, but without decimal display I dont know which direction I’m going and often I’ll end up back at 1 (and I cant easily tell if thats + or - one).

no perf macros, and calibration didnt fix it! i’m bummed!

it is a MK2.

Was the machine on for about 2 hours before calibration?

yes.

did you try it again. i remember when i had the problem it also didnt work the first time calibration but the second time it was right.

This is a bug that was acknowledged by Elektron a few months ago. They plan to fix it.

2 Likes

awesome! any chance you could point me to a thread where they acknowledged it?