You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this is clearly not architecturally sound. maiden calls norns.script.clear(), which is in like the "public API." the "private API" call _norns.free_engine() should just be added to norns.script.clear() if the desired behavior is for clearing the script to always stop the running audio engine. otherwise it won't be freed until a new engine is requested.
The text was updated successfully, but these errors were encountered:
... i haven't checked: maybe there are times that we do in fact want to run the script cleanup without affecting supercollider. but it seems unlikely, right?
suggest addresing this user-surprising discrepancy in behaviors:
(https://llllllll.co/t/norns-studies/14109/231)
[quote]
Is there a specific reason why maiden “stop” behaves like this? I would expect the “stop” button to be identical to K1 + K3.
[/quote]
there is no specific reason. the K1+K3 behavior was hacked in at some point, directly to the menu input code:
https://github.com/monome/norns/blob/main/lua/core/menu/home.lua#L25-L26
this is clearly not architecturally sound. maiden calls
norns.script.clear()
, which is in like the "public API." the "private API" call_norns.free_engine()
should just be added tonorns.script.clear()
if the desired behavior is for clearing the script to always stop the running audio engine. otherwise it won't be freed until a new engine is requested.The text was updated successfully, but these errors were encountered: