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

Renamble client names / Pretty Names (Saved in the session) #35

Open
diovudau opened this issue Jul 2, 2020 · 0 comments
Open

Renamble client names / Pretty Names (Saved in the session) #35

diovudau opened this issue Jul 2, 2020 · 0 comments

Comments

@diovudau
Copy link
Contributor

diovudau commented Jul 2, 2020

This depends on #32 for saving additional data.

Proposal to let the user give names in the NSM GUI, to rename individual instances to keep them apart or rename them according to a role: I usually name my instrument-programs like Carla or Zyn "Melody", "Bass" etc.

This cannot be implemented by existing mechanisms: Clients can specificy their own name on announce, which are used to save the session.nsm so they cannot change (see API docs). Clients can give themselves a label. These are deleted when the client stops, or the session is closed. And they are already used for other purposes (for example Fluajho reports the loaded soundfont name via label).

Argodejo implemented this as a proof of concept through the non-music client "nsm-data" (together with session notes)
On the one hand this already works and prevents further complexity in the daemon, on the other hand this creates overhead both in broadcast messages, in the GUI and the mere existence of the speciality-client.

And for clients without NSM support this will never work on the client side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant