Moln

[coreyr]

That’s a sleep after installing/updating error. Any script using a new engine needs norns to power cycle to be properly recognized.

[carl]

Error still persists after a sleep cycle.

[csboling]

@carl

core/params/control.lua:75: attempt to perform arithmetic on a nil value (field 'quantum')

Unfortunately I think this is a bug I introduced when adding the quantum option for ControlSpecs in the latest norns release which was fixed a few days later that causes problems when you copy a ControlSpec. So the error is on the Lua side. To tide you over until the next norns update you could make the one-line edit to ~/norns/lua/core/controlspec.lua – it’s possible you may need to revert this change before the next time you update. Sorry for the trouble.

[Simone_Tomaselli]

Hi. I found out, after some time that I wasn’t using it, that Enc 2 and 3 are not selecting cutoff and resonance anymore. Enc1 is working, as are all the keys.
Moreover, if you go into parameters, only env>filter frequency is editable.
A friend tried the same and he has the same issues.
Tried removing/reinstalling but no way…

[jah]

As @csboling mentioned - this is a regression bug in norns core, and not specific to this script.

This appears to be fixed by the temporary oneline measure suggested by him above.

[Simone_Tomaselli]

which one in particular? I saw some workarounds but I thought they were superseded by some update.

[Justmat]

That’ll be this one

Moln

Unfortunately I think this is a bug I introduced when adding the quantum option for ControlSpecs in the latest norns release which was fixed a few days later that causes problems when you copy a ControlSpec. So the error is on the Lua side. To tide you over until the next norns update you could make the one-line edit to ~/norns/lua/core/controlspec.lua – it’s possible you may need to revert this change before the next time you update. Sorry for the trouble.