Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

should clearing the script always stop the engine? #1782

Open
catfact opened this issue May 27, 2024 · 3 comments
Open

should clearing the script always stop the engine? #1782

catfact opened this issue May 27, 2024 · 3 comments
Assignees
Labels

Comments

@catfact
Copy link
Collaborator

catfact commented May 27, 2024

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 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.

@catfact catfact added the lua label May 27, 2024
@catfact
Copy link
Collaborator Author

catfact commented May 27, 2024

... 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?

@tehn
Copy link
Member

tehn commented May 27, 2024 via email

@tehn
Copy link
Member

tehn commented Jul 9, 2024

month late but i'm scheduling time next week for this, along with a new norns software release

@tehn tehn self-assigned this Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants