Akai is back at NAMM this year

T-Monk wrote:For those of you who do not want the LFO to reset on every key press in 2.15 keygroups, there is a hack.

Open the XPM with a text editor. There is a line in there that controls the key reset. It is set to (false), but you can change it to true for any key group you want to have a free running LFO for.

If this works, then it is insane and absolutely shameful on Akai's part. I remember seeing the No-reset field turn up in the desktop software (it didn't do anything) and then they removed it in the next update, so it was obviously a thing they were testing out once. Before the devs and beta testers gathered for a cuddle and decided that 'nobody needs an LFO in an MPC'

John Schaefer wrote:Before the devs and beta testers gathered for a cuddle and decided that 'nobody needs an LFO in an MPC'

Nah, I'm sure it didn't happen like that. It actually happened when they gathered for a cuddle and decided that since John Schaefer wants it, they'd purposely leave it out.

That's very dramatic, and the reality is probably more like 'they wanted to bring in this feature but there were various issues that they couldn't resolve so they had to drop it for legacy keygroups but later found a way to incorporate it within the advanced keygroup feature'.

John Schaefer wrote:

T-Monk wrote:For those of you who do not want the LFO to reset on every key press in 2.15 keygroups, there is a hack.

Open the XPM with a text editor. There is a line in there that controls the key reset. It is set to (false), but you can change it to true for any key group you want to have a free running LFO for.

If this works, then it is insane and absolutely shameful on Akai's part. I remember seeing the No-reset field turn up in the desktop software (it didn't do anything) and then they removed it in the next update, so it was obviously a thing they were testing out once. Before the devs and beta testers gathered for a cuddle and decided that 'nobody needs an LFO in an MPC'

I tested it on Force 3.2.3 and setting "lfoReset": true to "lfoReset": false in the .xpj file seemed to make the LFO to not reset on note-on. First the settings were like this



There's value0 and value1, don't ask what that means.

Anyway. The LFO was freed from getting reset at note-on, BUT it didn't feel consistent. The LFO phase was not tied to note-ons, but WHAT it was tied to, I couldn't figure out. But it seemed good enough for getting some random feeling at least.

What makes this useful is, the LFO behavior seemed to survive a resave/reboot/reload cycle.

I did try to set "lfoFreeRunning" to true, but it didn't make the LFO free-running.

MPC-Tutor wrote:That's very dramatic, and the reality is probably more like 'they wanted to bring in this feature but there were various issues that they couldn't resolve so they had to drop it for legacy keygroups but later found a way to incorporate it within the advanced keygroup feature'.

An LFO in audio DSP coding will free-run by its very nature. To have it reset on pads/keys was something actively coded, not a byproduct of it being an LFO. If they couldn't code it to run freely like other gear had been doing for 30 years then they probably shouldn't be in audio software development.

The problem is that its not ddp anymore