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

Tuning: Choose different stable notes #1043

Closed
baconpaul opened this issue Aug 18, 2019 · 2 comments
Closed

Tuning: Choose different stable notes #1043

baconpaul opened this issue Aug 18, 2019 · 2 comments
Labels
Tuning Non-standard tuning extensions
Milestone

Comments

@baconpaul
Copy link
Collaborator

Right now the stable note (unchanged by tuning) is fixed in the synth. With 1.6.3 we may want to move the midi note and frequency which is stable (although this may come better through kbm files - lets see)

But so I don’t forget to think about it add this issue as I closes #828

@baconpaul baconpaul added the Tuning Non-standard tuning extensions label Aug 18, 2019
@baconpaul baconpaul added this to the 1.6.3 milestone Aug 18, 2019
@SeanArchibald
Copy link

Kbm files specify the "stable" MIDI note and frequency - so if full kbm support happens then you could close both issues in one go. :)

The benefit of kbm support is that it doesn't lock the user in to using linear mappings only - users could specify their own custom key mappings. I can think of a few use cases where custom key mappings are useful, including:

  • Making fingerings more easy for standard keyboard controllers (e.g. the user has an 11-note scale, but their standard MIDI keyboard repeats every 12 notes, so they could make a mapping that skips every 'E' key so the 11-note scale repeats every 12 keys, thereby keeping fingerings more regular)
  • Added flexibility for isomorphic keyboard controllers (e.g. the user has a Linnstrument or AXiS and wants to change the mappings so that certain intervals line up along certain directions)
  • One mapping can be used for multiple scales (e.g. the user has hundreds of 7-note scl scales, and would only require a single kbm file to map any of those scl scales to the white keys)

The above examples are just for illustration. Kbm support means the user has the power to come up with their own solutions to all the above!

@baconpaul
Copy link
Collaborator Author

I agree. KBM (#1041) is the way to go so I’ll close this issue (but link it to 1041 so your useful comments carry over there).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Tuning Non-standard tuning extensions
Projects
None yet
Development

No branches or pull requests

2 participants