@WilliamHazard + @rajaTheResidentAlien , hihi! hope all’s well with you both
thanks so much for engaging the library in your scripts + for reporting back on weirdness!
i think it might be helpful to build a few test cases, so we can narrow things down to library-specific issues – here are two scripts which test well on my side!
lfo_test1.lua instantiates and controls 60 LFOs via the direct-address API, whereas
lfo_test2.lua instantiates and controls 60 LFOs via the params API. they each use K3 to start/stop and K2 to randomize rate of each LFO.
@WilliamHazard, not seeing any LFO stalling with either script, but lmk if things test differently for you!
@rajaTheResidentAlien, i did find some shape trouble, tho not the same as you’re describing – basically, the square + random shapes don’t use the correct scaling. i can get that corrected, but happy to hear out any additional shape change issues you can repro!
LFOs can be nested as a group via
my_lfo:add_params(id, separator_name, group_name). if a
group_name is provided, then norns will attempt to group them with a
> UI formatter.
lfo_test2.lua demonstrates one occurrence of a collision, where an
all the lfos group is created to house the 60 LFOs, but then i also specify that LFO #60 should build a
special nest for LFO 60 group. since the
all the lfos group is still iterating when we hit the instruction to also build
special nest for LFO 60, norns sends out the warning that it cannot nest groups – this is a heads up so you know that you won’t see
special nest for LFO 60 > inside of the
all the lfos group menu.
norns will build the LFO parameters you requested, though, with the fancy disappearing act. so, in essence: the parameter menu build process simply ignores the secondary group, since we’re already inside of a group, and builds the rest of the parameters requested.
hope this helps! please lmk where y’all end up