-
Notifications
You must be signed in to change notification settings - Fork 24
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
brainstorm: possible items for second release (0.2) #1
Comments
input modes for .note() :
examples of "degree" mode: tune.note(0) is tonic. tune.note(2,1) is the second scale degree, 1 octave up. tune.note(-1) is the note below tonic. tune.note(5,-2) is the fifth scale degree, two octaves down. does this accomplish a clarity and ease of use? goal is for something as immediate as "C4" format. |
I wonder if a .fifthAbove() or more generally like a .plus(x) or .offset(x) could be interesting.... as in a way to momentarily tonicize a note without calling .tonicize() Case: Say I'm composing a piece in Partch mode and I want to play notes 23, 24, 25, but then I want to play note 25 w/ a second note that's a 5th above it. That "fifth above" might not exist in the scale, or I may not easily know what it is. So a helper function would be great. tune.note(23) tune.note(24) tune.note(25) tune.note(25); tune.note(25).offset(x) |
It would be nice for there to be a way for users to compose their own scales and add it to the archive. As it is, they could add their scale manually to the scales JSON. It might be necessary to store the scales in a database. This would make the program as whole smaller in size. This could possibly address the fifthAbove()/offset() idea. If you want a certain scale with an extra interval, just copy that scale and add to it. |
+1 for the matrix UI |
The text was updated successfully, but these errors were encountered: